#128199 - 2004-10-21 10:43 AM
Re: wkix32 console, not what expected.
|
Richard H.
Administrator
Registered: 2000-01-24
Posts: 4946
Loc: Leatherhead, Surrey, UK
|
Quote:
doing a settitle() on wkix32 without output says error=6
this is more of an design flaw than bug.
when you output something to wkix32 console, it gets created and settitle() works.
same goes for things like setconsole("hidden")
I disagree that it's a design flaw, it's what you would expect to happen. If the console does not exist, then attempting to manage it is going to cause an error.
It would be like trying to write to a file that has not been opened.
It's actually a neat way to determine if there is a console.
The process of automatically creating a console when there is output queued is presumably because there is no explicit "CreateConsole()".
Quote:
going further...
doing a spawn:
run "wkix32 somescript.kix"
and outputting from somescript, well, it outputs to window.
but using multiple spawns, all of them output to SAME window!
That's not surprising considering KiXtart's pedigree. The console is associated with the process, and there is (normally) only one. The console is inherited by any child process that is started so output will appear on the same one.
Quote:
suggestion of changes...
making the console the way expected, either make more control to the console.
make the console an "object" that can be controlled as any com-object.
or make the console work as wsh shelll does, open each console in it's own window.
Why re-invent the wheel 
Code:
$objShell=CreateObject("Wscript.Shell")
$=$objShell.Run("%COMSPEC% /C DIR && pause")
$=$objShell.Run("%COMSPEC% /C DIR && pause")
$=$objShell.Run("%COMSPEC% /C DIR && pause")
$=$objShell.Run("%COMSPEC% /C DIR && pause")
|
|
Top
|
|
|
|
Moderator: Lonkero, ShaneEP, Jochen, Radimus, Glenn Barnas, Allen, Ruud van Velsen, Mart
|
0 registered
and 200 anonymous users online.
|
|
|
