Download the demo:
Mouse proc parameters show inaccurate icon-x and icon-y values when interacting with a scaled atom in the vis_contents of a parent atom with KEEP_TOGETHER set.
This does, however, bring up another issue:
This is an ideal way to handle mouse catching, scaling up an invisible object to cover a specific area for UIs. The problem with that is that icon-x and icon-y are exposed to the developer with the scaling factored out. Because of the rounding, there is no way to tell how many pixels from the bottom-left of the visual x,y of the object as rendered on screen the mouse was interacting with the object.
This makes accurate mouse interaction with scaled up objects impossible, and necessitates two new mouse params: vis-x and vis-y, which should report the number of pixels from the bottom-left of the visible area of the icon as rendered on screen the mouse is currently resting. This means that if I scale up a 32x32 icon 10x, the range of vis-x and vis-y should be between 1 and 320.
Feature request incoming.
Apr 29, 12:28 am
Login to reply.