I am trying to execute the prowin32.exe with the -b param.
Without the parameter the program executes fine without showing any window.
But when i add the -b parameter, the default window shows in the taskbar.
Is there a way to use the -b parameter without showing any window?
I am on Windows 10 with 11.6.1
Oh and the procedure is completely empty so it's not my code ;)
When running with a gui client in batch mode we assign the default-window:title with a guid and then use the windows API calls FindWindowA to find the window with the guid title and then use ShowWindow to hide it.
You are right. Same issue on 11.6.2 and 10.2B.
Holy crap. Are you kidding? I really did not expect this from *you*. It's probably because your eye is too slow to see it. Put PAUSE 1 in the empty.p (well, then it stops being empty.p, doesn't it?) Why is it always such a problem to understand a simple question? Are you deliberately playing dumb all the time or is it something else?
Although I truly don't understand the problem with seeing the hidden Progress window in the taskbar, but for once just try to understand the problem w/o being so picky. And dumb, of course.
This is why I stopped opening support cases with you long long time ago. Either it took too many effort to explain what the problem really was or 'I was doing it all wrong'.
No offense.
-b session is visible in the taskbar and deal with it.
"No offense."
This is not very obvious. I'm glad you are adding this here - otherwise others might misunderstand this.
No offence but why are you trying to start the 'graphical' client in batch mode instead of just doing that with the 'character' one (_progres.exe)? And, how do you execute that? From command prompt, starting the process from some other language, from another Progress runtime?
Anyway, back to the topic at hand:
"Is there a way to use the -b parameter without showing any window?"
1. Use _progres.exe instead of prowin32.exe/prowin.exe.
2. Make sure to redirect stdout to a file.
I cannot use _progres because my code usere "GUI" controls (ocx and so on) and .Net stuff in many places (i nerver show anything though)
Afaik the Character client can't deal with this stuff.
@Brian not really since i don't wan't any message to block the execution i just want to log everything
Also i don't create a window, OE does and as i said it doesn't do this without the -b param
@Mike Sadly my code is far from ready to run on the char client :/
KEEP-MESSAGES doesn't work with "VIEW AS ALERT BOX" Messages, which my code uses and i don't wand to suppress any messages i want to log them....
yeah...i am very sorry that i can't explain my whole application to you
To clear things up:
1.) I need to use prowin32.exe because my code is written for it and i can't rewrite my huge application
2.) I don't want anything to block the execution and i don't want any window to open (which shouldnt happen from my code but programming errors happen and legacy code is a ***)
The thing i don't get is why OE opens a window when you use -b and doesn't when you don't use this parameter.
It doesn't make any sense....
When running with a gui client in batch mode we assign the default-window:title with a guid and then use the windows API calls FindWindowA to find the window with the guid title and then use ShowWindow to hide it.
[quote user="Stefan Drissen"]
When running with a gui client in batch mode we assign the default-window:title with a guid and then use the windows API calls FindWindowA to find the window with the guid title and then use ShowWindow to hide it.
[/quote]
Thats a good idea, thx