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
For what it's worth, this would for now be OK in the Display Builder running on Phoebus:
But I don't want to guarantee that it'll always function that way, and there is a dedicated 'Spinner' widget, shown at the bottom, for the purpose of having both a text entry and up/down buttons.
In BOY, the reason for the somewhat unpredictably behavior could be that BOY uses a mix of SWT and Draw2D widgets, and who gets a mouse click event when they're layered isn't always clear. I think at one time there was an issue that one type of widget would always show up on top, no matter how you think they should be layered, because again these are different widget technologies.
So if you want to guarantee this behavior in BOY, you might have to implement a 'Spinner' type widget.
I have an OPI with a TextInput control overlayed on a Scrollbar control.
In CS Studio 4.5, clicking on the TextInput would cause the text field to have focus and allow the user to input a new value.
In CS Studio 4.6, clicking on TextInput activates a pageup/pagedown event on the scrollbar, and the text field do not get focus.
Example OPI file: Scrollbar_Issue_CSS46.opi.zip
The text was updated successfully, but these errors were encountered: