1. Re: Bleeding Edge VEL bug? -- New Version of VEL
Wow, that was amazingly fast!! Thanks a ton for the hard work, everythings
working great now!
----- Original Message -----
From: Gary Dumer <dumer9354 at MY-DEJA.COM>
To: <EUPHORIA at LISTSERV.MUOHIO.EDU>
Sent: Monday, October 25, 1999 8:49 AM
Subject: Re: Bleeding Edge VEL bug? -- New Version of VEL
> Hi,
>
> I've uploaded a new version of the bleeding edge VEL to my WEB page at:
>
> http://personal.atl.bellsouth.net/atl/t/d/tdwalsh/
>
> The version corrects the problem below, plus a few minor glitches. It also
> adds a new attribute to the RICHEDITOR control. The attribute is
DELETELINE
> and allows the user to delete specific lines of code from the editor
> programmatically.
>
> The UPDOWN control now recognizes the ARROWKEYS attribute which, when set
> to TRUE, allows the user to use the up and down keyboard keys as well as
> the mouse to direct the UpDown control.
>
> I hope you enjoy it... Gary.
>
>
> Naflign <naflign at MEDIAONE.NET> wrote:
>
> >Hmmm......I've either found a bug in the bleeding edge version of VEL, or
> more likley I'm just missing something :) For some reason, it's getting
> upset when I try to use SetAttribute with an updown button. When I attemp
> to setattribute with an updown button, I am now getting a windows error
> message before the program starts, which says
> >"The specified attribute is invalid for the setattribute procedure"
> >
> >After being unable to figure out what was wrong in the little thing I'm
> writing, I went over and did a quick mod of the demo2, included in the
> normal VEL zip. Just changing the showform command to
ShowForm(Form1,MODAL)
> in order to get it compatable with the bleeding edge VEL. After doing so,
I
> noticed that it too had the same problem with the updown buttons that I'd
> been having before.
> >When SetAttribute(UpDown1,s) on line 80 of demo2 is removed, the error
> message no longer appears, so it's definitly this setattribue that's doing
> it. The question is whether it's something I didn't notice in the
> experimental.doc, or if it's an actual bug :)
> >
>
