ID:95460
 
Not a bug
BYOND Version:467
Operating System:Windows 7 Pro
Web Browser:Firefox 3.5.9
Applies to:DM Language
Status: Not a bug

This is not a bug. It may be an incorrect use of syntax or a limitation in the software. For further discussion on the matter, please consult the BYOND Developer forums.
Descriptive Problem Summary:
While working with certain mouse procedures, such as MouseExited() and MouseEntered(), if you attempt to grab the icon-x and icon-y, the values will always be null. But, if you were to use Click(), the icon-x and icon-y will provide you with the correct value.

Code Snippet (if applicable) to Reproduce Problem:
atom
MouseExited(atom/t, control, params)
params = params2list(params)
var/pixelx = text2num(params["icon-x"])
var/pixely = text2num(params["icon-y"])
world<<"MouseExited: ([pixelx], [pixely])"
Click(atom/t, control, params)
params = params2list(params)
var/pixelx = text2num(params["icon-x"])
var/pixely = text2num(params["icon-y"])
world<<"Click: ([pixelx], [pixely])"
MouseEntered(atom/t, control, params)
params = params2list(params)
var/pixelx = text2num(params["icon-x"])
var/pixely = text2num(params["icon-y"])
world<<"MouseEntered: ([pixelx], [pixely])"


Expected Results:
That the values of the icon-x and icon-y will not be null while using MouseEntered() and MouseExited().

Actual Results:
Click: (18, 7)
MouseEntered: (, )
MouseExited: (, )

Does the problem occur:
This problem occurs every time I move the mouse.
This is not a bug. The icon-x and icon-y params simply aren't available for all mouse procs.
Lummox JR wrote:
This is not a bug. The icon-x and icon-y params simply aren't available for all mouse procs.

May I ask why and do you have any plans to implement them into all mouse procedures? It would be fairly helpful seeing as we currently do not have 'mouse pixel recognition'.