Re: mb-applet-launcher and gtk app kill problem

Matthew Allum <[email protected]> Wed, 14 Dec 2005 08:50:23 +0000
Newsgroups gmane.comp.handhelds.matchbox
Message-ID <[email protected]>
Hi;

On Tue, 2005-12-13 at 13:03 -0500, Paul Fox wrote:
> hi --
> 
> i'm hoping this is a common problem, with an easy fix.
> 
> one of the apps i start and stop using mb-applet-launcher is
> the mapping program called RoadMap.
> 
> the mbdock.session line looks like:
>     mb-applet-launcher -k /usr/share/pixmaps/usa.xpm roadmap
> 
> this works fine, most of the time.  the app comes and goes on
> demand.
> 
> however, if the app has a modal dialog up, the launcher's kill operation
> has no effect.  the result is that i can easily get multiple copies
> of the app running at once.
> 
> roadmap will build as either a gtk or a gtk2 app, and the behavior
> is the same in either mode.
> 
> has anyone else seen this?  know of a workaround?

Basically I suspect it limitations of how mb-applet-launcher tracks
windows in its default way or perhaps related to;

http://bugzilla.openedhand.com/show_bug.cgi?id=22

As your running a GTK2 app, a potential fix is to add a .desktop file
for roadmap with the StartupNotify and SingleInstance keys set to true.
Then run mb-applet-launcher with the --desktop switch. You also will
need to make sure you build matchbox with startup notify support.
That *should* work.

I really need to rewrite mb-applet-launcher... Its quite old and crusty
nowadays.

  -- Matthew

--
To unsubscribe send a mail to [email protected]
--