64 bits faster but...

I’ve just received this email from one of my users:

[quote]64-bit WinTess is working fine after I uninstalled anti-virus software from my PC.
WOWWW! It is not double faster.
I run analysis on a quite complicated model. 64-bit took 7m 9s (429s) for 27 iterations while 32-bit took 22m 4s (1324s) for the exact same number of iterations. So, it is faster by 3.08 times!
Very impressive!

By the way, I can’t move the model using middle button on 64-bit version.[/quote]

It’s a pity that something as usual in CAD as moving an image by dragging middle (wheel) button is so difficult to do in Xojo 64 bits.
All the possibilities that Xojo shows about mouse buttons are thought for OSX environment.

I have used the WndProcHelpers part of (I think) Aaron Ballman’s work to subclass a window and get events for Middle button and scroll wheels.

Essentially you subclass the window and direct windows events through a custom method.
if the W and LPARAMS match ones you are looking for ( eg MK_MBUTTON = 0x0010 ) then you do something with the values you get.
Otherwise you pass it on unhandled.

Should still work in 64bit land

[quote=236255:@Ramon SASTRE]It’s a pity that something as usual in CAD as moving an image by dragging middle (wheel) button is so difficult to do in Xojo 64 bits.
All the possibilities that Xojo shows about mouse buttons are thought for OSX environment.[/quote]

I think someone filed a bug report similar to this during the 2015r3 beta cycle and the issue ended up being incorrect declares.

Thanks Joe. I will revisit this subject.

Jeff,
I been using middle button perfectly with 32 bits. Using WndProc and others. But when I tried to transfer my code to 64 bits I failed completely. But as it was during beta versions, maybe it’s time to try again. Thanks anyway for your information.

[quote=236344:@Jeff Tullin]I have used the WndProcHelpers part of (I think) Aaron Ballman’s work to subclass a window and get events for Middle button and scroll wheels.

Essentially you subclass the window and direct windows events through a custom method.
if the W and LPARAMS match ones you are looking for ( eg MK_MBUTTON = 0x0010 ) then you do something with the values you get.
Otherwise you pass it on unhandled.

Should still work in 64bit land[/quote]