'Open with' popup menu position

[admin]

This post delete itself in 10 minutes...

.

lecker!

[j_c_hallgren]

If I don't I get loads of mails and posts bombarding me about why I don't stick to the standard. I'm just fed up with this. Yes, in a way I gave up to the trolls. But I just have no capacity to deal with these loads of, uhm, fascinating user feedback.

Did you really think that you'd get complaints about showing just a bit more info to the user? Ok, so the standard is to hide half the name...I may be totally wrong here but seriously doubt that making the entire name visible would cause problems for anyone...in fact, it's my belief that this "standard" is wrong and anything that can be done to improve on it should be applauded!

The only justification I can see to hide part of name is to maybe "better" indicate which file name is being opened, but come on, it's marked as selected...do we really think it'll open another one?

So I'm glad you decided to reconsider this...and if you get complaints here, we''l just point them to this thread!

[admin]

If I don't I get loads of mails and posts bombarding me about why I don't stick to the standard. I'm just fed up with this. Yes, in a way I gave up to the trolls. But I just have no capacity to deal with these loads of, uhm, fascinating user feedback.

Did you really think that you'd get complaints about showing just a bit more info to the user? Ok, so the standard is to hide half the name...I may be totally wrong here but seriously doubt that making the entire name visible would cause problems for anyone...in fact, it's my belief that this "standard" is wrong and anything that can be done to improve on it should be applauded!

The only justification I can see to hide part of name is to maybe "better" indicate which file name is being opened, but come on, it's marked as selected...do we really think it'll open another one?

So I'm glad you decided to reconsider this...and if you get complaints here, we''l just point them to this thread!

Well, usually I know what file I'm ging to open before I click the open button. So I don't need any visual hints after the click. But for those of you with ultra-short memories the next version will remind you of which file you just wanted to open.

[Stefan]

v8.30.0017 - 2009-09-12 18:42
+[...]
* Tree, Catalog, List: Default context menu position now shifted a
bit to the right and down to enable reading at least part of the
captions of the selected items.

Works fine for me, thanks.

Could and shouldn't this work for script pop-ups too?

If script is launched by mouse click show pop-up at pointer pos
ElseIf item selected show pop-up at selected item
Else show pop-up at center of screen

[j_c_hallgren]

Well, usually I know what file I'm ging to open before I click the open button. So I don't need any visual hints after the click. But for those of you with ultra-short memories the next version will remind you of which file you just wanted to open.

Yes, I do like the revisions!

It's not so much a reminder as the ability to visually confirm as last chance once more that you're on the desired file before going through overhead of opening it.

[admin]

v8.30.0017 - 2009-09-12 18:42
+[...]
* Tree, Catalog, List: Default context menu position now shifted a
bit to the right and down to enable reading at least part of the
captions of the selected items.

Works fine for me, thanks.

Could and shouldn't this work for script pop-ups too?

If script is launched by mouse click show pop-up at pointer pos
ElseIf item selected show pop-up at selected item
Else show pop-up at center of screen

Not every script is on the selected files...

[Gandolf]

...The current position is Windows standard exactly.

Menu click triggered popups must always popup at mouse cursor. It's the law.

No it's not.

In at least three file managers (and many other applications) that I use the context menu opens at the point of focus and not at the mouse pointer. I have an auto-park facility that places the mouse off screen if not used for a period of time, so I very quickly know where the context menu opens.

It's these sort of small irritations that make or break an applications ease of use.

Never ever saw this and it would be totally irritating. Where have you seen this?

