jguest82179
2005-09-07, 04:32 AM
A question to the moderators: Can we please have a new wish list specific to the ACAD 2006 CUI? (Or did I just create one by making this post? :confused: )
If so, then here are a few thing to kick it off:
i) When viewing the list of commands with them filtered by custom commands only and you then click the "New" button the CUI switches back to viewing all commands forcing you to go back to the pull down and switch back to viewing only custom commands again. Personally I find this very frustrating. If I am viewing custom commands only and I click the "New" button, then surely it is obvious that I am creating a new custom command, is it not? (Aside from that, how can you create a new command that is not a custom command?)
ii) As far as I can tell there is no way to copy a command to then modify it to make a new command. It would be really helpful to have, for example, a "New Command Based On..." button or similar to achieve this end. At the moment it takes five copy and pastes to replicate a command to base a new command on.
iii) What is up with the "Edit Properties" option in the context menu that results from a right click in the command list? If I want to edit a command I can simply click that command and then move over into the lower right portion of the window. "Edit Properties" appears to do absolutely nothing. If this is true then it probably should be removed to reduce confusion.
iv) A similar situation exists with the "New Command" option in the right click context menu, in that it appears to be redundant. The difference here is that it combines its irritational qualities with points i and ii - it immediately switches you back to viewing the entire command list. It would be far more useful if this option were to create the "New Command Based On" that I mentioned earlier.
Does anyone else have other suggestions to add to this list?
Aside from the frustrations caused by the CUI, I still stand by my earlier statements elsewhere on this site that the CUI has a great deal of potential as a customization tool. What is needed is some useful documentation and a lot of fine tuning based on customer feedback. Of course the latter can not happen unless we provide the feedback :)
Cheers,...Jon.
BTW, has anybody else noticed the surge in popularity of this little fellow :banghead: since the introduction of the CUI?
If so, then here are a few thing to kick it off:
i) When viewing the list of commands with them filtered by custom commands only and you then click the "New" button the CUI switches back to viewing all commands forcing you to go back to the pull down and switch back to viewing only custom commands again. Personally I find this very frustrating. If I am viewing custom commands only and I click the "New" button, then surely it is obvious that I am creating a new custom command, is it not? (Aside from that, how can you create a new command that is not a custom command?)
ii) As far as I can tell there is no way to copy a command to then modify it to make a new command. It would be really helpful to have, for example, a "New Command Based On..." button or similar to achieve this end. At the moment it takes five copy and pastes to replicate a command to base a new command on.
iii) What is up with the "Edit Properties" option in the context menu that results from a right click in the command list? If I want to edit a command I can simply click that command and then move over into the lower right portion of the window. "Edit Properties" appears to do absolutely nothing. If this is true then it probably should be removed to reduce confusion.
iv) A similar situation exists with the "New Command" option in the right click context menu, in that it appears to be redundant. The difference here is that it combines its irritational qualities with points i and ii - it immediately switches you back to viewing the entire command list. It would be far more useful if this option were to create the "New Command Based On" that I mentioned earlier.
Does anyone else have other suggestions to add to this list?
Aside from the frustrations caused by the CUI, I still stand by my earlier statements elsewhere on this site that the CUI has a great deal of potential as a customization tool. What is needed is some useful documentation and a lot of fine tuning based on customer feedback. Of course the latter can not happen unless we provide the feedback :)
Cheers,...Jon.
BTW, has anybody else noticed the surge in popularity of this little fellow :banghead: since the introduction of the CUI?