As long as you treat your form reference as a thread variable; aren't trying to set or retrieve values on/from the thread/form; and are creating, updating, and destroying the form completely within the context of the thread, then there shouldn't be any real problem.
The only question is form object ownership/parentage. Since pointers (including VCL object references) are typically unsafe to pass across thread boundaries, you'll likely want the create the forms with nil owners, and set the parent to the desktop. This will limit your display options somewhat; for instance you can't have the forms be modal to the application or any of its forms, and your application will have little access to or control over the form's behavior without some fancy thread synchronization footwork. But if those limitations are agreeable, I don't see a problem. Stephen Posey [email protected] -----Original Message----- >From: JH <[email protected]> >Sent: Nov 24, 2014 1:34 AM >To: Moderated List for the Discussion of Delphi Programming excluding >Database-related topics <[email protected]> >Subject: Re: Separate thread with own form? > >Well, I may have written too little info in my first entry, because >threads are certainly not unknown to me. but having a thread using >visual components is! VCL is not known to be thread safe, at least not >on the same form. Or ... ? > >The 4 current display channels are all shown on the same form. > >And I am using D6 under Windows XP. > >Sid Gudes skrev den 21/11/2014 20:14: > >> Talk about coincidence: within minutes of your e-mail coming in, I >> received an e-mail from Embarcadero announcing the RAD Studio >> Parallel Programming Library. It may do want you want. Here's a link: >> >> http://s608.t.en25.com/e/es?s=608&e=1254014 [2]HTH >> >> At 04:30 AM 11/20/2014, JH wrote: >> >>> I have an application that is updating 4 rather large display channels in... <snippage> _______________________________________________ Delphi mailing list [email protected] http://lists.elists.org/cgi-bin/mailman/listinfo/delphi