(Just to be sure: I'm talking about clicking a main menu item which then opens a popup menu.)

Apologies Don for the confusion.
I should have made it clear that I was referring to Keyboard operation and not mouse click.
I read your remark "The current position is Windows standard exactly." to imply that it was standard for the pop-up position to be at the mouse pointer, regardless of how the pop-up was initiated.

Because I have so much work on at the moment I have only just found time to look at this thread. Since I obviously can't concentrate fully on the forum, I think I'll keep quiet for a few months.

[Stefan]

v8.30.0017 - 2009-09-12 18:42
+[...]
* Tree, Catalog, List: Default context menu position now shifted a
bit to the right and down to enable reading at least part of the
captions of the selected items.

Works fine for me, thanks.

Could and shouldn't this work for script pop-ups too?

If script is launched by mouse click show pop-up at pointer pos
ElseIf item selected show pop-up at selected item
Else show pop-up at center of screen

Not every script is on the selected files...

>Not every script is on the selected files...
That's why i suggest an decision how the pop-up appears -- regarding how the script was triggered

[admin]

v8.30.0017 - 2009-09-12 18:42
+[...]
* Tree, Catalog, List: Default context menu position now shifted a
bit to the right and down to enable reading at least part of the
captions of the selected items.

Works fine for me, thanks.

Could and shouldn't this work for script pop-ups too?

If script is launched by mouse click show pop-up at pointer pos
ElseIf item selected show pop-up at selected item
Else show pop-up at center of screen

Not every script is on the selected files...

>Not every script is on the selected files...
That's why i suggest an decision how the pop-up appears -- regarding how the script was triggered

Your logic does not take into account the content of the script. Why should a menu offering different locations to goto popup at the selected files?

[admin]

Because I have so much work on at the moment I have only just found time to look at this thread. Since I obviously can't concentrate fully on the forum, I think I'll keep quiet for a few months.

A touch too extreme for my taste. Make it a few weeks.

[Stefan]

v8.30.0017 - 2009-09-12 18:42
+[...]
* Tree, Catalog, List: Default context menu position now shifted a
bit to the right and down to enable reading at least part of the
captions of the selected items.

Works fine for me, thanks.

Could and shouldn't this work for script pop-ups too?

If script is launched by mouse click show pop-up at pointer pos
ElseIf item selected show pop-up at selected item
Else show pop-up at center of screen

Not every script is on the selected files...

>Not every script is on the selected files...
That's why i suggest an decision how the pop-up appears -- regarding how the script was triggered

Your logic does not take into account the content of the script. Why should a menu offering different locations to goto popup at the selected files?

>Why should a menu offering different locations to goto popup at the selected files?
Sorry, I think i didn't get you.

The main thing i want to say is:
i dislike it if an script-dialog, IF launched by an key-press, appears at the cursor position.

Because the cursor is somewhere else, and so the dialog appears far on the side of my screen.

So i try to discuss if this script-pop-up appearing could be related how the script is executed.

- IF launched by shortcut THEN
------ IF there is an selection THEN position pop-up there at that selection
------ ELSE pop-up at center of screen
- ELSE (launched by mouse click) THEN let it appear at cursor pos

Changes that i miss smtg? Or no one others have an issue with this?



Arrg! , now i get you!;
>Why should a menu --offering different locations to goto--- popup at the selected files?
O.K. that's an point! .... stay tuned.

[admin]

Arrg! , now i get you!;
>Why should a menu --offering different locations to goto--- popup at the selected files?
O.K. that's an point! .... stay tuned.

Yes, I admit I had to read my own sentence 2 times to understand it!

BTW, there's a tweak called PopupMenusAtSelection ... could be interesting for you.

[Stefan]

BTW, there's a tweak called PopupMenusAtSelection ... could be interesting for you.

http://88.191.26.34/XYwiki/index.php/IN ... _Selection

Indeed it is ... but not for this issue.


"PopupMenusAtSelection=1" ==> It's pop-up at upper left corner
This tweak is enabled by default, but didn't work for this script-pop-up's i am talking about. (what is fine!)


"PopupMenusAtSelection=0" ==> It's pop-up at mouse pointer
But PopupMenusAtSelection didn't open the pop-up at an selection but at mouse pointer?!? (I tested this with Ctrl+H and Ctrl+Backspace)
(i mean "...AtSelection" is irritating me)

BTW:
I disable this tweak now because i always disliked it when the menu appears in the upper left corner, "far" away from my view.
I test now how this setting will work for me. So thanks anyway for this tip.
It would be nice if there where "PopupMenusAtSelection=2" => center pop-up to screen



Something like this tweak could be used for pop-up's from scripts too.
PopupScriptsAtSelection=0|1|2 ==> 0=always at mouse pointer as it is now / 1=pop-up at upper left corner(bad) / 2=center screen
So this would not be related to how the script was launched, but an general tweak how the script pop-up's appears.
Don't know right now if this will be ok for scripts relating to selections.
Maybe you want to add an new script command ---"AppearAt="--- for using inside the scripts too.
Or PopupScriptsAtSelection=0|1|2|3 ==> 3=at selection, don't matter if this script is related to the selection, but the selection is "in the current view", so it's O.K.

What do others think about this?

[admin]

Hmmm, now that kinook is gone (who started all this mess ) I could simply go back to the original state.

Indeed my recent changes went into the wrong direction (and jacky was right once again): The iPopupMenusAtSelection tweak (default = 1, you are right, Stefan) would only come to effect when the function was triggered by keyboard, so
IF ByKey AND iPopupMenusAtSelection = 1 THEN popup at selection

Yes, "at selection" is not an ideal term... "at/in context" would maybe better for a context menu. Too late.

Your other 0/1/2/3 idea is ok, and would probably best be handled under CEA.