ACA 2011 - Property Editing Irritant

[rellison]

On my computer, In ACA 2011, when typing information into the Properties palette, hitting "Enter" returns keyboard control to the command line - not to the next available property field. IMHO this is undesireable behavior. Is it just me? Draw a wall of ACA default type "Standard", highlight it and right click "Properties" to launch the properties palette. Click in the field "Width" and type 8.0 followed by the Enter key. For me, the palette focus moves to the property "Base height" but keyboard control returns to the command prompt. I have to use the mouse to return keyboard control to the field in focus each and every time. This was not the case in 2010 - I've tested it. How do these things happen?

[Anonymous]

Same thing happened to me today on ACA 2010. Closing the drawing and
reopening the drawing restored things for me.


wrote in message
news:6385342@discussion.autodesk.com...
On my computer, In ACA 2011, when typing information into the Properties
palette, hitting "Enter" returns keyboard control to the command line - not
to the next available property field. IMHO this is undesireable behavior.
Is it just me? Draw a wall of ACA default type "Standard", highlight it and
right click "Properties" to launch the properties palette. Click in the
field "Width" and type 8.0 followed by the Enter key. For me, the palette
focus moves to the property "Base height" but keyboard control returns to
the command prompt. I have to use the mouse to return keyboard control to
the field in focus each and every time. This was not the case in 2010 -
I've tested it. How do these things happen?

[Anonymous]

Sometimes when my mouse cable is stiff and bent it won't allow focus to stay
on the properties pallete and moves away. adjusting the mouse & cable
position helps.

"Doug Broad" wrote in message
news:6387041@discussion.autodesk.com...
Same thing happened to me today on ACA 2010. Closing the drawing and
reopening the drawing restored things for me.


wrote in message
news:6385342@discussion.autodesk.com...
On my computer, In ACA 2011, when typing information into the Properties
palette, hitting "Enter" returns keyboard control to the command line - not
to the next available property field. IMHO this is undesireable behavior.
Is it just me? Draw a wall of ACA default type "Standard", highlight it and
right click "Properties" to launch the properties palette. Click in the
field "Width" and type 8.0 followed by the Enter key. For me, the palette
focus moves to the property "Base height" but keyboard control returns to
the command prompt. I have to use the mouse to return keyboard control to
the field in focus each and every time. This was not the case in 2010 -
I've tested it. How do these things happen?

[Anonymous]

That could be but my last experience had nothing to do with the mouse
position. It was a glitch in the program.


"Nathan" wrote in message
news:6387322@discussion.autodesk.com...
Sometimes when my mouse cable is stiff and bent it won't allow focus to stay
on the properties pallete and moves away. adjusting the mouse & cable
position helps.

"Doug Broad" wrote in message
news:6387041@discussion.autodesk.com...
Same thing happened to me today on ACA 2010. Closing the drawing and
reopening the drawing restored things for me.


wrote in message
news:6385342@discussion.autodesk.com...
On my computer, In ACA 2011, when typing information into the Properties
palette, hitting "Enter" returns keyboard control to the command line - not
to the next available property field. IMHO this is undesireable behavior.
Is it just me? Draw a wall of ACA default type "Standard", highlight it and
right click "Properties" to launch the properties palette. Click in the
field "Width" and type 8.0 followed by the Enter key. For me, the palette
focus moves to the property "Base height" but keyboard control returns to
the command prompt. I have to use the mouse to return keyboard control to
the field in focus each and every time. This was not the case in 2010 -
I've tested it. How do these things happen?

[cam-nav]

I am having this issue also and it is very irritating. There has to be some kind of variable set or maybe a registry key?

[leothebuilder]

Same problem here and it is irritating.