1. Win32Lib Docs
Just a note for people who are just beginning to use Dave Cuny's =
Win32Lib. In the documentation, the controls LText, RText, and CText (? =
- I can't remember the one for center) are best described as static text =
controls, not line edits. To create a line edit box, you need to use =
the EditText control. This isn't mentioned in the docs, but you can =
find it in the example programs that are included in the package. Also, =
for multiple windows, don't forget that UnloadWindow is only for the =
main window. If you use it on any other windows, it kills your program. =
You should SetText(control,"") for each EditText control and =
setVisible(window,0) to get rid of any windows you don't need.
[David]
As much as I would like to see win32lib finished, I appreciate all the =
effort you've been putting into the Euphoria community as a whole =
without compensation. Take care of yourself and don't burn yourself =
out. Then who would finish it? :)
Michael J. Sabal
mjs at osa.att.ne.jp
http://home.att.ne.jp/gold/mjs/
2. Re: Win32Lib Docs
- Posted by Hawke <mdeland at NWINFO.NET>
Aug 17, 1998
-
Last edited Aug 18, 1998
Michael Sabal wrote:
> [David]
> As much as I would like to see win32lib finished,
> I appreciate all the effort you've been putting
> into the Euphoria community as a whole without
> compensation. Take care of yourself and don't
> burn yourself out. Then who would finish it? :)>
> Michael J. Sabal
I'd like to wholeheartedly echo this eloquently
stated sentiment as a P.S. to my last post, and
also apply it to several others as well...
3. Re: Win32Lib Docs
- Posted by David Cuny <dcuny at LANSET.COM>
Aug 17, 1998
-
Last edited Aug 18, 1998
Hawke wondered if I was ever getting around to Win32Lib again.
Yesh, I *do* plan an taking a look at Win32Lib, once my poor head starts
hurting from all this C programming (the horror! the horror!). I'll have to
get used to *not* placing a semicolon at the end of every line, and the
transition back from // to -- comments won't be no fun, neither. 
Rumour had it that someone else (names omitted to protect the potentially
guilty) might perhaps maybe be releasing a visual Win32 library in the near
future. Is there truth to this rumour? If so, would that [unnamed]
hypothetical person be willing to verify this (via private e-mail) to me, so
I can decide if I need to start looking at a visual interface to Win32Lib
(I'm not promising nothing!), or if Win32Lib will soon become obsolete?
Thanks!
-- David Cuny
4. Re: Win32Lib Docs
David Cuny wrote:
>
> Hawke wondered if I was ever getting around to Win32Lib again.
>
> Yesh, I *do* plan an taking a look at Win32Lib, once my poor head starts
> hurting from all this C programming (the horror! the horror!).
Don't say you weren't warned ;)
[VISUAL WIN32]
> (I'm not promising nothing!), or if Win32Lib will soon become obsolete?
Whether there is a VisualEuphoria or not, it will still have to write
some
windows code. Hopefully, it will call Win32lib - not the API directly. I
would like to be able to *read* the resulting programs. Maybe even
modify
them.
So, please do not let the possible Visual stuff affect what you do.
On the other hand, the Visual stuff may not be practical without
Win32Lib!
I was wondering, however: would it help if someone divided the Win32Lib
into
pieces that could be worked on independently? It's already big, and will
get bigger. Breaking it up would make it possible to add lots of
comments
and documentation, and perhaps simplify maintenance later on.
Just a thought..
Irv
5. Re: Win32Lib Docs
David:
> Yesh, I *do* plan an taking a look at Win32Lib,
Welcome back to Win32lib, (and sorry for Gnuphoria..)
Could you please priorize the control formatting issue?.
I'd like to have controls responding (to, i.e. setFont) the same way the
window does:
fontSize = 9 -- initialize
setFont( thisButton, "Arial", fontSize, 1 )
That will improve a lot the general aspect of all our applications.
Thanks
Jesús Consuegra
