Stan wrote:
>>      I wouldn't expect the FLTK docs to go into details of odd
>>      window manager behavior for different platforms/OS releases.
>>
>>      Do you think it should?
>>
>    I think it should when there are known issues (and it does, often).
>    Why hold back?

        The only reason I can think of is to avoid having FLTK docs
        be responsible for tracking the behavior of external software
        over which it has no control.

        Problems that occur today on those platforms might not be a problem
        tomorrow with a new update to the wm's.

        I could see vague caveats such as: "Depending on your window manager,
        some systems may exhibit unexpected behavior with width/height values
        that approach zero, or that exceed the size of the physical screen."

>>      In this case, FLTK is just passing the values on to the
>>       window manager, and the wm 'does what it does' with the values.
> 
>    If that's the case (and I have no reason to doubt it), the
>    doc should say so, don't you agree?  Perhaps I had more trouble
>    understanding this bit of documentation than I thought, because
>    it never occurred to me that this call was a pass-through.

        When it comes to window sizes, positions, title bars, and decorations,
        these are all a function of the window manager, and the behavior is
        subject to its discretion.

        FLTK tells the window manager it wants to set the initial size/position,
        but the window manager gets the "last say", as it might or might not
        abide by those "recommendations" depending on either its default 
behaviors,
        or user-customizable config options.

        A window manager configured to, for instance, force positions of windows
        to be 'stacked' in some way might override an app's desire to position
        windows at particular points on the screen initially. The window manager
        might also disallow windows to be sized larger than the screen's 
physical
        dimensions.

        I suppose the docs for Fl_Window's ctors, position/size/resize/etc.
        could all warn about the above, or at very least link to a section
        of the docs that covers platform specific warnings, such as might be
        described under 'Operating System Issues' with respect to window
        manager's ability to veto sizing/positioning/decoration requests.
_______________________________________________
fltk mailing list
[email protected]
http://lists.easysw.com/mailman/listinfo/fltk

Reply via email to