Skip to main content
A
Anonymous
February 9, 2007
Question

Remove Inconsistencies

  • February 9, 2007
  • 1 reply
  • 3906 views
<ul><li>Sometimes it is not clear where the user input goes to. Although an input field is yellow, the typed in value does not appear until the ENTER key</li><li>Some commands (e.g. 2D) don't have a way to input values at all although the prompt says to input a value</li><li>UI flow different in similar or comparable commands</li><li>Missing user guidance (yellow input fields, prompting)</li></ul><p><br />Please report concrete examples of where you see inconsistencies.</p><p></p>

    1 reply

    A
    Anonymous
    February 17, 2007
    Users do not understand &quot;Auto Accept on lost focus.&quot; When they see a form-like dialog in Windows, they expect they can input and go. On the other hand, settings dialogs commit to change instantly, without any &quot;apply&quot; or &quot;ok.&quot; The dialog expects more interaction from the user while the settings menu does not give the user a way to op-out.<br /><br />Create 2D geometry commands require numeric input in the User Input Line. This makes input of number+unit not possible, unlike a dialog. Maybe the key is a new User Input Line that changes it's input type based on the variable type of the active field. This means the user can type in <em><font color=""#0033cc"">.25 in</font></em> when working in mm, or <font color=""#0033cc""><em>p1 p2</em></font> instead of having to type &quot;/p1, /p2.&quot;
    P
    ptc-18821571-Visitor
    1-Visitor
    March 1, 2007
    Users are often frustrated due to the lack of consistency between the different modules. I know that this has been an issue for some time but I hear it quite often. This is very apparent when using cabling and IDF modules in regard to moving objects. Sometimes the user can input from the menu during translations but with others this is not possile. I guess we just need consistency.
    P
    ptc-19004551-Visitor
    1-Visitor
    March 1, 2007
    In our tests with AutoCAD users who never used CoCreate before, we found most don't understand the ""Click OK"" command. That is, they often believe they have finished a command, and then ""lose"" their work mysteriously. While logic exists behind when you click okay and when you don't, it often just makes the software seem difficult and tempermental to the new user.
    Terms & ConditionsAccessibility statement