[ros-bugs] [Bug 3339] start button doesn't answer if you open the run dialog

ReactOS.Bugzilla at www.reactos.org ReactOS.Bugzilla at www.reactos.org
Sat Feb 28 00:53:26 CET 2009


http://www.reactos.org/bugzilla/show_bug.cgi?id=3339





--- Comment #5 from di64 <unik64 at gmail.com>  2009-02-28 00:53:22 CET ---
Created an attachment (id=3628)
 --> (http://www.reactos.org/bugzilla/attachment.cgi?id=3628)
adds a WindowReenablerThread that spins in the background after the run dialog
is started

This is a patch for the 'old' explorer that seems to do the trick.

Unfortunately the Run dialog is very much a modal thing, and there's no way to
stop it locking up & disabling whatever owner window the hwnd of which it is
provided with.  I did try passing 0, but it seemed slightly worrying and it
made the run window open at the top-left of the screen. :(

The, er, totally not over-engineered solution provided here (honest, its not
that bad!) is to create a thread just before the run dialog is started, that
waits and checks every 50ms if IsWindowEnabled(the task bar) == false.
If so, it re-enables the window and stops.
If the run dialog call ends before the thread has stopped, then its stopped.

It works perfectly apart from the fact that the start button stays pressed-in
until either its clicked or the run dialog finishes. I don't know how to fix
this.

If there's anything wrong with the patch, please say, its my first. thanks in
advance.


-- 
Configure bugmail: http://www.reactos.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
You are the assignee for the bug.


More information about the Ros-bugs mailing list