1. More GUI stuff
FWIW &FYI:
I have posted a copy of a very primitive "windoz" pkg to
my web page. This is pre-pre alpha, but it does *do*
something. Someone asked about a GUI interface to
a database, so I did that, just so we could experiment
with something more than just moving windows around.
At present, you can drag/hide/show windows, enter
and save data, use wallpaper, and a few more things.
No minimize/maximize yet, and it does not automatically
move from input field 1 to field 2.... et and cetera. You
have to click on a new field to begin editing.
Gotta fix that - maybe next week.
No tricks are used to improve speed, but if anyone
wants to add some, feel free. Oh -- it is set up for mode
256 (vesa). In mode 19, everything is REALLY BIG.
Irv
http://www.mindspring.com/~mountains
filename is windoz.zip, about 40k
2. Re: More GUI stuff
Irv wrote:
>I have posted a copy of a very primitive "windoz" pkg to
>my web page.=20
I downloaded it last night. I am *very* impressed. It's much less =
primitive than you make it out to be. Very readable code. No doubt about =
it, I'm going to have to use inheritance.=20
I read the warning in the README before running the code. Good thing I =
did, because SVGA modes cause my machine to lock up (I hope someone can =
find Robert a "safe" SVGA test). I changed the resolution to mode 18 and =
it worked just fine - except for the colors, of course. You might want =
to set that as the default video mode.
After going your code examples, I see what Ralf was trying to get =
through my thick skull. :)
I've been unsure exactly how to approach inheritance. All the GUI =
libraries I've looked at use it extensively, and your code is an =
excellent source. Thanks for posting it! [Sound of code being pilfered]
One small nit - multiple assignments on a line are confusing, because =
they look like a C-like comparison is going on.
Bravo!
[WinMan Status]
I've been hammering away at WinMan for the last couple of evenings, =
retrofitting it with a new graphic engine. It's 98% done - I just need =
to take care of some mouse droppings, and junk left on the screen after =
the menus are erased. Visually, there's nothing new to see. Internally, =
it's a whole new ballgame, with support for all the graphic modes, =
color, better font handling and the like. The graphic kernel is based on =
BitBlt, so it's much more rational. Like Irv's code, though, =
optimizations should be added later, for you folks with 386s.
[Win32Lib Status]
Sorry, all - I've been spending all my time on WinMan. If there is a bug =
that's hanging you up, drop me a note and I'll try to take care of it =
ASAP. I'm going to be sticking to WinMan for a while.
[Minor Complaint for Rob]
Here's a nit about the Euphoria error message:
Subscript value <n> is out of bounds, reading from a length-<n> =
sequence.
always confuses me, because it initially looks like there is a negative =
length to the sequence. I *think* that there are other similar messages =
that also use a leading hypen before numbers.
Thanks!
-- David Cuny
I changed the video mode to 18, and it worked just fine. Modes > 19 =
cause my machine freeze up, so thanks for the warning - but could you =
default it to mode 18?
>>something. Someone asked about a GUI interface to
>>a database, so I did that, just so we could experiment
>>with something more than just moving windows around.
>>
>>At present, you can drag/hide/show windows, enter
>>and save data, use wallpaper, and a few more things.
>>No minimize/maximize yet, and it does not automatically
>>move from input field 1 to field 2.... et and cetera. You
>>have to click on a new field to begin editing.
>>Gotta fix that - maybe next week.
>>
>>No tricks are used to improve speed, but if anyone
>>wants to add some, feel free. Oh -- it is set up for mode
>>256 (vesa). In mode 19, everything is REALLY BIG.
>>
>>Irv
>>
>>http://www.mindspring.com/~mountains
>>filename is windoz.zip, about 40k
>>End of message
3. Re: More GUI stuff
At 10:24 AM 4/28/98 -0700, David Cuny wrote:
>Irv wrote:
>
>>I have posted a copy of a very primitive "windoz" pkg to
>>my web page.
>
>I downloaded it last night.
<snip>
You'll want to download it again. I made *several* changes
this morning to remove *undocumented features* (thanks,
Bill Gates, for the euphemism -- hope I didn't violate a trademark)
>I read the warning in the README before running the code. Good thing I
>did, because SVGA modes cause my machine to lock up (I hope someone can =
>find Robert a "safe" SVGA test). I changed the resolution to mode 18 and =
>it worked just fine - except for the colors, of course. You might want =
>to set that as the default video mode.
>
I'll try that.
>[Minor Complaint for Rob]
>
>Here's a nit about the Euphoria error message:
>
> Subscript value <n> is out of bounds, reading from a length-<n>
>sequence.
>
>always confuses me, because it initially looks like there is a negative =
>length to the sequence. I *think* that there are other similar messages =
>that also use a leading hypen before numbers.
>
Me too! It makes me think an index has run away.
Irv
4. Re: More GUI stuff
>I have posted a copy of a very primitive "windoz" pkg to
>my web page. This is pre-pre alpha, but it does *do*
>something.
Primitive you said?. What's your idea of a sophisticated thing then?
It looks great!
>At present, you can drag/hide/show windows, enter
>and save data, use wallpaper, and a few more things.
Just a minor suggestion: When moving the second window (in the dbf example)
the first one is redrawn before doing anything else. I would redraw it after
moving the second window.
>No minimize/maximize yet, and it does not automatically
>move from input field 1 to field 2.... et and cetera. You
>have to click on a new field to begin editing.
>Gotta fix that - maybe next week.
Just add tabbing would do the work. Don't it?
Jesus-
5. Re: More GUI stuff
>[Win32Lib Status]
>Sorry, all - I've been spending all my time on WinMan. If there is a bug
that's >hanging you up, drop me a note and I'll try to take care of it ASAP.
I'm going to be >sticking to WinMan for a while.
(Please, give me a clue just to solve the white text background over the
coloured window... if not too complicated).
Thanks. Jesus.
6. Re: More GUI stuff
Jesus wrote:
>(Please, give me a clue just to solve the white text background over =
the
>coloured window... if not too complicated).
I *thought* that setBackColor() would have taken care of it. There may =
be an issue with how I actually set the colors, since I'm doing some =
sneaky stuff behind the scenes. Most of that code has been thrown out in =
the next release.
You can probably hack a solution by calling SetBkMode (not implemented =
in Win32Lib, but easy to add) and setting the mode to TRANSPARENT. I =
haven't had a chance to try it.
Sorry the release is taking so long.
-- David Cuny
7. Re: More GUI stuff
At 10:24 AM 4/28/98 -0700, David Cuny wrote:
>I read the warning in the README before running the code.
>Good thing I did, because SVGA modes cause my machine to >lock up (I hope
someone can find Robert a "safe" SVGA test).
>I changed the resolution to mode 18 and it worked just fine - >except for
the colors, of course. You might want
>to set that as the default video mode.
>
I considered that, but I really like to use bmps to decorate
things, and they don't look good in only 16 colors. Well,
some can be converted ok, others can't. Mode 19 works
ok, especially if you have poor vision, because everything
is REALLY BIG.
Anyway, once I get more gadgets working, I'll consider
putting in some code to allow choosing the mode and
palette. (I are easily confused)
Irv
8. Re: More GUI stuff
At 04:58 PM 4/28/98 -0400, you wrote:
>---------------------- Information from the mail header -----------------------
>Sender: Euphoria Programming for MS-DOS <EUPHORIA at
>MIAMIU.ACS.MUOHIO.EDU>
>Poster: Irv <irv at ELLIJAY.COM>
>Subject: Re: More GUI stuff
>-------------------------------------------------------------------------------
>
>At 10:24 AM 4/28/98 -0700, David Cuny wrote:
>
>>I read the warning in the README before running the code.
>>Good thing I did, because SVGA modes cause my machine to >lock up (I hope
>someone can find Robert a "safe" SVGA test).
>>I changed the resolution to mode 18 and it worked just fine - >except for
>the colors, of course. You might want
>>to set that as the default video mode.
>>
Here I am replying to my own message. But I changed
the code to use mode 18. BMPs look horrible, but I posted
the code for anyone who can't use mode 256.
I'll have both available tomorrow.
Irv
>
>Irv
>
