In order for this site to work correctly we need to store a small file (called a cookie) on your computer. Most every site in the world does this, however since the 25th of May 2011, by law we have to get your permission first. Please abandon the forum if you disagree.
Para que este foro funcione correctamente es necesario guardar un pequeño fichero (llamado cookie) en su ordenador. La mayoría de los sitios de Internet lo hacen, no obstante desde el 25 de Marzo de 2011 y por ley, necesitamos de su permiso con antelación. Abandone este foro si no está conforme.
Para que este foro funcione correctamente es necesario guardar un pequeño fichero (llamado cookie) en su ordenador. La mayoría de los sitios de Internet lo hacen, no obstante desde el 25 de Marzo de 2011 y por ley, necesitamos de su permiso con antelación. Abandone este foro si no está conforme.
WinExec() isue
- Dionisis Divaris
- Mensajes: 485
- Registrado: Jue Jul 12, 2007 8:48 pm
- Ubicación: Athens Greece
WinExec() isue
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
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
- ignacio
- Site Admin
- Mensajes: 9440
- Registrado: Lun Abr 06, 2015 8:00 pm
- Ubicación: Madrid, Spain
- Contactar:
WinExec() isue
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
>
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
>
Ignacio Ortiz de Zúñiga
[OZ Software]
https://www.ozs.es
--
[Equipo de Xailer / Xailer team]
https://www.xailer.com
[OZ Software]
https://www.ozs.es
--
[Equipo de Xailer / Xailer team]
https://www.xailer.com
WinExec() isue
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
>
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
>
WinExec() isue
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
> 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
WinExec() isue
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
> 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 Divaris
- Mensajes: 485
- Registrado: Jue Jul 12, 2007 8:48 pm
- Ubicación: Athens Greece
WinExec() isue
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
>
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 Divaris
- Mensajes: 485
- Registrado: Jue Jul 12, 2007 8:48 pm
- Ubicación: Athens Greece
WinExec() isue
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
>
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
>
WinExec() isue
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
> 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
WinExec() isue
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
> 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
WinExec() isue
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
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
WinExec() isue
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
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 Divaris
- Mensajes: 485
- Registrado: Jue Jul 12, 2007 8:48 pm
- Ubicación: Athens Greece
WinExec() isue
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
>
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
>
- Dionisis Divaris
- Mensajes: 485
- Registrado: Jue Jul 12, 2007 8:48 pm
- Ubicación: Athens Greece
WinExec() isue
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
>
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
>