----- Josip Deanovic <djosip+n...@linuxpages.net> a écrit : > Quoting message written on Saturday 2014-06-14 00:06:14: > > Quoting message written on Monday 2014-06-09 11:13:14 by Carlos R. > Mafra: > > > It would be great if you could 'git bisect' the issue to > > > a particular patch. That would speed up the fix greatly > > > since there is even a confusion about the issue itself. > > > > Hello, > > > > I am done with git bisect. Let me know if the following output > > helps: > > > > > > 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 > > > > > > > > Regards > > > Hi everyone > > Since we are not far away from the releasing of the Windowmaker 0.95.7 > I would like to remind everyone about the issue in this thread since > I can see that it has not been resolved in current "next" branch and > it would be nice to solve it before the 0.95.7.
Hi, On my side I can re-run a new instance of an application by doing "Ctrl+DblClick" which is an official feature. Do we really need to add an ugly hack to implement an unexpected side effect, which would be configured through an option that is totally unrelated to the behaviour controlled? -- To unsubscribe, send mail to wmaker-dev-unsubscr...@lists.windowmaker.org.
