TrackBank.followCursorTrack problem

[k0k0c]

Hello KVR!
In my Java controller extension, I use TrackBank to navigate the arranger. TrackBank.followCursorTrack (cursorTrack) is initialized for the bank. And there is one problem with that. I will try to describe. Let's take a project with a large number of tracks, for example 64. Let's set the bank page size = 8. When you select a track in UI Bitwig, sometimes the bank page switches incorrectly. The adjacent bank page is selected, instead of the one in which the selected track is located. As a result, the device cannot display the currently selected track. Perhaps I am missing something? I've tested this with several scripts included with Bitwig and scripts from Moss and the same thing happens there.

[k0k0c]

I'll add a couple of screenshots to illustrate the problem.
In this screenshot the Inst 26 track is selected and the track bank corresponds to the selected track.
https://snipboard.io/eJSpnd.jpg

Next, I select the Inst 6 track in UI Bitwig. The TrackBank switches to the wrong page.
https://snipboard.io/ielS2E.jpg

[moss]

I guess it is that one:
https://github.com/teotigraphix/Framewo ... issues/251

[k0k0c]

I guess it is that one:
https://github.com/teotigraphix/Framewo ... issues/251

Hi Moss! Thanks for the answer and great framework) I left a comment on this issue on how it reproduces for me. Is this the official Bitwig Bug Tracking API and is it an efficient way to solve such problems? Are the API developers in control of this? I have already accumulated several similar problems and I just now saw that I was not alone) This one is also very relevant for me
https://github.com/teotigraphix/Framewo ... issues/266

[moss]

I guess it is that one:
https://github.com/teotigraphix/Framewo ... issues/251

Hi Moss! Thanks for the answer and great framework) I left a comment on this issue on how it reproduces for me. Is this the official Bitwig Bug Tracking API and is it an efficient way to solve such problems? Are the API developers in control of this? I have already accumulated several similar problems and I just now saw that I was not alone) This one is also very relevant for me
https://github.com/teotigraphix/Framewo ... issues/266

No, it is not an official one. I use it to keep track of the known issues and wishes and push them towards Bitwig from time to time