fxruby-users Mailing List for FXRuby (Page 7)
Status: Inactive
Brought to you by:
lyle
You can subscribe to this list here.
2003 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
(75) |
Jul
(90) |
Aug
(61) |
Sep
(56) |
Oct
(56) |
Nov
(39) |
Dec
(83) |
---|---|---|---|---|---|---|---|---|---|---|---|---|
2004 |
Jan
(56) |
Feb
(45) |
Mar
(61) |
Apr
(40) |
May
(95) |
Jun
(79) |
Jul
(63) |
Aug
|
Sep
(4) |
Oct
|
Nov
|
Dec
|
From: Lyle J. <ly...@kn...> - 2004-05-27 13:19:05
|
On May 27, 2004, at 8:28 AM, jeroen wrote: > So this problem is fixed in the latest 1.2 FXRuby. :s/is/will be/ ;) |
From: jeroen <je...@fo...> - 2004-05-27 12:27:10
|
On Wednesday 26 May 2004 07:10 pm, Tom wrote: > This is FOX 1.0 with FXRuby 1.0.28. > Tom That's what I suspected. FOX 1.0's FXDirList starts the scan from the current drive letter. In FOX 1.2, the problem is fixed:- all the drives are listed at the toplevel and the scan will proceed from all drive letters (multiple driveletters may be opened up or unfolded). So this problem is fixed in the latest 1.2 FXRuby. Regards, - Jeroen -- +----------------------------------------------------------------------------+ | Copyright (C) 23:50 12/11/2003 Jeroen van der Zijp. All Rights Reserved. | +----------------------------------------------------------------------------+ |
From: Tom <tku...@so...> - 2004-05-27 00:11:03
|
This is FOX 1.0 with FXRuby 1.0.28. Tom jeroen wrote: > On Tuesday 25 May 2004 08:41 pm, Tom wrote: > >>Here is something very interesting. This only affects windows, of >>course. When I have two FXDriveBox's and two FXDirList's, paired up so >>the dirlists are supposed to only respond to their own drive box's >>events, it turns out that when I select a drive in either of the >>FXDriveBox's, both of the FXDirLists change! Is there some way to keep >>the FXDirList's separate so that each FXDriveBox only changes the >>appropriate FXDirList? >> >>When I comment out the connect() for either the left or the right, >>changing the live drive box still changes the directories both dirlists. >> With neither connected, of course, nothing happens, but as long as >>one is connected, all FXDirLists get the same thing. I *must* be doing >>something wrong here. >> >>Here's the sample code: >> >> >>require 'fox' >> >>include Fox >> >>class DriveDialogs < FXMainWindow >> def initialize(owner) >> super(owner, "DriveDialogThingy", nil, nil, DECOR_ALL, 0, 0, 0, 0) >> createUI() >> end >> >> def create >> super() >> show(PLACEMENT_SCREEN) >> end >> >> def createUI() >> @contents = FXHorizontalFrame.new(self, >> LAYOUT_FILL_X|LAYOUT_FILL_Y) >> @leftvframe = FXVerticalFrame.new(@contents, >> LAYOUT_FILL_X|LAYOUT_FILL_Y) >> @rightvframe = FXVerticalFrame.new(@contents, >> LAYOUT_FILL_X|LAYOUT_FILL_Y) >> @leftdrivebox = FXDriveBox.new(@leftvframe,5) >> @rightdrivebox = FXDriveBox.new(@rightvframe,5) >> @leftdirlist = FXDirList.new(@leftvframe,10) >> @rightdirlist = FXDirList.new(@rightvframe,10) >> >> @leftdrivebox.connect(SEL_COMMAND) { |send,sel,ptr| >> @leftdirlist.directory = @leftdrivebox.drive >> } >> @rightdrivebox.connect(SEL_COMMAND) { |send,sel,ptr| >> @rightdirlist.directory = @rightdrivebox.drive >> } >> >> end >> >>end >> >>def run >> application = FXApp.new("DriveDialogThingy","DriveDialogThingy") >> DriveDialogs.new(application) >> application.create >> application.run >>end > > > Just asking, is this FOX 1.0 or FOX 1.2? > > > - Jeroen > |
From: jeroen <je...@fo...> - 2004-05-26 22:34:08
|
On Tuesday 25 May 2004 08:41 pm, Tom wrote: > Here is something very interesting. This only affects windows, of > course. When I have two FXDriveBox's and two FXDirList's, paired up so > the dirlists are supposed to only respond to their own drive box's > events, it turns out that when I select a drive in either of the > FXDriveBox's, both of the FXDirLists change! Is there some way to keep > the FXDirList's separate so that each FXDriveBox only changes the > appropriate FXDirList? > > When I comment out the connect() for either the left or the right, > changing the live drive box still changes the directories both dirlists. > With neither connected, of course, nothing happens, but as long as > one is connected, all FXDirLists get the same thing. I *must* be doing > something wrong here. > > Here's the sample code: > > > require 'fox' > > include Fox > > class DriveDialogs < FXMainWindow > def initialize(owner) > super(owner, "DriveDialogThingy", nil, nil, DECOR_ALL, 0, 0, 0, 0) > createUI() > end > > def create > super() > show(PLACEMENT_SCREEN) > end > > def createUI() > @contents = FXHorizontalFrame.new(self, > LAYOUT_FILL_X|LAYOUT_FILL_Y) > @leftvframe = FXVerticalFrame.new(@contents, > LAYOUT_FILL_X|LAYOUT_FILL_Y) > @rightvframe = FXVerticalFrame.new(@contents, > LAYOUT_FILL_X|LAYOUT_FILL_Y) > @leftdrivebox = FXDriveBox.new(@leftvframe,5) > @rightdrivebox = FXDriveBox.new(@rightvframe,5) > @leftdirlist = FXDirList.new(@leftvframe,10) > @rightdirlist = FXDirList.new(@rightvframe,10) > > @leftdrivebox.connect(SEL_COMMAND) { |send,sel,ptr| > @leftdirlist.directory = @leftdrivebox.drive > } > @rightdrivebox.connect(SEL_COMMAND) { |send,sel,ptr| > @rightdirlist.directory = @rightdrivebox.drive > } > > end > > end > > def run > application = FXApp.new("DriveDialogThingy","DriveDialogThingy") > DriveDialogs.new(application) > application.create > application.run > end Just asking, is this FOX 1.0 or FOX 1.2? - Jeroen -- +----------------------------------------------------------------------------+ | Copyright (C) 23:50 12/11/2003 Jeroen van der Zijp. All Rights Reserved. | +----------------------------------------------------------------------------+ |
From: Claus S. <Doc...@gm...> - 2004-05-26 13:56:30
|
In my (limited) experience, you could catch the mouse events... e.g. @table.connect( SEL_LEFTBUTTONPRESS, method( :onDown ) ) @table.connect( SEL_LEFTBUTTONRELEASE, method( :onUp ) ) and then create the methods onDown and onUp. Capture the x/y location on each method, def onDown( sender, sel, event ) x = event.win_x y = event.win_y # What row and column was clicked. row = @table.rowAtY( y ) col = @table.colAtX( x ) ... end There is probably a better way to do it, but I'm just a beginner with FXRuby I'm afraid... On Wed, 26 May 2004 13:43:55 +0200, Fredrik Jagenheim <fr...@po...> wrote: > > Hi, > > I'm currently using anchor[Row|Column] and current[Row|Column] to see > which cells are selected in a FXTable, but that only works when the > cells are selected using 'Shift+cursor' selection. When selecting > using the mouse I get that the anchor == current. > > Am I missing something obvious, or doing it the wrong way? > > Thanks, > //F > > ------------------------------------------------------- > This SF.Net email is sponsored by: Oracle 10g > Get certified on the hottest thing ever to hit the market... Oracle 10g. > Take an Oracle 10g class now, and we'll give you the exam FREE. > http://ads.osdn.com/?ad_id=3149&alloc_id=8166&op=click > _______________________________________________ > Fxruby-users mailing list > Fxr...@li... > https://lists.sourceforge.net/lists/listinfo/fxruby-users > |
From: Fredrik J. <fr...@po...> - 2004-05-26 11:45:24
|
Hi, I'm currently using anchor[Row|Column] and current[Row|Column] to see which cells are selected in a FXTable, but that only works when the cells are selected using 'Shift+cursor' selection. When selecting using the mouse I get that the anchor == current. Am I missing something obvious, or doing it the wrong way? Thanks, //F |
From: Tom <tku...@so...> - 2004-05-26 01:42:20
|
Here is something very interesting. This only affects windows, of course. When I have two FXDriveBox's and two FXDirList's, paired up so the dirlists are supposed to only respond to their own drive box's events, it turns out that when I select a drive in either of the FXDriveBox's, both of the FXDirLists change! Is there some way to keep the FXDirList's separate so that each FXDriveBox only changes the appropriate FXDirList? When I comment out the connect() for either the left or the right, changing the live drive box still changes the directories both dirlists. With neither connected, of course, nothing happens, but as long as one is connected, all FXDirLists get the same thing. I *must* be doing something wrong here. Here's the sample code: require 'fox' include Fox class DriveDialogs < FXMainWindow def initialize(owner) super(owner, "DriveDialogThingy", nil, nil, DECOR_ALL, 0, 0, 0, 0) createUI() end def create super() show(PLACEMENT_SCREEN) end def createUI() @contents = FXHorizontalFrame.new(self, LAYOUT_FILL_X|LAYOUT_FILL_Y) @leftvframe = FXVerticalFrame.new(@contents, LAYOUT_FILL_X|LAYOUT_FILL_Y) @rightvframe = FXVerticalFrame.new(@contents, LAYOUT_FILL_X|LAYOUT_FILL_Y) @leftdrivebox = FXDriveBox.new(@leftvframe,5) @rightdrivebox = FXDriveBox.new(@rightvframe,5) @leftdirlist = FXDirList.new(@leftvframe,10) @rightdirlist = FXDirList.new(@rightvframe,10) @leftdrivebox.connect(SEL_COMMAND) { |send,sel,ptr| @leftdirlist.directory = @leftdrivebox.drive } @rightdrivebox.connect(SEL_COMMAND) { |send,sel,ptr| @rightdirlist.directory = @rightdrivebox.drive } end end def run application = FXApp.new("DriveDialogThingy","DriveDialogThingy") DriveDialogs.new(application) application.create application.run end run |
From: Simon S. <ne...@ad...> - 2004-05-25 22:38:26
|
Simon Strandgaard <ne...@ad...> wrote: > Simon Strandgaard <ne...@ad...> wrote: > > The attached code should reproduce the problem. > > > > I spawn an filedialog like this, but it doesn't recieve focus. > > > > I have attached a much shorter piece code which can > reproduce it on my machine. > > Please tell me what I am doing wrong... I cannot see it myself. > > > Few times this code actually works.. but most times it doesn't. > I cannot see anything in it which could be the source to this random > behaviour. I have now switched to another window manager, where focus are working correct. So never mind. I am still learning, I wasn't aware that there were such problems with fox <--> X11 window managers. I tried these WM's out in top-down order, my current WM are fvwm2. I have gotten the following problems, while trying to make my application able to switch between windowed-mode and fullscreen-mode. WM symthom blackbox 0.65.0 in windowed mode, DECOR_RESIZE are ignored. Resulting in a window which cannot be resized. openbox 3.2 windowed mode, problems passing focus to dialogboxes. Resulting in that the parent (in the background) keeps focus. If you type on the keyboard then the machine beeps at you. fvwm2 2.4.18 fullscreen mode, DECOR_NONE is ignored and a titlebar is visible. Resulting in a fullscreen sized window, where the bottom part is 20 pixels outside the display-border. What WM does fox interact best with (reference implementation) ? -- Simon Strandgaard |
From: Claus S. <Doc...@gm...> - 2004-05-25 21:03:42
|
Perhaps a spash screen? I wouldn't know how to approach this in FXRuby though On Tue, 25 May 2004 16:45:40 +0200, Christian von Mueffling <chr...@pd...> wrote: > > Hi! > > I have an application that needs some time until the main window build > up is finished (lots of data to read, etc.) > > It would be convenient to provide a small dialog that shows some > progress while doing that (something like a small window in the middle > of the screen without decorations ...). > > I was playing around running a second thread in which the widgets are > build and mapped while the main app already is running. But I'm not > really satisfied with this solution (and I guess this is also rather > dangerous). > > Any idea how else I could do that? > > Thanks, > -- > chris > > ------------------------------------------------------- > This SF.Net email is sponsored by: Oracle 10g > Get certified on the hottest thing ever to hit the market... Oracle 10g. > Take an Oracle 10g class now, and we'll give you the exam FREE. > http://ads.osdn.com/?ad_id=3149&alloc_id=8166&op=click > _______________________________________________ > Fxruby-users mailing list > Fxr...@li... > https://lists.sourceforge.net/lists/listinfo/fxruby-users > |
From: Simon S. <ne...@ad...> - 2004-05-25 19:43:38
|
Simon Strandgaard <ne...@ad...> wrote: > The attached code should reproduce the problem. > > I spawn an filedialog like this, but it doesn't recieve focus. > I have attached a much shorter piece code which can reproduce it on my machine. Please tell me what I am doing wrong... I cannot see it myself. Few times this code actually works.. but most times it doesn't. I cannot see anything in it which could be the source to this random behaviour. -- Simon Strandgaard |
From: Simon S. <ne...@ad...> - 2004-05-25 18:54:10
|
The attached code should reproduce the problem. I spawn an filedialog like this, but it doesn't recieve focus. dialog = FXFileDialog.new(self, "pick file") break if dialog.execute == 0 The problem is that the examples distributed with fxruby works, and mine doesn't. I have tried the whole day to figure out what could be the reason. I have look at how FXDialogBox.execute was implemented and played around trying to hide the parent.. but no luck either. I simply cannot spawn the dialogbox with focus. Any hints will be appreciated :-) -- Simon Strandgaard |
From: Simon S. <ne...@ad...> - 2004-05-25 16:54:44
|
On Tue, 25 May 2004 16:45:40 +0200 Christian von Mueffling <chr...@pd...> wrote: > I have an application that needs some time until the main window build > up is finished (lots of data to read, etc.) > > It would be convenient to provide a small dialog that shows some > progress while doing that (something like a small window in the middle > of the screen without decorations ...). > > I was playing around running a second thread in which the widgets are > build and mapped while the main app already is running. But I'm not > really satisfied with this solution (and I guess this is also rather > dangerous). > > Any idea how else I could do that? I guess you could have an invisible MainWindow, which doesn't contains anything. The MainWindow are able to spawn dialogs. So what now is your mainwindow would then become a dialog. This way you would be able to show a progressbar dialog while waiting for the build to complete. -- Simon Strandgaard |
From: Christian v. M. <chr...@pd...> - 2004-05-25 14:45:48
|
Hi! I have an application that needs some time until the main window build up is finished (lots of data to read, etc.) It would be convenient to provide a small dialog that shows some progress while doing that (something like a small window in the middle of the screen without decorations ...). I was playing around running a second thread in which the widgets are build and mapped while the main app already is running. But I'm not really satisfied with this solution (and I guess this is also rather dangerous). Any idea how else I could do that? Thanks, -- chris |
From: Christian v. M. <chr...@pd...> - 2004-05-25 14:15:56
|
Hi! I have an application that needs some time until the main window build up is finished (lots of data to read, etc.) It would be convenient to provide a small dialog that shows some progress while doing that (something like a small window in the middle of the screen without decorations ...). I was playing around running a second thread in which the widgets are build and mapped while the main app already is running. But I'm not really satisfied with this solution (and I guess this is also rather dangerous). Any idea how else I could do that? Thanks, -- chris |
From: Lyle J. <ly...@kn...> - 2004-05-25 12:37:11
|
On May 25, 2004, at 7:27 AM, Simon Strandgaard wrote: > maybe also add link to your verbose document about 1.2 changes? I probably will do that also, as soon as the latter is up-to-date. If I recall correctly, it's only up-to-date as of fox-1.1.45 or so. |
From: Simon S. <ne...@ad...> - 2004-05-25 12:32:03
|
Lyle Johnson <ly...@kn...> wrote: > On May 25, 2004, at 5:39 AM, Simon Strandgaard wrote: > > > <proposal> > > Add a brief notice to the homepage's download section, about the > > status of > > fxruby 1.2. Just in case people are looking fore it. > > </proposal> > > Proposal accepted and implemented. Thanks for the suggestion. ;) Excelent! maybe also add link to your verbose document about 1.2 changes? -- Simon Strandgaard |
From: Lyle J. <ly...@kn...> - 2004-05-25 12:21:36
|
On May 25, 2004, at 5:39 AM, Simon Strandgaard wrote: > <proposal> > Add a brief notice to the homepage's download section, about the > status of > fxruby 1.2. Just in case people are looking fore it. > </proposal> Proposal accepted and implemented. Thanks for the suggestion. ;) |
From: Simon S. <ne...@ad...> - 2004-05-25 11:23:13
|
Matthew Miller <nam...@na...> wrote: > On Tue, May 25, 2004 at 01:28:03AM +0200, Simon Strandgaard wrote: > > My current windowmanager Blackbox, seems to be inactive, the last release > > is 2 years old. Perhaps I just should switch back to fvwm2. > > I used to run Blackbox and I still like to use it. I now use a similar, and I > thing be better WM, openbox. Openbox was once based on Blackbox, but the version > 3 branch is a rewrite and it is very easy to use. The best thing about it? I can > use the mouse scroll wheel to change desktops! The scroll wheel will also > (un)shade windows. Check it out. I downloaded and begun making myself a cup tea, at the same time when the tea was ready, the openbox was ready. Its quick to compile on my 700 MHz wardrobe machine. More importantly in openbox the DECOR_RESIZE are working on FXDialogBox'es. All my resize problems has been solved, thanks for all the many suggestions I have gotten. Thanks to you, Jeroen, Lyle, Rich. -- Simon Strandgaard |
From: Simon S. <ne...@ad...> - 2004-05-25 10:43:28
|
Lyle Johnson <ly...@kn...> wrote: > On May 24, 2004, at 6:28 PM, Simon Strandgaard wrote: > > > BTW: Does fxruby work with fox-1.2 ? > > Please check the mailing list archives for the answer to this question. > > http://sourceforge.net/mailarchive/forum.php?forum_id=33510 I spend 5 minutes searching the archive and found the answer http://sourceforge.net/mailarchive/message.php?msg_id=7047828 > It's getting a little silly to answer to this question every other day. I browsed the fxruby.org homepage, but could not see any downloads for it. I saw the note about fxruby version 1.0.x are compatible with fox-toolkit 1.0.x. So I guessed fxruby 1.2 wasn't here yet. I asked just because it was unclear to me, Sorry. <proposal> Add a brief notice to the homepage's download section, about the status of fxruby 1.2. Just in case people are looking fore it. </proposal> -- Simon Strandgaard |
From: Lyle J. <ly...@kn...> - 2004-05-25 00:35:21
|
On May 24, 2004, at 6:28 PM, Simon Strandgaard wrote: > BTW: Does fxruby work with fox-1.2 ? Please check the mailing list archives for the answer to this question. http://sourceforge.net/mailarchive/forum.php?forum_id=33510 It's getting a little silly to answer to this question every other day. |
From: Lyle J. <ly...@kn...> - 2004-05-25 00:30:32
|
On May 23, 2004, at 8:48 PM, Tom wrote: > Aha! This is what I put in, after creating with "drivebox = > FXDriveBox..." and "dirbox = FXDirBox..." > > drivebox.connect(SEL_COMMAND) { |send,sel,ptr| > dirbox.directory = send.drive > } > > Is this an appropriate usage of the sender or should I have used > "drivebox.drive" instead? Either one is fine. In this case, the drivebox *is* the sender of the SEL_COMMAND message, so "send" is a reference to your FXDriveBox object. |
From: Matthew M. <nam...@na...> - 2004-05-24 23:47:45
|
Hi, On Tue, May 25, 2004 at 01:28:03AM +0200, Simon Strandgaard wrote: > My current windowmanager Blackbox, seems to be inactive, the last release > is 2 years old. Perhaps I just should switch back to fvwm2. I used to run Blackbox and I still like to use it. I now use a similar, and I thing be better WM, openbox. Openbox was once based on Blackbox, but the version 3 branch is a rewrite and it is very easy to use. The best thing about it? I can use the mouse scroll wheel to change desktops! The scroll wheel will also (un)shade windows. Check it out. Matthew -- So far as I can remember, there is not one word in the Gospels in praise of intelligence. -- Bertrand Russell (1872-1970) |
From: Simon S. <ne...@ad...> - 2004-05-24 23:32:21
|
jeroen wrote: > On Monday 24 May 2004 04:28 pm, Simon Strandgaard wrote: > > I looked at both the examples with fxruby and the examples with fox itself, > > to see how they made their dialogs resizable. I discovered that resizing > > does'nt work there either. I looked at the FXWindow.cpp file, but way it > > deal with 'options' looked ok to me. > > > > Is it a known problem that resizing decorations doesn't work (except the > > mainwindow)? > > It depends on the window manager. Under KDE WM it works, under Motif also. > Sometimes, options may be coupled, i.e. DECOR_RESIZE may have no effect > unless DECOR_BORDER is also turned on. Do you have a web page where one can see an overview of all known issues? My current windowmanager Blackbox, seems to be inactive, the last release is 2 years old. Perhaps I just should switch back to fvwm2. > > I am curious to if resizing works on you box, perhaps with a different > > version of fox? > > > > Please help. > > > > > > I have installed fox-1.0.51. > > I will try to install an older version to see if resizing works there. > > It should make no difference; but you can try newer versions of FOX which > support extended window manager hints... > Do you know if fvwm2 supports extended window manager hints ? Besides KDE WM and Motif, do you know other WM's that supports it? BTW: Does fxruby work with fox-1.2 ? Thanks in advance. -- Simon Strandgaard |
From: Simon S. <ne...@ad...> - 2004-05-24 22:52:36
|
jeroen <je...@fo...> wrote: > On Monday 24 May 2004 09:09 am, Simon Strandgaard wrote: > > I somewhere read a reply by Jeroen, that some windowmanagers ignore > > the decoration requests.. I guess in order to switch from > > window-mode (with decorations) to full-screen (borderless) then > > I have to close the window and spawn a full-screen window. > > The maximize requires the window manager to understand "extended window manager > hints". See freedesktop.org for details. > > My first choice would be to see if the blackbox people have added this already, > and if not, request it from them [it'll help with ALL modern GUI apps, not > just FOX but also gnome and kde]. I just tried a quick switch to FWM, there resize are working. However I forgot to close my mail-client (sylpheed), and it of cause hadn't written it configuration to disk. The fxruby folder I created today did not survive *sigh*. I would have liked to reply to your other mail, but cannot. Conclusion1: write config to file immediately after a the user have changed something. Conclusion2: close all windows before switching window-manager. > While you're waiting, you can create a borderless toplevel window and reparent > into that. This should work AFIAK. > The advantage of reparenting is that you can reparent again to move back to > the original toplevel window when you come out of full screen mode again. I think I understand what you are saying, however I don't know how to 'reparent'. Any hints ? I partially solved it myself by inherit from FXDialogBox, except that A) when in windowed mode, the window is not resizable. B) don't know how to hide MainWindow. My Ruby implementation can be seen here: http://rubyforge.org/cgi-bin/viewcvs/cgi/viewcvs.cgi/projects/experimental/buffer/viewfox.rb?rev=1.29&cvsroot=aeditor&content-type=text/vnd.viewcvs-markup BTW: thanks for the suggestions :-) -- Simon Strandgaard |
From: jeroen <je...@fo...> - 2004-05-24 22:15:45
|
On Monday 24 May 2004 04:28 pm, Simon Strandgaard wrote: > I looked at both the examples with fxruby and the examples with fox itself, > to see how they made their dialogs resizable. I discovered that resizing > does'nt work there either. I looked at the FXWindow.cpp file, but way it > deal with 'options' looked ok to me. > > Is it a known problem that resizing decorations doesn't work (except the > mainwindow)? It depends on the window manager. Under KDE WM it works, under Motif also. Sometimes, options may be coupled, i.e. DECOR_RESIZE may have no effect unless DECOR_BORDER is also turned on. > I am curious to if resizing works on you box, perhaps with a different > version of fox? > > Please help. > > > I have installed fox-1.0.51. > I will try to install an older version to see if resizing works there. It should make no difference; but you can try newer versions of FOX which support extended window manager hints... - Jeroen -- +----------------------------------------------------------------------------+ | Copyright (C) 23:50 12/11/2003 Jeroen van der Zijp. All Rights Reserved. | +----------------------------------------------------------------------------+ |