>>So, what you're saying is the application should behave differently than all other Windows applications?
>>
>>
>>>Disagree totally.
>
>Of course the problem as described isn't really a problem with double-click events per se. From what I can tell from the description, there was enough of a "gap" in time between the clicks that the first click is indeed registered by the dropdown (which then "retracted") and the following click was registered by a control that was previously covered by dropdown. I've noticed that there are some users which get into the habit of trying to double-click *everything* -- probably based on remember that they've got to double-click a desktop icon. Unfortunately this means they tend to double-click input fields, labels, control buttons, treeviews, etc. There are variations to this theme -- they may not double-click everything (they learned at some point that double-clicking on command buttons doesn't give what they want) -- so they tend to double-click only on items with a picture on it (which unfortunately means they still double-click on command buttons if it has a picture on it, and double-click on toolbar items).

And we shouldn't dismiss these users. My MIL has been using computers for at least a decade and still, every time I have to walk her through anything, I have to be really clear about what to click and what to double-click. While the underlying rules may seem obvious to us, they're not at all obvious to everyone.

Tamar