Re: Double-click on application in wmdock does not launch the application if one instance is already running
On Monday 2015-06-22 21:55:55 Charles Philip Chan wrote: On 22 Jun 2015, djosip+n...@linuxpages.net wrote: Yes but if you select Shared application icon check box in the window attributes then the double click would start another instance of the application. This is how it worked up until and including 0.95.3. Doesn't happen here. I use Shared application icon all the time and double clicking does not launch a new instant. Sorry, my mistake. Its No application icon option, not Shared application icon. I have just retested it. Windowmaker up until and including 0.95.3 would allow subsequent double clicks on the docked appicon to start new instances of the application which was probably incorrect from the windowmaker design (look and feel) perspective but some people learned to use that feature. I have used Window Maker since the beginning and have never seen this. I have tested it with 0.80.2, windowmaker-0.95.3 and windowmaker-0.95.4. I have even used got bisect to find which patch changed the behavior. So the behavior I am reporting does exist, I have just mistakenly referred to Shared application icon instead of No application icon. You can test it yourself if you are running 0.95.3 or older. -- Josip Deanovic -- To unsubscribe, send mail to wmaker-dev-unsubscr...@lists.windowmaker.org.
Re: Double-click on application in wmdock does not launch the application if one instance is already running
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 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? Regards, BALATON Zoltan -- To unsubscribe, send mail to wmaker-dev-unsubscr...@lists.windowmaker.org.
Re: Double-click on application in wmdock does not launch the application if one instance is already running
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. :04 04 7c58877ad5af211acaddac5288848c2ade7b04cb 33d52affb385d22fbf04ebad3c628b714008785d M src -- Josip Deanovic -- To unsubscribe, send mail to wmaker-dev-unsubscr...@lists.windowmaker.org.
Re: Double-click on application in wmdock does not launch the application if one instance is already running
Quoting message written on Sunday 2015-06-21 21:36:27: On 21 Jun 2015, djosip+n...@linuxpages.net wrote: But it worked in 0.95.3 and I am inclined to believe that author wanted it that way rather than the doubleclick was implemented by mistake. If it actually was a mistake it is still something users saw as a feature. Isn't double clicking on the docked appicon of a running app suppose to raise that app to the front? Charles Yes but if you select Shared application icon check box in the window attributes then the double click would start another instance of the application. This is how it worked up until and including 0.95.3. After thoroughly testing the behavior of the current version I have found that Windowmaker currently works like this (please read my conclusion on the end of the message): Without Shared application icon selected in the window attributes window: - every instance of an application creates its own appicon - double click on some appicon would bring up and focus its application instance - ctrl + double click on any appicon would start a new instance of the application and the application would get its own appicon - right click - Launch from the appicon menu would act exactly the same as the ctrl + double click on the appicon - docked appicon acts a bit differently, double click, ctrl + double click and right click - Launch in the docked appicon menu would all start a new instance of the application but without creating an appicon. - subsequent double click on the docked appicon would not start a new instance of the application but would bring up and focus the window of the instance which has been created through the docked appicon - subsequent ctrl + double click or right click - Launch in the docked appicon menu would both start a new instances of the application but now they would have their own appicons created (this is both confusing and nonintuitive) - double click on the docked appicon would still bring up and focus only the window of the first instance of the application created through the docked appicon. With Shared application icon selected in the window attributes window: - only the first instance of the application creates the appicon - double click on the appicon would bring up and focus all of the windows of all instances of the application (of course only one of them get focused) - ctrl + double click on the appicon would start a new instance of the application and the application would use the same appicon (the instances are sharing the appicon) - right click - Launch from the appicon menu would act exactly the same as the ctrl + double click on the appicon - docked appicon acts a bit differently, double click, ctrl + double click and right click - Launch in the docked appicon menu would all start a new instance of the application but without creating an appicon - subsequent double click would not start a new instance of the application but would bring up and focus windows of all the application instances (of course only one window get focused) - subsequent ctrl + double click or right click - Launch in the docked appicon menu would both start new instances of the application but now they would not create their own appicons as in the first example because they are sharing the same appicon and that appicon is docked in the wmdock. - double click on the docked appicon would bring up and focus all the windows that belongs to any instance of the application (of course only one window gets focused) My conclusion here is that the docked appicon still acts as an appicon which is not intuitive but its probably correct from the windowmaker design (look and feel) perspective. Windowmaker up until and including 0.95.3 would allow subsequent double clicks on the docked appicon to start new instances of the application which was probably incorrect from the windowmaker design (look and feel) perspective but some people learned to use that feature. I am now aware that Windowmaker is actually working correctly and I cannot any longer insist on putting the double click feature back into the current version as this IMHO would be wrong thing to do. Instead, I would like to propose a new option under the Application Specific options, in the application attributes winow which would: - make docked appicon behave more like an launcher for the application instead of the application's instance appicon - allow double click and subsequent double clicks on the docked appicon to launch new instances of the application Users would then be able to drag an appicon to the dock and configure the window attributes in a way that the docked appicon doesn't ack as a docked appicon but as a launcher which would be much more intuitive taking into account the year we live in. :-) -- Josip Deanovic -- To unsubscribe, send mail to
Re: Double-click on application in wmdock does not launch the application if one instance is already running
Quoting message written on Sunday 2015-06-21 20:30:46: Quoting message written by Christophe on Sunday 2015-06-21 20:12:23: 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? But it worked in 0.95.3 and I am inclined to believe that author wanted it that way rather than the doubleclick was implemented by mistake. If it actually was a mistake it is still something users saw as a feature. In the meantime some users (not me because I am not using wmdock to start applications) became dependent on that feature and even chose to stick with the 0.95.3 because of it. I know how they feel since I used 0.80.2 for years because 0.9x version changed a way things are done (these have been fixed in the meantime and I am very grateful to the developers and maintainers for this). Since I don't like to see losing perfectly valid features with new versions of WindowMaker I have started this thread some time ago hoping that this feature (even if it is not documented it is still feature) could find its way back into windowmaker. I'll reply here to myself... In the meantime I have tested the feature thoroughly and I have somewhat changed my mind about it. Please check my response to the message sent by Charles Philip Chan. -- Josip Deanovic -- To unsubscribe, send mail to wmaker-dev-unsubscr...@lists.windowmaker.org.
Re: Double-click on application in wmdock does not launch the application if one instance is already running
Quoting message written on Monday 2015-06-22 07:48:58: I'd like to chime in with following notes and queries: 1) Ctrl+DblClick is rather weird-looking feature, way out of what's commonly expected in 2015. Not a good usability, too. One time you open the item by a single-click, and in another context (suddenly) you have to use something completely different? Your penguin may explode. I just checked -- yes, even with 'single click activation' you still have to use DblClick with Ctrl. That's why I generally open instances off the popup menu and shun Dock/Clip completely -- the menu functions in an expected manner. 2) How problematic would it be to add _additional_ Click/DblClick for _indiscriminate_ opening of an instance? 2.1) Or add it as an alternative? 2.2) Without breaking the things for guys used to Ctrl+DblClick behaviour, too, of course. Hi Yury, I have just thoroughly checked the feature. Please check my response to message sent by Charles Philip Chan. In short, the docked appicon is still an appicon and it acts as it has never been docked. I suppose this is the correct behavior not matter how unintuitive it might look to us. There is a huge possibility that some people rely on this. That's why I have proposed (similar to your idea) to add another option in the window attributes window which would (not by default) change the behavior of the docked appicon in order to make it possible to use docked appicon in more intuitive way. Subsequent double clicks on the docked appicons would also be much easier to use on tablets as you wouldn't have to open a menu to launch another instance of the application. Not to mention that you usually can't combine CTRL and double click on touch display which are these days more and more common. -- Josip Deanovic -- To unsubscribe, send mail to wmaker-dev-unsubscr...@lists.windowmaker.org.
Re: Double-click on application in wmdock does not launch the application if one instance is already running
On Mon, 22 Jun 2015, Josip Deanovic wrote: My conclusion here is that the docked appicon still acts as an appicon which is not intuitive but its probably correct from the windowmaker design (look and feel) perspective. In my opinion it is more intuitive than having a docked appicon behave differrently. The dock is really just a place to attach appicons to, they are still appicons. This is how it was working in *step and how it still works on OS X. Windowmaker up until and including 0.95.3 would allow subsequent double clicks on the docked appicon to start new instances of the application which was probably incorrect from the windowmaker design (look and feel) perspective but some people learned to use that feature. I've never seen this behaviour but maybe I've skipped the buggy versions that had this feature or used settings where this didn't happen. Double click raised app windows and Ctrl+DblClick started another instance whenever I've tried. The ability to use Ctrl+DblClick on undocked appicons was added recently, previously it only worked on the dock/clip. Instead, I would like to propose a new option under the Application Specific options, in the application attributes winow which would: - make docked appicon behave more like an launcher for the application instead of the application's instance appicon - allow double click and subsequent double clicks on the docked appicon to launch new instances of the application Users would then be able to drag an appicon to the dock and configure the window attributes in a way that the docked appicon doesn't ack as a docked appicon but as a launcher which would be much more intuitive taking into account the year we live in. :-) Window attributes are app specific. This setting seems to be a dock/clip option so maybe it should be a pref setting for dock/clip instead. A window attribute does not make much sense here unless you want it selectively for different apps, but that's really bad ergonomics as that would be very confusing if icons for different apps would behave differently when docked. So this looks more like a dock feature to me to have click on running appicon start new instance more like a launcher. Regards, BALATON Zoltan -- To unsubscribe, send mail to wmaker-dev-unsubscr...@lists.windowmaker.org.
Re: Double-click on application in wmdock does not launch the application if one instance is already running
On Monday 2015-06-22 15:06:36 BALATON Zoltan wrote: On Mon, 22 Jun 2015, Josip Deanovic wrote: Windowmaker up until and including 0.95.3 would allow subsequent double clicks on the docked appicon to start new instances of the application which was probably incorrect from the windowmaker design (look and feel) perspective but some people learned to use that feature. I've never seen this behaviour but maybe I've skipped the buggy versions that had this feature or used settings where this didn't happen. Double click raised app windows and Ctrl+DblClick started another instance whenever I've tried. The ability to use Ctrl+DblClick on undocked appicons was added recently, previously it only worked on the dock/clip. Yes, you would have to set the Shared application icon option in the application attributes window. Instead, I would like to propose a new option under the Application Specific options, in the application attributes winow which would: - make docked appicon behave more like an launcher for the application instead of the application's instance appicon - allow double click and subsequent double clicks on the docked appicon to launch new instances of the application Users would then be able to drag an appicon to the dock and configure the window attributes in a way that the docked appicon doesn't ack as a docked appicon but as a launcher which would be much more intuitive taking into account the year we live in. :-) Window attributes are app specific. This setting seems to be a dock/clip option so maybe it should be a pref setting for dock/clip instead. A window attribute does not make much sense here unless you want it selectively for different apps, but that's really bad ergonomics as that would be very confusing if icons for different apps would behave differently when docked. So this looks more like a dock feature to me to have click on running appicon start new instance more like a launcher. I have suggested application attributes window because there are already Shared application icon and No application icon options and they both allow you to configure some applications to act different then the others. So it seems to be logical place for such option if its going to be added in the future. -- Josip Deanovic -- To unsubscribe, send mail to wmaker-dev-unsubscr...@lists.windowmaker.org.
Re: Double-click on application in wmdock does not launch the application if one instance is already running
On Monday 2015-06-22 15:41:51 Yury Tarasievich wrote: I quite agree and would only amend this by using turn of phrase double OR single clicks (w/r to the 'Single click activation' configuration setting). Well, can YOU implement this? :) I surely would but my programming skills are rusty and I am always short with time. I got some spare time last few days and this is why I became so active on the list lately. -- Josip Deanovic -- To unsubscribe, send mail to wmaker-dev-unsubscr...@lists.windowmaker.org.
Re: Double-click on application in wmdock does not launch the application if one instance is already running
I'd like to chime in with following notes and queries: 1) Ctrl+DblClick is rather weird-looking feature, way out of what's commonly expected in 2015. Not a good usability, too. One time you open the item by a single-click, and in another context (suddenly) you have to use something completely different? Your penguin may explode. I just checked -- yes, even with 'single click activation' you still have to use DblClick with Ctrl. That's why I generally open instances off the popup menu and shun Dock/Clip completely -- the menu functions in an expected manner. 2) How problematic would it be to add _additional_ Click/DblClick for _indiscriminate_ opening of an instance? 2.1) Or add it as an alternative? 2.2) Without breaking the things for guys used to Ctrl+DblClick behaviour, too, of course. -Yury On 06/21/2015 09:30 PM, Josip Deanovic wrote: Quoting message written on Sunday 2015-06-21 20:12:23: ... 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? But it worked in 0.95.3 and I am inclined to believe that author wanted it that way rather than the doubleclick was implemented by mistake. If it actually was a mistake it is still something users saw as a feature. ... -- To unsubscribe, send mail to wmaker-dev-unsubscr...@lists.windowmaker.org.
Re: Double-click on application in wmdock does not launch the application if one instance is already running
- 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. :04 04 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.
Re: Double-click on application in wmdock does not launch the application if one instance is already running
Quoting message written on Sunday 2015-06-21 20:12:23: 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? But it worked in 0.95.3 and I am inclined to believe that author wanted it that way rather than the doubleclick was implemented by mistake. If it actually was a mistake it is still something users saw as a feature. In the meantime some users (not me because I am not using wmdock to start applications) became dependent on that feature and even chose to stick with the 0.95.3 because of it. I know how they feel since I used 0.80.2 for years because 0.9x version changed a way things are done (these have been fixed in the meantime and I am very grateful to the developers and maintainers for this). Since I don't like to see losing perfectly valid features with new versions of WindowMaker I have started this thread some time ago hoping that this feature (even if it is not documented it is still feature) could find its way back into windowmaker. -- Josip Deanovic -- To unsubscribe, send mail to wmaker-dev-unsubscr...@lists.windowmaker.org.
Re: Double-click on application in wmdock does not launch the application if one instance is already running
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. :04 04 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. -- Josip Deanovic -- To unsubscribe, send mail to wmaker-dev-unsubscr...@lists.windowmaker.org.
Re: Double-click on application in wmdock does not launch the application if one instance is already running
Quoting message written on Monday 2014-06-09 08:39:59 by Yury: I don't understand Josip's problem. Would someone clarify? The more-than-one-instance-unlaunchable-by-simple-action icons in Dock are there since ever. I definitely remember those in 0.92? (what was that stale version before Carlos took over?). And I think I can recall my initial confusion with 0.80? (well before Y2K). However, the more-than-one-instance-unlaunchable-by-simple-action icons in Dock are not intuitive, indeed, and not practical, too -- in this Josip's quite right. I use single-click-activation, still, having to reach for the CTRL is a source of irritation (albeit very minor). And I had to stumble upon the CTRL-click combination, too, after long using right click\Launch. Yury, it looks to me that you understand the problem quite well and the problem is: starting from 0.95.4 if you have dragged some app icon to the wmdock you would need to use CTRL + double click or CTRL + single click (in case you are using the SingleClickLaunch = YES option) to launch additional instances of the application represented by the app icon in the wmdock. Before 0.95.4 in the case described above CTRL key was not required. The change of this long standing behavior is the problem although it's not mine own problem since I don't use that particular feature. A friend of mine pointed it to me and I am trying to see if it's possible to convince developers to change that particular behavior as it were before 0.95.4. I am inclined to believe to believe that if there is a one person who suffers from some particular change there must be more. P.S. Many things regarding different behavior have changed with 0.9x. Unfortunately when I have tried it back then (I believe it was 2007) I had no time to write complaints and from my point of view back then it looked completely /fucked up/ so I decided to stick with 0.80.2 which worked perfectly well for me until few months back when I had to use multiple monitors and xinerama. I have decided to actively communicate with the developers hoping to either make them change few things the way they worked in previous releases (e.g. 0.80.2) or to make some quick and dirty patches myself as some of the bugs were a real show-stoppers for me. I succeed in my goal and almost all of the discrepancies between 0.80.2 and 0.95.5 I have noticed (or at least those that were particularly important to me) are now fixed or in line if you don't see the word fixed as appropriate here. :-) Regards -- Josip Deanovic -- To unsubscribe, send mail to wmaker-dev-unsubscr...@lists.windowmaker.org.
Re: Double-click on application in wmdock does not launch the application if one instance is already running
Quoth Yury Tarasievich, I had to stumble upon the CTRL-click combination, too, after long using right click\Launch. This is purely an aside because I entirely agree that changes to the user experience need careful consideration but you can also Launch from the window menu and, consequently, from a shortcut. -- To unsubscribe, send mail to wmaker-dev-unsubscr...@lists.windowmaker.org.
Re: Double-click on application in wmdock does not launch the application if one instance is already running
On 06/09/2014 09:53 AM, Josip Deanovic wrote: Quoting message written on Monday 2014-06-09 08:39:59 by Yury: Yury, it looks to me that you understand the problem quite well and the problem is: starting from 0.95.4 if you have dragged some app icon to the wmdock you would need to use CTRL + double click or CTRL + single click (in case you are using the SingleClickLaunch = YES option) to launch additional instances of the application represented by the app icon in the wmdock. Yes, yes, but hadn't this behaviour been there since ever? You mention the 0.95.4 as a milestone for this change, and I fairly well remember having to right click\Launch to get an additional instances of xterm as far back as 0.92/0.93, and I definitely remember this wmaker behaviour in 2009. So I'm wondering, might you be talking about something (subtly) different? Personally, I wouldn't mind the change of this behaviour, anyway. Right now the icon of the app already launched does nothing useful on single/double click and just takes up the screen space. That, or completely do without the icons' strips of any kind. Optionally, if you please. You can already switch off the Dock and the Clip, why not dispense with the icons completely? Yury -- To unsubscribe, send mail to wmaker-dev-unsubscr...@lists.windowmaker.org.
Re: Double-click on application in wmdock does not launch the application if one instance is already running
Quoting message written on Monday 2014-06-09 10:43:25 by Yury: Yes, yes, but hadn't this behaviour been there since ever? You mention the 0.95.4 as a milestone for this change, and I fairly well remember having to right click\Launch to get an additional instances of xterm as far back as 0.92/0.93, and I definitely remember this wmaker behaviour in 2009. So I'm wondering, might you be talking about something (subtly) different? I have tested 0.80.2, 0.95.3, 0.95.4 and 0.95.5. The behavior I have described has changed in 0.95.4. Maybe you are talking about app icon while I am referring to an app icon dragged into the wmdock? Personally, I wouldn't mind the change of this behaviour, anyway. Right now the icon of the app already launched does nothing useful on single/double click and just takes up the screen space. That, or completely do without the icons' strips of any kind. Optionally, if you please. You can already switch off the Dock and the Clip, why not dispense with the icons completely? I am disabling app icon for every single application I use so app icons don't really bother me because I see them only once per application (first time I launch an application). -- Josip Deanovic -- To unsubscribe, send mail to wmaker-dev-unsubscr...@lists.windowmaker.org.
Re: Double-click on application in wmdock does not launch the application if one instance is already running
And that's the subtle difference: I'm talking about the app icons auto-created by wmaker (I think I've used the dragged-to-dock icons like once or twice). That's the bug, of course, such difference shouldn't be there at all. On 06/09/2014 11:09 AM, Josip Deanovic wrote: ... That, or completely do without the icons' strips of any kind. Optionally, if you please. You can already switch off the Dock and the Clip, why not dispense with the icons completely? I am disabling app icon for every single application I use so app icons don't really bother me because I see them only once per application (first time I launch an application). Disabling every app icon as they appear doesn't look like a productive scenario to me. :) Yury -- To unsubscribe, send mail to wmaker-dev-unsubscr...@lists.windowmaker.org.
Re: Double-click on application in wmdock does not launch the application if one instance is already running
Quoting message written on Monday 2014-06-09 11:24:28 by Yury: Disabling every app icon as they appear doesn't look like a productive scenario to me. :) It doesn't but I can live with it as in my case it doesn't happen too often that I have to launch completely new application. -- Josip Deanovic -- To unsubscribe, send mail to wmaker-dev-unsubscr...@lists.windowmaker.org.
Re: Double-click on application in wmdock does not launch the application if one instance is already running
On Mon, 9 Jun 2014, Yury Tarasievich wrote: Personally, I wouldn't mind the change of this behaviour, anyway. Right now the icon of the app already launched does nothing useful on single/double click and just takes up the screen space. For launched apps it brings the app forward or acts as a place holder for the hidden app and unhides it (and also opens the app menu on right click where you can do actions like kill a frozen app, etc.). This is what all app icons do (regardless if docked or not). If some would launch additional instances instead that would be inconsistent. Launching with Ctrl is an additional function not clashing with the primary function. I think they cannot do both at the same time in a consistent way. You said when it worked the way you described it only launched additional instances of apps with some setting but behaved like other appicons for others if I got that correctly. This does not sound more consistent than the current behaviour to me so I don't think it should be a default option. That, or completely do without the icons' strips of any kind. Optionally, if you please. You can already switch off the Dock and the Clip, why not dispense with the icons completely? You can disable appicons per app already and you could add a default to disable it for all apps. (I did not try it but it may work.) In the window inspector (that you can bring up selecting Attributes in a Window menu) select Defaults for all windows in the Window Specification tab then No application icon on Applicaion Specific tab. If Window Maker becomes unusable as a result you can revert it by deleting the appropriate section from your GNUstep/Defaults/WMWindowAttributes. Regards, BALATON Zoltan -- To unsubscribe, send mail to wmaker-dev-unsubscr...@lists.windowmaker.org.
Re: Double-click on application in wmdock does not launch the application if one instance is already running
On Mon, 9 Jun 2014 at 10:09:47 +0200, Josip Deanovic wrote:
Quoting message written on Monday 2014-06-09 10:43:25 by Yury:
Yes, yes, but hadn't this behaviour been there
since ever? You mention the 0.95.4 as a
milestone for this change, and I fairly well
remember having to right click\Launch to get
an additional instances of xterm as far back as
0.92/0.93, and I definitely remember this wmaker
behaviour in 2009. So I'm wondering, might you
be talking about something (subtly) different?
I have tested 0.80.2, 0.95.3, 0.95.4 and 0.95.5.
The behavior I have described has changed in 0.95.4.
If some behavior changed that was not intentional and
we must fix it.
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.
I am disabling app icon for every single application
I use so app icons don't really bother me because I
see them only once per application (first time I launch
an application).
I guess you can have something like
* = {NoAppIcon = YES;};
in your WMWindowAttributes file to disable them entirely.
Perhaps we should have an 'expert' option in WPrefs doing this,
because I've seen this subject come up many times already.
--
To unsubscribe, send mail to wmaker-dev-unsubscr...@lists.windowmaker.org.
Re: Double-click on application in wmdock does not launch the application if one instance is already running
If I have no Dock and no Clip active, app icons are created anyway (couple of weeks old #next). These app icons are sort of skeleton ones -- they react only to double-click (although I have single-click activation in config), and their only reaction is self-highlighting. Ctrl-double-click works, however. :) And disabling the app icon individually for anything I might start does not seem a viable solution. It is good onloy for the likes of Firefox's flash container or LibreOffice java instance. Yury On 06/09/2014 12:47 PM, BALATON Zoltan wrote: ... You can disable appicons per app already and you could add a default to disable it for all apps. (I did not try it but it may work.) In the window inspector (that you can bring up selecting Attributes in a Window menu) select Defaults for all windows in the Window Specification tab then No application icon on Applicaion Specific tab. If Window Maker becomes unusable as a result you can revert it by deleting the appropriate section from your GNUstep/Defaults/WMWindowAttributes. -- To unsubscribe, send mail to wmaker-dev-unsubscr...@lists.windowmaker.org.
Re: Double-click on application in wmdock does not launch the application if one instance is already running
Quoting message written on Monday 2014-06-09 11:13:14 by Carlos R. Mafra:
If some behavior changed that was not intentional and
we must fix it.
I agree but sometimes I am not sure if something has been
changed intentionally to increase consistency.
For example, recently (last week) Windowmaker has returned
some of it's previous behavior regarding cycling shaded
windows. I am very happy because of that. :-)
However, when you cycle through windows (with switchpanel
disabled) and if you stop on the shaded window, the shaded
window will unshade.
This behavior is the same whether switchpanel is disabled
or not but in the 0.80.2 it wouldn't unshade, it would just
focus and rise.
So, what to do in the example such as this one? Is this
intentional behavior or not and which behavior looks more
logical? To unshade or not to unshade, it is a question now.
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.
Ok. I'll need some time to read the git documentation as I
don't know how to use it.
I guess you can have something like
* = {NoAppIcon = YES;};
in your WMWindowAttributes file to disable them entirely.
I know about that option but I chose not to use it. I like
to see the icon of the application I am launching for the
first time and then I simply either disable it for that
particular application or drag the app icon to wmdrawer.
Perhaps we should have an 'expert' option in WPrefs doing this,
because I've seen this subject come up many times already.
I have no opinion on the matter but I do agree that some kind
of warning should be set in the description of the option.
--
Josip Deanovic
--
To unsubscribe, send mail to wmaker-dev-unsubscr...@lists.windowmaker.org.
Re: Double-click on application in wmdock does not launch the application if one instance is already running
Quoting message written on Saturday 2014-06-07 03:34:27 by BALATON Zoltan: On Sat, 7 Jun 2014, Josip Deanovic wrote: I suggest restoration of the behavior from pre-0.95.4 version I don't mind either way (not using that option) but isn't double click with Ctrl pressed sufficient to launch another instance? Double click brings forward the running application and if it behaved differently for some applications it would be inconsistent. I prefer to see an app icon and an app icon added to a wmdock as two different things so they don't have to operate in the the same way. In fact it worked like this until recently (up until 0.95.4). Insisting on CTRL + double-click on app icons in the wmdock or app icons in the wmdock looks awfully unintuitive and it's not practical if you tend to start multiple instances of some applications in the wmdock very often (xterm for example). I don't use app icons in the wmdock (I like to bind FN or Win key to start my terminals) but since some people decided to downgrade back to 0.95.3 when they found that the behavior in 0.95.4 and 0.95.5 has changed, it gives us the answer to a question whether CTRL + double-click is enough or not. In short, people would rather chose to stick with old 0.95.3 version than use CTRL + double-click on the wmdocked app icon. As I said, I don't use that option either but since it was there up until 0.95.4 (even in 0.80.x versions and probably earlier versions) and since it's intuitive and practical, I would suggest to bring the described behavior back to Windowmaker. In addition to that, since internal wmdrawer support came after 0.95.4 in order to keep the consistency, app icons in the wmdrawer should be able to start additional instances when double-clicked. BTW, what is the meaning of the Shared application icon option in the Application Specific Attributes window? It's what it says, that multiple instances of one application will share a single icon. For example you can have a single icon for all terminal windows so you can hide them at once. (Actually on *step the icons belong to applications which can have multiple windows. So these windows all belong to a single application and thus icon. This can be emulated by the shared application icon when the windows are separate instances of an X application.) Thank you for the explanation. Kind regards -- Josip Deanovic -- To unsubscribe, send mail to wmaker-dev-unsubscr...@lists.windowmaker.org.
Re: Double-click on application in wmdock does not launch the application if one instance is already running
I don't understand Josip's problem. Would someone clarify? The more-than-one-instance-unlaunchable-by-simple-action icons in Dock are there since ever. I definitely remember those in 0.92? (what was that stale version before Carlos took over?). And I think I can recall my initial confusion with 0.80? (well before Y2K). However, the more-than-one-instance-unlaunchable-by-simple-action icons in Dock are not intuitive, indeed, and not practical, too -- in this Josip's quite right. I use single-click-activation, still, having to reach for the CTRL is a source of irritation (albeit very minor). And I had to stumble upon the CTRL-click combination, too, after long using right click\Launch. I have a different proposition, however. How about enabling Wmaker to work without creating those app/mini icons at all? I've been trying a similar setup for a while (no Dock, no Clip, miniwindows either enabled or disabled) and it MIGHT have its plusses, BUT some sort of icons is always created, messing the significant part of the screen space. Yury On 06/08/2014 11:58 PM, Josip Deanovic wrote: ... -- To unsubscribe, send mail to wmaker-dev-unsubscr...@lists.windowmaker.org.
Re: Double-click on application in wmdock does not launch the application if one instance is already running
On 06/07/2014 04:34 AM, BALATON Zoltan wrote: On Sat, 7 Jun 2014, Josip Deanovic wrote: docked application using double-click. I don't mind either way (not using that option) but isn't double click with Ctrl pressed And there is an option of launching with single click, so it's double/single click, really. I have it active on recent #next (0.95.5-something) and the Ctrl-click combination works on my system. Yury -- To unsubscribe, send mail to wmaker-dev-unsubscr...@lists.windowmaker.org.
Re: Double-click on application in wmdock does not launch the application if one instance is already running
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 wmaker-dev-unsubscr...@lists.windowmaker.org.
Re: Double-click on application in wmdock does not launch the application if one instance is already running
On Sat, 7 Jun 2014, Josip Deanovic wrote: 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 I don't mind either way (not using that option) but isn't double click with Ctrl pressed sufficient to launch another instance? Double click brings forward the running application and if it behaved differently for some applications it would be inconsistent. BTW, what is the meaning of the Shared application icon option in the Application Specific Attributes window? It's what it says, that multiple instances of one application will share a single icon. For example you can have a single icon for all terminal windows so you can hide them at once. (Actually on *step the icons belong to applications which can have multiple windows. So these windows all belong to a single application and thus icon. This can be emulated by the shared application icon when the windows are separate instances of an X application.) Regards, BALATON Zoltan -- To unsubscribe, send mail to wmaker-dev-unsubscr...@lists.windowmaker.org.
Double-click on application in wmdock does not launch the application if one instance is already running
Hello As said in the subject, double-click on an application in wmdock does not launch the application in case there is an instance of the application already running. As I heard from a friend of mine it used to work in 0.95.3 and previous versions of Windowmaker with Shared application icon check box turned on for a specific application that has been added to wmdock. With version 0.95.5 and version from current git repository it is not the case any more. It is possible to launch additional instance by using right-click and selecting Launch option but this really sucks. Is this behavior intentional? A friend of mine decided to downgrade to 0.95.3 until this is resolved. It seems that Windowmaker users constitute a class of users that really don't like unexpected changes. :-) -- Josip Deanovic -- To unsubscribe, send mail to wmaker-dev-unsubscr...@lists.windowmaker.org.
Re: Double-click on application in wmdock does not launch the application if one instance is already running
On Thu, 5 Jun 2014, Josip Deanovic wrote: As said in the subject, double-click on an application in wmdock does not launch the application in case there is an instance of the application already running. As I heard from a friend of mine it used to work in 0.95.3 and previous versions of Windowmaker with Shared application icon check box turned on for a specific application that has been added to wmdock. With version 0.95.5 and version from current git repository it is not the case any more. It is possible to launch additional instance by using right-click and selecting Launch option but this really sucks. Is this behavior intentional? 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. Regards, BALATON Zoltan -- To unsubscribe, send mail to wmaker-dev-unsubscr...@lists.windowmaker.org.
Re: Double-click on application in wmdock does not launch the application if one instance is already running
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. -- To unsubscribe, send mail to wmaker-dev-unsubscr...@lists.windowmaker.org.
