On Sun, Jul 13, 2008 at 2:46 PM, Rick McGuire <[EMAIL PROTECTED]> wrote:
> I committed fixes for this problem....but unfortunately, I also > committed your changes to oodialog by mistake. I'll take care of > reverting those changes in a minute. I reverted them, so we are good to go. > I still recommend that your invoking code just do a single > AttachThread() when the thread initializes rather than storing the > instance information in the objects and attaching every time you want > to invoke a method . Absolutely. I did see your other post and was going to reply that it helped me on several levels. Helped with my Windows debugging. And this recommendation made a lot of sense. So, with this route, just doing a single AttachThread(), then when the dialog is destroyed, I will need to do a DetachThread() correct? The basic question being, do you need to be careful to always match an AttachThread() with a corresponding DetachThread()? -- Mark Miesfeld ------------------------------------------------------------------------- Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW! Studies have shown that voting for your favorite open source project, along with a healthy diet, reduces your potential for chronic lameness and boredom. Vote Now at http://www.sourceforge.net/community/cca08 _______________________________________________ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
