RE: A nice window vs Win console
Mike wrote:
>
>
> Hi jondolar,
>
> You wrote:
> >=20
> > Al Getz wrote:=20
> > >=20
> > > You could also use the Display Server in the archive.
> --snip
> > > You can print anything you want
> --snip
> > > Take care,
> > > Al
> >=20
> > Hi al
> >=20
> > Thanks for your program. This is exactly what the doctor prescribed
> > 
.=
> =20
> >=20
> > I'm using the Meditor. I don't know if there are incompatibilities=20
> > between the two program but it does not seem to work. Here is my code
> > in=
> =20
> >=20
> > the Meditor:
> >=20
> >=20
> > include connect.ew
> > integer wk
> > ServerPrint("Hello")
> > wait_key()
> >=20
> > Then I start DisplayServer201.exe
> > come back to Meditor and press F5 to run.
> >=20
> > I end up on good old Windows console
> >=20
> > What I'm I missing?
> >=20
> > Thanks
> >=20
> > Serge Lavigne
> >=20
>
>
> When I wrote the editor (which Meditor is based on) I thought I was=20
> being clever by deliberately not providing for text files that had=20
> non-ACSII caharacters, ie, anything above char 127.
>
> I had a quick look at Al's DisplayServer bundle and noticed that this=20
> line is in connect.ew:
>
> MultiProcessMessageName=3D"DisplayWindowServerGlobalClass{=CC=C8=C9=CA-X295=
>
> 7-Y1523}"
>
>
> Meditor will corrupt it if the file is edited. Perhaps this is what
> has=20
> happened in which case you must restore the damage.
>
> Another possibility could be that that (the) Win32lib library used by=20
> Meditor *might* be interfering with Al's programs.
> I have noticed that when I am running a program through Meditor and I=20
> try to start some types of other applications, these will
> not execute until the first program has finished.
>
> If this anomaly is due to Win32lib then you should try another=20
> editor/program runner.
>
> Regards,
> Mike
>
Hello there,
I'll make a change in the next version to use all standard
characters. Thanks for bringing this up.
Take care,
Al
|
Not Categorized, Please Help
|
|
