maemo.org Bugzilla – Bug 3828
Act like a standard task navigator (don't rely on StartupWMClass)
Last modified: 2010-03-11 17:37:46 UTC
You need to
before you can comment on or make changes to this bug.
All Maemo versions up to the latest Diablo release
STEPS TO REPRODUCE THE PROBLEM:
Write an application that has a different StartupWMClass than the binary name
or (even worse!) the "StartupWMClass=" property in the .desktop file.
Alternatively, just write an SDL application and always have this problem!
I don't need to specify "StartupWMClass=" in the .desktop file and all windows
appear in the task navigator, like on a standard GNOME/KDE/XFCE Desktop.
The window does not appear in the task navigator. Switching away from the
window makes it disappear and no way to make it re-appear, with the program
still running (!!!!)
EXTRA SOFTWARE INSTALLED:
This section in the Wiki describes "Adding support for the Task Navigator". In
an ideal world, we would not need to do this. Other task navigators/window
managers work fine without these "hacks":
TN implementations (already in 770) have been tightly bound to the concept of
Desktop file objects (which contain translated app names, D-BUS services names,
icons etc), windows are just mapped to these (using WMCLASS property).
Changing this will require major changes i.e. this will not happen in Diablo,
but hopefully in Fremantle.
Note: NB#87419 is about being able to manage windows that don't have their
WMClass properly set. Even with that fixed, correct WMClass would still be
needed for single instance launching.
As a comment aside, this report is listed at
Still valid in Fremantle, but very low priority.
Is this really still an issue on Maemo 5? AFAIK the first window that gets
mapped after the application icon has been clicked replaces the "loading"
window, so as far as I'm concerned the bug has been fixed in Fremantle at least
since the Summit image.
(This was an issue for Diablo, but in Fremantle, the task navigator seems to
show all toplevel windows, including SDL apps.)
As far as I'm concerned, this bug can be closed as FiF.
What about Desktop stuff that e.g. uses splash screens / startup progress
windows which go away once the real program window comes up? Do those work