|
|
Post by u9 on Apr 30, 2007 5:43:28 GMT -5
I see no difference in any of the functions wether i call mouse.update or not between every time i call the mouse functions such as leftbutton, dx, x etc.
Has the mouse.update become obselete?
|
|
|
|
Post by Guilect on Apr 30, 2007 17:39:12 GMT -5
I agree it seems not to be needed.
|
|
|
|
Post by u9 on May 5, 2007 5:38:35 GMT -5
Well, now i found out that sometimes i do need to call mouse.update... I don't wknow when yet..
|
|
|
|
Post by Guilect on May 5, 2007 7:35:03 GMT -5
According to MS DirectX info, you are supposed to call it in order to get updated DX,DY,DZ and button info.
While it does appear to work without it, I would leave it in, no harm to have it.
|
|
|
|
Post by u9 on May 6, 2007 8:09:55 GMT -5
I believe you are calling the update method yourself inside the mouse button functions?
|
|
|
|
Post by Guilect on May 6, 2007 12:12:51 GMT -5
That is true.
The mouseDX, DY and DZ used to be that way.
But usually you want to know both DX and DY, so by not having this call in each request it saves one call per call to DX and DY.
|
|
|
|
Post by u9 on May 8, 2007 3:45:27 GMT -5
But if i test for left and right button i again get two calls to update. I think either mouse.update should be called in all functions or none... or it should be explained in the documentation when update needs to be called.
As it is now people are likely to get confused (and have been) because mouse.update only sometimes needs to be called.
|
|
|
|
Post by Guilect on May 8, 2007 6:47:40 GMT -5
As everyone seems to prefer ease, I will make it so that you do not need to call mouse.update.
|
|
