i'll have to concede for practical reasons thenby mennonite (no login)just because as you said, you feel certain you are right. just as i feel that you might not see what i see, there is always the very good chance you are considering a point i haven't thought of, and since you understand the language you're translating to (i really don't do gpp) then it's more likely. however, i probably will continue to write mouse programs that ignore most of the information your loop makes available, it's easier to code the loop that way, and if people complain the mouse is not responsive, i understand how to alter the mouseinput loop. it would probably be an issue in a graphics editor for instance. anyway thanks for listening and i'll return to my experiments with qb64 ("i "+chr$(3)+" 0.79") until i have another idea. thanks for the floating mouse coordinates by the way, that was cool. from IP address 193.200.150.23 |
| Response Title | Author and Date |
| There's no reason you couldn't code your own "getmouse" routine | on Jun 3 |
| isn't mousewheel just a button that you can click over and over? | mennonite on Jun 3 |
| oh except that it is also a button, not just a wheel | mennonite on Jun 3 |
| RE: Isn't the mouse wheel just a button? | on Jun 4 |
| * Wouldn't ABSOLUTE and INTERRUPT code ignore that? | on Jun 4 |
| *More mouse buttons than the normal 3? Oh! Those fancy ones with Back/Forward buttons? :-P | rpgfan3233 on Jun 4 |