Allow users to set the origin of Control Nodes
**Describe the project you are working on:** Card game, Action game with items, menus. **Describe the problem or limitation you are having in your project:** When working on menus, anything with drag'n'drop functionality, items, cards, or even a simple debug text label, I find myself in dire need to have control over the Control nodes origin every single time. I work with a Control nodes as well as those inheriting from Control, but Godot currently does not seem to offer a way to adjust the origin. `rect_pivot_offset` is not an option since it is an absolute value (pixels I assume), not a percentage. The default origin for all Control nodes is the top right corner. This makes centering and scaling and positioning incredibly tedious and unintuitive. **Describe how this feature / enhancement will help you overcome this problem or limitation:** Controling scale, positioning and grow direction is currently a nightmare from UX perspective. It forces you to use multiple nested nodes and properties of those nodes and absolut pixel values. This proposal would reduce all that to just one single setting. Personally I would think having the origin of Control nodes and Node2Ds work the same way would be the solution, even if they have different defaults (top left vs centered) and Control nodes having additional parameters like padding/margins. **Show a mock up screenshots/video or a flow diagram explaining how your proposal will work:** ![control_origin](https://user-images.githubus
Posted by golddotasksquestions on Oct 6, 2019, 1:20 PM
Tags
Related issues
- To be fair, Inform7 can't succeed, generally, because there is no market for the kind of games that you create with Inform7.
- > The notion that somehow LR reliability is misunderstood by Consumer Reports, JD Power, Car & Driver, Automobile etc.
- Custom trigger IDs are not displayed in the new 2026.10 trigger selector
- I hate that too, but I think it’s more the ux than the concept of a default.
- > The biggest problem with UX developers is they know better than you AND force you into their paradigm.
- "Focus follows mouse" is what I use to keep the file manager from popping up when click-dragging files.
Raise real-world problems, find people facing the same issue, and discuss solutions.3,500 issues0 comments
ux (Other)
To be fair, Inform7 can't succeed, generally, because there is no market for the kind of games that you create with Inform7.
New> The notion that somehow LR reliability is misunderstood by Consumer Reports, JD Power, Car & Driver, Automobile etc.
Custom trigger IDs are not displayed in the new 2026.10 trigger selector
I hate that too, but I think it’s more the ux than the concept of a default.
> The biggest problem with UX developers is they know better than you AND force you into their paradigm.
"Focus follows mouse" is what I use to keep the file manager from popping up when click-dragging files.
The biggest problem with this is if the target URL doesn't load but also doesn't quickly error out, like e.g.
Google wants to build up a private web here.
Allow users to set the origin of Control Nodes
**Describe the project you are working on:** Card game, Action game with items, menus. **Describe the problem or limitation you are having in your project:** When working on menus, anything with drag'n'drop functionality, items, cards, or even a simple debug text label, I find myself in dire need to have control over the Control nodes origin every single time. I work with a Control nodes as well as those inheriting from Control, but Godot currently does not seem to offer a way to adjust the origin. `rect_pivot_offset` is not an option since it is an absolute value (pixels I assume), not a percentage. The default origin for all Control nodes is the top right corner. This makes centering and scaling and positioning incredibly tedious and unintuitive. **Describe how this feature / enhancement will help you overcome this problem or limitation:** Controling scale, positioning and grow direction is currently a nightmare from UX perspective. It forces you to use multiple nested nodes and properties of those nodes and absolut pixel values. This proposal would reduce all that to just one single setting. Personally I would think having the origin of Control nodes and Node2Ds work the same way would be the solution, even if they have different defaults (top left vs centered) and Control nodes having additional parameters like padding/margins. **Show a mock up screenshots/video or a flow diagram explaining how your proposal will work:** 
No comments yet. Start the discussion.