OpenEuphoria

Re: Capture console output - edita 0.0.7

• Posted by Al Getz <Xaxo at aol.com> Feb 20, 2005
• 423 views

Pete Lomax wrote:
> 
> On Fri, 18 Feb 2005 05:39:53 -0800, Al Getz <guest at RapidEuphoria.com>
> wrote:
> 
> >Get 'file' error... traced to 'exwc' wasnt recognized because
> >i never created one on my system.
> Doh, I'm so used to having it, my bad.
> 
> >Added PROCESS_DUP_HANDLE to OpenProcess() call.
> Thanks. Strange I don't need it here, but I've added it no prob.
> 
> >-------------------------------------------------------------
> >press any key but q
> >ReadConsoleOutput failed
> >-------------------------------------------------------------
> >(and see nothing in message area)
> OK, it has got 99.9% along, but eacons.exw (as opposed to eacons.ew)
> has failed in function getErrorMessages(). (I've added similar changes
> here re GetLastError, renaming ErrorExit as is to ErrorExit0 and
> adding a new one after the link_c_func setups)
> >
> >Close console by pressing ENTER,
> >see in message area:
> >press any key but q
> 
> Good!
> 
> >In short, the console opened, showed the program output, also 
> >showed an error message, and nothing was displayed in the message
> >area until after the console was closed by pressing ENTER.
> Pretty much as I expect. )
> >
> >It might help if i knew what the message area was supposed to be
> >showing, both now and what your long range intentions are for that,
> >and exactly when it's supposed to appear there.
> The console program should run "as-is", ie if it displays messages and
> accepts input (including error messages) edita does not try and change
> that. However it saves a copy of that dialogue. In the test program I
> gave with 0.0.7 all it does is display "press any key but q", which
> you got. It does exactly what it should but is failing at the very
> last hurdle, trying to read (non-existant) error messages.
> 
> getErrorMessages() should read the screen, find nothing it had not
> already sent, and return "".
> 
> Hope that makes sense,
> Pete
> PS once you get round this, you can uncomment some of the lines in
> test2.exw to catch interactive console i/o.
> 
> 

Hi again Pete,

Get around what?  I thought you said it was supposed to work that way?
I'll try it again after uncommenting the code and see what happens...

It does look interesting...


Take care,
Al

And, good luck with your Euphoria programming!

My bumper sticker: "I brake for LED's"