PR# 12741 Changing arguments for profile in Debug Options window leads to crash

Changing arguments in a profile in Debugging Options window sometimes does
not dismiss the "..." button that appears when entering the arguments.
This can lead to a crash.  Details below.

Start estudio and compile sample basic application.
Right-click on Start button to bring  up Debugging Options window.
Click Add button.
Double-click in area to right of Arguments for profile #0,
   enter "weasel" and then hit the Tab key instead of Return.
   Note that the "..." button is still present but probably should not be.
Click OK.  "..." button still visible.
Right-click on Start button again to bring up Debugging Options window.
Left-click on "..." button.
Estudio crashes with attached trace.

The last time I tested this, it still crashed.  However, I cannot
reproduce it on Solaris SPARC because when I click on the Close button
the "..." button disappears even if it has the focus.  So I think this
really is fixed.  I will try tonight on Solaris x86 to verify but I
think this may be fixed.  Sorry for the confusion.

The behavior I observed previously when I clicked on Close was that the
"..." button, when it had focus, did not disappear but the Debugging Options
window closed.  I can't make that happen on Solaris SPARC.

Closing report.  I will reopen if I can reproduce a problem on Solaris x86.

I am puzzled ... if you edit the argument field.
when you press <Tab>  the focus should be on the [...] button 
if you press <tab> again, the focus should come back to the edited argument field
and so on ... the only way to cancel or valid the change is to press <Esc> or <Return>.

When you press <tab> and <tab> again ... where is the focus ?

Not fixed in Solaris 10 on x86, rev 68837.  The problem seems to be that
after entering the argument if I hit Tab instead of Return then the "..."
button does not disappear, which later leads to the crash after I close
Debugging Options window and then bring it up again.  Reopening report.

It seems this issue is fixed, I am not able to reproduce it anymore, at least with ec built after rev#68817.

Attachments for problem report #12741