Descriptive Problem Summary:
If an user clicks on the border of their screen, the screen-loc parameter from the argument 'param' in Click() will not appear.
For example, here I'm clicking a red object that covers the entire screen and when clicked, it spits out the screen-loc: http://i.imgur.com/jMxFSc8.gif
It takes a bit to get the mouse in the correct spot, as its exactly in the border
I wasn't able to get this error working on the top and bottom borders of the screen and when creating a new project to test if this happened outside of ss13, the right side reproduced the error at first, but didn't want to later on for some reason ¯\_(ツ)_/¯
It happens with both objects and turfs, I didn't test with mobs.
unless this is intended then just close it or whatever
ID:1921075
 Aug 20 2015, 12:05 am
|
|||||||||||||
| |||||||||||||
|
Aug 20 2015, 12:29 am
|
|
Pomf123
 |
obviously this is a pebkac issue
|
The black edges around your map aren't actually part of the screen, they're simply padding, screen_loc extends from the bottom left of the map to the top right, not beyond.
I'm more surprised Click() is actually triggering at all out there. | |
I'm more surprised Click() is actually triggering at all out there. If it's padding at the edge of the map, it shouldn't be triggering a mouse proc at all. | |
Ter13 wrote:
I'm more surprised Click() is actually triggering at all out there. From my experience, it triggers mouseup, but not mousedown or Click. | |
so is this a bug or what
| |
bump
| |