API: TimeMap2_beatsToTime() vs. swing grid? (SOLVED BY SCRIPT)

[nofish]

edit:
Justin posted a script which does this, thanks so much.

https://forum.cockos.com/showpost.ph...7&postcount=10


=== original post ===

from here (since I got no reply there):

This

_nextGridPos = reaper.TimeMap2_beatsToTime(0, 0.25, 0)

should, to my understanding, give the position (in time) of the first visible grid line in my project.
It seems to work correctly for non swing grid:




However, when I set a swing grid, and run the script again, the same position is returned and not the actual position of the grid line.

[Justin]

The swing grid does not affect that function, the swing grid is purely for guidance. You could do your own swing calculation though I suppose...

[nofish]

Thanks.
Hm..I'm a bit surprised to be honest.
Setting swing affects beats positions (edit: or rather sub-beats positions) which I'm evaluating with this function, no? Hence I'd have expected this function respects a swing grid.

Anyway, the actual issue is that some SWS API functions which use this (e.g. BR_GetNextGridDivision() are broken with a swing grid set currently because of this.
https://github.com/reaper-oss/sws/issues/1137

Any suggestion for a fix by chance?
(I guess that's better asked in the scripters/extension forum though.)

edit2:
Alternatively, since Reaper has the actual grid positions present/stored anyway I suppose, couldn't there be an additional API function to get them rather having to do our own swing calculation?