Bug 262 - Workrave always stealing user input in fvwm
Status:
RESOLVED FIXED
Component:
GUI :: gtkmm
Version:
1.2.2
Hardware:
PC Linux
Importance:
P2 normal
Target Milestone:
---
Assignee:
Rob Caelers
URL:
http://sourceforge.net/mailarchive/forum.php?thread_id=2883832&forum_id=12161
Depends on:
Blocks:
Reported:
Aug 2 2003 11:52:10 UTC
by:
Hugo Haas
Modified:
Aug 7 2003 14:16:35 UTC
| Id | Who | When | Size | Type |
|---|---|---|---|---|
| 17 | fvwm2rc causing trouble | |||
| Hugo Haas | Aug 4 2003 13:59:10 UTC | 8119 | text/plain | |
| Who | When | What | Removed | Added |
|---|---|---|---|---|
| Rob Caelers | Aug 3 2003 12:59:13 UTC | status | NEW | ASSIGNED |
| Rob Caelers | Aug 6 2003 13:54:33 UTC | component | Core :: UNIX | GUI :: gtkmm |
| Rob Caelers | Aug 7 2003 14:16:35 UTC | status | ASSIGNED | RESOLVED |
| resolution | FIXED |
Description
Hugo Haas Aug 2 2003 11:52:10 UTC
Hi. I am using fvwm 2.4.16. Whenever a Workrave popup window shows up, it steals the keyboard input. I tried enabling and disabling the "Block user input" option without any success. I am using SloppyFocus in my fvwm configuration. I tried setting GrabFocusTransientOff for Workrave, but it didn't change anything either. Regards, Hugo
Comment 1
Rob Caelers Aug 3 2003 12:59:13 UTC
Using the debian default fvwm configuration, I get the normal behaviour: The workrave windows (both warning and break window) do not get the focus and the focussed window stil gets all the keystrokes. I can image that if the break window appears on the location of the mousepointer, fvwm gives workrave's window the focus. I this the case? If not, could you attache you .fvwmrc to this bug?
Comment 2
Hugo Haas Aug 4 2003 13:59:10 UTC
Created attachment 17 fvwm2rc causing trouble
Comment 3
Hugo Haas Aug 4 2003 14:00:54 UTC
Indeed, the default fvwm configuration of Debian works fine. Yet, mine doesn't, and trying to tweak different settings (Workrave's style, SloppyFocus/MouseFocus, etc.) didn't change their interaction. Regards, Hugo
Comment 4
Rob Caelers Aug 6 2003 13:54:33 UTC
I fixed the problem. I'm keeping the bug open until we are sure this fix didn't break the windows version....