1. Interesting VEL Error (But who will fix it?)
In a program made with VEL005, if you click on a control _and do not release_
and then move the mouse cursor off of the control and release the mouse
button, a crash will occur with the following message (or similar):
"C:\WINDOWS\DESKTOP\cpt\vel005\vel005.e:534 in function MyCallBack()
type_check failure, q is 4294967295
"^^^ call-back from Windows
"... called from C:\WINDOWS\DESKTOP\cpt\vel005\vel005.e:436 in procedure
ShowForm()
id = 1
"... called from C:\WINDOWS\DESKTOP\cpt\vel005\Demo1.exw:516"
This will even occur, as you can see, in the Demo programs.
Anyway, VEL rocks, and I hope it ends up being supported by someone... it
would be a shame to let something that great fade away.
2. Re: Interesting VEL Error (But who will fix it?)
RedWordSmith,
I discovered the 'bug' also, it is because the variables p and q in
MyCallBack() are defined as integers. Rename them to atoms and I'm sure the
error will not occur again. In VEL006 this will be updated (IF there will
be a VEL006, Gary ;)
^ |
/-\<|
On Sun, 19 Sep 1999 10:41:43 -0500, RedWordSmith
<redwordsmith at NIC.DREAMHOST.COM> wrote:
>In a program made with VEL005, if you click on a control _and do not
release_
>and then move the mouse cursor off of the control and release the mouse
>button, a crash will occur with the following message (or similar):
>
>"C:\WINDOWS\DESKTOP\cpt\vel005\vel005.e:534 in function MyCallBack()
>type_check failure, q is 4294967295
>
>"^^^ call-back from Windows
>
>"... called from C:\WINDOWS\DESKTOP\cpt\vel005\vel005.e:436 in procedure
>ShowForm()
> id = 1
>
>"... called from C:\WINDOWS\DESKTOP\cpt\vel005\Demo1.exw:516"
>
>This will even occur, as you can see, in the Demo programs.
>
>Anyway, VEL rocks, and I hope it ends up being supported by someone... it
>would be a shame to let something that great fade away.
3. Re: Interesting VEL Error (But who will fix it?)
Ad,
I concur with you. I was not aware that the params could ever be bigger than
a euphoria "integer"
Replace the line in VEL005 :
function MyCallBack (integer id, integer event, integer p, integer q)
with:
function MyCallBack (integer id, integer event, atom p, atom q)
This has fixed the bug on my system. Also to be on the safe side, I would
change your event procedure params too..
Hope this helps,
Greg Harris
----- Original Message -----
From: Ad Rienks <kwibus at DOLFIJN.NL>
To: <EUPHORIA at LISTSERV.MUOHIO.EDU>
Sent: Sunday, September 19, 1999 12:29 PM
Subject: Re: Interesting VEL Error (But who will fix it?)
> RedWordSmith,
>
> I discovered the 'bug' also, it is because the variables p and q in
> MyCallBack() are defined as integers. Rename them to atoms and I'm sure
the
> error will not occur again. In VEL006 this will be updated (IF there will
> be a VEL006, Gary ;)
>
> ^ |
> /-\<|
>
> On Sun, 19 Sep 1999 10:41:43 -0500, RedWordSmith
> <redwordsmith at NIC.DREAMHOST.COM> wrote:
>
> >In a program made with VEL005, if you click on a control _and do not
> release_
> >and then move the mouse cursor off of the control and release the mouse
> >button, a crash will occur with the following message (or similar):
> >
> >"C:\WINDOWS\DESKTOP\cpt\vel005\vel005.e:534 in function MyCallBack()
> >type_check failure, q is 4294967295
> >
> >"^^^ call-back from Windows
> >
> >"... called from C:\WINDOWS\DESKTOP\cpt\vel005\vel005.e:436 in procedure
> >ShowForm()
> > id = 1
> >
> >"... called from C:\WINDOWS\DESKTOP\cpt\vel005\Demo1.exw:516"
> >
> >This will even occur, as you can see, in the Demo programs.
> >
> >Anyway, VEL rocks, and I hope it ends up being supported by someone... it
> >would be a shame to let something that great fade away.
>
