hagand3
commented
3 weeks ago Linking a bug report related to this feature. The x/y positions (and maybe the width/height too?) don't update when creating a view at a different position but using the same label (even if it's deleted prior). My hunch is the label is a key or something that is not being properly deleted from some internal struct, or just isn't being garbage collected though that's just a naive guess ;)
Is your feature request related to a problem?
Since the debug overlay has an option to automatically open the FPS view, it would be nice to also be able to set its starting position on screen. I find this would be useful to do for devices you can't grab and move the FPS view easily, such as on steam deck if you only have controller support and have the mouse disabled.
The dbg_view function allows for x and y coordinates to set the default position of a view, so I think it would be nice for us to be able to set the starting coordinates of the default FPS view as well.
Describe the solution you'd like
Add x and y optional arguments for the starting position of the FPS view.
Describe alternatives you've considered
A custom dbg_view with the fps real, but it would not have such a neat bar to view all the other things the fps view offers by default in its minimized form.
Additional context
No response