1. win32lib v0.57.6 released
Thanks again to all the people who are helping make this library so useful.
I've placed v0.57.6 onto the website for your inspection.
http://www.users.bigpond.com/ddparnell/euphoria/w320576.zip
The changes this week included...
Fixes
--------
Using relative widths for panel sizes in a Statusbar no longer crashes when
using non-integer values.
Enhancements
--------------
wPuts() and drawText() can also supply the text as a RAM address rather than
a sequence.
setHandler() can now add routines to form a chain to execute when an event
is triggered.
Additions
--------------
selectDirectory() function. Uses a dialog to allow user to select a
directory.
drawText() is now implemented.
tk_mem:zStringLength() function returns the length of a zero-delimited
string given its address.
invokeHandler() function to trigger a win32lib event.
getReturnValue() function to get the value that will be returned to Windows.
onXXX() function to turn on/off the support for onXXX[] syntax. Turning this
is off results in faster event handling.
getHandler(). Returns the routines set up for event handling.
Known Bugs
----------------
* There is a serious resource leakage with the drawLines() routine.
* Tooltips are not working for buttons in a FlatToolBar control.
----------
Derek.
2. Re: win32lib v0.57.6 released
Derek,
I like the new, un-cluttered look of the 57.6!
It does present a problem for running the demos, though, which is how I
usually first test a new version of Win32Lib. Previously when you released
a new version, it could be tested in its own directory without putting it &
its includes into the Euphoria "include" folder. Now some demos won't run
from their new folder without doing that first, and the ones that do run are
not running the new version, but rather whatever is in the "include" folder.
I'm not sure what would solve this, as you can't just hard code the "include
win32lib.ew" into each demo with the path of the new win32lib, since it's
not known where the user put it, and I don't *think* relative paths work,
though I could be wrong.
Any thoughts?
One way this could be possibly be addressed is to put "RunDemos.exw" into
the base folder with win32Lib.ew, & just run the demos from it, (since
that's its purpose, grin), because it can store path info for running demos;
but I'm not sure yet whether the demos themselves would run from the new
Win32Lib or from the "include" folder. I'll look into what I could do with
RunDemos to allow running the demos from sub-folders using the "base"
version of Win32Lib rather than the "include" folder version.
And I see that the "readme" file needs to inform the new user that
win32lib.ew & its includes need to be put into the Euphoria include folder.
Maybe that readme file also needs to be in the base folder? Just a thought,
don't want to destroy the nice uncluttered look!
Dan Moyer
----- Original Message -----
From: "Derek Parnell" <ddparnell at bigpond.com>
To: "EUforum" <EUforum at topica.com>
Sent: Sunday, May 19, 2002 11:11 AM
Subject: win32lib v0.57.6 released
>
> Thanks again to all the people who are helping make this library so
useful.
>
> I've placed v0.57.6 onto the website for your inspection.
>
> http://www.users.bigpond.com/ddparnell/euphoria/w320576.zip
>
> The changes this week included...
>
> Fixes
> --------
> Using relative widths for panel sizes in a Statusbar no longer crashes
when
> using non-integer values.
>
> Enhancements
> --------------
> wPuts() and drawText() can also supply the text as a RAM address rather
than
> a sequence.
>
> setHandler() can now add routines to form a chain to execute when an event
> is triggered.
>
>
> Additions
> --------------
> selectDirectory() function. Uses a dialog to allow user to select a
> directory.
>
> drawText() is now implemented.
>
> tk_mem:zStringLength() function returns the length of a zero-delimited
> string given its address.
>
> invokeHandler() function to trigger a win32lib event.
>
> getReturnValue() function to get the value that will be returned to
Windows.
>
> onXXX() function to turn on/off the support for onXXX[] syntax. Turning
this
> is off results in faster event handling.
>
> getHandler(). Returns the routines set up for event handling.
>
> Known Bugs
> ----------------
> * There is a serious resource leakage with the drawLines() routine.
> * Tooltips are not working for buttons in a FlatToolBar control.
>
>
> ----------
> Derek.
>
>
>
>
3. Re: win32lib v0.57.6 released
I think I have a likely solution to this problem, using getcurrentdirectory
and putting a re-directing include into each demo, that's written by
RunDemos to have the path of the new Win32Lib in it...but I probably can't
do it right now 'cause my younger brother just had a mild heart attack & is
in the hospital. :(
Dan Moyer
----- Original Message -----
From: "Dan Moyer" <DANIELMOYER at prodigy.net>
To: "EUforum" <EUforum at topica.com>
Subject: Re: win32lib v0.57.6 released
>
> Derek,
>
> I like the new, un-cluttered look of the 57.6!
>
> It does present a problem for running the demos, though, which is how I
> usually first test a new version of Win32Lib. Previously when you
released
> a new version, it could be tested in its own directory without putting it
&
> its includes into the Euphoria "include" folder. Now some demos won't run
> from their new folder without doing that first, and the ones that do run
are
> not running the new version, but rather whatever is in the "include"
folder.
>
> I'm not sure what would solve this, as you can't just hard code the
"include
> win32lib.ew" into each demo with the path of the new win32lib, since it's
> not known where the user put it, and I don't *think* relative paths work,
> though I could be wrong.
>
> Any thoughts?
>
> One way this could be possibly be addressed is to put "RunDemos.exw" into
> the base folder with win32Lib.ew, & just run the demos from it, (since
> that's its purpose, grin), because it can store path info for running
demos;
> but I'm not sure yet whether the demos themselves would run from the new
> Win32Lib or from the "include" folder. I'll look into what I could do
with
> RunDemos to allow running the demos from sub-folders using the "base"
> version of Win32Lib rather than the "include" folder version.
>
> And I see that the "readme" file needs to inform the new user that
> win32lib.ew & its includes need to be put into the Euphoria include
folder.
> Maybe that readme file also needs to be in the base folder? Just a
thought,
> don't want to destroy the nice uncluttered look!
>
> Dan Moyer
>
>
> ----- Original Message -----
> From: "Derek Parnell" <ddparnell at bigpond.com>
> To: "EUforum" <EUforum at topica.com>
> Sent: Sunday, May 19, 2002 11:11 AM
> Subject: win32lib v0.57.6 released
>
>
> >
> > Thanks again to all the people who are helping make this library so
> useful.
> >
> > I've placed v0.57.6 onto the website for your inspection.
> >
> > http://www.users.bigpond.com/ddparnell/euphoria/w320576.zip
> >
> > The changes this week included...
> >
> > Fixes
> > --------
> > Using relative widths for panel sizes in a Statusbar no longer crashes
> when
> > using non-integer values.
> >
> > Enhancements
> > --------------
> > wPuts() and drawText() can also supply the text as a RAM address rather
> than
> > a sequence.
> >
> > setHandler() can now add routines to form a chain to execute when an
event
> > is triggered.
> >
> >
> > Additions
> > --------------
> > selectDirectory() function. Uses a dialog to allow user to select a
> > directory.
> >
> > drawText() is now implemented.
> >
> > tk_mem:zStringLength() function returns the length of a zero-delimited
> > string given its address.
> >
> > invokeHandler() function to trigger a win32lib event.
> >
> > getReturnValue() function to get the value that will be returned to
> Windows.
> >
> > onXXX() function to turn on/off the support for onXXX[] syntax. Turning
> this
> > is off results in faster event handling.
> >
> > getHandler(). Returns the routines set up for event handling.
> >
> > Known Bugs
> > ----------------
> > * There is a serious resource leakage with the drawLines() routine.
> > * Tooltips are not working for buttons in a FlatToolBar control.
> >
> >
> > ----------
> > Derek.
> >
> >
> >
4. Re: win32lib v0.57.6 released
Oh, ok, using EUINC in autoexec.bat does work under Eu2.3 to allow demos in
a sub-directory under the newest Win32Lib version to access & use it :) I
hadn't installed 2.3, so I also hadn't RTFM either.
But I did have a problem: after I set EUINC to the directory with Win23Lib
57.6 in it, & re-booted, my system hung up. After some moments of panic, I
used the emergency disk & rem'd that EUINC line out in autoexec.bat, & it
booted fine. I had put the set EUINC line last in autoexec.bat, after a set
PATH, and when I moved the set EUINC to *above* set PATH, it boots ok now.
Is that a known problem that I missed seeing in the doc, or is it a not
previously known problem, or has no one else ever had that problem besides
me?
Dan Moyer
----- Original Message -----
From: "Derek Parnell" <ddparnell at bigpond.com>
To: "EUforum" <EUforum at topica.com>
Sent: Sunday, May 19, 2002 8:13 PM
Subject: RE: win32lib v0.57.6 released
>
> Dan Moyer wrote:
> > Derek,
> >
> > I like the new, un-cluttered look of the 57.6!
> >
> > It does present a problem for running the demos, though, which is how I
> > usually first test a new version of Win32Lib. Previously when you
> > released
> > a new version, it could be tested in its own directory without putting
> > it &
> > its includes into the Euphoria "include" folder. Now some demos won't
> > run
> > from their new folder without doing that first, and the ones that do run
> > are
> > not running the new version, but rather whatever is in the "include"
> > folder.
> >
> > I'm not sure what would solve this, as you can't just hard code the
> > "include
> > win32lib.ew" into each demo with the path of the new win32lib, since
> > it's
> > not known where the user put it, and I don't *think* relative paths
> > work,
> > though I could be wrong.
> >
> > Any thoughts?
> >
> > One way this could be possibly be addressed is to put "RunDemos.exw"
> > into
> > the base folder with win32Lib.ew, & just run the demos from it, (since
> > that's its purpose, grin), because it can store path info for running
> > demos;
> > but I'm not sure yet whether the demos themselves would run from the new
> > Win32Lib or from the "include" folder. I'll look into what I could do
> > with
> > RunDemos to allow running the demos from sub-folders using the "base"
> > version of Win32Lib rather than the "include" folder version.
> >
> > And I see that the "readme" file needs to inform the new user that
> > win32lib.ew & its includes need to be put into the Euphoria include
> > folder.
> > Maybe that readme file also needs to be in the base folder? Just a
> > thought,
> > don't want to destroy the nice uncluttered look!
> >
> Hi Dan,
> thanks for the comment about its appearance. I did actually meant to
> mention that in the release notes but I was rushed (had to catch a
> plane).
>
> Anyhow, the solution is simple enough. Using Euphoria v2.3 onwards, add
> to the DOS environment symbol EUINC, the directory where win32lib is
> installed. For example mine looks like...
>
> set EUINC=F:\Projects\EUInc;D:\Win32lib\Current;H:\EuContribs
>
> and I install the latest version of the library under
> D:\Win32Lib\Current
>
> -------
> Derek.
>
>
>
>
5. Re: win32lib v0.57.6 released
Ray wrote:
<snip>
> Did you keep a copy of the autoexec.bat that failed to boot?
> Possibly somehow your autoexec.bat became currupt after it was
> modified???
No, not exactly, but in the original, I rem'd out the set EUINC, didn't have
the hang, then to test it, un-rem'd the same line, and it hung again. Seems
to suggest not corrupt file.
> When you say it failed to boot do you remember what the last piece
> of information was that was displayed on the screen?
Well, it just showed the Windows screen logo, and the drive stopped
accessing shortly after that point; with the set EUINC rem'd, it continued
on normally, & since it looked perfectly fine, I just re-rem'd it, &
re-wrote it above the set PATH, just to see what that would do, & it then
didn't hang, and the EUINC setting also functioned .
Dan Moyer
----- Original Message -----
From: "Ray Smith" <smithr at ix.net.au>
To: "EUforum" <EUforum at topica.com>
Sent: Monday, May 20, 2002 9:28 PM
Subject: RE: win32lib v0.57.6 released
>
>
> Dan Moyer wrote:
>
> [snip]
>
> > But I did have a problem: after I set EUINC to the directory with
> > Win23Lib
> > 57.6 in it, & re-booted, my system hung up. After some moments of
> > panic, I
> > used the emergency disk & rem'd that EUINC line out in autoexec.bat, &
> > it
> > booted fine. I had put the set EUINC line last in autoexec.bat, after a
> > set
> > PATH, and when I moved the set EUINC to *above* set PATH, it boots ok
> > now.
> >
> > Is that a known problem that I missed seeing in the doc, or is it a not
> > previously known problem, or has no one else ever had that problem
> > besides
> > me?
>
>
> I haven't actually installed the software but with over 12 years of
> experience playing with autoexec.bat and config.sys files it
> shouldn't matter where the "SET EUINC=???" line is in your
> autoexec.bat file.
> Did you keep a copy of the autoexec.bat that failed to boot?
> Possibly somehow your autoexec.bat became currupt after it was
> modified???
> When you say it failed to boot do you remember what the last piece
> of information was that was displayed on the screen?
> That might help indentify what the problem was.
>
> I'm glad it's working now!
>
> Regards,
>
> Ray Smith
> http://rays-web.com
>
>
>
>
6. Re: win32lib v0.57.6 released
- Posted by jluethje at gmx.de
May 21, 2002
Hello Derek,
you wrote:
> Thanks again to all the people who are helping make this library so useful.
> I've placed v0.57.6 onto the website for your inspection.
> http://www.users.bigpond.com/ddparnell/euphoria/w320576.zip
> [...]
Many thanks to you, and all others who contributed to Win32Lib!
I like the high level windows programming, that it makes possible.
Best regards,
Juergen
