Currently, the only way to get mouse coordinates is to trigger one of the six mouse related procedures and call the parameters through there. Unfortunately, I have found this to be far too inaccurate for a lot of the uses that I have tried it on. Unfortunately, calling a mouse procedures manually gives no parameters either, so there seems to be no workaround.
What I want, is a procedure, or some other way, to get mouse coordinates at any given point in time.
The main reason that I would like it is for my HUD Buttons Library. I have spent the last few days adding pixel movement to the "draggable screen objects" portion of my library and it would be awesome if I could use it properly. For now, it works okay, but not accurately enough.
ID:260803
 Oct 7 2009, 11:11 pm (Edited on Oct 12 2009, 10:23 am)
|
|
|
Oct 7 2009, 11:52 pm
|
|
Sonder
 |
Love it. Work of art.
|
Bump.
Maybe as a placeholder, we could have a procedure that returns the mouse's actual coordinates on the screen. This is currently easy to do via JavaScript but it comes out very slow. Something built in would be fantastical [si-wait, that's actually a word?]. Seriously, this is the only thing holding me back from some gorgeous HUD systems and would be ridiculously appreciated (at least by me). | |
I'm also searching for this functionality right now. I need it for an RTS pixel based HUD interface which is apparently out the window now.
ts | |
Tsfreaks wrote:
I'm also searching for this functionality right now. I need it for an RTS pixel based HUD interface which is apparently out the window now. I made a library that may help you. It will allow you to update your mouse coordinates (in pixels) at any point in time on any of up to four maps, and allows you to output screen and map coordinates as well. If you want to take a look, I can upload the library for you. There is a version in my member files, but it's old and buggy. There is also another library that specifically does pixel-based HUD interfaces. I could give you that as well, if you wish. The only reason I haven't released them or put them up as updates is that they are both completely reworked from the versions I released six months ago and their isn't any documentation for them. I have not tested either library on multiplayer so I am not sure how it will hold up in that respect. If you do use it, test it and let me know. | |
For a demonstration on single-player capabilities, check out Ultimate Jigsaw. Now, those are some extremes on the both of the libraries and limits, so I wouldn't expect that kind of use in multiplayer.
In the mean time, I can upload the libraries themselves in an hour or so, but tonight is my 21st birthday and everyone else is trying to get me hammered so I'll try and get some documentation going tomorrow. | |
heh... Happy Birthday... No rush. I don't suspect you will be in any condition to think for the next couple of days. ;)
ts | |
Here is the most updated versions that I have with me. It's a .rar that I keep on a flash drive and move from computer to computer at home. I just extract it into the lib folder.
There is some documentation for the Mouse Update library and it shouldn't be out of date from what I saw. The documentation on the other one is massively out of date and the datum's name has changed, though the general syntax should be intact. I'd read through the library itself before using the documentation. | |