Forum for XYplorer Users and Developers
https://www.xyplorer.com/xyfc/
Yes, this wish is currently accumulating...ugus wrote:Can you make it possible to get
the #<Command> as well when performing
Options | Copy Cheat Sheat in Customize Keyboard Shortcuts
dialog.
or have I missed something...
In what format? Should I attach it to the Command caption in brackets like:I think putting a tab between the command caption and #<Command> will do best, (if you want to import it into Excel or similar...)admin wrote:Yes, this wish is currently accumulating...ugus wrote:Can you make it possible to get
the #<Command> as well when performing
Options | Copy Cheat Sheat in Customize Keyboard Shortcuts
dialog.
or have I missed something...
Edit / Cut [#200] Ctrl+X
?
Yes, a new "column" would definitely be the way to go IMOugus wrote:I think putting a tab between the command caption and #<Command> will do best, (if you want to import it into Excel or similar...)
Super, that was fast!+ CKS | Options button context menu: added toggle command "Include
Command IDs".
Only that character is displayed messed up.No, only "/" (forward slash) and "»" (french open quote?).infimum wrote:Is the character "|" or "#" used in the context menu? It's not showing up correctly in my environment
A new column is what I'd suggested in the other thread at http://www.xyplorer.com/xyfc/viewtopic.php?t=2082jacky wrote:Yes, a new "column" would definitely be the way to go IMOugus wrote:I think putting a tab between the command caption and #<Command> will do best, (if you want to import it into Excel or similar...)
I've heard you, but the implications are many... still in pre-decision mode...j_c_hallgren wrote:A new column is what I'd suggested in the other thread at http://www.xyplorer.com/xyfc/viewtopic.php?t=2082jacky wrote:Yes, a new "column" would definitely be the way to go IMOugus wrote:I think putting a tab between the command caption and #<Command> will do best, (if you want to import it into Excel or similar...)
That would lend itself to Excel and such...
I don't disagree with that...just that for us who can use it, having it visible is very valuable...so if this display needs to be triggered and set on thereafter via INI tweak, or some other similar less visible method, I'd be happy with that!admin wrote:Hint: the call by ID scripting is considered absolute hardcore by me, and I'm hesitating to make it too visible. It's just too dangerous for newbies.
I won't add a 3rd col without adding column headers. But I have currently no time to add column headers to my little list. You should see my desktop...j_c_hallgren wrote:I don't disagree with that...just that for us who can use it, having it visible is very valuable...so if this display needs to be triggered and set on thereafter via INI tweak, or some other similar less visible method, I'd be happy with that!admin wrote:Hint: the call by ID scripting is considered absolute hardcore by me, and I'm hesitating to make it too visible. It's just too dangerous for newbies.
Maybe within 'Options' on CKS panel as done would ok...I'd have it at the Option level though...and that should then also cause display within CKS itself as 3rd col, and unless done, even the existing single CID display wouldn't be visible...but this setting should be retained in INI, for sure!
AFAIK, the existing columns don't have headers either, right?admin wrote:I won't add a 3rd col without adding column headers. But I have currently no time to add column headers to my little list. You should see my desktop...
OK, "»" isn't displayed correctly in my environment.admin wrote:No, only "/" (forward slash) and "»" (french open quote?).
So I guess I better take my hands off all upper ASCII chars...pity! I will use comma or semicolon instead...infimum wrote:OK, "»" isn't displayed correctly in my environment.admin wrote:No, only "/" (forward slash) and "»" (french open quote?).
Or full-fledged unicode supportadmin wrote:So I guess I better take my hands off all upper ASCII chars...pity! I will use comma or semicolon instead...