><snip>
>>>
>>>First off all, it's Microsoft's design. It is the default behavior of the combobox. A single click is enough. If you do a second click (which isn't the same as a double click) and if there is another object exactly below the cursor, then yes, of course, it will be activated.
>>
>>Yes that's true, but doesn't negate the fact that your design allows for this behavior. Change the design so the next clickable item is not under the combobox. You owe it to your customers to help prevent I-D-10-T errors.
>
>Agreed. This is exactly what I was suggesting. Either handle the possibility for the erroneous second click (as I suggested to the OP) and/or change the form design so that it has no effect (good app design).
Huh? I find no message where you was suggesting this all. Neither in your unfriendly interaction with me, nor in another place. The only suggestion you made (in Message ID #1600297) was to code away (my words) the second click. And that is not what John suggested.
>
>>End of my posts to you on the subject. You circumvented the real issue with Jos and I will not be dragged into this.
>
>Ditto.
Groet,
Peter de Valença
Constructive frustration is the breeding ground of genius.
If there’s no willingness to moderate for the sake of good debate, then I have no willingness to debate at all.
Let's develop superb standards that will end the holy wars.
"There are three types of people: Alphas and Betas", said the beta decisively.
If you find this message rude or offensive or stupid, please take a step away from the keyboard and try to think calmly about an eventual a possible alternative explanation of my message.
