Re: Xinerama support for IconBox style?
On Mon, Aug 20, 2001 at 08:05:14PM -0400, Dan Espen wrote: Dmitry Yu. Bolkhovityanov [EMAIL PROTECTED] writes: On Mon, 20 Aug 2001, Dan Espen wrote: Dominik Vogt fvwm-workers@fvwm.org writes: Currently, fvwm uses the icon boxes in the order of creation. So, if one icon box is created on screen 0 and one is created on screen 1, all icons are placed on screen 0 until the icon box is full, then all icons are put on screen 1. My question was if it is necessary to skip icon boxes that are not on the same screen as the window. I don't think we'd want to apply the same screen test unless the user indicated that the iconbox was for a specific screen. Right now, theres no way to do that. Would it be possible to remember the screen# together with translated geometry? It can be saved, but what for? For recalculation of the icon boxes when the Xinerama command is used. Let's assume Xinerama is enabled with two screens. Style * IconBox [EMAIL PROTECTED] puts the icon box at 0 0 of screen 1. Now, Xinerama off is issued. The @1 must now refer to the global screen since there are no more Xinerama screens. Bye Dominik ^_^ ^_^ -- Dominik Vogt, [EMAIL PROTECTED] Reply-To: [EMAIL PROTECTED] -- Visit the official FVWM web page at URL:http://www.fvwm.org/. To unsubscribe from the list, send unsubscribe fvwm-workers in the body of a message to [EMAIL PROTECTED] To report problems, send mail to [EMAIL PROTECTED]
CVS domivogt: * Somewhat lessen the problem with multiple keysyms w/ same keycode.
CVSROOT:/home/cvs/fvwm Module name:fvwm Changes by: domivogt01/08/25 08:40:54 Modified files: . : ChangeLog NEWS fvwm : cursor.c focus.c icons.c libs : Bindings.c Colorset.c modules: ChangeLog modules/FvwmButtons: FvwmButtons.c modules/FvwmIconBox: FvwmIconBox.c icons.c modules/FvwmIconMan: readconfig.c xmanager.c modules/FvwmIdent: FvwmIdent.c modules/FvwmRearrange: FvwmRearrange.c modules/FvwmScript: FvwmScript.c modules/FvwmTaskBar: FvwmTaskBar.c modules/FvwmWharf: FvwmWharf.c icons.c modules/FvwmWinList: FvwmWinList.c Log message: * Somewhat lessen the problem with multiple keysyms w/ same keycode. * -Wall fixes when compiling w/o XPM or SHAPE. * replaxed all strlen(XINERAMA_CONFIG_STRING) with sizeof(...). -- Visit the official FVWM web page at URL:http://www.fvwm.org/. To unsubscribe from the list, send unsubscribe fvwm-workers in the body of a message to [EMAIL PROTECTED] To report problems, send mail to [EMAIL PROTECTED]
CVS domivogt: * Fixed backwards compatibility in FvwmBacker.
CVSROOT:/home/cvs/fvwm Module name:fvwm Changes by: domivogt01/08/25 09:45:19 Modified files: . : NEWS modules: ChangeLog modules/FvwmBacker: FvwmBacker.1 FvwmBacker.c Log message: * Fixed backwards compatibility in FvwmBacker. -- Visit the official FVWM web page at URL:http://www.fvwm.org/. To unsubscribe from the list, send unsubscribe fvwm-workers in the body of a message to [EMAIL PROTECTED] To report problems, send mail to [EMAIL PROTECTED]
Re: Incompatible change to FvwmBacker?
On Thu, Aug 23, 2001 at 12:40:03PM +0100, Tim Phipps wrote: [EMAIL PROTECTED] wrote: Did I miss something when I concluded that FvwmBacker can no longer do what it did before? No, if FvwmBacker does what the man page says: *FvwmBackerCommand (Desk d, Page x y) command Specifies the command to execute when the viewport matches the arguments for the desk d, page x coordinate and y coordinate. Any or all of these three numeric arguments can be replaced with an asterisk (*) to indi- cate that any value matches, in this case Desk or Page parts can be skipped. Note these three lines are equivalent: *FvwmBackerCommand (Page * *, Desk *) -solid navy *FvwmBackerCommand () -solid navy *FvwmBackerCommand -solid navy plus this: There is continued support for the now deprecated option: *FvwmBackerDesk d command It is functionally equivalent to using an asterisk for both page coordinates with *FvwmBackerCommand. So *FvwmBackerDesk 0 ... gets translated to *FvwmBackerCommand (Page * *, Desk 0) ... which isn't quite the same thing. There seems to be no way to stop FvwmBacker doing its thing when the page changes and the desk matches. I think we should change the behaviour of FvwmBacker when the Page specifers are not included so that it _doesn't_ do its thing if only the page changes. Similarly if the Desk specifier is not included it _shouldn't_ do its thing when only the desk changes. Then translating *FvwmBackerDesk 0 ... into *FvwmBackerCommand (Desk 0) ... would work in the old way. Done. Omitting either Desk or Page now indicates to ignore desk or page changes. FvwmBackerDesk n ... is equivalent to FvwmBackerCommand (Desk n) ... Bye Dominik ^_^ ^_^ -- Dominik Vogt, [EMAIL PROTECTED] Reply-To: [EMAIL PROTECTED] -- Visit the official FVWM web page at URL:http://www.fvwm.org/. To unsubscribe from the list, send unsubscribe fvwm-workers in the body of a message to [EMAIL PROTECTED] To report problems, send mail to [EMAIL PROTECTED]
CVS domivogt: * Applied ShowOnlyIcons patch by Simon Kagstrom.
CVSROOT:/home/cvs/fvwm Module name:fvwm Changes by: domivogt01/08/25 11:07:23 Modified files: fvwm : focus.c modules: ChangeLog modules/FvwmIconMan: FvwmIconMan.h globals.c readconfig.c xmanager.c Log message: * Applied ShowOnlyIcons patch by Simon Kagstrom. * Partially backed out xfm double-click patch. -- Visit the official FVWM web page at URL:http://www.fvwm.org/. To unsubscribe from the list, send unsubscribe fvwm-workers in the body of a message to [EMAIL PROTECTED] To report problems, send mail to [EMAIL PROTECTED]
CVS dane: * fvwm/style.c (CMD_Style): Fix up iconboxes using negative geom specs.
CVSROOT:/home/cvs/fvwm Module name:fvwm Changes by: dane01/08/25 15:03:38 Modified files: . : ChangeLog fvwm : style.c Log message: * fvwm/style.c (CMD_Style): Fix up iconboxes using negative geom specs. -- Visit the official FVWM web page at URL:http://www.fvwm.org/. To unsubscribe from the list, send unsubscribe fvwm-workers in the body of a message to [EMAIL PROTECTED] To report problems, send mail to [EMAIL PROTECTED]
CVS migo: * quote both missing function name and menu name for MissingSubmenuFunction
CVSROOT:/home/cvs/fvwm Module name:fvwm Changes by: migo01/08/25 15:17:14 Modified files: . : NEWS ChangeLog fvwm : menus.c functions.c libs : Strings.c Strings.h Log message: * quote both missing function name and menu name for MissingSubmenuFunction _ (now fvwm-menu-directory gets directories with spaces/tabs correctly) * added and used new function QuoteString() -- Visit the official FVWM web page at URL:http://www.fvwm.org/. To unsubscribe from the list, send unsubscribe fvwm-workers in the body of a message to [EMAIL PROTECTED] To report problems, send mail to [EMAIL PROTECTED]
CVS dane: * fvwm/style.c (CMD_Style):
CVSROOT:/home/cvs/fvwm Module name:fvwm Changes by: dane01/08/25 15:19:52 Modified files: . : ChangeLog fvwm : fvwm.h style.c Log message: * fvwm/style.c (CMD_Style): * fvwm/fvwm.h (icon_boxes_struct): Add screen to iconbox struct when using geometry spec. -- Visit the official FVWM web page at URL:http://www.fvwm.org/. To unsubscribe from the list, send unsubscribe fvwm-workers in the body of a message to [EMAIL PROTECTED] To report problems, send mail to [EMAIL PROTECTED]
Re: icon box problem
Dominik Vogt [EMAIL PROTECTED] writes: I'm using this icon box spec: Style * IconBox [EMAIL PROTECTED] I just noticed that only the first window I iconify goes into the icon box. All further icons go into the default icon box, i.e. they fill the screen top to bottom first, starting in the top left corner of the screen. Fixed. Sorry, all these x/y and width and height things get confusing. -- Dan Espen 444 Hoes Lane Room RRC 1C-214 E-mail: [EMAIL PROTECTED] Piscataway, NJ 08854 Phone: (732) 699-5570 -- Visit the official FVWM web page at URL:http://www.fvwm.org/. To unsubscribe from the list, send unsubscribe fvwm-workers in the body of a message to [EMAIL PROTECTED] To report problems, send mail to [EMAIL PROTECTED]
Re: Xinerama support for IconBox style?
Dominik Vogt [EMAIL PROTECTED] writes: On Mon, Aug 20, 2001 at 08:05:14PM -0400, Dan Espen wrote: Dmitry Yu. Bolkhovityanov [EMAIL PROTECTED] writes: On Mon, 20 Aug 2001, Dan Espen wrote: Dominik Vogt fvwm-workers@fvwm.org writes: Currently, fvwm uses the icon boxes in the order of creation. So, if one icon box is created on screen 0 and one is created on screen 1, all icons are placed on screen 0 until the icon box is full, then all icons are put on screen 1. My question was if it is necessary to skip icon boxes that are not on the same screen as the window. I don't think we'd want to apply the same screen test unless the user indicated that the iconbox was for a specific screen. Right now, theres no way to do that. Would it be possible to remember the screen# together with translated geometry? It can be saved, but what for? For recalculation of the icon boxes when the Xinerama command is used. Let's assume Xinerama is enabled with two screens. Thanks, now I understand. I added the screen spec to the iconbox structure for the case when a geometry style spec is used, but the IconBox can also be defined in l r t b format. There are times when that format is required. I don't know what format you'd like to use in that case. I suppose just another string and pass it over to XineramaSupportParseScreenBit? Like: Style * Iconbox -80 240 -1 -1 g I didn't do anything but put the value in the structure. -- Dan Espen 444 Hoes Lane Room RRC 1C-214 E-mail: [EMAIL PROTECTED] Piscataway, NJ 08854 Phone: (732) 699-5570 -- Visit the official FVWM web page at URL:http://www.fvwm.org/. To unsubscribe from the list, send unsubscribe fvwm-workers in the body of a message to [EMAIL PROTECTED] To report problems, send mail to [EMAIL PROTECTED]
