On 11/02/18 18:11, Francois Gouget wrote:
On Thu, 1 Feb 2018, Zebediah Figura wrote: [...]
- user32:win, perhaps one of the most notorious offenders, has three
consistent failures left, and possibly some more intermittent ones.
- Lines 3364-5 (test_SetForegroundWindow) and 9940-4
(test_LockWindowUpdate) were determined by jwhite to be the fault of the hwndMain test window being minimized during the test. I further investigated and traced this down, surprisingly enough, to a bug in fvwm, which I've reported at [5]. The bug involves a lot of steps to trigger, notably, and we can (and, I think, should) work around it by modifying the test machine configuration: either by changing the focus mode from MouseFocus, or by removing the RaiseTransient or StackTransientParent style. [5] https://github.com/fvwmorg/fvwm/issues/51
I'm not sure what to do for this. Here's the fvwm configuration of the cw1 and cw2 machines:
$ cat ~/.fvwm/config Style * ClickToFocus DesktopSize 1x1
The rest comes from the standard Debian configuration file: /usr/share/fvwm/default-config/config
So I think that means MouseFocus should not be an issue. RaiseTransient however seems to be controlled by StackTransientParent which the Debian configuration file sets as follows:
# Transient Windows (such as open file windows) Style * DecorateTransient, StackTransientParent Style * !FPGrabFocusTransient, FPReleaseFocusTransient
What setting do you recommend?
Hmm, I just realized I proscribed contradictory settings... I guess there's some reason other than mouse-focus mode why the user32:msg window doesn't activate. But the solution should be the same regardless.
Anyway, with regard to user32:win, I would either set a different focus mode, or add
Style * DontStackTransientParent
to override the previous setting.
Thanks!