Feeling free to comment here ;-)....heheby (Login MystikShadows)R So far so good Galleon, looks like good standard support is plan so far. ;-). The likes of which we'd probably expect to see. Here's a question/suggestion depending on your answer ;-). WHen you're calling these do they represent actual wait states like inkey$ or do the essentially poll for mouse events so to speak? The reason I ask is because when creating for example a GUI project. if the mouse statements could just see if there's something and keep on keeping on with the rest of the program it would be much easy for the GUI builders to attempt things like multitasking if they want. Let me know for now. Also, One thing I always thought, for a long time now, which any and all mouse code should have is a means of returning a very consecutive set of events. For example if I click the mouse button at 100,100 keep it clicked and move the mouse to 200,200 and release the button, having a Selected Event return, somehow, the starting X,y and ending X,y somewhere. I think this should be part of a standard set of mouse events, especially today, especially in a windows environment. I'm sure we could all see a use for that too ;-). hehe Text or Graphic could make use of this I think....;-)...now, it could be in a mouse toolkit perhaps....doesn't have to be an intrinsic part of the language, but I think it would be a cool to have feature. :-). Otherwise, mouse support is deifnitaly on the right track. from IP address 69.205.201.142 |
| Response Title | Author and Date |
| You are referring to AX = 5 for press and AX = 6 for release | on Apr 28 |