solved General GUI troubles

[NRA]

Hi,

Hey in fact there are problems in MANY GUI ELEMENTS, "text box", buttons, etc!!!

[Dad72]

Yesterday I reported some problem that you cited.They have been correcting.

Do you use the latest version 4 of today ?

[NRA]

Hi @Dad72

 I am developing directly in Playground and in last sunday my code is working normally, yesterday night it started to became strange and today it is totally strange! Some of buttons do not appear, all the text blocks too. And I do not see any error message in javascript console of the browser!

Were i can find the related changes to see if I find what I need to change in my code?

Thanks  

[Dad72]

This problem seems to be related to your other subject:

http://www.html5gamedevs.com/topic/41692-scroll-viewer-not-working/

 

[NRA]

Hi @Deltakosh

Can you help please!

[NRA]

I received this message in javascript console

BJS - [08:44:44]: Layout cycle detected in GUI (Container uniqueId=53)

What it means?

 

[Guest]

Sure I can help. The GUI is going under heaving rework to make it better so you may have faced unwanted side effects.

Can you share the faulty playgrounds?

[ssaket]

Hello All, I would like to add one - https://playground.babylonjs.com/#42LMAC
Previously the grid used to work fine, and the above PG creates 3 inputTexts, but now it's just creating or I should say "showing" only 1 inputText.
I'll check on it tomorrow  

[NRA]

Oh @Deltakosh thanks the attention and excuse the hurry! But I was worried because I am developing an system for a client,  which has similarity with this one https://webshed.royssheds.com.au/#, and since monday its has a strange behavior related to GUI elements, which are so many in my code. But if you said than is maintenance, I believe that soon it will be normalized again.

 

 

 

[NRA]

@Deltakosh

Excuse again my ignorance, but how can I call the stable version 3.3.0 in the .html file <header> on my server, to not had this happening again.

Now this are the scripts been called.

 

        <script src="https://code.jquery.com/pep/0.4.2/pep.min.js"></script>
        <script src="https://cdnjs.cloudflare.com/ajax/libs/dat-gui/0.6.2/dat.gui.min.js"></script>
        <script src="https://preview.babylonjs.com/cannon.js"></script>
        <script src="https://preview.babylonjs.com/Oimo.js"></script>
        <script src="https://preview.babylonjs.com/earcut.min.js"></script>
        <script src="https://preview.babylonjs.com/babylon.js"></script>
        <script src="https://preview.babylonjs.com/inspector/babylon.inspector.bundle.js"></script>
        <script src="https://preview.babylonjs.com/materialsLibrary/babylonjs.materials.min.js"></script>
        <script src="https://preview.babylonjs.com/proceduralTexturesLibrary/babylonjs.proceduralTextures.min.js"></script>
        <script src="https://preview.babylonjs.com/postProcessesLibrary/babylonjs.postProcess.min.js"></script>
        <script src="https://preview.babylonjs.com/loaders/babylonjs.loaders.js"></script>
        <script src="https://preview.babylonjs.com/serializers/babylonjs.serializers.min.js"></script>
        <script src="https://preview.babylonjs.com/gui/babylon.gui.min.js"></script>

 

[Guest]

Just replace preview.babylonjs.com by cdn.babylonjs.com

But I'm still interested by the failing examples (without them, I cannot fix)

[Guest]

@ssaket fix on its way

[Guest]

Ok fixed. It was a bug in the recent InputText changes: https://github.com/BabylonJS/Babylon.js/commit/7596cba2f43a30be6d77d69995bb3d83b9037625

Pushing the nightly right now

[NRA]

21 minutes ago, Deltakosh said:

Just replace preview.babylonjs.com by cdn.babylonjs.com

But I'm still interested by the failing examples (without them, I cannot fix)

Ok, I will do it, but I will spend some time to do it, because I need to pick parts of my code which is long.

Thanks

[Guest]

I understand but that is the only way to make sure we fix it

[NRA]

@Deltakosh

Hi, the bug you fix in InputText solved my troubles! But I will see carefully if there are any other issue to relate.

Thanks

[NRA]

Shame on me!

I forgot to mention that the "thickness" of InputText  IS NOT WORKING, or we can not change it color!

[Dad72]

Try to accompany a PG as much as possible to help with the correction.

[NRA]

Shure @Dad72 and @Deltakosh

Here is the PG https://www.babylonjs-playground.com/#YP180Z

The THICKNESS is not with the BLACK color or are not working like before.

[Dad72]

For more accuracy for correctors: The black thickness should be seen before we click in the inputText ?

There, there is no border and when you click on the inputText, the border becomes black. Should not it be the opposite?

[ssaket]

It's because the border code is being sitting inside the the isFocused for like 2 months ?  It's strange no one noticed it. Even me, while working on it last week ! ohh God! 

[Dad72]

The ideal would be to have a border color when we not have the focus and another border color when we have the focus.

input.color = "black"; // No focus
input.focusedColor = "grey"; // Focused;

I saw in the code of PG: thicknessColor, but I think that does not exist. I did not see this property in the documentation. Maybe it was not added and it exists in the source code ?

[ssaket]

@Dad72 yeah.. there's no thicknessColor property at all,  in docs as well as in code. The border takes it's color value from input.color

[Guest]

I'm gonna add a focusedColor for the border. Demo to come...

[Guest]

Here we are: https://www.babylonjs-playground.com/#YP180Z#1