<div>
It's normal. Common dialog box closes on WM_LBUTTONDBLCLK, and WM_LBUTTONUP goes to your window.<br />
<br />
<br />

</div>


It's normal. Common dialog box closes on WM_LBUTTONDBLCLK, and WM_LBUTTONUP goes to your window.




<div>
Thanks; although it didn't help him solve his problem, it was good to know it was normal, and I think that your answer was the best that I could have hoped for without finding a TCL guru.<br />
<br />
Sorry it's taken so long to grade, but I've just started a new contract, so I'm a bit busy at the moment!
</div>


Thanks; although it didn't help him solve his problem, it was good to know it was normal, and I think that your answer was the best that I could have hoped for without finding a TCL guru.

Sorry it's taken so long to grade, but I've just started a new contract, so I'm a bit busy at the moment!

<div>
<div class="content wysiwyg-content">
Hi folks,<br />
<br />
A friend of mine is having difficulties with a rogue WM_LBUTTONUP being sent to his window when using the open file dialog box (he's using TCL, but I've reproduced it with a straight GetOpenFileName() call and with the CFileDialog MFC class.)<br />
<br />
Everything's fine unless you choose a file in the dialog by double-clicking on a file in the list. &nbsp;If you double-click, the file is chosen correctly, but the window behind the open file dialog gets a WM_LBUTTONUP message -- presumably from the last LBUTTONUP event of the double click.<br />
<br />
Is this normal? &nbsp;Is there any way to make the open file dialog &quot;eat&quot; the stray message? &nbsp;Any other suggestions? &nbsp;I don't know much about this bit of Windows, myself, so all help gratefully received.<br />

</div>
</div>


Hi folks,

A friend of mine is having difficulties with a rogue WM_LBUTTONUP being sent to his window when using the open file dialog box (he's using TCL, but I've reproduced it with a straight GetOpenFileName() call and with the CFileDialog MFC class.)

Everything's fine unless you choose a file in the dialog by double-clicking on a file in the list.  If you double-click, the file is chosen correctly, but the window behind the open file dialog gets a WM_LBUTTONUP message -- presumably from the last LBUTTONUP event of the double click.

Is this normal?  Is there any way to make the open file dialog "eat" the stray message?  Any other suggestions?  I don't know much about this bit of Windows, myself, so all help gratefully received.


WM_LBUTTONUP received after double-click in &quot;open file&quot; dialog

Most development for the Microsoft platform is done utilizing the technologies supported by the.NET framework. Other development is done using Visual Basic for Applications (VBA) for programs like Access, Excel, Word and Outlook, with PowerShell for scripting, or with SQL for large databases.

WM_LBUTTONUP received after double-click in &quot;open file&quot; dialog

WM_LBUTTONUP received after double-click in "open file" dialog