Customized Toolbar forgets... temporarily

Abraham Lee

I've customized my toolbar with a few extra shortcuts, but the shortcuts don't always appear when I startup the app. I can go to the "Customize Toolbar" menu and all my prior selections are there so when I hit "Done", then things are back where I expected. Not sure why there's the hiccup.

I'm on iPhone 11, iOS 17.3.1, pianoscope 2.6.2.

Frank Illenberger

Abraham Lee Hello Abraham, thank you for reporting this. When this happens: Do only the toolbar items disappear, or are other settings also reset?

Abraham Lee

Frank Illenberger the toolbar items just disappear. When I click on "Customize Toolbar" again, all my prior selections show up in the list, as expected. Clicking "Done", then makes them reappear in the toolbar itself.

Frank Illenberger

Thanks. Today I tried to reproduce the issue you described but so far I haven't been successful. Sorry if this is a stupid question: Are you sure that it has nothing to do with device orientation? Because when running pianoscope in portrait orientation, there is less space for additional toolbar items and so they are dropped. Once you rotate pianscope to landscape, they will be shown again.

Abraham Lee

Maybe it was just the orientation that caused it, but I thought I saw it happen in landscape mode, too. I can't seem to make it happen again at the moment, but I will come back if I discover something repeatable.

Abraham Lee

Ok, I discovered a repeatable way of getting it do show the bug. Here's how I can make the original report happen consistently on my iPhone:

Go to either Tuning Curve or Inharmonicity.
Rotate device to portrait view (if not already there)
Rotate device to landscape view
While in landscape view, click Done to return to main tuning screen
Custom toolbar items are not visible

If I rotate to portrait and then back to landscape, they will then appear as expected. So, not a big deal, but worth addressing anyway, I think.

Frank Illenberger

Abraham Lee Wow, great! Now I could reproduce it, too. Thanks for nailing this down. I've fixed the underlying problem and will release an update soon.