Re: [Fxruby-users] show(PLACEMENT_MAXIMIZED) > maximized?

[Jeroen v. d. Z. <je...@fo...>]

On Wednesday 23 June 2004 11:07 am, ly...@kn... wrote:
> On Wed, 23 Jun 2004 08:33:17 -0600, rich lyman <fx...@gm...> wrote :
> > Oh... ok. Sorry. I don't want to bug you or put pressure on you.
>
> You were not bugging me or pressuring me. ;) I just wanted to clear up that
> little bit of confusion about the maximize() method.


I apologize for sending anyone on a wild-goose chase; I realized this morning
that indeed FXRuby still uses FOX 1.0 and thus doesn't have the method yet.

Anyway, I hope you can proceed with your development and when the new
FXRuby rolls around, you should be able to use the new method.

I played with things earlier this week, and I found window managers like to
see the decoration state *prior* to the window being mapped.  

So, depending on your Window Manager, you may have to:

	1) hide() the window
	2) setDecorations(DECOR_NONE)
	3) show(PLACEMENT_MAXIMIZED)
	
Step (1) MAY not be needed on all Window Managers; but I recommend doing
this if your program is to work well on arbitrary WM's.

Likewise, getting back to the old size involves calling setDecorations(DECOR_ALL),
also possibly after withdrawing the window first [for the same reason].  You can
call either restore() or show() (and resize() if needed to go back to old size).

The restoring is more tricky as it depends on WM's proper implementation of
new "Extended Window Manager hints".  See freedesktop.org for more.

The bottom line is, FOX does try to be a good citizen under different Window
Managers, but various WM's have their quirks; since these WM's are not our
own code, we just have to live with what's available and make the best of it.

	- Jeroen