Godot: Shouldn't TouchScreenButton inherit from Control instead of Node2D?

[razcore-art]

[ghost]

Why?

[razcore-art]

Because all other button nodes are descendants of Control. Why is TouchScreenButton special? Control nodes have the property of drawing on top of everything else and you can place them in nice containers etc.

[ghost]

If you need to use containers, use Button. The main difference between Node2D and Control is positioning. It's the same reason why you'd want to use Sprite instead of TextureRect.

[volzhs]

maybe it's behavior is different from Control.
like, moving(dragging) a finger from "<" and ">" button on screen acts like press it.

[groud]

Honestly, I don't even know why a TouchScreenButton is needed. The normal button should also handle touch events.

[reduz]

TouchScreenButton is different than a Control because it does not captute
the input. It just activates when you slide the finger over it or press it

On Dec 25, 2017 4:29 PM, "Gilles Roudiere" [e-mail] wrote:

Honestly, I don't even know why a TouchScreenButton is needed. The normal
button should also handle touche events.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/godotengine/godot/issues/15039#issuecomment-353886940,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AF-Z2zmxBbjkjtGBqwP6-MscBiK7yYA7ks5tD_edgaJpZM4RMRwe
.

[Zylann]

Ooh ok that might cause confusion then https://godotengine.org/qa/35806/how-to-stop-overlapping-button-pressed-trigger.
People are trying to use the pressed and released signals, but it's confusing when you realize it doesn't behave like usual controls, taps go through it and reach other things behind it if you do that.

[Calinou]

Feature and improvement proposals for the Godot Engine are now being discussed and reviewed in a dedicated Godot Improvement Proposals (GIP) (godotengine/godot-proposals) issue tracker. The GIP tracker has a detailed issue template designed so that proposals include all the relevant information to start a productive discussion and help the community assess the validity of the proposal for the engine.

The main (godotengine/godot) tracker is now solely dedicated to bug reports and Pull Requests, enabling contributors to have a better focus on bug fixing work. Therefore, we are now closing all older feature proposals on the main issue tracker.

If you are interested in this feature proposal, please open a new proposal on the GIP tracker following the given issue template (after checking that it doesn't exist already). Be sure to reference this closed issue if it includes any relevant discussion (which you are also encouraged to summarize in the new proposal). Thanks in advance!