Xailer & OZ Software

Hello to EveryOne
How can make a WinExec(application) runs from one form (i.e. Mainform) but
the focus staying on Application runs with the WinExec() function.(i.e.
application)
many thanks
We will stay tuned for the new release !!!!
Dionisis

Dionisis,
Try to use Execute() or ShellExecute (ShellExecute( hWnd, cOper, cFile,
cParam, cDir, nShowMode ) --> nReturn )
Regards,
"Dionisis Divaris" <sv1fkk@hol.gr> escribió en el mensaje
news:44905359$[email=1@ozsrvnegro.ozlan.local...]1@ozsrvnegro.ozlan.local...[/email]
> Hello to EveryOne
>
> How can make a WinExec(application) runs from one form (i.e. Mainform)
> but the focus staying on Application runs with the WinExec()
> function.(i.e. application)
>
> many thanks
> We will stay tuned for the new release !!!!
>
> Dionisis
>

Dionisis,
Try to use Execute() or ShellExecute (ShellExecute( hWnd, cOper, cFile,
cParam, cDir, nShowMode ) --> nReturn )
Regards,
"Dionisis Divaris" <sv1fkk@hol.gr> escribió en el mensaje
news:44905359$[email=1@ozsrvnegro.ozlan.local...]1@ozsrvnegro.ozlan.local...[/email]
> Hello to EveryOne
>
> How can make a WinExec(application) runs from one form (i.e. Mainform)
> but the focus staying on Application runs with the WinExec()
> function.(i.e. application)
>
> many thanks
> We will stay tuned for the new release !!!!
>
> Dionisis
>

Dionisis,
> How can make a WinExec(application) runs from one form (i.e. Mainform)
> but the focus staying on Application runs with the WinExec()
> function.(i.e. application)
Use SW_SHOWNOACTIVATE at the last parameter of ShellExecute()
--
Regards,
Jose F. Gimenez
http://www.xailer.com

Dionisis,
> How can make a WinExec(application) runs from one form (i.e. Mainform)
> but the focus staying on Application runs with the WinExec()
> function.(i.e. application)
Use SW_SHOWNOACTIVATE at the last parameter of ShellExecute()
--
Regards,
Jose F. Gimenez
http://www.xailer.com

Ignacio , Jose
Many thanks both for yours answers , but the problem stays.
When the external application (process) start runing imediately the focus
goes to the parent form (the main form of my program , the one with menus
etc) ,on the next statement after the process (which is a definition of a
FileOperation object that copies files on a floppy) that i want to avoid.
I want the control stays on the process until finishes , and it when finish
then open the FileOperation for copying the files.
With function Execute( procces,Directory,.T.) the control stays on the
process program but when drag-over the process form on the parent area
(i.e. MaiForm) this area disturbed , (the process leaves a white trace , and
many times hangs the whole program).
TIA
Dionisis
Ï "Jose F. Gimenez" <jfgimenez@wanadoo.es> Ýãñáøå óôï ìÞíõìá
news:44905768$[email=1@ozsrvnegro.ozlan.local...]1@ozsrvnegro.ozlan.local...[/email]
> Dionisis,
>
>> How can make a WinExec(application) runs from one form (i.e. Mainform)
>> but the focus staying on Application runs with the WinExec()
>> function.(i.e. application)
>
> Use SW_SHOWNOACTIVATE at the last parameter of ShellExecute()
>
> --
> Regards,
>
> Jose F. Gimenez
> http://www.xailer.com
>

