awkward number field behavior

[i8bozo]

the number field in the upper right hand corner that controls the opacity of the overlay...

i highlight that and then accidentally bump my cursor into the image window and it becomes unhighlighted. highly annoying and time consuming.because i'd think i was typing in a number for my opacity and my image viewing experienced has changed because i've instead envoked some hidden hot key for foreground or composite mode.

i'm glad i figured this out because it was causing some weird things to happen that i just couldn't put my finger on.

any way to get all the number fields to react like the ones in the roto options menu? one click and the box highlights? it'd be killer if the position of the mouse didn't have an effect on whether or not those boxes remained highlighted as well.

thoughts?

[paulm]

This is a catch 22.

Some people like fields to "accept" the number when pressing TAB or losing focus, while some like hitting ENTER to accept the value. Except in Dialog boxes, pressing ENTER usually accepts the dialog, so you HAVE to use TAB. So, througout the app, ENTER (when not in a dialog) or TAB (or losing focus) accepts the values in edit fields.

BUT - to fix the key focus problem in the viewer (explained in another thread), I have to force the focus to the viewer when the mouse moves into it (which of course causes active edit fields to lose their focus and accept their value).

Catch 22.

Bummer, but a necessary evil.