On Tue, Jan 15, 2002 at 12:55:03PM +0100, Olivier Chapuis wrote: > On Tue, Jan 15, 2002 at 12:03:11PM +0100, Dominik Vogt wrote: > > On Mon, Jan 14, 2002 at 04:30:50PM -0500, MonMotha wrote: > > > Config as requested: > > > > > > DestroyModuleConfig FvwmIconBox* > > > *FvwmIconBox: Colorset 1 > > > *FvwmIconBox: MaxIconSize 16x16 > > > *FvwmIconBox: Geometry 10x1+0-0 > > > *FvwmIconBox: HideSC Vertical > > > *FvwmIconBox: HideSC Horizontal > > > *FvwmIconBox: FrameWidth 2 2 > > > *FvwmIconBox: Font -*-nil-*-*-*-*-*-*-*-*-*-*-*-* > > > *FvwmIconBox: Resolution Desk > > > *FvwmIconBox: SetWMIconSize > > > *FvwmIconBox: Padding 0 > > > *FvwmIconBox: IconColorSet 1 > > > *FvwmIconBox: IconHiColorSet 1 > > > *FvwmIconBox: Mouse 1 Click Iconify > > > > > > That's the entire config for my iconbox. Someone reccomended setting > > > the font really tiny and using the same colorset to get what looks like > > > transparent text, but it still draws the raised border thingy for the > > > text. > > > > > > Still have no idea what's up with the "delay" issue I'm seeing. > > > > With your config I can see the problem. If you use > > > > ClickTime 150 > > > > *before* you start FvwmIconBox, the delay decreases. Furthermore > > I have problems with iconifying/deiconifying windows. About every > > second click is completely ignored. I'll look into that. > > > > I've already a fix on my machine for that (if there is no double > click action defined the action is executed "immediately" with the > method 4 below).
I've already committed a fix. I couldn't reproduce the other problem (clicks being ignored) though. > The only problem is the "usual problem": if there is > no double click action should we do the action at: > 1 - button press (do not think so). > 2 - button release; action executed on the window of the button release > (bad to ? FvwmWinList and FvwmTaskBar do that!) > 3 - button release; action executed on the window of the button press > (bad to ? FvwmIconMan do this (not always)) > 4 - button release; action only if the button release window is the same > than the button press window and do not care here about motion or > timeout (seems good) FvwmIconMan has a copy of the action checking code in functions.c. It works quite the same, it even has a move threshold and its own click time. It would be good to use fvwm's ClickTime and MoveThreshold settings at run time, but otherwise it works nicely now. Bye Dominik ^_^ ^_^ -- Dominik Vogt, email: [EMAIL PROTECTED] LifeBits Aktiengesellschaft, Albrechtstr. 9, D-72072 Tuebingen fon: ++49 (0) 7071/7965-0, fax: ++49 (0) 7071/7965-20 -- 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]