Ignacio , Jose
Many thanks both for yours answers , but the problem stays.
When the external application (process) start runing imediately the focus
goes to the parent form (the main form of my program , the one with menus
etc) ,on the next statement after the process (which is a definition of a
FileOperation object that copies files on a floppy) that i want to avoid.
I want the control stays on the process until finishes , and it when finish
then open the FileOperation for copying the files.
With function Execute( procces,Directory,.T.) the control stays on the
process program but when drag-over the process form on the parent area
(i.e. MaiForm) this area disturbed , (the process leaves a white trace , and
many times hangs the whole program).
TIA
Dionisis
Ï "Jose F. Gimenez" <jfgimenez@wanadoo.es> Ýãñáøå óôï ìÞíõìá
news:44905768$[email=1@ozsrvnegro.ozlan.local...]1@ozsrvnegro.ozlan.local...[/email]
> Dionisis,
>
>> How can make a WinExec(application) runs from one form (i.e. Mainform)
>> but the focus staying on Application runs with the WinExec()
>> function.(i.e. application)
>
> Use SW_SHOWNOACTIVATE at the last parameter of ShellExecute()
>
> --
> Regards,
>
> Jose F. Gimenez
> http://www.xailer.com
>

Dionisis,
> With function Execute( procces,Directory,.T.) the control stays on the
> process program but when drag-over the process form on the parent area
> (i.e. MaiForm) this area disturbed , (the process leaves a white trace ,
> and many times hangs the whole program).
The third parameter means that your app will remain halted until the other
process is running. This causes your app to stop processing messages, and
WinXP advises it like if your app is hang. In this case, you should control
the execution of the other process. Simething like:
hProcess := Execute( process, directory, .F. )
WHILE IsRunning( hProcess )
ProcessMessages()
ENDDO
This lets your app to process any windows message, and it is not hanged for
the windows point of view.
--
Regards,
Jose F. Gimenez
http://www.xailer.com

Dionisis,
> With function Execute( procces,Directory,.T.) the control stays on the
> process program but when drag-over the process form on the parent area
> (i.e. MaiForm) this area disturbed , (the process leaves a white trace ,
> and many times hangs the whole program).
The third parameter means that your app will remain halted until the other
process is running. This causes your app to stop processing messages, and
WinXP advises it like if your app is hang. In this case, you should control
the execution of the other process. Simething like:
hProcess := Execute( process, directory, .F. )
WHILE IsRunning( hProcess )
ProcessMessages()
ENDDO
This lets your app to process any windows message, and it is not hanged for
the windows point of view.
--
Regards,
Jose F. Gimenez
http://www.xailer.com

Dionisis,
sorry,
> The third parameter means that your app will remain halted until the other
> process is running.
Should read:
"The third parameter means that your app will remain halted until the other
process FINISHED."
--
Regards,
Jose F. Gimenez
http://www.xailer.com

Dionisis,
sorry,
> The third parameter means that your app will remain halted until the other
> process is running.
Should read:
"The third parameter means that your app will remain halted until the other
process FINISHED."
--
Regards,
Jose F. Gimenez
http://www.xailer.com

Jose
With the While.. Enddo loop runs perfect.as expected !!
Again Many thanks
regards
Dionisis
"Jose F. Gimenez" <jfgimenez@wanadoo.es> wrote in message
news:44912c71$[email=1@ozsrvnegro.ozlan.local...]1@ozsrvnegro.ozlan.local...[/email]
> Dionisis,
>
> sorry,
>
>> The third parameter means that your app will remain halted until the
>> other process is running.
>
> Should read:
>
> "The third parameter means that your app will remain halted until the
> other process FINISHED."
>
>
> --
> Regards,
>
> Jose F. Gimenez
> http://www.xailer.com
>

Jose
With the While.. Enddo loop runs perfect.as expected !!
Again Many thanks
regards
Dionisis
"Jose F. Gimenez" <jfgimenez@wanadoo.es> wrote in message
news:44912c71$[email=1@ozsrvnegro.ozlan.local...]1@ozsrvnegro.ozlan.local...[/email]
> Dionisis,
>
> sorry,
>
>> The third parameter means that your app will remain halted until the
>> other process is running.
>
> Should read:
>
> "The third parameter means that your app will remain halted until the
> other process FINISHED."
>
>
> --
> Regards,
>
> Jose F. Gimenez
> http://www.xailer.com
>