XYplorer Beta Club

jacky wrote:I'll repeat that a button next to the red "[KS] is alreay assigned to..." would be nice to jump there, so one doesn't have to search to locate a command/KS he wants to remove. (Or, simply a button to remove/replace that assignation with a new one?)

Also, when you say the location of that command, you seem to use [Category]/[Command] which lacks the submenu(s) it can be in, therefore makes it a bit hard to locate.
I mean, sure View/Random Order helps, but since we can't "jump" there it would be nice to have to full "access" name, eg. View/Current Tab/Sort By/Random Order

There we run into a space problem... "Jump" function is better.

jacky wrote:In Misc, you have "Cycle Focus". Could there be a "Move/Set Focus To List" command added there too? Because that one I could actually use

Let's open a new topic and collect some of those little macros that you folks would find useful, and then I add them in one bang.

jacky wrote:Lastly, I am not sure how the "Default" button works It doesn't seem to do anything... 2 KS for one command, clicking it does say/get which is the default (isn't it the first one on list?); and clicking it to add or after having added a new KS doesn't set the default either.

Misunderstanding: this button does just display the factory default KS. It does not set the displayed KS.

jacky wrote:Very lastly, instead of " ..." I would have used ", ..." to show there are more shortcuts, (strip the space/remove a dot if you wanna reduce used space as much as possible) only because it clearly has a separator, currently I find it quite "weird looking"... could even be confusing a bit IMO

Very good!

Not much productive to add just yet, but wanted to express how thrilled I am to see CKS under development. After 5 weeks offline, it was a wonderful surprise to return to -- my first act online was updating XY :)

Since the v5.80.0025 where CKS for edit menu was finished, pressing ctrl+N multiple times doesnt create many folders. now only one folder is created and asks to be renamed. this worked fine in the previous version v5.80.0022.
ditto ctrl+shift+N.

admin wrote:There we run into a space problem... "Jump" function is better.

"Jump" function is pretty cool Although just te be a pain I could say, maybe adding a little button, just a little arrow (like the usual XY orange arrow, pointing to the right) after "assign to:" could help the unaware user to find out about this, and also make it available for keyboard-only user?

Also, IMO when overwriting a KS a little confirmation popup would be a good thing.

admin wrote:Misunderstanding: this button does just display the factory default KS. It does not set the displayed KS.

Right, ok I got it now. Well then, maybe have a little text shown when there are no default KS, like where the red warning (for already assigned KS) is shown, have a "no default KS" displayed. I mean, or else one could wonder what does that button do, as clicking it (can) (seem to) do absolutely nothing...

admin wrote:

surrender wrote:This i think is inevitable,

Right-clicking on CKS toolbar button shows categories.

Done

I find this really useful, would that be possible for configuration too? I mean tabs such as General, Advanced ... dropping down on toolbar right-click?

allen wrote:Not much productive to add just yet, but wanted to express how thrilled I am to see CKS under development. After 5 weeks offline, it was a wonderful surprise to return to -- my first act online was updating XY

Hey allen, long time no see. Hope you're fine.

So, as you were bumping into CKS without warning: do you find it intuitive to use?

surrender wrote:Since the v5.80.0025 where CKS for edit menu was finished, pressing ctrl+N multiple times doesnt create many folders. now only one folder is created and asks to be renamed. this worked fine in the previous version v5.80.0022.
ditto ctrl+shift+N.

Okay, I enlarged the scope to Global. Now it works as before.

admin wrote:So, as you were bumping into CKS without warning: do you find it intuitive to use?

I've also not really tried to use it yet that much, so when I did now, I'm a bit puzzled by how best to handle this situation:
User (me) puts focus on "Press new key"...at that point, AFAIK, any key clicked will set that one as new value...ok, fine but suppose user did not intend to type something there? How is best (and obvious to new user) way to clear out that field? 1) Clicking "Default" gets the red warning msg in many cases...2) "Remove" clears out current assigned, which is undesired 3) Cancel exits entire CKS screen, also likely undesired...

Update: When I click "default" in above situation and then use Cancel, without Assign, the current key assigned is removed! Huh?

j_c_hallgren wrote:

admin wrote:So, as you were bumping into CKS without warning: do you find it intuitive to use?

