XProfan

look time To WinExec:
Help

since Version 11 supply The function The process-ID the launched Program back, as in the Taskmanager displayed becomes. in the Fehlerfall is it the worth 0. with previous versions was the worth in the Erfolgsfall without weight.

then time look what GetExitCode(ProzessID) returns - vlt. helps the already.

Specifically of OpenOffice white I but that this with the Prozessen self already herumspielt - means many Process only others launch or benachrichtigt and itself self but then same again exits - here remaining then vlt. only a on OO adjusted Solution How z.B. FensterFinden etc. .

Paul
Glatz

Starte time at Portable not The normal exe separate The under APP

Thomas
Freier

@Paul, the have I already tested and has none influence with: "@WinExecWait(Prog$,1)"
@iF, with:
Compile Mark Separation

Prog$ = Ooo_Pfad$+" "+text$
x&=WinExec(Prog$,1)

while GetExitCode(x&)=256

    sleep 100

wend

Prog$ = XCVIEW_Pfad$+" "+text$
WinExecWait(Prog$,1pan>

brought nothing. possibly, that 256 not correctly. is.

Nachtrag: has someone experience at Umbennen of odt-Files with XProfan?
Compile Mark Separation

LOESCH_SEITE(ODT_Pfad$,L_Seite$,R_Seite$,".odt")
....

Proc LOESCH_SEITE

    Parameters a$,b$,c$,d$
    Assign #3, a$+b$+d$
    Rename #3, a$+c$+d$
    Close #3

ENDPROC

lead always moreover, that Ooo a "beschädigte" File restore wants.

Gruß Thomas
Windows XP SP2, XProfan X2

@Thomas: Yes, habs vermutet - OO uses many Process only circa a others To inform. I know now only once more with AddWindows/ FindWindow To look whether one it on it somehow "festmachen" can.

Thomas
Freier

@iF: with the FindWindow suspect I, if I not already first thing tested having, end How with the Test, The on Ooo übergebene File to open. D.h. the Window Title is first complete present, if The File opened watts. means n-Time Waiting To the Window Title abfragbar is.

Gruß Thomas
Windows XP SP2, XProfan X2

>> means n-Time Waiting To the Window Title abfragbar is.

or simply "warten To the Window Title abfragbar ist" means while hardship window there Waiting...

Perhaps. helps you too a processes-list: [...]

Thomas
Freier

means the example have I once tested with
Compile Mark Separation

x&=WinExec(Prog$,1)

and then attempts x& to find with
Compile Mark Separation

case Str$(x&)=Str$(Entry#.th32ProcessID&)

and not found. Mach I as a Error? is PID not The process-ID?
Eingentlich have I any Examples from the babybox.exe through.

Gruß Thomas
Windows XP SP2, XProfan X2

very, PID is the Process-ID - if the Process but already exits is then becomes it neither More in the list stand.

thatswhy meant I Yes: "also many Process only others launch or benachrichtigt and itself self but then same again beendet"...

Perhaps but uses it you a list all processes to Openoffice-Prozessen To search in order to look whether at all yet one active or not.