🚀 go-pugleaf

I would, except that the application that uses this thread form in not a C++ 
Builder application.  In fact, it does not have its own support for 
multi-thread, however it does allow dll calls.

Hence, I decided to wrap up a form object into a thread and place that into 
a dll.  Then they can create an instance and the form runs.  The reason I 
need this is because in their main application they may be executing a 
lengthy database query.  I wanted to provide a progress bar that shows that 
the application has not hung, but is retrieving data.  They also want to use 
this when they download files, to indicate things are going well.

Thanks,


James
"Ed Mulroy [TeamB]" <dont_email_me@bitbuc.ket> wrote in message 
news:4853e7cb$1@newsgroups.borland.com...
> For reliability and best performance VCL visuals are best handled in a 
> single thread as the VCL does not contain elements to by default handle 
> intra-thread issues.  My opinion is that you should post something to the 
> main thread for that form.
>
> To get others' opinions post to a group which better relates to the 
> subject of your message.  This group might be a good one to post in:
>    borland.public.cppbuilder.vcl.components.using
>
> .  Ed
>
>> James L. Williams wrote in message
>> news:4853e32c$1@newsgroups.borland.com...
>>
>> I would like to create a form that exists inside a Thread.  I want this 
>> so that the forms graphics updates are handled inside of a thread.
>>
>> I do something like the following:
>>
>> Thread::Execute()
>> {
>>        MSG msg;
>>        TmyForm * myForm = new TmyForm(NULL);
>>        myForm->Parent = NULL;
>>        myForm->ParentWindow = GetDesktopWindow();
>>        myForm->Left = 10;
>>        myForm->Top = 10;
>>        myForm->Width = 500;
>>        myForm->Height = 500;
>>        myForm->Visible = true;
>>        while(GetMessage(msg,NULL,0,0))
>>        {
>>
>>             if(Terminated) break;
>>                TranslateMessage(&msg);
>>              DispatchMessage(&msg);
>>        }
>>        delete myForm;
>> }
>>
>> Is this a good way to do it, or is there a better way?
>
>