Descriptive Problem Summary:
Mouse params screen-loc returns unexpected values.
Numbered Steps to Reproduce Problem:
1.Have object visible
2.Click left corner and check params.
3.Click right corner and check params.
Code Snippet (if applicable) to Reproduce Problem:
Any visible object will do.
Expected Results:
Absolute coordinates in screen-loc
Actual Results:
x:px,1:1 in lower left corner
x:px,32:32 in upper right
Does the problem occur:
Every time? Or how often? Y
In other games? Y
In other user accounts? Y
On other computers? Y
When does the problem NOT occur? Seems to be constant.
Did the problem NOT occur in any earlier versions? If so, what was the last version that worked?
WAS present in 512.1468 - my bad i only noticed the icon-y
Wasn't present in 512.1467 and before.
Workarounds: Not really.
ID:2470185
 May 25 2019, 3:34 am
|
|||||||||||||
Resolved
| |||||||||||||
|
May 25 2019, 10:46 am
|
|
Lummox JR
  |
A test project would be helpful.
|
Sure, i'll prepare one.
| |
Not much to it but test project here.
https://www.sendspace.com/file/gymas4 | |
I think I see what's going on here. The screen loc is supposed to be represented as TileX:PixelX , TileY:PixelY
It's currently (1469) showing up as TileX:TileY, PixelX:PixelY This runs contrary to pixel offsets for the screen_loc var which work as described above It is also possible to specify a pixel offset. Screen objects do not use pixel_x and pixel_y for this purpose, because it is intended that an object could exist on the map and in the screen object list simultaneously, so positioning must be independent. Pixel offsets are specified after a colon like this: "1:16,1:16". In this case the object is shifted to the northeast by 16 pixels. | |
Can confirm Bravo nailed it.
| |
Lummox JR resolved issue with message:
Another regression in 512.1468 involved the screen-loc mouse parameter: the X pixel offset and Y tile values were accidentally switched. | |