Manage UDC

[admin]

Conc. your EDIT: Yeah! I think I forgot to mention this. Yes, with IncludeCommandIDs = 1 ALL commands are printed to the cheat sheet.

Ok...so they are printed, which satisfies one of my requests/comments in the other thread, but this one is still not, which makes CKS a bit less than perfect, IMHO...so from that thread:

Why aren't the command ID nbrs listed as a third column in the list, right after the shortcut? Why should I have to select that particular entry if all I want to do is find the ID nbr? Or am I missing something obvious here (which may be true)?

Patience... the IDs will soon lose in importance compared to the real scripting...

[j_c_hallgren]

Patience... the IDs will soon lose in importance compared to the real scripting...

Oh, I realize that these funky CID nbrs are just an interim thing, based on latest beta posting, but there will still likely need to be some shorter vers or abbreviation or code for some of the existing commands that have lengthy multi-word titles...like #1037 which is "Set Modified Date to Created Date"...I'd not want to have to type all of that to use it!
Can you share some of your plans on how those type of commands will be labeled/titled/whatever when used in scripting?

[serendipity]

Patience... the IDs will soon lose in importance compared to the real scripting...

Oh, I realize that these funky CID nbrs are just an interim thing, based on latest beta posting, but there will still likely need to be some shorter vers or abbreviation or code for some of the existing commands that have lengthy multi-word titles...like #1037 which is "Set Modified Date to Created Date"...I'd not want to have to type all of that to use it!
Can you share some of your plans on how those type of commands will be labeled/titled/whatever when used in scripting?

Is that where aliases come into play?I totally agree with JC that one doesnt have to type those sentences (I am sure Don too would never plan such a thing). In fact, my guess is Don will provide us with another field like assigning CKS where user can write his/her own aliases for UDCs. For eg: ":: xy" will take me to xy folder.
OK, thats all my imagination. I'd like to see what Don has in mind. Worth the wait though.

[j_c_hallgren]

In fact, my guess is Don will provide us with another field like assigning CKS where user can write his/her own aliases for UDCs. For eg: ":: xy" will take me to xy folder.

That's a further expansion on the issue, as I was only thinking about the existing built-in functions that have long command names, like my example...should one create a UDC, then there would need to be a way to have a shortcut name for that also, and this is where alias might come in?

BTW, the ":" followed with a "x" creates the "mad" emoticon (:x), and that wasn't what you intended in your example so I spaced it out in my quote!

[admin]

It was not my plan to come up with scripting that fast, but I was so fascinated by the sudden easy possibility of Custom Reports, that I decided to create a quick test bed for it. So, one of the next SCs (scripting commands) will be report. And if it's good I raise it to GUI level as a new UDC category.

You see, that's flower power programming... code where the wind blows... (what do you expect from an electric guitarist anyway?)

[Jeff Bellune]

(what do you expect from an electric guitarist anyway?)

Hendrix riffs.

[admin]

- Yes, the button to assign a KS is nice, but what's really missing IMO is a way to press the key and have it selected, instead of having to go through that long list - who's not really alpha-sorted, and while I understand the idea there, it makes it hard to find the key you're looking for at times, when all you see is a bunch of Ctrl, Alt and Shift's

- When using the menu UDC (through menu User or a KS-triggered popup) it'd be nice if, on Statusbar, we'd get the pattern/location/etc ideally with variables (eg. <curbase>, etc) replaced.

1) done!
2) yes, agreed, but not possible (not easily enough possible for now, to be correct)