Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Canvas editor problems #1659

Closed
knowledgenude opened this issue Apr 14, 2020 · 5 comments · Fixed by armory3d/armory2d#53
Closed

Canvas editor problems #1659

knowledgenude opened this issue Apr 14, 2020 · 5 comments · Fixed by armory3d/armory2d#53
Labels
bug This issue describes a bug

Comments

@knowledgenude
Copy link
Collaborator

knowledgenude commented Apr 14, 2020

Here I will report all the problems I have been facing with the Canvas editor and some nodes related to it.

  1. The first one is the Canvas Set Check Box Visible node; it is currently not possible to set the visibility value of this node without an error and a freeze being returned. The Check Box element does not appear to have the 'visibility' property.

  2. Another frustrating bug is not being able to define the color of the text of the elements without first changing the background color or another color. This bug does not make sense for me, it seems that while it does not change any color before the text, it is stuck in the original color.

@knowledgenude knowledgenude added the bug This issue describes a bug label Apr 14, 2020
@MoritzBrueckner
Copy link
Collaborator

MoritzBrueckner commented Apr 16, 2020

Unfortunately I cannot reproduce any of the bugs, do you have some more information (like an error message or a test file?)

  1. You mean the Canvas Set Visible node right? It indeed fails if the element has no visible attribute but this doesn't happen in my test, even if I manually remove the visible attribute from the canvas source file. Are you sure the element does exist? Anyway, I will fix the issue with the error if the element does not exist.

  2. I also cannot reproduce that. The canvas editor is running just fine, in Krom (Blender) and HTML5 (debugging)

@knowledgenude
Copy link
Collaborator Author

  1. I will test again and send a test file if it happens again later.

  2. The problem related is very simple: when you create a Canvas element, for example, a button; you can't go right in the text color and edit it. You first have to edit or background color or another value first before you can change the text color properly. It is not a problem that appears in the console, just a little bug.

I can't send a test file for number 2, because it is a bug right in Canvas Editor when you do the steps above.

@MoritzBrueckner
Copy link
Collaborator

Thanks :)

I still cannot reproduce the second bug. What I did:

  1. Create a new canvas
  2. Open the Canvas Editor
  3. Add a button
  4. Without changing anything (not even moving the button), I change the text color. It just works.

Do you have git installed? If yes, can you take a look if the "armory_tools" submodule in ArmorySDK/lib/ is checked out on the master branch?

@knowledgenude
Copy link
Collaborator Author

Hi, @MoritzBrueckner. I tested it again and the problem does not occur with Button element.

Issue 1: Maybe i have do something wrong, now it is working perfectly. Sorry for the mistake. I will disconsider this issue.

Issue 2: The problem just occur with Check Box and Radio element. Do the steps again but now with one of those elements. If you already tested with these, then the problem is with me.

The steps:

  1. Create a new Canvas element (Radio or Check Box).
  2. Don't do nothing and try to change the text color.
  3. When you release the mouse button, the text color will be reseted.

But if you change background color first, when you change the text color it will works.

@MoritzBrueckner
Copy link
Collaborator

Thanks, it will be fixed in armory3d/armory2d#53

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug This issue describes a bug
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants