Thread: Re: [Fxruby-users] show(PLACEMENT_MAXIMIZED) > maximized?
Status: Inactive
Brought to you by:
lyle
From: <ly...@kn...> - 2004-06-23 13:49:11
|
On Wed, 23 Jun 2004 07:01:24 -0600, Rich <ri...@li...> wrote : > When I try it, I get: > > >ruby shell_hotkey.rb > shell_hotkey.rb:96:in `exec': undefined method `maximize' for > #<Fox::FXMainWindow:0xb14b668> (NoMethodError) > from shell_hotkey.rb:101 > >Exit code: 1 > > Is there a specific time when I should call this method? > > I'm calling it between the show method of the FXMainWindow and the run > method of the FXApp. The maximize() method comes in with FOX 1.2. FOX 1.0 (which FXRuby is still based on) is but a faint glimmer in Jeroen's memory. ;) |
From: <ly...@kn...> - 2004-06-23 15:07:18
|
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. > P.s. - I don't know a lick of C/C++, but is there something I can do to help? Not yet, but I appreciate the offer. I will keep it in mind. ;) Part of the delay, other than of course the usual lack of time, is that I'm actually trying to complete two different projects. One is, as you know, the update of FXRuby to FOX 1.2 compatibility. This is going pretty well in the sense that all of the existing classes have been updated, tests are passing, and the example programs have been updated. Most of the completely new classes have not been "wrapped" yet, but I think I'm probably at a good point for the first alpha release of FXRuby 1.2. The *other* project is completion of the "What's New in FOX 1.2" guide (http://www.knology.net/~lyle/fox/1.2/WhatsNew.html). I think it would be foolhardy of me to release FXRuby 1.2 without at least giving some heads-up about what to expect in terms of API changes and so forth. With a C++-based FOX application, you'd at least get a lot of complaints from the compiler when you're trying to port from FOX 1.0 to FOX 1.2. With FXRuby, of course, some of those porting problems due to name changes, changes to method arguments, etc. won't (necessarily) show up when you run your application. -- Lyle |
From: Jeroen v. d. Z. <je...@fo...> - 2004-06-23 15:40:02
|
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 |
From: rich l. <fx...@gm...> - 2004-06-23 14:33:19
|
Oh... ok. Sorry. I don't want to bug you or put pressure on you. That's good to know... I've been wanting that for a while... Thanks for the work that you do! -Rich P.s. - I don't know a lick of C/C++, but is there something I can do to help? On 23 Jun 2004 13:49:08 -0000, ly...@kn... <ly...@kn...> wrote: > > > On Wed, 23 Jun 2004 07:01:24 -0600, Rich <ri...@li...> wrote : > > > When I try it, I get: > > > > >ruby shell_hotkey.rb > > shell_hotkey.rb:96:in `exec': undefined method `maximize' for > > #<Fox::FXMainWindow:0xb14b668> (NoMethodError) > > from shell_hotkey.rb:101 > > >Exit code: 1 > > > > Is there a specific time when I should call this method? > > > > I'm calling it between the show method of the FXMainWindow and the run > > method of the FXApp. > > The maximize() method comes in with FOX 1.2. FOX 1.0 (which FXRuby is still > based on) is but a faint glimmer in Jeroen's memory. ;) > > > > > ------------------------------------------------------- > This SF.Net email sponsored by Black Hat Briefings & Training. > Attend Black Hat Briefings & Training, Las Vegas July 24-29 - > digital self defense, top technical experts, no vendor pitches, > unmatched networking opportunities. Visit www.blackhat.com > _______________________________________________ > Fxruby-users mailing list > Fxr...@li... > https://lists.sourceforge.net/lists/listinfo/fxruby-users > |
From: Tom <tku...@so...> - 2004-06-23 14:39:10
|
Is the ETA for FXRuby for FOX 1.2 still within June? Thanks, Tom ly...@kn... wrote: > The maximize() method comes in with FOX 1.2. FOX 1.0 (which FXRuby is still |