Zaphod Beeblebrox wrote:
> No, not really. :-) Actually, the limitation works pretty well with
> a borderless window dragged through fltk-based callback (that is without
> "illegal" positions), but for now I want to use the WM bar. [..]
Yes, I'd think if you derive from Fl_Window and override resize(),
you can implement custom constraining for position and/or size.
(IIRC, position() and size() are all wrappers for resize())
As Ian said, you're kind of at the mercy of the window manager's
behavior on this; depending on the window manager, its own rules
for tiled or 'stacked' placement positioning can sometimes affect
or override some of the behavior you try to procedurally implement.
I've run into this myself with my borderless app, 'nixieclock', where
sometimes my dragging and positioning logic is overridden by
e.g. some of the newer linux window managers. (you might not run into
it yourself in your dev environment, but some of your users might hit it
with custom window manager behaviors enabled)
_______________________________________________
fltk mailing list
[email protected]
http://lists.easysw.com/mailman/listinfo/fltk
