Descriptive Problem Summary:

It seems that if you set maptext width above 32 pixels, and set mouse_opacity to 2 it expands the detection box to the width of the maptext instead of the width of the object.

Numbered Steps to Reproduce Problem:

1: Create an object, image, or probably anything else you can apply maptext to.

2: Set the aboves mouse_opacity to 2, and its maptext_width to 96.

3: Set up MouseEntered() to set its maptext to a non-null value, and set MouseExited() to null the maptext

4: Set up a row of the object, image, or whatever and move your mouse between them. If you're moving the mouse from right to left, it's fine. If you go left to right, it'll only change every 96 instead of 32, even if the thing with maptext is only 32.

Code Snippet (if applicable) to Reproduce Problem:


Expected Results: To be able to create maptext that exceeds 32 pixels in length, without having the MouseEntered() detection box increased beyond a width of 32 pixels.

Actual Results: Lengthy maptext screws up the boundaries for mouse detection.

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

When does the problem NOT occur? When you do not set mouse_opacity to 2.

Did the problem NOT occur in any earlier versions? If so, what was the last version that worked? Probably applies to all versions.

Workarounds: There's probably a couple. The main one off the top of my head would be making sure the icon fills enough space for mouse_opacity to not need to be set to 2.



Notes: I know this is probably pretty minor, I'm not 100% sure this is a bug, but I could see it causing a lot of problems for new developers, and maybe even experienced ones if the right need comes up; so reporting this just for good measure.