I've also not really tried to use it yet that much, so when I did now, I'm a bit puzzled by how best to handle this situation:
User (me) puts focus on "Press new key"...at that point, AFAIK, any key clicked will set that one as new value...ok, fine but suppose user did not intend to type something there? How is best (and obvious to new user) way to clear out that field? 1) Clicking "Default" gets the red warning msg in many cases...2) "Remove" clears out current assigned, which is undesired 3) Cancel exits entire CKS screen, also likely undesired...

1) this is normal for all CKS interfaces Í know, 2) it is not necessary to clear this field, 3) you can clear it by pressing and releasing Ctrl or Shift or Alt.

admin wrote:1) this is normal for all CKS interfaces Í know, 2) it is not necessary to clear this field, 3) you can clear it by pressing and releasing Ctrl or Shift or Alt.

The one CKS I had used required you to type in the command, so to set "F6", you had to type "F" + "6"...

The "clear" keys could/should be added to "HINTS" so people like me would see it...

BTW, did you see my Update to prior post?

j_c_hallgren wrote:

admin wrote:1) this is normal for all CKS interfaces Í know, 2) it is not necessary to clear this field, 3) you can clear it by pressing and releasing Ctrl or Shift or Alt.

The one CKS I had used required you to type in the command, so to set "F6", you had to type "F" + "6"...

The "clear" keys could/should be added to "HINTS" so people like me would see it...

But why would you want to clear it?

j_c_hallgren wrote:User (me) puts focus on "Press new key"...at that point, AFAIK, any key clicked will set that one as new value...ok, fine but suppose user did not intend to type something there? How is best (and obvious to new user) way to clear out that field?

hmm.. what do you mean by "any key clicked will set that one as new value" exactly?
Because, whe you press say Ctrl+A then this comba appears on the text area here. That's right, but at this point it has NOT been added as KS for the selected command yet. So basically, you can just type something else, select another command, nothing has been made yet at that point.

Only when you press Enter or click on "Assign" will the KS be added/assigned, and then appear on the list of KS above.

BTW, IMO it's much better/faster not to leave the focus out of the comman list, since pressing key there will "add" them the the new shortcut textarea, and after that pressing Enter still without moving the focus will add/assign the KS!

I would suggest, though, Don, that after a KS is assigned you autoselect it on the KS list, that way if after pressing Enter one realize the KS is wrong, or it was assigned to the wrong command, pressing Del will "undo" it, removing the newly added KS.

I'm simply trying to address the situation where a user gets a value in the "new key" field and says: "OOPS! I didn't want that!"
And just wants to undo that keystroke(s)...that's what I mean by clearing it, and yes, it hasn't yet been locked in, but a user who wants to make 100% sure and is new to interface would then likely click on Hints, so having a msg there about using Shift/etc to 'clear' it would be helpful, IMO.

Update: Maybe if the "new key" is same as current, that would also 'clear' it?

jacky wrote:I would suggest, though, Don, that after a KS is assigned you autoselect it on the KS list, that way if after pressing Enter one realize the KS is wrong, or it was assigned to the wrong command, pressing Del will "undo" it, removing the newly added KS.

Goody, done.

jacky wrote:

admin wrote:There we run into a space problem... "Jump" function is better.

"Jump" function is pretty cool Although just te be a pain I could say, maybe adding a little button, just a little arrow (like the usual XY orange arrow, pointing to the right) after "assign to:" could help the unaware user to find out about this, and also make it available for keyboard-only user?

Also, IMO when overwriting a KS a little confirmation popup would be a good thing.

admin wrote:Misunderstanding: this button does just display the factory default KS. It does not set the displayed KS.

Right, ok I got it now. Well then, maybe have a little text shown when there are no default KS, like where the red warning (for already assigned KS) is shown, have a "no default KS" displayed. I mean, or else one could wonder what does that button do, as clicking it (can) (seem to) do absolutely nothing...

1) still thinking...
2) really? is the red warning not enough? i don't like clicking thru confirmations to much. I imagine you sometimes want to quickly redo a number of keys, and you know what you are doing... you don't want that safety belt.
3) better solution: enable the "Default" button only if there is a default key