From: Thomas L. <ta...@ec...> - 2002-05-09 15:23:05
|
On Thu, May 09, 2002 at 04:08:32PM +0100, Geoff Youngs wrote: > On Thu, May 09, 2002 at 09:30:19AM -0400, Gregory Spath wrote: > > What about WM's that allow you to specify which button you prefer? (I > > use 2 anyway, so no biggie). I would think that ROX should honor the > > WM's configuration. Is there a way for this to be done? > > Sawfish seems to work like this anyway: right click menu works OK here. > Unfortunately button 2 doesn't work anymore: I don't have sawfish > configured to use it for anything, but I do have ROX configured to use > button 2 as the menu button which no longer works :( Good point. Should be fixed now (button-2 for WM menu, button-3 for ROX menu -- trying to make a button-3 press look like a button-2 press to the window manager is just asking for trouble ;-) I've also made quite a lot of other changes to the pinboard today: - The method for external applications to set the backdrop has completely changed. It should mean that the application will reliably terminate, even if the filer crashes, and not keep trying to set the backdrop. See the manual for details... the example given renders XEarth's image onto the backdrop, updating once a minute. - Pinboard icons were being draw onto a drawing area with a ParentRelative backdrop. Unfortunately, this caused the X server's memory to increase by about 1Mb each time the backdrop changed, and quitting the filer didn't get the memory back! Therefore, icons are now drawn directly on the backdrop, with a floating InputOnly window above each one to catch events. - The above InputOnly trickery is actually implemented already in the GtkButton class, so I just made the icons borderless buttons. This has created an interesting new highlight effect (haven't decided if I like it or not yet...), and also means that the sensitive region of the icon is now the rectangular area surrounding it, not just the image (good!). More testing welcome! -- Thomas Leonard http://rox.sourceforge.net ta...@ec... ta...@us... |