[fuse-emulator-devel] [ fuse-emulator-Bugs-3516228 ] Closing debugger and memory browser windows locks emulation

[SourceForge.net <no...@so...>]

Bugs item #3516228, was opened at 2012-04-09 13:42
Message generated for change (Comment added) made by sbaldovi
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=596648&aid=3516228&group_id=91293

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: None
Group: None
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Guesser ()
Assigned to: Nobody/Anonymous (nobody)
Summary: Closing debugger and memory browser windows locks emulation

Initial Comment:
This bug's been around for ages but I kept forgetting to log in and submit it.

Using the win32 UI open the Debugger (emulation pauses)
Open the Memory Browser
Close the Debugger (emulation still paused because Memory Browser is open)
Close Memory Browser - emulation should unpause but doesn't

Invoking a hard reset has no effect - the emulator remains paused.

----------------------------------------------------------------------

Comment By: Sergio Baldovi (sbaldovi)
Date: 2012-04-15 14:08

Message:
Nice one. When emulation stops, calls to ui_event() stops too. Therefore a
new message loop (win32ui_process_messages) is launched until a custom
message notify its ending. The problem is that the modal dialog override
this message loop, so the message never arrives where it is expected.

Possible fixes are:
- Rethink the message loop.
- Transform modal dialogs in pseudo-modal (as MFC does).
- Workaround this issue.

Currently, I can only provide a workaround by this patch:
http://pastebin.com/1WkT2vGU

Thanks for reporting.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=596648&aid=3516228&group_id=91293