[Plib-users] RE: Crash while deleting puDialogBox... access violation
Brought to you by:
sjbaker
From: McEvoy, N. <nic...@ds...> - 2003-04-02 23:15:05
|
Ralf Pietersz wrote: >I am certain its a bug in PUI or a real bad design decision. >I wasnt able to delete the dialogbox in the callback, whatever I tried. >But then, where else should I delete it if not in the callback? I know this is not ideal ... but as a temporary fix ... you could hide the dialog, in the callback, instead of deleting it. >The redraw doesnt help for me.... my problem is that its only a >noticebox, >so there is no time being used in between, but anyway having the app >rely on >a fulfilled race condition is really bad anyway. Yes, I agree. That's what I'm worried about in my app ... it works ... but in the back of my mind I know a bug lurks. I hate that ! :) >Still didnt get it to work... I think someone who REALLY knows (like the >developer who >wrote it :P) needs to tell us what its doing and why... they should >know... >Searching through the code didnt help me at all, whatever its doing must >be hidden somewhere. Yes, I suggest take your problem to the devel list. Someone there (ie. the pui author) should be more helpful. >I was trying to pop the dialogbox from the stack but it still gets the >mouse event and crashes. >I dont know what else I can do to persuade PUI that I REALLY deleted it. >:P >It doesnt say anywhere in the docs how the deletion works, but somehow >the example apps seem to >work... really weird. Damn, I hate it when the example works ... but then crashes in your own framework. Happens to me all the time. :) What you need is a simple example that demonstrates the problem. Cya, Nick |