| |
| |
On 1/7/22 5:14 PM Greg Ercolano wrote:
On 1/7/22 6:22 AM, 'Matthias Melcher' via fltk.general wrote:
Not that I know of, but IMHO what you describe should be the
default behaviour.
Actually the default behavior is to display the menu in a place
where it fits on the screen. This can be below or above the widget
and it can move to the left as far as necessary. That's from testing
by moving the window around until the Fl_Input_Choice widget is near
one of the borders of the screen (monitor).
I believe to support the user fully redefining positioning
of the internal input/pulldown widgets, the currently private
methods inp_{xywh}() and menu_{xywh}() would
need to be virtual and protected so that a
subclass could redefine them, and thus redefine the
positioning during e.g. resizing.
Also, it'd probably be good if the align() method
for the Fl_Group could be changed for LEFT or RIGHT
aligned for the input field, with the current orientation being
the default.
I'm not sure if changing the meaning of the align() member is such a
good idea. However, this is a specialized widget and we could add
another flag member if necessary. It's now a good time to change the
ABI before FLTK 1.4.0 will be released.
I'll try making a patch and if it works as expected, and
if so, add it.
See above, take care not to prevent the default positioning
mechanism. I think, if whatever you do only changes the *default
position* it should be okay.
--
You received this message because you are subscribed to the Google Groups "fltk.general" group.
To unsubscribe from this group and stop receiving emails from it, send an email to fltkgeneral+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/fltkgeneral/d8db773b-100d-ca82-bde8-57ba44f554e6%40online.de.
[ Direct Link to Message ] | |
|
| |
