cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
Showing results for 
Search instead for 
Did you mean: 

Publish list of all ProCmd commands available

Publish list of all ProCmd commands available

Publish list of all ProCmd commands available. Example in trail file:

!Command ProCmdEnvShaded was pushed from the software.

!%CI Shaded model will be displayed

< 0 0.938667 1467 0 0 792 1920 0 0 1080 13

~ Command `ProCmdDwgNewSheets`

!%CISheet number 2 has been added to the drawing.

< 0 0.935111 1467 0 0 789 1920 0 0 1080 13

~ Activate `main_dlg_cur` `main_dlg_cur`

~ Command `ProCmdDwgNewSheets`

!%CISheet number 3 has been added to the drawing.

~ Command `ProCmdDrwModels`

~ Command `ProCmdFileInsert`

~ Command `ProCmdModelSave`

5 Comments
Emerald I

A quick text search of the loadpoint shows that many of these commands are located in the pro_default_resources.dll file (in the C:\Program Files\PTC\Creo 3.0\M050\Common Files\proe\text\compiled_resource\ folder).  Both the command names and descriptions are clearly visible, so if someone had a good way of extracting the information (regex??), it would probably be fairly simple to compile a list.

I'm not sure if there is any duplication, but this one file has 9,746 occurrences of "ProCmd..."

Participant

Well I did do extraction from xtop.exe and got list of 9593; there were duplicates.

Still does not reduce the need for an official list from PTC.

Emerald I

I highly doubt they will ever give it out...  Don't forget to vote up your own idea. 

Regular Member

Though the commands are by no means secret (as already noted, their UI components can be found in the loadpoint), it is a decidedly large list, and an official list would need updates to avoid getting out of date as we add commands and occasionally obsolete one in favor of a new one.  So, you'd need to point to some benefit to having the list that would be worth the time to compile and maintain it.  What would you expect to do with the list, and would that be satisfied by a list of names/descriptions, or would you need additional information?

Participant

Header file in ProToolkit seems like good choice or similar.