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

Default Modification's sign isn't defined by default as expected. #5519

Open
1 task done
Bouh opened this issue Jul 30, 2023 · 1 comment
Open
1 task done

Default Modification's sign isn't defined by default as expected. #5519

Bouh opened this issue Jul 30, 2023 · 1 comment
Labels
😤Non optimal UI A bug/issue where the UI is usable but not optimal

Comments

@Bouh
Copy link
Collaborator

Bouh commented Jul 30, 2023

Is there an existing issue for this?

Describe the bug

When I use the quick menu to setup an event the modification's sign isn't correctly set by default as it is the case when I choose en event in the instruction editor.

test

Steps to reproduce

1 - Right-Click, add an action like "variable number"
2 - There is no "=" by default.

GDevelop platform

Desktop, Web, Mobile

GDevelop version

5.2.168

Platform info

All platforms

Additional context

No response

@Bouh Bouh added the 😤Non optimal UI A bug/issue where the UI is usable but not optimal label Jul 30, 2023
@AlexandreSi
Copy link
Collaborator

Technically speaking, it's "normal":

  • When you use the right click on the "Add event" button, you select the action/condition and it's directly added in the project event sheet with no parameter set.
  • When you use the dialog, the UI guides you to select the action/condition, set the parameters and when you're done and click OK, it adds the action/condition in the project event sheet.

I'm ok with the idea that the default operator can be set when adding an action/condition through the quick way but my question is: should it behave like that?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
😤Non optimal UI A bug/issue where the UI is usable but not optimal
Projects
None yet
Development

No branches or pull requests

2 participants