You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Suggestion from Lars:
The workaround where you manually call emit_signal("pressed") on the StartButton is not necessary. Buttons have a Shortcut property in the inspector where you can define what action can be used to press that button.
The text was updated successfully, but these errors were encountered:
I'd prefer leaving it out altogether to using script code. A property has exactly one place and exactly one purpose. Script code could go pretty much anywhere and could do pretty much anything, so it will statistically introduce more bugs and will be harder to debug.
How about visually showing that this step is optional? For example you could use a shaded box like for the "Tip"-elements. Or even link to a new page if you worry that it might look complicated enough to demotivate people.
Well, I've confirmed that the button ShortCut property is currently broken in 3.0. I'll keep an eye on this and hopefully by release we'll be able to use it.
Suggestion from Lars:
The workaround where you manually call emit_signal("pressed") on the StartButton is not necessary. Buttons have a Shortcut property in the inspector where you can define what action can be used to press that button.
The text was updated successfully, but these errors were encountered: