On Sat, Oct 09, 1999 at 05:42:28PM +0000, harbaugh_at_math.georgetown.edu wrote:
> The situation described roughly in the Subject line happens in several
> situations, most simply in the following situation:
>
> I bring up an FvwmConsole using a menu.
> In the console, I type
> ChangeDecor decor-root
> where decor-root is a decor that has already been defined
> via an AddToDecor command in my .fvwmrc file.
> The mouse pointer changes to a large dot,
> requesting a window selection for this action,
> so I click in that window (no problem there).
> But then the expected action, changing the HilightColor,
> only happens to a very thin outermost border of the window,
> the bulk of the window frame stays in its original color.
> However, if I move the mouse pointer into another active window,
> then back to the window whose decor had been requested to be changed,
> (this is what I meant by "manual intervention")
> then the entire window frame switches to the requested color.
>
> What do I have to do programatically to make the ChangeDecor take full effect,
> without having to move the mouse around?
You can call a fvwm function that issues a 'RefreshWindow' after the ChangeDecor:
AddToFunc ChangeDecorAndRefresh
+ "I" ChangeDecor decor-root
+ "I" RefreshWindow
This bug is fixed in the current development sources already.
Bye
Dominik ^_^
--
Dominik Vogt, Hewlett-Packard GmbH, Dept. BVS
Herrenberger Str.130, 71034 Boeblingen, Germany
phone: 07031/14-4596, fax: 07031/14-3883, dominik_vogt_at_hp.com
--
Visit the official FVWM web page at <URL: http://www.fvwm.org/>.
To unsubscribe from the list, send "unsubscribe fvwm" in the body of a
message to majordomo_at_fvwm.org.
To report problems, send mail to fvwm-owner_at_fvwm.org.
Received on Sun Oct 10 1999 - 17:17:28 BST