'Jump up/down by measure' doesn't let me return to the first row in a pattern

Started by dhr2, September 06, 2025, 13:59:41

Previous topic - Next topic

dhr2

Hello,

I just updated my openmpt for the first time since 2022 and I've now found that when using Page Up to jump up a pattern, if there is less than a measure of rows between the cursor row and the start, the cursor just stays put and doesn't return to the first row.

I couldn't find any configuration option in the settings menu to restore the previous behaviour. Does anyone know how to change it back?

This is something I rely on heavily for my workflow and I have ~16 years of habits and muscle memory built around it.

Thanks,
dhr2

Saga Musix

Are you saying that you have both "Cursor wrap in pattern editor" enabled and "Continuous scroll" disabled, and yet the behaviour does not work like that? Because it should only ever go back to the beginning of the current pattern if those two options are set like that, both previously and in the current version.
» No support, bug reports, feature requests via private messages - they will not be answered. Use the forums and the issue tracker so that everyone can benefit from your post.

dhr2

Hi, thanks for your reply.

To be clear:
"Cursor wrap in pattern editor" is unticked (disabled).
"Continuous scroll" is unticked (disabled).

If it would be helpful, I can provide my settings .ini files. Let me know and I'll upload them.

In the previous version of OpenMPT I was using (1.30.02.00) pressing Page Up enough times would eventually put the cursor on the first row of the currently focused pattern.
On the current version, it stays put if there's less than a measure of space between the cursor and the first row.

After experimenting with the settings, it looks like enabling "Continuous scroll" restored the behaviour I want for the first pattern in the orderlist, but for later patterns in the orderlist, it moves from the current pattern to the previous pattern in the orderlist, which isn't what I want.

Thanks,
dhr2

----- edit -----
I add this as an edit so as not to bump the thread and spam the forum: Thank you a lot for your work and for solving this issue. I appreciate it a lot.

Saga Musix

I see now there was an unintended change in behaviour in OpenMPT 1.31.01.00. I'll see what can be done to fix that, while keeping the other intended behaviour changes working as well.
» No support, bug reports, feature requests via private messages - they will not be answered. Use the forums and the issue tracker so that everyone can benefit from your post.

Saga Musix

This should now be fixed in r24164. You can wait for the build to show up here: https://builds.openmpt.org/builds/ or set the update channel in OpenMPT to "Next". The fixed version should appear there within a few hours.
» No support, bug reports, feature requests via private messages - they will not be answered. Use the forums and the issue tracker so that everyone can benefit from your post.