Re: Double-click on application in wmdock does not launch the application if one instance is already running

[Josip Deanovic]

On Tuesday 2015-06-23 10:57:24 BALATON Zoltan wrote:
> On Tue, 23 Jun 2015, Josip Deanovic wrote:
> > Sorry, my mistake.
> > Its "No application icon" option, not "Shared application icon".
> > I have just retested it.
> 
> Ah, ok, that makes sense. If an app is set to not have an app icon it
> cannot be attached to the dock so when you start it the instance will
> not have an app icon so the docked one is not linked to the running
> instance. Hence clicking on it again may start a new instance. This is
> kind of consistent even if quite unintuitive.

I agree.

> > I have even used got bisect to find which patch changed the behavior.
> 
> Did you find the patch that changed it? Or is this behaviour still
> there?

Yes, check my message sent in this thread on 2014-06-14 00:06

I'll paste it here so that you don't have to look for it.

bc0700e016c67791d3e3eab855543d849f4ce786 is the first bad commit
commit bc0700e016c67791d3e3eab855543d849f4ce786
Author: Rodolfo García Peñas (kix) <k...@kix.es>
Date:   Mon Jun 18 11:15:19 2012 +0200
    
    Create WAppIcon always
    
    When the application is created, the WAppIcon now is created always,
    but it is only painted if the flag is not set.

    The icon initialization to NULL can be done now at 
app_icon_create_from_docks
    because it is always called.

:040000 040000 7c58877ad5af211acaddac5288848c2ade7b04cb 
33d52affb385d22fbf04ebad3c628b714008785d M      src


-- 
Josip Deanovic


--
To unsubscribe, send mail to wmaker-dev-unsubscr...@lists.windowmaker.org.