Catalog Display when tree is not present

[allen]

This bug report also contains a few wishes.
I tend to have the tree disabled unless I explicitly need it -- I tend to get around by way of location typing rather than tree navigating. Unfortunately, when doing so I do not have access to the catalog. I'd love to see (a)a keyboard shortcut to toggle the tree panel off/on (b) a means of accessing the catalog without the tree being enabled -- either through the favorites menu or just the ability to enable the catalog independent of the tree.

At any rate, with tree and info panel disabled, enabling the catalog causes the catalog to attempt to appear. Unfortunately, only a few pixels of it make it to the screen, as pictured.


Before, tree and info panel are hidden

After hitting F8

[admin]

At any rate, with tree and info panel disabled, enabling the catalog causes the catalog to attempt to appear. Unfortunately, only a few pixels of it make it to the screen, as pictured.

How do you do this? Cannot reproduce...

EDIT: okay, I could...

[admin]

I'd love to see (a)a keyboard shortcut to toggle the tree panel off/on (b) a means of accessing the catalog without the tree being enabled -- either through the favorites menu or just the ability to enable the catalog independent of the tree.

Yes, this seems a reasonable wish. No time now, remind me later.

[admin]

I'd love to see (a)a keyboard shortcut to toggle the tree panel off/on (b) a means of accessing the catalog without the tree being enabled -- either through the favorites menu or just the ability to enable the catalog independent of the tree.

Yes, this seems a reasonable wish. No time now, remind me later.

Finally done! Comes today...

[mgalusha]

Finally done! Comes today...

Not sure if it's just this machine (have to update my home PC still) but this doesn't work in 7.30.0000 after upgrading from 7.20.0000.

Shift+F8 does nothing. I was able to edit the keyboard shortcuts to make this work but thought you would like to know of the initial configuration.

BTW, love XYplorer, can't imagine doing without.

-mike

[TheQwerty]

Not sure if it's just this machine (have to update my home PC still) but this doesn't work in 7.30.0000 after upgrading from 7.20.0000.

New Shortcuts keys are never applied when upgrading XY. This is to ensure they don't overwrite the user's current settings.

More specifically, if ks.dat exists when XYplorer is executed the default, as well as any new, shortcuts are ignored.


Personally, I'm torn on whether this is appropriate or not. Part of me thinks it would be nice if XY were smarter (insert new shortcuts that don't conflict), as that would help users discover new features without this confusion.

But another part is glad that XY respects that I may already be using the key combination for a system-wide shortcut.

[admin]

Personally, I'm torn on whether this is appropriate or not. Part of me thinks it would be nice if XY were smarter (insert new shortcuts that don't conflict), as that would help users discover new features without this confusion.

But another part is glad that XY respects that I may already be using the key combination for a system-wide shortcut.

Same here. But I don't see a smart way to make everybody (every side of me) happy. A message box when starting up an upgrade "Any default keyboard shortcuts to new functions must be manually assigned." ?? Would not look very good ...

[TheQwerty]

Same here. But I don't see a smart way to make everybody (every side of me) happy. A message box when starting up an upgrade "Any default keyboard shortcuts to new functions must be manually assigned." ?? Would not look very good ...

Indeed, it's a challenging issue. Certainly a static dialog with that text wouldn't be good at all.

But if there were a way to do an optional dynamic dialog the first time a new version of XY were run that could list new features and shortcuts, it might not be bad.

Of course then you have issues in tracking when features were added so you can detect all the features when users skip versions, etc.


I could see a lot of good coming from such functionality, but I envision it would also take a lot of work to add this in cleanly. Not so sure it would be worth the effort.

EDIT: BTW, hope you had a good break Don, and got plenty of rest to tackle our demands, er I mean, wishes.

[jacky]

Well, it would seem possible (from my user POV of course ) to have on CKS a new option, along with Reset & Remove all shortcuts, that could be like "Add Currently Unassigned Default KS" or something.

So it would not remove or change anything, only add all the currently unassigned KS that are defaults to their commands.

That way, any and all user changes done manually would be preserved. No, there's no consideration for your global KS, but you can't have it all.

One could think XY could list all such default KS currently unassigned in some list, even make that a checkbox list so the user could chose which to assign, that that might be just a little too much.

I think only adding unset default KS might be good enough, as if one likes XY defaults and has the previous ones (from his first installation), and as long as his own KS aren't affected, it shouldn't be a problem.

If you don't like that, you'll have to keep track manually of all changes, or temporarily export the XY default KS, export your own KS cheat sheet, and compare yourself!

[admin]

I think that it's not worth the effort. That's from a programmer's POV, and also from a user's POV since any action on this will complicate the UI and potentially raise further questions or discomfort.

The current situation is quite clear and straight once you have understood that Keyboard Shortcuts are customizable and that the Keyboard Shortcuts settings are remembered between versions.

Advantage of current implementation: without looking at the change log you can be sure that -- after an upgrade -- the same key combo will trigger the same action, resp. will continue to trigger NO action.

If a new feature is advertised with a new default KS, and you happen to be baffled because it does not work -- well: look at the menu command caption and you will note that there is no KS displayed. So you open CKS and assign it. Since only upgraders will meet this situation they are likely to know about a central feature as CKS and will quickly understand what to do. The others come to the forum...

[jacky]

Advantage of current implementation: without looking at the change log you can be sure that -- after an upgrade -- the same key combo will trigger the same action, resp. will continue to trigger NO action.

Well, that would have remained unchanged if you only added a new command on the "Options" menu on CKS, as it would only allowed the user to get up to date with new default KS still available, but it was nothing automatic.

Anyways, I'm fine with the current situation anyhow...

[j_c_hallgren]

Although this thread isn't exactly for this subject, but based on above comments, I'm wondering if there could be a way to flag which CKS's are non-standard (changed from default) and/or show the original CKS value.

This was result of another topic where it was pointed out by Don that I was using a custom setting but didn't realize it.

IMHO, it would appear that even something as simple as a "Y"/"N" switch indicating that user has made a customization to that function might help when new KS's are defined or defaults changed, but showing orig/dflt could be better, as user wouldn't thus need to consult wiki/help.

[jacky]

Well, assuming this isn't to be done every day, you could always do that by exporting into text files your cheat sheet and the default one, and comparing the results with an app made for it.

It would list you what KS you're "missing" (eg. new default you haven't assigned), which ones you changed from default value, etc

[admin]

IMHO, it would appear that even something as simple as a "Y"/"N" switch indicating that user has made a customization to that function might help when new KS's are defined or defaults changed, but showing orig/dflt could be better, as user wouldn't thus need to consult wiki/help.

Where? In CKS dialog?

[j_c_hallgren]

Where? In CKS dialog?

Yes, that would be the ideal place...possibly as a new "column" in the 'Command' window.

And rethinking it slightly: just the user customized entries would need the "Y" flag or default KS to avoid clutter...

This would also likely need to be shown on the 'cheat sheet' to allow viewing it in a global manner.