Yincognito wrote: ↑May 8th, 2020, 7:43 pm
What could be the cause of that? Some rounding thing maybe? Is this the expected behavior? If not, could it be fixed or it's just something that I missed and everything should behave correctly otherwise?
This is more than likely a rounding issue when calculating the size of the meter (since no W or H is given on the string meter). If you put W=1100 on the Text meter, the movement stops.
I am not sure there is much we can due since D2D likes to work with DPI (device independent pixels), meaning fractional pixels which then get aliased by the GPU and converted to the device as "whole" pixels. We eventually want to work more with DPI's in our meters, so I am not sure we want to mess with this now.
Brian wrote: ↑May 8th, 2020, 7:59 pmThis is more than likely a rounding issue when calculating the size of the meter (since no W or H is given on the string meter). If you put W=1100 on the Text meter, the movement stops.
Ah, yes - didn't thought of setting the W value (although I remember using this trick over the years). I only tried setting X and Y to hardcoded values and it didn't change anything. Thanks for pointing this out.
Brian wrote: ↑May 8th, 2020, 7:59 pmI am not sure there is much we can due since D2D likes to work with DPI (device independent pixels), meaning fractional pixels which then get aliased by the GPU and converted to the device as "whole" pixels. We eventually want to work more with DPI's in our meters, so I am not sure we want to mess with this now.
-brian
Makes sense - no point in tweaking an "old" approach if you're going to adopt a "new" one anyway, eventually.
