Re: win32lib v0.57.6 released

new topic     » goto parent     » topic index » view thread      » older message » newer message

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.
> >
> >
> >

new topic     » goto parent     » topic index » view thread      » older message » newer message

Search



Quick Links

User menu

Not signed in.

Misc Menu