1. How's this for an error
D:\EUPHORIA\include\win32lib.ew:31228 in function fDoMouse()
type_check failure, lWheelPosn is -1.525
-- i get this message when i use the scroll wheel on my new Microsoft
Optical Cordless Mouse. I plug my old one in and the app works fine.
Perhaps Win32Lib should allow for a more generic object type for
lWheelPosn, the only thing i can think of is that the scroll on my new
mouse is more accurate in sending the scroll value message, or perhaps
this is due to the drivers??? any comments??
2. Re: How's this for an error
- Posted by Derek Parnell <ddparnell at bigpond.com>
Oct 21, 2004
-
Last edited Oct 22, 2004
spent memory wrote:
>
> D:\EUPHORIA\include\win32lib.ew:31228 in function fDoMouse()
> type_check failure, lWheelPosn is -1.525
>
> -- i get this message when i use the scroll wheel on my new Microsoft
> Optical Cordless Mouse. I plug my old one in and the app works fine.
> Perhaps Win32Lib should allow for a more generic object type for
> lWheelPosn, the only thing i can think of is that the scroll on my new
> mouse is more accurate in sending the scroll value message, or perhaps
> this is due to the drivers??? any comments??
Weird, yes. The value given by Windows for the wheel position is supposed
to be in multiples of 120. So I divide the raw value by 120 to give
the simple value. But of course, I used an integer to hold the result.
I've changed this now from
lWheelPosn /= 120
to
lWheelPosn = floor(lWheelPosn / 120)
Hope this still gives an accurate reading 
--
Derek Parnell
Melbourne, Australia
3. Re: How's this for an error
ok thanks Derek, where can i get a copy of your win32lib with this new
lWheelPosn? , is it on your website or are you planning on releasing
it in v.60.7?
On Thu, 21 Oct 2004 13:41:35 -0700, Derek Parnell
<guest at rapideuphoria.com> wrote:
>
> posted by: Derek Parnell <ddparnell at bigpond.com>
>
>
> spent memory wrote:
> >
> > D:\EUPHORIA\include\win32lib.ew:31228 in function fDoMouse()
> > type_check failure, lWheelPosn is -1.525
> >
> > -- i get this message when i use the scroll wheel on my new Microsoft
> > Optical Cordless Mouse. I plug my old one in and the app works fine.
> > Perhaps Win32Lib should allow for a more generic object type for
> > lWheelPosn, the only thing i can think of is that the scroll on my new
> > mouse is more accurate in sending the scroll value message, or perhaps
> > this is due to the drivers??? any comments??
>
> Weird, yes. The value given by Windows for the wheel position is supposed
> to be in multiples of 120. So I divide the raw value by 120 to give
> the simple value. But of course, I used an integer to hold the result.
>
> I've changed this now from
> lWheelPosn /= 120
> to
> lWheelPosn = floor(lWheelPosn / 120)
>
> Hope this still gives an accurate reading
>
> --
> Derek Parnell
> Melbourne, Australia
>
>
>
>
4. Re: How's this for an error
spent memory wrote:
> On Thu, 21 Oct 2004 13:41:35 -0700, Derek Parnell
> <guest at rapideuphoria.com> wrote:
> >
> > posted by: Derek Parnell <ddparnell at bigpond.com>
> >
> >
> > spent memory wrote:
> > >
> > > D:\EUPHORIA\include\win32lib.ew:31228 in function fDoMouse()
> > > type_check failure, lWheelPosn is -1.525
> > >
> > > -- i get this message when i use the scroll wheel on my new Microsoft
> > > Optical Cordless Mouse. I plug my old one in and the app works fine.
> > > Perhaps Win32Lib should allow for a more generic object type for
> > > lWheelPosn, the only thing i can think of is that the scroll on my new
> > > mouse is more accurate in sending the scroll value message, or perhaps
> > > this is due to the drivers??? any comments??
> >
> > Weird, yes. The value given by Windows for the wheel position is supposed
> > to be in multiples of 120. So I divide the raw value by 120 to give
> > the simple value. But of course, I used an integer to hold the result.
> >
> > I've changed this now from
> > lWheelPosn /= 120
> > to
> > lWheelPosn = floor(lWheelPosn / 120)
> >
> > Hope this still gives an accurate reading
> >
> > --
> > Derek Parnell
> > Melbourne, Australia
> >
> >
> ok thanks Derek, where can i get a copy of your win32lib with this new
> lWheelPosn? , is it on your website or are you planning on releasing
> it in v.60.7?
You have three choices:
(1) You wait til I release the next version (v0.61) in about a week.
(2) You use your favorite editor and make the change in fDoMouse().
(3) Goto (1)
--
Derek Parnell
Melbourne, Australia
5. Re: How's this for an error
Thanks Derek, no wories i changed it myself, thanx it works fine :)
On Fri, 22 Oct 2004 10:21:39 +1000, spent memory <spent.memory at gmail.com>
wrote:
>
>
> ok thanks Derek, where can i get a copy of your win32lib with this new
> lWheelPosn? , is it on your website or are you planning on releasing
> it in v.60.7?
>
> On Thu, 21 Oct 2004 13:41:35 -0700, Derek Parnell
> <guest at rapideuphoria.com> wrote:
> >
> > posted by: Derek Parnell <ddparnell at bigpond.com>
> >
> >
> > spent memory wrote:
> > >
> > > D:\EUPHORIA\include\win32lib.ew:31228 in function fDoMouse()
> > > type_check failure, lWheelPosn is -1.525
> > >
> > > -- i get this message when i use the scroll wheel on my new Microsoft
> > > Optical Cordless Mouse. I plug my old one in and the app works fine.
> > > Perhaps Win32Lib should allow for a more generic object type for
> > > lWheelPosn, the only thing i can think of is that the scroll on my new
> > > mouse is more accurate in sending the scroll value message, or perhaps
> > > this is due to the drivers??? any comments??
> >
> > Weird, yes. The value given by Windows for the wheel position is supposed
> > to be in multiples of 120. So I divide the raw value by 120 to give
> > the simple value. But of course, I used an integer to hold the result.
> >
> > I've changed this now from
> > lWheelPosn /= 120
> > to
> > lWheelPosn = floor(lWheelPosn / 120)
> >
> > Hope this still gives an accurate reading
> >
> > --
> > Derek Parnell
> > Melbourne, Australia
> >
> >
6. Re: How's this for an error
Derek Parnell wrote:
>
> spent memory wrote:
> > On Thu, 21 Oct 2004 13:41:35 -0700, Derek Parnell
> > <guest at rapideuphoria.com> wrote:
> > >
> > > posted by: Derek Parnell <ddparnell at bigpond.com>
> > >
> > >
> > > spent memory wrote:
> > > >
> > > > D:\EUPHORIA\include\win32lib.ew:31228 in function fDoMouse()
> > > > type_check failure, lWheelPosn is -1.525
> > > >
> > > > -- i get this message when i use the scroll wheel on my new Microsoft
> > > > Optical Cordless Mouse. I plug my old one in and the app works fine.
> > > > Perhaps Win32Lib should allow for a more generic object type for
> > > > lWheelPosn, the only thing i can think of is that the scroll on my new
> > > > mouse is more accurate in sending the scroll value message, or perhaps
> > > > this is due to the drivers??? any comments??
> > >
> > > Weird, yes. The value given by Windows for the wheel position is supposed
> > > to be in multiples of 120. So I divide the raw value by 120 to give
> > > the simple value. But of course, I used an integer to hold the result.
> > >
> > > I've changed this now from
> > > lWheelPosn /= 120
> > > to
> > > lWheelPosn = floor(lWheelPosn / 120)
I think using floor() actually makes it (slightly) faster.
> > >
> > > Hope this still gives an accurate reading
> > >
> > > --
> > > Derek Parnell
> > > Melbourne, Australia
> > >
> > >
> > ok thanks Derek, where can i get a copy of your win32lib with this new
> > lWheelPosn? , is it on your website or are you planning on releasing
> > it in v.60.7?
>
> You have three choices:
>
> (1) You wait til I release the next version (v0.61) in about a week.
I hope it doesn't break CJBN, it took me 3 weeks to get it working
with the latest release! Except for a few problems with controls
no longer being positioned properly and a small glitch
caused by NVIDIA nView, it seems to finally work!
Why is it that every other program works fine?...
> (2) You use your favorite editor and make the change in fDoMouse().
> (3) Goto (1)
Lol...
>
>
> --
> Derek Parnell
> Melbourne, Australia
>
7. Re: How's this for an error
it's not a factor of my program not being compatible, it's a factor of
the hardware interface of my new mouse. So in essence i believe using
my new mouse with other win32lib programs without the floor() will
crash those when i scroll aswell.
On Thu, 21 Oct 2004 17:58:28 -0700, CoJaBo <guest at rapideuphoria.com> wrote:
>
> posted by: CoJaBo <cojabo at suscom.net>
>
> Derek Parnell wrote:
> >
> > spent memory wrote:
> > > On Thu, 21 Oct 2004 13:41:35 -0700, Derek Parnell
> > > <guest at rapideuphoria.com> wrote:
> > > >
> > > > posted by: Derek Parnell <ddparnell at bigpond.com>
> > > >
> > > >
> > > > spent memory wrote:
> > > > >
> > > > > D:\EUPHORIA\include\win32lib.ew:31228 in function fDoMouse()
> > > > > type_check failure, lWheelPosn is -1.525
> > > > >
> > > > > -- i get this message when i use the scroll wheel on my new Microsoft
> > > > > Optical Cordless Mouse. I plug my old one in and the app works fine.
> > > > > Perhaps Win32Lib should allow for a more generic object type for
> > > > > lWheelPosn, the only thing i can think of is that the scroll on my new
> > > > > mouse is more accurate in sending the scroll value message, or perhaps
> > > > > this is due to the drivers??? any comments??
> > > >
> > > > Weird, yes. The value given by Windows for the wheel position is
> > > > supposed
> > > > to be in multiples of 120. So I divide the raw value by 120 to give
> > > > the simple value. But of course, I used an integer to hold the result.
> > > >
> > > > I've changed this now from
> > > > lWheelPosn /= 120
> > > > to
> > > > lWheelPosn = floor(lWheelPosn / 120)
> I think using floor() actually makes it (slightly) faster.
>
>
> > > > Hope this still gives an accurate reading
> > > >
> > > > --
> > > > Derek Parnell
> > > > Melbourne, Australia
> > > >
> > > >
> > > ok thanks Derek, where can i get a copy of your win32lib with this new
> > > lWheelPosn? , is it on your website or are you planning on releasing
> > > it in v.60.7?
> >
> > You have three choices:
> >
> > (1) You wait til I release the next version (v0.61) in about a week.
> I hope it doesn't break CJBN, it took me 3 weeks to get it working
> with the latest release! Except for a few problems with controls
> no longer being positioned properly and a small glitch
> caused by NVIDIA nView, it seems to finally work!
> Why is it that every other program works fine?...
>
> > (2) You use your favorite editor and make the change in fDoMouse().
> > (3) Goto (1)
> Lol...
>
>
> > --
> > Derek Parnell
> > Melbourne, Australia
> >
>
>
>
>
8. Re: How's this for an error
spent memory wrote:
>
> it's not a factor of my program not being compatible, it's a factor of
> the hardware interface of my new mouse. So in essence i believe using
> my new mouse with other win32lib programs without the floor() will
> crash those when i scroll aswell.
If you applied the patch to win32lib.ew file, then any application that
*you* run which includes that file will also pick up the same fix. If you
have programs that use private copies of win32lib, then you will have
to patch each copy.
--
Derek Parnell
Melbourne, Australia
9. Re: How's this for an error
yeah sorry Derek that wasn't meant 4 u, was meant for cojabo and his comment :)
On Thu, 21 Oct 2004 19:27:09 -0700, Derek Parnell
<guest at rapideuphoria.com> wrote:
>
>
> posted by: Derek Parnell <ddparnell at bigpond.com>
>
> spent memory wrote:
> >
> > it's not a factor of my program not being compatible, it's a factor of
> > the hardware interface of my new mouse. So in essence i believe using
> > my new mouse with other win32lib programs without the floor() will
> > crash those when i scroll aswell.
>
> If you applied the patch to win32lib.ew file, then any application that
> *you* run which includes that file will also pick up the same fix. If you
> have programs that use private copies of win32lib, then you will have
> to patch each copy.
>
> --
>
>
> Derek Parnell
> Melbourne, Australia
>
>
>
>
