1. Capture console output - edita 0.0.7
After 10 days hard slog, console capture seems to be working:
http://palacebuilders.pwp.blueyonder.co.uk/edita.htm
Date and time in the status bar now show the locale user default
settings (as set in control panel, regional settings).
Added tab text colourisation to show file requires saving. The tab
colour is properly reset by undo to the exact point of the last file
save.
Save as now resets the syntax if save with a different file
extension, esp. if saving an [untitled] (aka new) file, and also
resets the tab bar text.
Some bugs in text selection near the end of a line and in text
deletion fixed.
Added context menu to the edit area.
Added Capture console i/o. Pressing F5 runs test2.exw as a demo. [More
work is required to complete the run program logic, esp. save files
before run]. Output is in a new re-sizeable message area.
Regards,
Pete
PS can someone independently verify the length of this (in bytes):
typedef struct _CONSOLE_SCREEN_BUFFER_INFO { // csbi
COORD dwSize;
COORD dwCursorPosition;
WORD wAttributes;
SMALL_RECT srWindow;
COORD dwMaximumWindowSize;
} CONSOLE_SCREEN_BUFFER_INFO ;
where
typedef struct _COORD { // coord.
SHORT X; // horizontal coordinate
SHORT Y; // vertical coordinate
} COORD;
and
typedef struct _SMALL_RECT { // srct
SHORT Left;
SHORT Top;
SHORT Right;
SHORT Bottom;
} SMALL_RECT;
(I think it is either 22 or 24 bytes)
2. Re: Capture console output - edita 0.0.7
Pete Lomax wrote:
>PS can someone independently verify the length of this (in
>bytes):
>..........
>(I think it is either 22 or 24 bytes)
#include <windows.h>
#include <stdio.h>
int main() {
printf("size of CONSOLE_SCREEN_BUFFER_INFO is %d\n",
sizeof(CONSOLE_SCREEN_BUFFER_INFO));
return 0;
}
size of CONSOLE_SCREEN_BUFFER_INFO is 22
3. Re: Capture console output - edita 0.0.7
Hi Pete,
Can't get the 'console capture' or whatever it is to work.
I get error "Cant create process" under XP.
On second try, get "Console is already captured" or something like that.
Context menu is looking nice however.
The _CONSOLE_SCREEN_BUFFER_INFO struct is 22 bytes long.
If you add up each SHORT (which are 2 bytes each) you get
the total (the two other structs are also made up of SHORT's).
Take care,
Al
And, good luck with your Euphoria programming!
My bumper sticker: "I brake for LED's"
4. Re: Capture console output - edita 0.0.7
- Posted by "Juergen Luethje" <j.lue at gmx.de>
Feb 17, 2005
-
Last edited Feb 18, 2005
Pete Lomax wrote:
<snip>
> Added tab text colourisation to show file requires saving. The tab
> colour is properly reset by undo to the exact point of the last file
> save.
Cool.
> Save as now resets the syntax if save with a different file
> extension, esp. if saving an [untitled] (aka new) file, and also
> resets the tab bar text.
Much appreciated.
> Some bugs in text selection near the end of a line and in text
> deletion fixed.
>
> Added context menu to the edit area.
Nice. But what does "Cuta" and "Copya" mean? 
> Added Capture console i/o. Pressing F5 runs test2.exw as a demo. [More
> work is required to complete the run program logic, esp. save files
> before run]. Output is in a new re-sizeable message area.
When I re-size that area with the mouse, several black lines are
appearing. That way, I can make the whole Edita window look like
a zebra.
And shouldn't have each window it's own vertical scrollbar?
Regards,
Juergen
5. Re: Capture console output - edita 0.0.7
On Thu, 17 Feb 2005 20:14:13 +0100, Juergen Luethje <j.lue at gmx.de>
wrote:
>> Added context menu to the edit area.
>
>Nice. But what does "Cuta" and "Copya" mean?
Cut append and copy append. I've expanded then.
I'm still after ideas on making this thing multi-lingual.
If, in your mind, this is trivial, please show me how!
[[via proper, pukka changes to edita source]] )
(Of course, I think this is difficult; I do actually want
to be proved wrong...)
I would also like to tie in user-customisation, eg whether
Ctrl Ins is Copy or Comment. Maybe that is asking too much.
>> Output is in a new re-sizeable message area.
>
>When I re-size that area with the mouse, several black lines are
>appearing. That way, I can make the whole Edita window look like
>a zebra.
Does not happen here. Can I ask, does it right itself when you release
the left mouse button or not? I may need some help from Mike on this.
>And shouldn't have each window it's own vertical scrollbar?
Fair point, I've added that to the suggestion list.
Regards,
Pete
6. Re: Capture console output - edita 0.0.7
Ed Davis wrote:
>size of CONSOLE_SCREEN_BUFFER_INFO is 22
Al Getz wrote:
>The _CONSOLE_SCREEN_BUFFER_INFO struct is 22 bytes long.
Thanks, I wan't sure if the rect was being dword aligned (its not).
>posted by: Al Getz <Xaxo at aol.com>
>
>
>Hi Pete,
>
>Can't get the 'console capture' or whatever it is to work.
>I get error "Cant create process" under XP.
>On second try, get "Console is already captured" or something like that.
Please try replacing approx ten lines at the start of eacons.ew:
function GetLastError()
return c_func(xGetLastError,{})
end function
integer initC, inUse
initC=0
procedure Ferror(sequence msg)
void = messageBox("Error",
sprintf("%s failed [%d]",{msg,GetLastError()}),0)
inUse=0
end procedure
Obviously, it will still fail, but maybe give a hint this time.
Thanks,
Pete
7. Re: Capture console output - edita 0.0.7
Pete Lomax wrote:
> On Thu, 17 Feb 2005 20:14:13 +0100, Juergen Luethje wrote:
<snip>
> I'm still after ideas on making this thing multi-lingual.
> If, in your mind, this is trivial, please show me how!
> [[via proper, pukka changes to edita source]] )
> (Of course, I think this is difficult; I do actually want
> to be proved wrong...)
I'll try to prove you wrong, and you please try to prove me wrong,
that's the best way to get a rock-solid result. I'll send you something
today. Maybe I'm just too short-sighted to see the problem ...
> I would also like to tie in user-customisation, eg whether
> Ctrl Ins is Copy or Comment. Maybe that is asking too much.
Sooner or later, there should be a "Options" > "Settings" dialog window
anyhow, no? Maybe I'm again on the wrong track ...?
>>> Output is in a new re-sizeable message area.
>>
>> When I re-size that area with the mouse, several black lines are
>> appearing. That way, I can make the whole Edita window look like
>> a zebra.
>
> Does not happen here. Can I ask, does it right itself when you release
> the left mouse button or not? I may need some help from Mike on this.
As I found out now, it depends. When I move the mouse up and down only
say 3 times with the left button pressed, then it rights itself when I
release the mouse button.
But when I move the mouse up and down over and over again with the left
button pressed, then the program usually (not always) freezes, and the
mouse cursor is trapped inside the Edita window. Sometimes Windows then
says: "Not enough resources". (I'm using Eu 2.5 beta on Windows 98.)
So maybe this is a memory leak?
<snip>
Regards,
Juergen
8. Re: Capture console output - edita 0.0.7
Pete Lomax wrote:
>
> Ed Davis wrote:
> >size of CONSOLE_SCREEN_BUFFER_INFO is 22
>
> Al Getz wrote:
> >The _CONSOLE_SCREEN_BUFFER_INFO struct is 22 bytes long.
>
> Thanks, I wan't sure if the rect was being dword aligned (its not).
>
> >posted by: Al Getz <Xaxo at aol.com>
> >
> >
> >Hi Pete,
> >
> >Can't get the 'console capture' or whatever it is to work.
> >I get error "Cant create process" under XP.
> >On second try, get "Console is already captured" or something like that.
>
> Please try replacing approx ten lines at the start of eacons.ew:
>
> function GetLastError()
> return c_func(xGetLastError,{})
> end function
>
> integer initC, inUse
> initC=0
>
> procedure Ferror(sequence msg)
> void = messageBox("Error",
> sprintf("%s failed [%d]",{msg,GetLastError()}),0)
> inUse=0
> end procedure
>
> Obviously, it will still fail, but maybe give a hint this time.
>
> Thanks,
> Pete
>
>
Hi Pete,
Ok, here's the latest on the message area display...
Added err number lines (as above).
Open Edita (with test2.exw loaded).
Press F5.
Get 'file' error... traced to 'exwc' wasnt recognized because
i never created one on my system.
Created exwc.exe and opened one .ex program with it, then
closed that program.
Open Edita.
Press F5.
Get msgbox error: Duplicate Handle failed
Close Edita.
Added PROCESS_DUP_HANDLE to OpenProcess() call.
Open Edita.
Press F5.
Console opens, prints out:
-------------------------------------------------------------
press any key but q
ReadConsoleOutput failed
-------------------------------------------------------------
(and see nothing in message area)
Close console by pressing ENTER,
see in message area:
press any key but q
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.
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.
Take care,
Al
And, good luck with your Euphoria programming!
My bumper sticker: "I brake for LED's"
9. Re: Capture console output - edita 0.0.7
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.
10. Re: Capture console output - edita 0.0.7
On Fri, 18 Feb 2005 05:39:53 -0800, Al Getz <guest at RapidEuphoria.com>
wrote:
>and exactly when it's supposed to appear there.
the message area should appear permanently (ie the next time you start
Edita) when selected via the Options menu/keyboard shortcut, but only
session-wise when it needs to appear because you ran a program and it
captured console output - I'll cement/document that behaviour when I
finish implementing run program (may be a while yet).
Any preferences vis a suitable hide/show keyboard shortcut?
(I'm thinking Ctrl Alt M)
Regards,
Pete
11. Re: Capture console output - edita 0.0.7
On Fri, 18 Feb 2005 13:07:42 +0100, Juergen Luethje <j.lue at gmx.de>
wrote:
>> I'll try to prove you wrong, and you please try to prove me wrong,
Yep, that's the general idea )
Your mods were helpful, but a gut feeling...
They have given me some great ideas, though:-
I am now thinking along the lines of eamenus.ew containing:
sequence menus={
{"&File",Main,{},0},
{"&New\t(Ctrl N)",{1},14,{routine_id("newFile"),{"",{""},{}}},
...
(ie the definitive set in english, and parent/shortcut/action stuff)
and eatext_de.e containing eg:
"&File" = "&Datei"
...
(ie a 1:1 translation)
and changing the create() calls and the menuHandler() routine and
possibly the charInput() routine in edita.exw to scan menus...
One point I had not even considered was mapping (Ctrl N) to (Strg N).
OK, I might just leave it as a plain text thing, assuming that (Strg
N) automatically means the same as (Ctrl N), but (Yksw D) in some
other language suggests (Ctrl D) ought to be the shortcut (NMP if the
translator fails to map all keys uniquely, you understand).
I suppose the file might start with:
"Ctrl" = "Strg"
"Shift" = "Umsch"
>I believe, my changes are... say... 99.3% pukka.
I could shoot you down... But you've given me a few ideas I would not
otherwise had. Leave it with me, I now have plenty to work on.
>When I include "eatext_de.e", everything seems to work fine.
>But when I include "eatext_en.e", and choose "File" > "New" and press
>[F5], then I get a message box, saying "[Error] DuplicateHandle failed",
>and no text is shown in Edita's Message Area.
This may be due to the problem Al Getz reported, in that
PROCESS_DUP_HANDLE is apparently required.
>The way I made it here, the language of course can only be changed at
>parse-time. But that is not a bad thing IMHO,
No real issue, but I would prefer an "Options" entry, even if it meant
shutdown/restart, over editing the source, however trivially.
>Any way, keeping all the text in a separate file
>saves time and reduces the probability, that some text will not be
>translated by mistake.
I plan on issuing warnings if an xlate file is missing entries, and
using a central message constant area and simple function, for
example:
puts(1,xlt("Out of bounds"))
Somewhere, there would be a complete table of English:German (or
whatever language) translations and if one was avaliable it would use
that. The total size is not going to be more than 50K, tops.
>One problem that I often saw in translation of other programs is with
>dialog windows, when the translated text requires more space than the
I'm aware. The only thing I think I can realistically do is design
using right-aligned labels, but there will always be some problems
that will need to be solved as and when they arise.
Regards and thanks,
Pete
12. Re: Capture console output - edita 0.0.7
Pete Lomax wrote:
> On Fri, 18 Feb 2005 13:07:42 +0100, Juergen Luethje wrote:
>
>> I'll try to prove you wrong, and you please try to prove me wrong,
> Yep, that's the general idea )
Sometimes I like to say the obvious. Please don't ask me why.
> Your mods were helpful, but a gut feeling...
> They have given me some great ideas, though:-
>
> I am now thinking along the lines of eamenus.ew containing:
>
> sequence menus={
> {"&File",Main,{},0},
> {"&New\t(Ctrl N)",{1},14,{routine_id("newFile"),{"",{""},{}}},
> ...
> (ie the definitive set in english, and parent/shortcut/action stuff)
>
> and eatext_de.e containing eg:
> "&File" = "&Datei"
> ...
> (ie a 1:1 translation)
Nice, that will make the work of translators rather comfortable.
<snip>
>> The way I made it here, the language of course can only be changed at
>> parse-time. But that is not a bad thing IMHO,
> No real issue, but I would prefer an "Options" entry, even if it meant
> shutdown/restart, over editing the source, however trivially.
I agree that this is better.
Just out of curiosity: Do you plan to put the words of the supported
languages (except of English) in plain text files, or DLLs, or ...?
<snip>
I have one more suggestion/wish:
I would appreciate it, if the console output was captured, without an
ugly black console window popping up. However, I don't know how much
efforts or whatever that requires.
Regards,
Juergen
PS: Have you already looked at Wolf's "multilingual.zip"?
13. Re: Capture console output - edita 0.0.7
- Posted by Pete Lomax <petelomax at blueyonder.co.uk>
Feb 19, 2005
-
Last edited Feb 20, 2005
On Sat, 19 Feb 2005 18:20:02 +0100, Juergen Luethje <j.lue at gmx.de>
wrote:
>Just out of curiosity: Do you plan to put the words of the supported
>languages (except of English) in plain text files, or DLLs, or ...?
plain text files
>
><snip>
>
>I have one more suggestion/wish:
>I would appreciate it, if the console output was captured, without an
>ugly black console window popping up.
I think that can be done, with two caveats.
1) the program should not accept any console input, as obviously any
prompts won't appear, if I'm hiding them.
2) It is not possible (on windows 98) to redirect standard error, so
error messages can only be captured by deliberately creating a shared
console before starting the app.
>PS: Have you already looked at Wolf's "multilingual.zip"?
I might yet nick the language detection code from that, but I think
I'll stick to text not bitmaps.
Regards,
Pete
14. Re: Capture console output - edita 0.0.7
- Posted by "Juergen Luethje" <j.lue at gmx.de>
Feb 19, 2005
-
Last edited Feb 20, 2005
Pete Lomax wrote:
<snip>
>> I have one more suggestion/wish:
>> I would appreciate it, if the console output was captured, without an
>> ugly black console window popping up.
>
> I think that can be done, with two caveats.
> 1) the program should not accept any console input, as obviously any
> prompts won't appear, if I'm hiding them.
> 2) It is not possible (on windows 98) to redirect standard error, so
> error messages can only be captured by deliberately creating a shared
> console before starting the app.
I see. Then this probably better should not be changed.
<snip>
Regards,
Juergen
15. Re: Capture console output - edita 0.0.7
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"
16. Re: Capture console output - edita 0.0.7
On Sat, 19 Feb 2005 23:43:20 +0100, Juergen Luethje <j.lue at gmx.de>
wrote:
>Pete Lomax wrote:
>
>>> I would appreciate it, if the console output was captured, without an
>>> ugly black console window popping up.
>>
>> I think that can be done, with two caveats.
>> 1) the program should not accept any console input, as obviously any
>> prompts won't appear, if I'm hiding them.
>> 2) It is not possible (on windows 98) to redirect standard error, so
>> error messages can only be captured by deliberately creating a shared
>> console before starting the app.
>
>I see. Then this probably better should not be changed.
No, I think I'll do it, I just have to ask the right questions, eg:
[X] Capture error messages (a console must be displayed)
[X] Show console window (strongly recommended if any input is expected)
as opposed to, say:
[X] Hide console
As you know, I am shy on quite a few options windows (so sue me, it's
a *seven week old* baby!
Ideally, you'll be able to configure edita to run one particular
source that fashion, but not others, however, that is way down my
(lengthy) to-do list.
Regards,
Pete
PS I have just finished mangling the menus (in English, less the
context menu); I have a point now at which I can attempt translation,
though I will migrate that context menu first. Part of me suddenly
suspects I might not have needed to bother, but it is data-driven now,
which is (usually) better anyway, and definitely much more flexible.
Thanks again for guiding me in the right direction.
17. Re: Capture console output - edita 0.0.7
On Sat, 19 Feb 2005 16:18:11 -0800, Al Getz <guest at RapidEuphoria.com>
wrote:
>Pete Lomax wrote:
>>
>> On Fri, 18 Feb 2005 05:39:53 -0800, Al Getz <guest at RapidEuphoria.com>
>> wrote:
>>
>> >ReadConsoleOutput failed
>> OK, it has got 99.9% along, but eacons.exw (as opposed to eacons.ew)
>> has failed in function getErrorMessages().
>> PS once you get round this
>Get around what?
It mostly worked, but failed in getErrorMessages() in eacons.exw.
Unfortunately I have no XP box to test ReadConsoleOutput() on.
Regards,
Pete
18. Re: Capture console output - edita 0.0.7
Me wrote:
> Pete Lomax wrote:
>
>> On Thu, 17 Feb 2005 20:14:13 +0100, Juergen Luethje wrote:
<snip>
>>>> Output is in a new re-sizeable message area.
>>>
>>> When I re-size that area with the mouse, several black lines are
>>> appearing. That way, I can make the whole Edita window look like
>>> a zebra.
>>
>> Does not happen here. Can I ask, does it right itself when you release
>> the left mouse button or not? I may need some help from Mike on this.
>
> As I found out now, it depends. When I move the mouse up and down only
> say 3 times with the left button pressed, then it rights itself when I
> release the mouse button.
> But when I move the mouse up and down over and over again with the left
> button pressed, then the program usually (not always) freezes, and the
> mouse cursor is trapped inside the Edita window. Sometimes Windows then
> says: "Not enough resources". (I'm using Eu 2.5 beta on Windows 98.)
> So maybe this is a memory leak?
BTW: If it turns out that this is an ARWEN problem, please let me know,
because I distribute programs that rely on ARWEN.
Regards,
Juergen
19. Re: Capture console output - edita 0.0.7
Hi Pete,
Well, except for displaying that error message it appears to be working
right? After the console window is closed it does in fact display
(message area) what had taken place in the console, and isnt that what
you wanted it to do, except for displaying an error too?
I've tried unremming the other lines in test2.exw and it seems to work,
as when i typed the letter 'g' and closed the console the 'g' also
appeared in the message window...that's the way it's supposed to work
right?
Ok, now the obvious question is...do you intend to do something else
with that info that's displayed in the message area or is it just
so the user can see the entire dialog that had taken place in the
console (which isnt a bad idea either)?
So i take it the only thing that's left to be done then is to simply
stop the error message from appearing and not break anything else?
Take care,
Al
And, good luck with your Euphoria programming!
My bumper sticker: "I brake for LED's"
20. Re: Capture console output - edita 0.0.7
On Sun, 20 Feb 2005 09:11:12 -0800, Al Getz <guest at RapidEuphoria.com>
wrote:
>Hi Pete,
Hi Al
>
>Well, except for displaying that error message it appears to be working
>right? After the console window is closed it does in fact display
>(message area) what had taken place in the console, and isnt that what
>you wanted it to do, except for displaying an error too?
Yes.
>
>I've tried unremming the other lines in test2.exw and it seems to work,
>as when i typed the letter 'g' and closed the console the 'g' also
>appeared in the message window...that's the way it's supposed to work
>right?
Yes
>
>Ok, now the obvious question is...do you intend to do something else
>with that info that's displayed in the message area or is it just
>so the user can see the entire dialog that had taken place in the
>console (which isnt a bad idea either)?
No, nothing else.
While a program that performs both console output and input must
(obviously) display a console, I may rethink the ReadConsoleOutput
approach and load say the top five(?) lines from the ex.err (I should
be able to work out when one has been created), to capture error info
without the "ugly black console", but I have no other plans.
In other words, I am ready to accept that capturing error output by
/forcing/ a console to appear may not be the ideal solution.
(so ultimately it may prove unnecessary to fix this particular prob)
The "idle" loop in eacons.ew may also undergo radical change...
>So i take it the only thing that's left to be done then is to simply
>stop the error message from appearing and not break anything else?
Yes.
>
>
>Take care,
I will, you too,
Pete
21. Re: Capture console output - edita 0.0.7
Hi again Pete,
Ok, what i did was ran it with Win98 and i see that the Read Error
didnt appear, so apparently it's something in XP that's causing
that error to appear. Everything else appears to work, so i'll try
to hunt down why it's only appearing in XP.
I'm sort of satisfied with the way it works anyway however, as
the error display doesnt seem to bother anything.
Take care,
Al
And, good luck with your Euphoria programming!
My bumper sticker: "I brake for LED's"
22. Re: Capture console output - edita 0.0.7
On Mon, 21 Feb 2005 06:28:18 -0800, Al Getz <guest at RapidEuphoria.com>
wrote:
>Hi again Pete,
>
>Ok, what i did was ran it with Win98 and i see that the Read Error
>didnt appear, so apparently it's something in XP that's causing
>that error to appear. Everything else appears to work, so i'll try
>to hunt down why it's only appearing in XP.
>I'm sort of satisfied with the way it works anyway however, as
>the error display doesnt seem to bother anything.
I've now (at last) seen it run on XP. I can say that XP does not
"share" the console in the same way 98 does, and reports the error as
"insufficient memory", between which I take to mean it plain don't
work. No matter, no-one was a fan of that approach anyway.
I will therefore re-think this final phase (which was a bit slow
anyway), and stop automatically creating a console (as asked for by
JL). I'll next get a chance to test on Tuesday (1/3).
Regards,
Pete
