On 2016-12-26 12:54:05 -0700, Jaimos Skriletz wrote: > On Mon, Dec 26, 2016 at 12:06 PM, Vincent Lefevre <vinc...@vinc17.net> wrote: > > On 2016-12-26 02:24:30 +0100, Vincent Lefevre wrote: > >> Since I've upgraded fvwm from 1:2.6.5.ds-4.1 to 1:2.6.7-2 (last night), > >> I have the following problems. I have the following in my config: > >> > >> Mouse 1 A SCM Raise > > > > and the problem is reproducible with just this line in the config file. > > Thank you for your bug report. > > It seems to me the issue is with the context A (anywhere) in your binding. > When you run the Raise function. Since this can be done Anywhere, the > context of which window to Raise may not be correctly set. > > I don't know the details completely, but my understanding is if the > context is not set to a window, Raise will want you to pick the > window to raise, so it will pause fvwm and let you click on the > window you want to raise.
But this is not what I observe. Well, if I click over the root window, I get this behavior as expected, and this is fine. Note that concerning the problem I've reported, I always clicked inside the window to be raised. Note also that if: * I SCM-click inside Window A, * the problem occurs, * I click inside Window B, then it is Window A that is raised, not Window B. This means that FVWM knew really which window had to be raised. Note also that when FVWM wants me to pick the window to raise (e.g. after a SCM-click over the root window), the mouse pointer changes to a cross. But when the problem occurs, the mouse pointer remains the same as usual and still changes depending on the context as usual. > It may also be the context is set to a different window than you > expect. This could also explain the inconsistency of being able to > reproduce it, since most times when you use the binding the context is > as you expect it to be and the correct window is raised, but sometimes > it is not, in which case you either have fvwm pause for you to pick > the window to raise or it preforms the action on a different window. I don't understand what you mean. > Two solutions would be to narrow the context to say the window and its > decorations, FSTW, or wrap the Raise command into a function on use a > conditional (such as ThisWindow or Current) to force the context. More > on the context for functions can be found here: > > http://fvwmforums.org/wiki/Config/FunctionContext/ I suppose that the context is correct since FVWM raises the correct window after a click anywhere (see above). To be sure, I wanted to test with: AddToFunc RaiseDbg + I Echo $[w.name] + I Raise Mouse 1 A SCM RaiseDbg but I can't reproduce the problem with this! -- Vincent Lefèvre <vinc...@vinc17.net> - Web: <https://www.vinc17.net/> 100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/> Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)
