-
Notifications
You must be signed in to change notification settings - Fork 96
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
Detached display width and height #1926
Comments
Not easily. The 'docking' mechanism has no idea about the content. It doesn't care if the pane contains a display builder runtime or an editor or probe or ... It's of course possible to change it, but we should NOT change it by making the docking pane check for a display builder runtime as a child, since that would introduce unnecessary coupling. What if you wanted to build a phoebus with only data browser? Couldn't, would now always need to include the display runtime... |
@kasemir Started looking into this one again, I see a year later or so (CSSTUDIO-1121) and can see where you're coming from with this implementation-wise. I'm curious if you've had any additional thoughts on this, since I'm working on (potentially) implementing it. |
When I detach a display in Phoebus, the width and height is calculated from the parent. The width and height shown in the display property panel is not used. Some of our users would prefer to use the values in the property panel. They report that they have to resize a lot of windows all the time when using the detach functionality. What is the main reason for using the current implementation to the determine the width and height? Would it be possible to use the width and height from the display property instead or will it have other consequences/side effects?
The text was updated successfully, but these errors were encountered: