XYplorer Beta Club

Quick File Preview is found in File menu and doesn't show a KS, and is defined in CKS as cmd #177, yet it seems to also be within CKS via Miscellaneous|Preview as cmd #1003 with default of F11, so are these in fact the same function or different?

I was a bit surprised to see that QFP via File didn't show a KS, yet I could invoke it via F11, so am just a tad confused...

It's not the same. On File you have Quick File View (Ctrl+Shift+Q), which always uses that window to show the content of a file.

Full Screen Preview (F11) is another feature that will preview in FS a picture. And when the selected file is not a picture, then Quick File View is used instead...

jacky wrote:On File you have Quick File View (Ctrl+Shift+Q),

Is that the default that I didn't see added because I've got a custom set of keys defined already? As in the "Shift+F8" thread as follows:

admin wrote:

graham wrote:Thanks -

The reason for asking is that when new default keys are announced then for existing users it seems to me that maybe the assignment should be made and if in conflict alert the user at the time.

Ok, stupid question but it is very easy to miss out on new features for users who update only occasionally.

Yeah, we had that discussion elsewhere recently. I decided it's not worth the effort, for two reasons:
(a) It's not that often that new KS are added.
(b) It's not that often that old users don't know how to handle this situation.

So this is another occurance of this issue, but for a different function...
BTW, since that thread had veered off the original, I chose to start this one.

j_c_hallgren wrote:

jacky wrote:On File you have Quick File View (Ctrl+Shift+Q),

Is that the default that I didn't see added because I've got a custom set of keys defined already?

Yes, that would be one of those new default KS you need to assign manually...

jacky wrote:Yes, that would be one of those new default KS you need to assign manually...

Me thinks that even though it doesn't happen that often, that there could be a slightly better way to handle this...but obviously with as little effort for Don as possible.

Maybe if there was a simple way to create a Cheat Sheet from the Defaults? Then one could use a compare to determine what's changed.

j_c_hallgren wrote:Maybe if there was a simple way to create a Cheat Sheet from the Defaults? Then one could use a compare to determine what's changed.

Well, it's really not that hard:

1. Open CKS
2. Options|Reset All Shortcuts
3. Options|Copy Cheat Sheet|[Choose your format]
4. Cancel

It's pretty much as easy as doing a cheat sheet of your own KS, which is done exactly the same way only minus step 2, of course!

Too bad that couldn't that be developed into a script that would then take those clipboard contents and save to file, then do same with user custom, and invoke an external compare...but I don't see any obvious way to perform those detailed options within CKS dialog.

j_c_hallgren wrote:Too bad that couldn't that be developed into a script that would then take those clipboard contents and save to file, then do same with user custom, and invoke an external compare...but I don't see any obvious way to perform those detailed options within CKS dialog.

uhhh, what's the purpose of all this? What's the problem that needs a solution?

admin wrote: uhhh, what's the purpose of all this? What's the problem that needs a solution?

Purpose/Problem: New functions that are added (or old functions that are changed) and thus new/chg KS that need to be merged/adapted into existing user CKS...granted that doing the actual merge may still need to be done manually by user, but having the differences available helps is locating the entries needed.

For instance, just because I may have customized only one KS, that blocks me from getting any new KS's added so I have to review each change log to see what's been modified, and if I'm behind, then there can be various ones to review and address.

It's not that big of an issue in scope of things, but when new features are added, having to manually adjust CKS can have an impact on usability, as shown by this thread plus the "Shift+F8" one.

P.S. And as there is no 'marker' on those KS that deviate from defaults, locating which ones have been adjusted by user is also not as easy as it might be.

j_c_hallgren wrote:

admin wrote: uhhh, what's the purpose of all this? What's the problem that needs a solution?

Purpose/Problem: New functions that are added (or old functions that are changed) and thus new/chg KS that need to be merged/adapted into existing user CKS...

But why? I don't see that need. To the opposite! No key mappings are auto-changed when upgrading and therefore there is no need to do anything -- which is good! Sure, if you want to change your settings, you got to do something -- that's the price of customizability. But you do not need to do anything.

I'm certainly not wanting to argue this, but suppose a user only cares to install "official releases"...and has chosen to create just one or two CKS for function(s) that don't have one...when that user upgrades to next vers, all new KS that would have been added automatically are not due to those very minor customizations, and user then has to either make all those additions (or changes) manually -or- remember/locate which ones he'd tweaked, reset to defaults, and then reapply custom.

Neither method is as user friendly as it might be, IMHO, and if there were a way to isolate user adjustments so they could more easily be located/applied, this would help not only me but the "average joe user", I believe.

Even something like being able to export just those KS that user has modified into a TXT file which could then be used to reapply them (even manually) after reset to defaults would be a great step in this direction.

i can also see a benefit from a button like "Assign empty shortcuts to new functions" (can't think of a better caption now) which would basically check if there are (new) default shortcuts available. If yes it would apply these shortcuts if not already taken by user customization.

However, if it's more complicated than i imagine here, then i say: it's not worth the effort.

j_c_hallgren wrote:I'm certainly not wanting to argue this, but suppose a user only cares to install "official releases"...and has chosen to create just one or two CKS for function(s) that don't have one...when that user upgrades to next vers, all new KS that would have been added automatically are not due to those very minor customizations, and user then has to either make all those additions (or changes) manually -or- remember/locate which ones he'd tweaked, reset to defaults, and then reapply custom.

I don't understand that need to update all the shortcuts to the latest defaults. For me, I only use shortcuts for functions that I use quite often and I know very well. Any new functions I would always first try via menu, and then -- if I like them and see a use for them for my daily work -- I would think about assigning a KS to them, my choice of KS. I'm only very slightly interested in the KS that the developer proposes.

admin wrote: I'm only very slightly interested in the KS that the developer proposes.

Well, that's your opinion and method, but I will tend to at least look at the KS that are supplied by default and use those if they make sense to me. Given that the developer would have taken care to develop sensible KS for new/chg functions, I'd trust him/her to give me a good starting point.

Remember that I'm not the only one who ran into this issue. In the "Shift+F8" thread, graham had a similar problem...(See just the first five posts)...A new KS was presented in change log, but without manual user action, it wasn't available, thus causing graham to ask why...this thread was started somewhat due to the same issue, in that I saw reference to a KS but it wasn't configured on my system even though I'd updated to release that had added it...we've answered other queries here with "use this KS: xxxx" but if that user has the same issue we did, then that solution will not work and just cause futher confusion.

We've seen this before here in other posts, and may likely again in the future, so I was just attempting to try and resolve this...pagat also believes there would be a benefit to this, and I agree with his proposal which is basically what I suggested.

Okay, I added a command "Reset Unused Shortcuts To Defaults...".