1. RE: Al Getz Display Server
jondolar wrote:
>
>
> I Have some problems with Display Server. Lokk at my previous message
> RE: A nice window vs Win console jondolar
>
> Thanks
>
> Serge
>
Hello there Serge,
I should have mentioned that the only thing to remember is
that the DisplayServer201.exe program has to be started
BEFORE you start your own program using the 'connect.ew'
file. The program doesnt use any processor time while it's
sitting idle, and it returns much faster then a dos console.
The default size starts out small, but you can drag it
to a larger window with the mouse.
Just to recap, the operating steps are as follows:
[1]
Start DisplayServer201.exe by double clicking on it.
This will start a window in the upper left corner of your screen.
[2]
Start your own program exw or exe with the 'include connect.ew'
file in it and some ServerPrint() calls.
If you do [2] first and then [1], your program wont connect
to the server so you wont be able to print anything.
Once the starting order is right, you'll see a message
that says something like:
"__ClientConnected__"
which tells you your own program can send data via ServerPrint().
As you already noticed, ServerPrint("Hello") is a very good
test to make sure your program is truely connected.
This is a very simple but VERY handy program, but
if any other problems come up, feel free to let me know
about them.
Take care for now,
Al
2. RE: Al Getz Display Server
Al
This is not the problem. I start DisplayServer201 first, then my program
second. I printed the doc and read it about 10 times to make sure I was
doing everything right. By the way, I'm on win XP Pro. (I don't know if
this is relevant)
Sincerly
Serge
3. RE: Al Getz Display Server
It appears the Display Server does not work on Windows XP. I just tried it.
>From: jondolar <lavigne.s at videotron.ca>
>Subject: RE: Al Getz Display Server
>
>
>Al
>This is not the problem. I start DisplayServer201 first, then my program
>second. I printed the doc and read it about 10 times to make sure I was
>doing everything right. By the way, I'm on win XP Pro. (I don't know if
>this is relevant)
>
>Sincerly
>
>Serge
>
4. RE: Al Getz Display Server
Pete Lomax wrote:
> I've put up a little program using Thomas Parslow's ipc handler, which
> is still in proof-of-concept stage. Can someone test it on XP?
>
> The url is http://palacebuilders.pwp.blueyonder.co.uk/euphoria.html
> It is the last item on that page.
>
> Originally I wrote this for an entirely different purpose.
> The files are:
> run.exw - similar-ish to the display server, it runs in the
> background. If you run this, it starts up test.exw automatically.
> test.exw - a test program. If you run this it will automatically load
> run.exw if it is not already running (there is a lost focus bug - tho
> I'm sure that can be fixed fairly easily).
> test2.exw is a tiny message_box example.
>
> Pressing Run should fire up the message box, closing that should post
> a message back to the calling program and display it. It is not at
> this stage supposed to look anything like Display Server.
>
> If (*IF*) it works on XP, it would have some advantages over Al Getz's
> Display Server: it is written entirely in Euphoria, so it would be
> easy for someone to make it scrollable, change the font, add a clear
> button, etc, and it is not necessary to remember to fire up the
> display server beforehand. Maybe someone would like to tidy it up? It
> needs a complete rewrite really, but hey, it's only 300 lines of code.
> The demo uses win32lib, but I don't think it would be too hard to make
> it cross-lib.
>
> Pete
Hi Pete
I tried your little program on my Win XP machine and it seems to work
correctly. When I fire test.exw, I get a little witndow and a counter
incrementing and scroling up automatically on the left side of the RUN
button. If I press RUN, I get the win console with some various called
functions from win32. Closing the box produce essentially the same
effect with a longer list of called functions.
Regards
Serge Lavigne
5. RE: Al Getz Display Server
jondolar wrote:
>
>
> Al
> This is not the problem. I start DisplayServer201 first, then my program
>
> second. I printed the doc and read it about 10 times to make sure I was
> doing everything right. By the way, I'm on win XP Pro. (I don't know if
> this is relevant)
>
> Sincerly
>
> Serge
>
Hello again,
I'll have to test the program in XP i guess and see what
is going on.
In the mean time, you can check the 'connect.ew' file to see
that it is version 2.01 as well as the DisplayServer201.exe
file. The older version wont work with some Windows versions.
Also, dont you get any error message?
Does the display server window even start up?
Take care,
Al
6. RE: Al Getz Display Server
Juergen Luethje wrote:
>
>
> Hello Al, you wrote:
>
> <snip>
>
> > This is a very simple but VERY handy program, but
> > if any other problems come up, feel free to let me know
> > about them.
>
> I like the idea in general, and I like your program. Nevertheless,
> *for me* it has ATM no practical advantage over the console window.
>
> For my needs, the most important improvement would be, to make the text
> inside the window scrollable, so that your server can show much more
> lines than currently (say 500 -- but I think, Windows allows even more).
>
> Secondly, displaying the text in a non-proportional font (such as
> "Courier New") is IMHO more versatile, than using a proportional font.
> In a non-proportional font, also tables and ASCII art will be shown
> correctly. Just try
> include connect.ew
> ServerPrint(" |\\ _,,,---,,_")
> ServerPrint(" /,`.-'`' -. ;-;;,_")
> ServerPrint(" |,4- ) )-,_..;\\ ( `'-'")
> ServerPrint("'---''(_/--' `-'\\_)")
>
> and see, what currently happens to the kitty.
> An advanced option also could be, that the user can choose a font. 
>
> *If* your DisplayServer should act as replacement for the console
> window,
> IMHO it should show the output of an Eu program in a similar way,
> especially
> - don't start with a new line after each call
> - interpret the "\n" as "newline" character.
>
> Also a button for clearing the window would be useful.
> You see, there is always room for improvement.
>
> Best regards,
> Juergen
>
> --
> Math problems? Call 1-800-[(10x)(13i)^2]-[sin(xy)/2.362x].
>
Hello again Juergen,
The practical advantage of something isnt always noticed
at first. Sometimes you have to use it a few times to
see the difference.
In particular, when you are debugging and you wish to see
variables over and over as you are doing something else in
your program, the console window gets slower sometimes
causing a delay in returning to the exw program. This is
a real pain when trying to debug. On the other hand,
after printing to the server it returns control to the calling
program very fast, so your program doesnt get interrupted.
The is especially true when trying to print data returned to
a Windows callback function.
To see the difference, try printing values passed to a window
procedure with the console, then with the server. The difference
is quite noticable. The server doesnt make the program skip a
beat, while the console sometimes delays the calling program by
a second or two.
Also, there's no reason why this program cant be updated
to allow changing fonts and format printing and stuff like
that. I already had ideas for multiple fonts and coloration.
If this turns out to be something anyone would like to see
in this just let me know.
Take care for now,
Al
7. RE: Al Getz Display Server
> jondolar wrote:
> > Al
> > This is not the problem. I start DisplayServer201 first, then my program
> >
> >
> > second. I printed the doc and read it about 10 times to make sure I was
> > doing everything right. By the way, I'm on win XP Pro. (I don't know if
> > this is relevant)
> >
> > Sincerly
> >
> > Serge
> >
>
> Hello again,
>
> I'll have to test the program in XP i guess and see what
> is going on.
>
> In the mean time, you can check the 'connect.ew' file to see
> that it is version 2.01 as well as the DisplayServer201.exe
> file. The older version wont work with some Windows versions.
>
> Also, dont you get any error message?
> Does the display server window even start up?
>
> Take care,
> Al
>
Hi Al
I do have version 201 for connect.ew and DisplayServer201.exw
DisplayServer does fire up properly prior to running my prog and is
sitting quietely on the task bar. I see no error messages whatsoever.
The usual window console opens and the output does not take place.
Hope this help your diagnosis.
Regards
Serge
8. RE: Al Getz Display Server
Al
I just notice that when I start DisplaySever201.exe, the title of the
window is..."Wondow Display Server Version 2.00". Did you just forget to
change the version number in the title or am I running version 2.00
disguised in 2.01 
. Perhaps you could check that.
Serge
9. RE: Al Getz Display Server
jondolar wrote:
>
>
> Al
> I just notice that when I start DisplaySever201.exe, the title of the
> window is..."Wondow Display Server Version 2.00". Did you just forget to
>
> change the version number in the title or am I running version 2.00
> disguised in 2.01 . Perhaps you could check that.
>
> Serge
>
Hello again Serge,
Yes, it's just an oversight on the version number that gets
shown in the title bar.
If you wish, you could put the following three lines into
the connect.ew file (using Notepad only) :
?hServer
?Identifier
?RegisteredMessage01
Then run DisplayServer and then your program with the
connect.ew file included.
If you tell me what three numbers get printed to the console
we might be able to tell what's wrong.
Amazingly, it runs just fine under Win98
and the DDE mem access method is very fast too.
Take care for now,
Al
10. RE: Al Getz Display Server
Al Getz wrote:
>
>
> jondolar wrote:
> >
> >
> > Al
> > I just notice that when I start DisplaySever201.exe, the title of the
> > window is..."Wondow Display Server Version 2.00". Did you just forget to
> >
> >
> > change the version number in the title or am I running version 2.00
> > disguised in 2.01 . Perhaps you could check that.
> >
> > Serge
> >
>
> Hello again Serge,
>
> Yes, it's just an oversight on the version number that gets
> shown in the title bar.
>
> If you wish, you could put the following three lines into
> the connect.ew file (using Notepad only) :
>
> ?hServer
> ?Identifier
> ?RegisteredMessage01
>
> Then run DisplayServer and then your program with the
> connect.ew file included.
> If you tell me what three numbers get printed to the console
> we might be able to tell what's wrong.
> Amazingly, it runs just fine under Win98
> and the DDE mem access method is very fast too.
>
> Take care for now,
> Al
>
Oh and, those three lines should be inserted at the very end of the
connect.ew file.
Take care for now,
Al
11. RE: Al Getz Display Server
> > Hello again Serge,
> >
> > Yes, it's just an oversight on the version number that gets
> > shown in the title bar.
> >
> > If you wish, you could put the following three lines into
> > the connect.ew file (using Notepad only) :
> >
> > ?hServer
> > ?Identifier
> > ?RegisteredMessage01
> >
> > Then run DisplayServer and then your program with the
> > connect.ew file included.
> > If you tell me what three numbers get printed to the console
> > we might be able to tell what's wrong.
> > Amazingly, it runs just fine under Win98
> > and the DDE mem access method is very fast too.
> >
> > Take care for now,
> > Al
> >
>
> Oh and, those three lines should be inserted at the very end of the
> connect.ew file.
>
> Take care for now,
> Al
>
Hi Al
those 3 lines at the end of connect.ew do not produce anything on the
console except my first "Hello".
I did....
include connect.ew
include get.e
integer wk
puts(1,"Hello")
wk = wait_key()
ServerPrint("Hello1")
ServerPrint("Hello2")
ServerPrint("Hello3")
Sorry
Serge
12. RE: Al Getz Display Server
Pete Lomax wrote:
>
>
> On Sun, 27 Jul 2003 13:32:55 +0000, jondolar <lavigne.s at videotron.ca>
> wrote:
>
> >Hi Pete
> >
> >I tried your little program on my Win XP machine and it seems to work
> >correctly. When I fire test.exw, I get a little witndow and a counter
> >incrementing and scroling up automatically on the left side of the RUN
> >button. If I press RUN, I get the win console with some various called
> >functions from win32. Closing the box produce essentially the same
> >effect with a longer list of called functions.
>
> Very droll.
>
> Never mind
> Pete
What's the matter Pete. Why do find that Funny ? Just trying to help.
Serge Lavigne
13. RE: Al Getz Display Server
jondolar wrote:
>
>
> > > Hello again Serge,
> > >
> > > Yes, it's just an oversight on the version number that gets
> > > shown in the title bar.
> > >
> > > If you wish, you could put the following three lines into
> > > the connect.ew file (using Notepad only) :
> > >
> > > ?hServer
> > > ?Identifier
> > > ?RegisteredMessage01
> > >
> > > Then run DisplayServer and then your program with the
> > > connect.ew file included.
> > > If you tell me what three numbers get printed to the console
> > > we might be able to tell what's wrong.
> > > Amazingly, it runs just fine under Win98
> > > and the DDE mem access method is very fast too.
> > >
> > > Take care for now,
> > > Al
> > >
> >
> > Oh and, those three lines should be inserted at the very end of the
> > connect.ew file.
> >
> > Take care for now,
> > Al
> >
> Hi Al
> those 3 lines at the end of connect.ew do not produce anything on the
> console except my first "Hello".
>
> I did....
>
> include connect.ew
> include get.e
> integer wk
> puts(1,"Hello")
> wk = wait_key()
>
> ServerPrint("Hello1")
> ServerPrint("Hello2")
> ServerPrint("Hello3")
>
> Sorry
>
> Serge
>
Hello again,
What you are telling me doesnt make that much sense because
when you put a question mark followed by a variable
into an include file at the top level after that variable
has at least been initialized means Euphoria does one of
two possible things:
1. opens a console and prints the variable value.
2. finds something wrong and prints an error message.
You might want to check to see that you have the three
lines at the very end of the connect.ew file and not
within a procedure.
All i was asking you to try was to
try to print those three variables at the end of the
connect file. This is a very basic Euphoria troubleshooting
technique. Do you understand this?
You might also try putting the include for the connect.ew file
last, just before your first ServerPrint() call.
Take care,
Al
14. RE: Al Getz Display Server
> > include connect.ew
> > include get.e
> > integer wk
> > puts(1,"Hello")
> > wk = wait_key()
> >
> > ServerPrint("Hello1")
> > ServerPrint("Hello2")
> > ServerPrint("Hello3")
> >
> > Sorry
> >
> > Serge
> >
>
> Hello again,
>
> What you are telling me doesnt make that much sense because
> when you put a question mark followed by a variable
> into an include file at the top level after that variable
> has at least been initialized means Euphoria does one of
> two possible things:
> 1. opens a console and prints the variable value.
> 2. finds something wrong and prints an error message.
>
> You might want to check to see that you have the three
> lines at the very end of the connect.ew file and not
> within a procedure.
>
> All i was asking you to try was to
> try to print those three variables at the end of the
> connect file. This is a very basic Euphoria troubleshooting
> technique. Do you understand this?
>
> You might also try putting the include for the connect.ew file
> last, just before your first ServerPrint() call.
>
>
> Take care,
> Al
>
Hi Al
I may not be the brightest programmer but what you asked me to do is
rather basic. I did EXACTLY as told. I even moved the include right
before ServerPrint() call as suggested. I have 3 copies of connect.ew,
one in my directory for DisplayServer, one in the Include directory and
a final one in my ProTest directory where I keep my test progs. I put
your 3 lines at the very end of each of them to make sure that whichever
one is used, it has the required code. The end result is the same. (even
if it does not make much sense to you)
Serge
15. RE: Al Getz Display Server
jondolar wrote:
>
>
> > > include connect.ew
> > > include get.e
> > > integer wk
> > > puts(1,"Hello")
> > > wk = wait_key()
> > >
> > > ServerPrint("Hello1")
> > > ServerPrint("Hello2")
> > > ServerPrint("Hello3")
> > >
> > > Sorry
> > >
> > > Serge
> > >
> >
> > Hello again,
> >
> > What you are telling me doesnt make that much sense because
> > when you put a question mark followed by a variable
> > into an include file at the top level after that variable
> > has at least been initialized means Euphoria does one of
> > two possible things:
> > 1. opens a console and prints the variable value.
> > 2. finds something wrong and prints an error message.
> >
> > You might want to check to see that you have the three
> > lines at the very end of the connect.ew file and not
> > within a procedure.
> >
> > All i was asking you to try was to
> > try to print those three variables at the end of the
> > connect file. This is a very basic Euphoria troubleshooting
> > technique. Do you understand this?
> >
> > You might also try putting the include for the connect.ew file
> > last, just before your first ServerPrint() call.
> >
> >
> > Take care,
> > Al
> >
> Hi Al
> I may not be the brightest programmer but what you asked me to do is
> rather basic. I did EXACTLY as told. I even moved the include right
> before ServerPrint() call as suggested. I have 3 copies of connect.ew,
> one in my directory for DisplayServer, one in the Include directory and
> a final one in my ProTest directory where I keep my test progs. I put
> your 3 lines at the very end of each of them to make sure that whichever
>
> one is used, it has the required code. The end result is the same. (even
>
> if it does not make much sense to you)
>
> Serge
>
Hello again,
Ok thanks.
What you could do next is put
printf(1,"%d\n",{1})
at the very START of the connect.ew file.
If the console doesnt open up now when you run your file
with the connect file included, then you have to be using
the wrong connect.ew file. That is, as you mentioned having
several copies, the wrong one must be running.
I'm pretty sure the only file you should have to
change is the one in the same directory as your exw file.
If you want, put some other stuff in there too to print to
the console window once it starts up.
As you said, this is very basic so you should be able to get
something to print to the console from the connect file.
Also, just a side note:
The Display Server doesnt WRITE to your processes memory,
it only READS it, so it's not likely that something is getting
overwritten.
BTW, did you try to run any of the demos first?
Take care for now,
Al
16. RE: Al Getz Display Server
>
> Hello again,
>
> Ok thanks.
> What you could do next is put
> printf(1,"%d\n",{1})
> at the very START of the connect.ew file.
> If the console doesnt open up now when you run your file
> with the connect file included, then you have to be using
> the wrong connect.ew file. That is, as you mentioned having
> several copies, the wrong one must be running.
> I'm pretty sure the only file you should have to
> change is the one in the same directory as your exw file.
> If you want, put some other stuff in there too to print to
> the console window once it starts up.
>
> As you said, this is very basic so you should be able to get
> something to print to the console from the connect file.
>
> Also, just a side note:
> The Display Server doesnt WRITE to your processes memory,
> it only READS it, so it's not likely that something is getting
> overwritten.
>
> BTW, did you try to run any of the demos first?
>
> Take care for now,
> Al
>
Now I'm getting somewhere. First thing first. To answer your question, I
did run your demos. The .exe demo both produce the little error window
"Couldn't connect to server......" but upon pressing OK works alright.
The 2 .exw work ok. I included printf(1,"%d\n",{1})at the beginning of
connect.ew. Now for my stuff:
--My code
include connect.ew
ServerPrint("Hello1")
ServerPrint("hello2"
--End code
Then...
Start DisplayServer201.exe
Start my prog TESTDISP.exw
Get a 1 on top of the window console plus the little error window
"Couldn't connect to server......"
Click the little window OK button (it disappears) then the window
console fills (after 1) with this:
1
0
2860
49623
c:\...........
Syntax error - expected to see possibly ')', not the end of file.
<end-of-file>
press enter...
Thanks for your patience.
Serge
17. RE: Al Getz Display Server
>From: Al Getz <Xaxo at aol.com>
>Subject: RE: Al Getz Display Server
>
>
>jondolar wrote:
> >
> >
> > Al
> > I just notice that when I start DisplaySever201.exe, the title of the
> > window is..."Wondow Display Server Version 2.00". Did you just forget to
> >
> > change the version number in the title or am I running version 2.00
> > disguised in 2.01 . Perhaps you could check that.
> >
> > Serge
> >
>
>Hello again Serge,
>
>Yes, it's just an oversight on the version number that gets
>shown in the title bar.
>
>If you wish, you could put the following three lines into
>the connect.ew file (using Notepad only) :
>
>?hServer
>?Identifier
>?RegisteredMessage01
I get:
459940
3764
49708
or something similar.
>Then run DisplayServer and then your program with the
>connect.ew file included.
>If you tell me what three numbers get printed to the console
>we might be able to tell what's wrong.
>Amazingly, it runs just fine under Win98
>and the DDE mem access method is very fast too.
However, when I press Scroll, or Write Text to Server, nothing show up on
the server. Also, there is no "Hello, I'm Connected" Oh, BTW, in the
Win32lib example, you should use setHandler(), not one of the onXXX event
handlers.
>Take care for now,
>Al
>
18. RE: Al Getz Display Server
jondolar wrote:
>
>
> > Hello again,
> >
> > Ok thanks.
> > What you could do next is put
> > printf(1,"%d\n",{1})
> > at the very START of the connect.ew file.
> > If the console doesnt open up now when you run your file
> > with the connect file included, then you have to be using
> > the wrong connect.ew file. That is, as you mentioned having
> > several copies, the wrong one must be running.
> > I'm pretty sure the only file you should have to
> > change is the one in the same directory as your exw file.
> > If you want, put some other stuff in there too to print to
> > the console window once it starts up.
> >
> > As you said, this is very basic so you should be able to get
> > something to print to the console from the connect file.
> >
> > Also, just a side note:
> > The Display Server doesnt WRITE to your processes memory,
> > it only READS it, so it's not likely that something is getting
> > overwritten.
> >
> > BTW, did you try to run any of the demos first?
> >
> > Take care for now,
> > Al
> >
> Now I'm getting somewhere. First thing first. To answer your question, I
>
> did run your demos. The .exe demo both produce the little error window
> "Couldn't connect to server......" but upon pressing OK works alright.
> The 2 .exw work ok. I included printf(1,"%d\n",{1})at the beginning of
> connect.ew. Now for my stuff:
>
> --My code
> include connect.ew
> ServerPrint("Hello1")
> ServerPrint("hello2"
> --End code
> Then...
> Start DisplayServer201.exe
> Start my prog TESTDISP.exw
> Get a 1 on top of the window console plus the little error window
> "Couldn't connect to server......"
> Click the little window OK button (it disappears) then the window
> console fills (after 1) with this:
> 1
> 0
> 2860
> 49623
> c:\...........
> Syntax error - expected to see possibly ')', not the end of file.
> <end-of-file>
> press enter...
>
> Thanks for your patience.
>
> Serge
>
Hi again Serge,
Thanks for your patience too, which has proved to be quite
more then mine i think
Anyway, the data you showed me is very informative, but
i still cant understand what's happening because the
server handle is 0 yet you are telling me you are still
seeing it work fine (even after the 'server not connected'
message).
That error message tells you that the connect.ew file couldnt
find the server, and with the server handle set to zero
any server prints should return quietly, not print anything to
the window. The reason for this is so that if you want to
leave the 'ServerPrint' calls in your program an also leave
the connect.ew file included in your program when there isnt
a server started your program will happily still truck along,
with the ServerPrint() call returning without doing anything.
The overhead time in this case is very slight, so it doesnt
matter that much. Then, if you decide later you want to
continue debugging your program all you have to do is fire
up the server and your program resumes sending data to it.
That was one of the original design concepts, as well as
to provide a 'void' file so that you dont have to remove
all of the 'ServerPrint()' statements and also dont have
to include much of a file (which adds very few bytes to the
bound executable).
Also, you're telling me that the .exe demos dont work
and the .exw demos do work, and that also doesnt make
sense.
All i can say at this point is i'll have to look at the problem
myself as soon as i can get on an XP machine and run the code.
Im not sure exactly when this will be yet.
In the mean time, if you feel like helping me debug this
i can send you files to try if you would like to do that.
In the future, i'll probably release a version that is
in clear source, if enough people feel this is interesting
enough.
You can also email me directly at xaxo at aol.com
Take care for now,
Al
19. RE: Al Getz Display Server
Elliott Sales de Andrade wrote:
>
>
> >From: Al Getz <Xaxo at aol.com>
> >Reply-To: EUforum at topica.com
> >To: EUforum <EUforum at topica.com>
> >Subject: RE: Al Getz Display Server
> >Date: Sun, 27 Jul 2003 15:34:22 +0000
> >
> >
> >jondolar wrote:
> > >
> > >
> > > Al
> > > I just notice that when I start DisplaySever201.exe, the title of the
> > > window is..."Wondow Display Server Version 2.00". Did you just forget to
> > >
> > > change the version number in the title or am I running version 2.00
> > > disguised in 2.01 . Perhaps you could check that.
> > >
> > > Serge
> > >
> >
> >Hello again Serge,
> >
> >Yes, it's just an oversight on the version number that gets
> >shown in the title bar.
> >
> >If you wish, you could put the following three lines into
> >the connect.ew file (using Notepad only) :
> >
> >?hServer
> >?Identifier
> >?RegisteredMessage01
>
> I get:
> 459940
> 3764
> 49708
> or something similar.
>
> >Then run DisplayServer and then your program with the
> >connect.ew file included.
> >If you tell me what three numbers get printed to the console
> >we might be able to tell what's wrong.
> >Amazingly, it runs just fine under Win98
> >and the DDE mem access method is very fast too.
>
> However, when I press Scroll, or Write Text to Server, nothing show up
> on
> the server. Also, there is no "Hello, I'm Connected" Oh, BTW, in the
> Win32lib example, you should use setHandler(), not one of the onXXX
> event
> handlers.
>
> >Take care for now,
> >Al
> >
>
Thanks Elliott.
There is no logical explanation yet how the connect file can
find the server and return a valid handle and still not
be able to write to it's window.
I'll have to look into this as soon as i can get on an XP
machine.
If you have time to try a few simple experiments i can send
some to try that will help determine what is happening.
Take care for now and thanks much,
Al
PS
i've been also using your GD library and have created a
new file viewer with it that is quite fast
20. RE: Al Getz Display Server
Pete Lomax wrote:
>
>
> On Mon, 28 Jul 2003 01:09:53 -0400, Elliott Sales de Andrade
> <quantum_analyst at hotmail.com> wrote:
>
> >
> > It appears that you are using a file name, or path, for something in
> >there. The IPC call uses Shared Memory. Somehow, the path you are giving
> >is
> >used as the name of the shared segment of memory. This is not allowed.
> I didn't know that. I've removed the path and put a revised version up
> I also cured the focus bug.
> <snip>
> >>The url is http://palacebuilders.pwp.blueyonder.co.uk/euphoria.html
> >>It is the last item on that page.
>
> Pete
>
Dont you have any original ideas to code?
Al
21. RE: Al Getz Display Server
>From: Al Getz <Xaxo at aol.com>
>Subject: RE: Al Getz Display Server
>
>
>Elliott Sales de Andrade wrote:
> >
> >
> > >From: Al Getz <Xaxo at aol.com>
> > >Reply-To: EUforum at topica.com
> > >To: EUforum <EUforum at topica.com>
> > >Subject: RE: Al Getz Display Server
> > >Date: Sun, 27 Jul 2003 15:34:22 +0000
> > >
> > >
> > >jondolar wrote:
> > > >
> > > >
> > > > Al
> > > > I just notice that when I start DisplaySever201.exe, the title of
>the
> > > > window is..."Wondow Display Server Version 2.00". Did you just
>forget to
> > > >
> > > > change the version number in the title or am I running version 2.00
> > > > disguised in 2.01 . Perhaps you could check that.
> > > >
> > > > Serge
> > > >
> > >
> > >Hello again Serge,
> > >
> > >Yes, it's just an oversight on the version number that gets
> > >shown in the title bar.
> > >
> > >If you wish, you could put the following three lines into
> > >the connect.ew file (using Notepad only) :
> > >
> > >?hServer
> > >?Identifier
> > >?RegisteredMessage01
> >
> > I get:
> > 459940
> > 3764
> > 49708
> > or something similar.
> >
> > >Then run DisplayServer and then your program with the
> > >connect.ew file included.
> > >If you tell me what three numbers get printed to the console
> > >we might be able to tell what's wrong.
> > >Amazingly, it runs just fine under Win98
> > >and the DDE mem access method is very fast too.
> >
> > However, when I press Scroll, or Write Text to Server, nothing show up
> > on
> > the server. Also, there is no "Hello, I'm Connected" Oh, BTW, in the
> > Win32lib example, you should use setHandler(), not one of the onXXX
> > event
> > handlers.
> >
> > >Take care for now,
> > >Al
> > >
> >
>Thanks Elliott.
>There is no logical explanation yet how the connect file can
>find the server and return a valid handle and still not
>be able to write to it's window.
>I'll have to look into this as soon as i can get on an XP
>machine.
>If you have time to try a few simple experiments i can send
>some to try that will help determine what is happening.
I have lots of time.....
>Take care for now and thanks much,
>Al
>
>PS
>i've been also using your GD library and have created a
>new file viewer with it that is quite fast
>
22. RE: Al Getz Display Server
Pete Lomax wrote:
>
>
> On Mon, 28 Jul 2003 16:12:38 +0000, Al Getz <Xaxo at aol.com> wrote:
>
> >Dont you have any original ideas to code?
> LOL. Actually it is just a bit of code I wrote last year, for an
> entirely different reason (so I could exec a program from MEditor
> without waiting for a result code, and hence preventing any further
> edits until the app closed, the purpose of my 'server' was to do that
> and fire a message back to MEditor should the app signal an error).
>
> The program is just a proof-of-concept test for that, flawed and
> unfinished. I just wondered if it worked on XP, as a possible
> alternative. BTW, is Display Server written in Eu?
>
> I shall cease and desist if you like
>
> Pete
>
It's just that i would have been happy to update the program
to include any ideas/suggestions. I suppose i could post
a clear source version at some point also...
BTW, the server starting technique was done to allow the
program to run normally it the server wasnt needed anymore,
but it would be just as easy to link to the shell execute
function and have it start up automatically, if that's really
what the user wanted to do. Myself, i didnt want that.
I wanted the server to start possibly from the start menu
and then it would be available at any time to any program,
including some C programs i run.
It also allows multiple clients etc.
I'll be testing on XP very soon so i should have the
XP problem resolved very soon.
Take care,
Al
23. RE: Al Getz Display Server
Elliott Sales de Andrade wrote:
> >If you have time to try a few simple experiments i can send
> >some to try that will help determine what is happening.
>
> I have lots of time.....
>
> >Take care for now and thanks much,
> >Al
Hello again Elliott,
Well thanks for taking the time to look at this, and if
you send me an email i can send you a program to try.
Not sure if i have your email address handy, and apparently
you cant post it on Topica for some reason...
Take care for now,
Al
24. RE: Al Getz Display Server
quantum_analyst at hotmail.com if you don't remember.
>From: Al Getz <Xaxo at aol.com>
>Subject: RE: Al Getz Display Server
>
>
>Elliott Sales de Andrade wrote:
>
> > >If you have time to try a few simple experiments i can send
> > >some to try that will help determine what is happening.
> >
> > I have lots of time.....
> >
> > >Take care for now and thanks much,
> > >Al
>
>Hello again Elliott,
>
>Well thanks for taking the time to look at this, and if
>you send me an email i can send you a program to try.
>Not sure if i have your email address handy, and apparently
>you cant post it on Topica for some reason...
>
>Take care for now,
>Al
>
25. RE: Al Getz Display Server
>I wrote:
>quantum_analyst at hotmail.com if you don't remember.
Oops, I meant to send that to your e-mail....
>>From: Al Getz <Xaxo at aol.com>
>>Subject: RE: Al Getz Display Server
>>
>>
>>Elliott Sales de Andrade wrote:
>>
>> > >If you have time to try a few simple experiments i can send
>> > >some to try that will help determine what is happening.
>> >
>> > I have lots of time.....
>> >
>> > >Take care for now and thanks much,
>> > >Al
>>
>>Hello again Elliott,
>>
>>Well thanks for taking the time to look at this, and if
>>you send me an email i can send you a program to try.
>>Not sure if i have your email address handy, and apparently
>>you cant post it on Topica for some reason...
>>
>>Take care for now,
>>Al
>>
>
26. RE: Al Getz Display Server
Juergen Luethje wrote:
>
>
> Hi Al, you wrote:
>
> > Juergen Luethje wrote:
> >>
> >>
> >> Hello Al, you wrote:
> >>
> >> <snip>
> >>
> >>> This is a very simple but VERY handy program, but
> >>> if any other problems come up, feel free to let me know
> >>> about them.
> >>
> >> I like the idea in general, and I like your program. Nevertheless,
> >> *for me* it has ATM no practical advantage over the console window.
> >>
> >> For my needs, the most important improvement would be, to make the text
> >> inside the window scrollable, so that your server can show much more
> >> lines than currently (say 500 -- but I think, Windows allows even more).
> >>
> >> Secondly, displaying the text in a non-proportional font (such as
> >> "Courier New") is IMHO more versatile, than using a proportional font.
> >> In a non-proportional font, also tables and ASCII art will be shown
> >> correctly.
>
> <snip>
>
> >> An advanced option also could be, that the user can choose a font.
> >>
> >> *If* your DisplayServer should act as replacement for the console
> >> window,
> >> IMHO it should show the output of an Eu program in a similar way,
> >> especially
> >> - don't start with a new line after each call
> >> - interpret the "\n" as "newline" character.
> >>
> >> Also a button for clearing the window would be useful.
> >> You see, there is always room for improvement.
> >>
> >> Best regards,
> >> Juergen
> >>
> >
> > Hello again Juergen,
> >
> > The practical advantage of something isnt always noticed
> > at first.
>
> I have no doubt about that.
>
> > Sometimes you have to use it a few times to
> > see the difference.
>
> It's not only a matter of the times I use it, but also a matter of
> how I use it.
>
> > In particular, when you are debugging and you wish to see
> > variables over and over as you are doing something else in
> > your program, the console window gets slower sometimes
> > causing a delay in returning to the exw program. This is
> > a real pain when trying to debug. On the other hand,
> > after printing to the server it returns control to the calling
> > program very fast, so your program doesnt get interrupted.
> > The is especially true when trying to print data returned to
> > a Windows callback function.
>
> I believe you, and I didn't say, that your progranm is useless or
> something like that.
>
> I wrote "*for me*", that has something to do with my personal needs.
> You can believe me, *I* know my needs.
>
> > To see the difference, try printing values passed to a window
> > procedure with the console, then with the server. The difference
> > is quite noticable. The server doesnt make the program skip a
> > beat, while the console sometimes delays the calling program by
> > a second or two.
> >
> > Also, there's no reason why this program cant be updated
> > to allow changing fonts and format printing and stuff like
> > that. I already had ideas for multiple fonts and coloration.
> >
> > If this turns out to be something anyone would like to see
> > in this just let me know.
>
> I already wrote some suggestions for improvement, and "Mr Trick" wrote,
> that he also would like to see a scrollbar.
>
> Best regards,
> Juergen
>
> --
> The difference between men and boys
> is the price of the toys.
>
Hello again Juergen,
Sorry, didnt mean to imply that you dont know your own needs
I've taken into consideration all the ideas and suggestions here
and i'll eventually incorporate them into the program.
I'll probably make a second and third version, so there will be
one short file for min debugging purposes, one debug version,
and one full blown version.
The short version takes up the smallest space in the executable,
so it doesnt matter much if it's left in or taken out, and if
you leave it in and have variables print out when someone else
uses the DisplayServer they can see your variables, whatever
you wanted them to see.
I'll probably start compiling a list of ideas and then start
implementing them one by one.
Take care for now,
Al
27. RE: Al Getz Display Server
Pete Lomax wrote:
>
>
> On Wed, 30 Jul 2003 05:41:51 +0200, Juergen Luethje <j.lue at gmx.de>
> wrote:
>
> >I already wrote some suggestions for improvement, and "Mr Trick" wrote,
> >that he also would like to see a scrollbar.
>
> I also think it would be quite cool to allow the application to pass a
> function which can be called by the display server to obtain the
> current values (and format) of selected named variables, and save the
> position for use in one session to the next, eg.
>
> integer v1
> integer init1 init1=0
> sequence v2
> integer init2 init2=0
>
> ...
> v1=??
> init1=1
> ...
>
> function ServerCallBack(sequence name)
> if equal(name,"v1") then
> if not init1 then return {"<no value>","%s"} end if
> return {v1,"%d"}
> end if
> if equal(name,"v2"......
> end function
> SetServerCallBack(routine_id("ServerCallBack"))
>
>
> Pete
>
Hello Pete,
Yes that sounds interesting too.
I was hoping to possibly have it execute strings too, which contain
formulae and stuff like that.
Since multiple clients are allowed, it might be an easy way to
pass data between them also, and share data without needing
to worry about synchronization and things like that.
Interestingly enough, any clients that connect are automatically
synchronized to the point where it is impossible for one client to
overwrite data while another client is reading. This makes some
tasks a whole lot easier
Take care for now,
Al
28. RE: Al Getz Display Server
- Posted by gertie at visionsix.com
Jul 31, 2003
On 31 Jul 2003, at 14:44, Al Getz wrote:
>
>
> Pete Lomax wrote:
> >
> >
> > On Wed, 30 Jul 2003 05:41:51 +0200, Juergen Luethje <j.lue at gmx.de>
> > wrote:
> >
> > >I already wrote some suggestions for improvement, and "Mr Trick" wrote,
> > >that he also would like to see a scrollbar.
> >
> > I also think it would be quite cool to allow the application to pass a
> > function which can be called by the display server to obtain the
> > current values (and format) of selected named variables, and save the
> > position for use in one session to the next, eg.
> >
> > integer v1
> > integer init1 init1=0
> > sequence v2
> > integer init2 init2=0
> >
> > ...
> > v1=??
> > init1=1
> > ...
> >
> > function ServerCallBack(sequence name)
> > if equal(name,"v1") then
> > if not init1 then return {"<no value>","%s"} end if
> > return {v1,"%d"}
> > end if
> > if equal(name,"v2"......
> > end function
> > SetServerCallBack(routine_id("ServerCallBack"))
> >
> >
> > Pete
> >
>
> Hello Pete,
>
> Yes that sounds interesting too.
> I was hoping to possibly have it execute strings too, which contain
> formulae and stuff like that.
Execute strings?!? Oh the horrors!
/me watches half the list faint.
> Since multiple clients are allowed, it might be an easy way to
> pass data between them also, and share data without needing
> to worry about synchronization and things like that.
> Interestingly enough, any clients that connect are automatically
> synchronized to the point where it is impossible for one client to
> overwrite data while another client is reading. This makes some
> tasks a whole lot easier
Oh my goddess, you have recreated win3.1!! Congrats, Al! Will it run on
dos,,,,,,, oh, nm, it won't, will it?
Kat
29. RE: Al Getz Display Server
gertie at visionsix.com wrote:
(snip a little)
> > I was hoping to possibly have it execute strings too, which
> >contain formulae and stuff like that.
>
> Execute strings?!? Oh the horrors!
> /me watches half the list faint.
>
Gee, sorry to scare you like that Kat
Maybe i meant something else....
What i meant was, to be able to execute something like:
y=x*x+2*x+3
and have it return the value of y. That's all really.
> > Since multiple clients are allowed, it might be an easy way to
> > pass data between them also, and share data without needing
> > to worry about synchronization and things like that.
> > Interestingly enough, any clients that connect are automatically
> > synchronized to the point where it is impossible for one client to
> > overwrite data while another client is reading. This makes some
> > tasks a whole lot easier
>
> Oh my goddess, you have recreated win3.1!! Congrats, Al! Will it
> run on
> dos,,,,,,, oh, nm, it won't, will it?
>
Not really sure what you mean there Kat, about the win3.1 part ?
Right now the basic communication is accomplished using
the win api's SendMessage() function, which might be callable
from Windows dos too.
> Kat
>
Take care for now,
Al
