08-23-2019, 05:00 PM
I can consider it, but it depends on the level of effort. If I add some kind of setting to control how the page is scaled by default in the annotations editor (maybe just a simple "Fit width" setting in the circle at the top left), and it just works without any additional changes, then I could slip it in an update. If it seems to introduce additional bugs that could cause instability, I don't want to invest a lot of time in something that's going to be thrown away soon, as it would just push the schedule further out. I'll also just have to use Google Translate or something for that setting as I don't want to have to reach out to all 13 translators just for that one entry. Adding to Windows means I should probably add it to Android as well to avoid confusion. If this is going to give you something that would significantly improve the annotations functionality for you and make it easier to wait for the annotations rework to be finished, then I'll certainly do what I can to add it.
As far as changing the display mode, I can look into adding a way to switch display modes with a pedal, but it's not going to be simple, because technically it should allow toggling between any two display modes. That means there needs to be some way of entering which two display modes you want to toggle between. That sounds to me like a completely new UI component or would require the addition of a different workflow such as popping up a dialog to ask which display mode to switch to. It would then save that mode and the one that was switched from, and allowing toggling between the two. There would have to be a way to clear this though if you wanted to switch modes later, but I don't know how that would be done with a single pedal press (in a manner that doesn't require additional custom code in the framework).
Thanks,
Mike
As far as changing the display mode, I can look into adding a way to switch display modes with a pedal, but it's not going to be simple, because technically it should allow toggling between any two display modes. That means there needs to be some way of entering which two display modes you want to toggle between. That sounds to me like a completely new UI component or would require the addition of a different workflow such as popping up a dialog to ask which display mode to switch to. It would then save that mode and the one that was switched from, and allowing toggling between the two. There would have to be a way to clear this though if you wanted to switch modes later, but I don't know how that would be done with a single pedal press (in a manner that doesn't require additional custom code in the framework).
Thanks,
Mike