Archived

This topic is now archived and is closed to further replies.

Mouse Buttons giving me curry!!!

This topic is 5537 days old which is more than the 365 day threshold we allow for new replies. Please post a new topic.

If you intended to correct an error in the post then please contact us.

Recommended Posts

Howdy, I have implemented the wrapper files used in the DirectInput tutes found here and it all works sweet except for the mouse button down function. The problem is that yes it does say that the mouse button is down but it never changes its state from true so every frame it thinks the mouse button has been pressed after the first time you press it. Any help would be great.

Share this post


Link to post
Share on other sites
Without seeing your code it''s kind of hard to tell, but:

Are you trapping a button up event? I thought this was the only way to know (with a message) if the mouse button has been released.

Will

Share this post


Link to post
Share on other sites
Thanks for the reply, I had just figured it when you replied that the mouse button down was still firing throughout the framecount, in other words 1 click of the mouse may last for 12 frames or more and so my events were firing for 12 times. i just put a wait event in which waits until a mouse up message is recieved until it allows another mouse down event.

Cheers

Share this post


Link to post
Share on other sites