sillysloft / fluxbox

Fluxbox Window Manager (Mirror)
http://fluxbox.org/news/
Other
0 stars 1 forks source link

KOrganizer always appears on current workspace #786

Open sillysloft opened 17 years ago

sillysloft commented 17 years ago

KOrganizer always appears on the current workspace instead of the remembered one (SVN-4983). The status of the items in the remember menu indicates that the window has been recognized successfully.

Sometimes it /takes/ me to the remembered workspace, most times it simply appears on the current workspace, and perhaps one out of a hundred times (read: very rarely) it works as expected.

Most other applications are fine, though file dialogs usually do not remember their dimensions and / or positions (i.e. firefox file dialog). Are there certain limitations to this feature or is it just a bug?

------------------------------------------ Fluxbox version: 1.0rc3-gentoo Compiled: Jul 11 2007 22:05:53 Compiler: GCC Compiler version: 4.1.2 (Gentoo 4.1.2)

Compiled options (- => disabled): -DEBUG EWMH GNOME IMLIB2 KDE NLS REMEMBER RENDER SHAPE SLIT TOOLBAR XFT XINERAMA XMB XPM

------------------------------------------

Reported by: hjudt

sillysloft commented 17 years ago

Logged In: YES user_id=1538990 Originator: NO

Transient windows (dialogs, usually) are ignored deliberately. It's usually what's wanted. I haven't looked into it, but the overwhelming odds in these circumstances are that KOrganizer is setting its window hints _after_ mapping the window. We can't do anything about that, except give them a patch and point them to the relevant standards (ICCCM 4.1.2.5). I'll look into this sometime this weekend.

Original comment by: mark-t

sillysloft commented 17 years ago

Logged In: YES user_id=1538990 Originator: NO

This is a KOrganizer bug. KOrganizer immediately sends an EWMH request to become the focused window, which is frankly none of their business. The varying behavior is a race condition (caused by KOrganizer's request) involving your followModel setting in the init file. You should report this to KOrganizer's bug system, which is probably bugs.kde.org .

Original comment by: mark-t

sillysloft commented 17 years ago

Original comment by: mark-t