Quoting message written on Thursday 2014-06-05 18:14:29 by Iain Patterson:
> Quoth BALATON Zoltan,
>
> > I don't think it ever worked the way you describe or if it did it was
> > probably a bug. What used to work and should still work is starting
> > additional instances with Ctrl+double click. So I think this is
> > intentional and not a regression.
>
> Going from memory, since I don't use the dock and haven't built from
> any recent commits, starting a docked application wait()s for the
> process so if it runs in the foreground you can't launch another one
> except via one of the methods already discussed. I thought it had
> always been that way.
I have just tested Windowmaker 0.80.2, 0.95.3 and 0.95.4.
I have found that the described (mis)behavior first started to occur in
version 0.95.4.
In previous versions e.g. 0.80.2 up until 0.95.3 when an application
attributes are set with "NoAppIcon = Yes;" ("No application icon" option
in attributes window), it was possible to launch multiple instances of
the application from wmdock using double-click.
Starting with version 0.95.4 Windowmaker doesn't behave the same way
any more and it is not possible to execute multiple instances of a
docked application using double-click.
It is still possible to execute additional instances of the application
in the wmdock using right-click and then selecting "Launch" from the
menu but this is not practical at all in every day use.
I suggest restoration of the behavior from pre-0.95.4 version
BTW, what is the meaning of the "Shared application icon" option in the
Application Specific Attributes window?
I was convinced that it was meant to instruct Windowmaker to allow
multiple instances of the applications in the wmdock when double-click is
used on them.
--
Josip Deanovic
--
To unsubscribe, send mail to [email protected].
