ID:102974
 
Not a bug
BYOND Version:477
Operating System:Windows 7 Ultimate 64-bit
Web Browser:Firefox 3.6.10
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 forums.
Descriptive Problem Summary: The MouseEntered() proc currently works as described as far as the Atom version of it. The client version does not work as described. Instead of firing off when the mouse enters an object, it only fires off if you click on something.

Numbered Steps to Reproduce Problem:
1. Inject the code below into your project.
2. Move the mouse around.
3. Observe.
4. Click on a few objects.
5. Observe.

Code Snippet (if applicable) to Reproduce Problem:
client/MouseEntered(object, location, control, params)
if(object && location=="mapwindow.map")
usr.FacePlace(object)
else if(location=="mapwindow.map")
usr.FacePlace(location)

mob
proc
FacePlace(target)
src.dir=get_dir(src,target)


Expected Results: Firing off when the clients mouse enters an object.

Actual Results: Fires off when the client clicks on an object.

Does the problem occur:
Every time? Or how often? Every time.
In other games? Yes.
In other user accounts? Yes.
On other computers? Yes.

When does the problem NOT occur? This problem so far, has always occured.

Did the problem NOT occur in any earlier versions? If so, what was the last version that worked? (Visit http://www.byond.com/download/build to download old versions for testing.) Other versions didn't seem to have different effects from what I've tested so far.

Workarounds: Use atom/MouseEntered() instead.
As I said in that feature request, client/MouseEntered() is working fine for me.
Falacy wrote:
As I said in that feature request, client/MouseEntered() is working fine for me.

It's not liking me for some reason. v.v
This is a code problem, not a bug. You're using the wrong argument; the argument you should be using is control, not location.