wx_object locks

[Mazen Harake]

Hi all,

If I create a frame using wx_object, then using an event destroy the 
frame and then start a new frame (wx_object or not doesn't matter I 
think) then the new frame is not created before the process that runs 
inside my callback function (specified with connect/3) returns from the 
callback. I find this very odd... so I was wondering if this is intended 
behaviour.

This code example (attached) shows what I'm trying to describe.
Instructions: do dlock:start(). then click on the middle of the frame 
that appears. I expected this to destroy the frame that was open and 
then create a new one but as long as the process in the callback is 
alive it will not. To unlock the process and let it complete type the 
following in the shell: pid(0,X,0) ! {continue}. where X is the Pid. 
Then you should see that the first frame is removed and the second one 
appears.

Is this intended?

Best regards,

/Mazen


-------------- next part --------------
A non-text attachment was scrubbed...
Name: dlock.erl
Type: application/x-extension-erl
Size: 1479 bytes
Desc: not available
URL: <http://erlang.org/pipermail/erlang-bugs/attachments/20091016/2a64f874/attachment.bin>