Bruze, could this stem from the fact that FMP12 uses points rather then pixels?
I don't see how that would be related.
In my test I used control up arrow and control down arrow to move between the records in list view. $$N incremented by various amounts between 12 and 23.
At present with five records I can see these values for N
The last value that was entered is in record number 2. N = 849, however the data viewer is open and there N=858. The value of N in the data viewer has not been the same as the value of N displayed in the record at any time during the test.
When you resize the window $$N is recalculated on the fly and increments differently between FMP11 and 12.
Since this is no longer dependent on screen resolution in FMP12, that may be a cause.
But if this is not the answer, I'm clueless, it is strange behaviour indeed.
Increments 20 in v12.2 vs 5 in FM11.04 - for 'Inline Test' for me (MacBook Pro 2008 - 2.8 Core Duo)
But perceived speed in 12.2 much better (didn't see this to test until updated to 12.2 unfortunately)
Presume engineers optimised when FM evaluates/renders layout objects in 12.2 to make scrolling, layout nav snappier.