[maemo-developers] Integration with hildon desktop

[From: Eero Tamminen]

Hi,

ext Jeffrey Barish wrote:
>> ext Jeffrey Barish wrote:
>>> I don't specify the WM_CLASS in the .desktop file because the application
>>> whose .desktop I stole doesn't specify it.  I tried previously putting
>>> StartupWMClass in the .desktop file, but it had no effect.  In any case,
>>> xprop reports that the WM_CLASS is the main Python module (not binary) in
>>> my package.
>> Well, WM Class in .desktop file and in the application window property
>> needs to match for things to work properly.
> 
> With all due respect, that assertion does not seem to be true.  As I said, I 
> started with a .desktop that worked.  That is, the application shows the 
> correct icons both in the menu and the navigator bar.  It is only when I 
> modified the .desktop by having it start my program instead of the 
> application for which it was designed that the icon in the navigator bar 
> reverted to the default.  The .desktop file did not have a StartupWMClass 
> specification when it worked, so I did not put one in (although I had 
> previously tried it, without effect).  The WM Class specifications seem to 
> match anyway.

Maybe Task Navigator assumes the Gtk default i.e. the basename of
.desktop file Exec field (or D-BUS service name) contents.

If the WM Class that Task Navigator expects (which can be set from
the .desktop file) doesn't match what the application window has,
window doesn't get matched to the .desktop file and therefore anything
else you have specified there (icon etc) isn't associated with the
window.

Have you tried set the StartupWMClass in .desktop file to same string
as what your application window WM_CLASS property has?


	- Eero