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.
