I apologize for not responding to you sooner. There are a lot of emails requesting support along with feature enhancements, so I try to stay on top of it all but sometimes things fall through the cracks. There have also been a lot of serious issues I've had to investigate the last several weeks, so that has taken priority over handling feature requests. As for your requests:
1. There is an enhancement request that is being tracked to create a seamless vertical scrolling mode. I just haven't had time to implement the changes for this yet.
2. This is being handled with the annotations rework.
3. Same as #2
4. This requires a large number of changes to the application and how things are displayed and managed. I can certainly look into supporting this in a future update. My plan will probably be just to use the tabs like a bookmark. So switching between tabs will reload whatever song or setlist was loaded on that tab and will jump to the last viewed page. I will not leave everything in memory for instant switching though, because that could easily cause out of memory errors on devices, and also consumes resources in the PDF libraries. Hopefully that would be sufficient for your needs.
5. The right button is editable (long press it to change the action). Making all of them editable is certainly something I can look into in the future, but it would be through a different mechanism, because long pressing on those buttons brings up their respective controls (i.e. the audio player, metronome window, scroll settings, etc). An editor for this is definitely more complex than what is currently present.
6. I could look into adding layout options for the metronome, such as a minimal view to hide things. You can display the metronome by long pressing the metronome icon in the quick action box. That's probably the fastest way to get to it if you don't want to go through the song overlay. I can also look into adding a touch action to display/hide the metronome window if you think that is useful.
7. There is no built-in support for three finger gestures in Android. The three finger tap was something I had to write a fair amount of code to handle. Adding support for three finger panning is certainly something I can try to do, but it's not going to be easy, as code has to be added to stop the regular gesture detectors from processing the input when three fingers are down (i.e. if a pinch gesture is in progress but another finger presses briefly, this would cause chaos if three finger panning was in the mix and it immediately canceled the pinch zoom). These things sound easy from the outside, but when you have to start writing the code with all of these different detectors in the mix, it gets more complicated quickly. At the moment, you can perform a two finger tap to switch to panning mode, pan the page, two finger tap to switch back to the last control used and continue annotating. It's not perfect, but it's the fastest way currently available. If you have a smart stylus and you enable stylus mode, then by default your fingers can pan and pinch zoom while the stylus annotates. This is by far the best way to use the app, but most tablets don't have a smart stylus available.
8. I do want to add a piano and pitch pipe. There are long term goals, but I need to get other important functionality in the app first.
9. Hopefully with the annotations rework this will work a little better. I'm going to include a radial menu that can be repositioned easily. Hopefully this will be sufficient by itself, otherwise a toolbar may also be present.
10. It's not easy to just switch out "Song" with "Scores" or some other word because there are hundreds of translation entries that all reference the word "Songs". The app is translated into 11 languages, so in order to make some kind of change like that, it would take getting updates to all 11 translations, and I'm sure the translators would not be too happy about that. Making it configurable so you could use Songs or Scores would be horribly complicated, as every entry would have to be changed so that you could insert one of those words in it, code would have to be changed to dynamically insert the correct word and I don't know if that would work well with every language. I definitely get where you are coming from, and perhaps just a simple switch when the app is first loaded to change what tabs are visible would help. Users can control what tabs are used themselves at the very least (Settings->Library Settings->Tab Order). If the tabs are the more important thing, I think that is something that can be dealt with without too much effort, but if the word "Song" versus "Score" is a big deal, I don't see any easy fix for that one.
I definitely appreciate your feedback, but many of your requests are going to require a fair amount of work and time. Zubersoft is a one-man show and I'm currently only working nights and weekends on MobileSheets, so progress is slower than I would like, but that will hopefully change next year as I'm aiming to go full time. This should help accelerate the handling of feature requests.
Thanks,
Mike
1. There is an enhancement request that is being tracked to create a seamless vertical scrolling mode. I just haven't had time to implement the changes for this yet.
2. This is being handled with the annotations rework.
3. Same as #2
4. This requires a large number of changes to the application and how things are displayed and managed. I can certainly look into supporting this in a future update. My plan will probably be just to use the tabs like a bookmark. So switching between tabs will reload whatever song or setlist was loaded on that tab and will jump to the last viewed page. I will not leave everything in memory for instant switching though, because that could easily cause out of memory errors on devices, and also consumes resources in the PDF libraries. Hopefully that would be sufficient for your needs.
5. The right button is editable (long press it to change the action). Making all of them editable is certainly something I can look into in the future, but it would be through a different mechanism, because long pressing on those buttons brings up their respective controls (i.e. the audio player, metronome window, scroll settings, etc). An editor for this is definitely more complex than what is currently present.
6. I could look into adding layout options for the metronome, such as a minimal view to hide things. You can display the metronome by long pressing the metronome icon in the quick action box. That's probably the fastest way to get to it if you don't want to go through the song overlay. I can also look into adding a touch action to display/hide the metronome window if you think that is useful.
7. There is no built-in support for three finger gestures in Android. The three finger tap was something I had to write a fair amount of code to handle. Adding support for three finger panning is certainly something I can try to do, but it's not going to be easy, as code has to be added to stop the regular gesture detectors from processing the input when three fingers are down (i.e. if a pinch gesture is in progress but another finger presses briefly, this would cause chaos if three finger panning was in the mix and it immediately canceled the pinch zoom). These things sound easy from the outside, but when you have to start writing the code with all of these different detectors in the mix, it gets more complicated quickly. At the moment, you can perform a two finger tap to switch to panning mode, pan the page, two finger tap to switch back to the last control used and continue annotating. It's not perfect, but it's the fastest way currently available. If you have a smart stylus and you enable stylus mode, then by default your fingers can pan and pinch zoom while the stylus annotates. This is by far the best way to use the app, but most tablets don't have a smart stylus available.
8. I do want to add a piano and pitch pipe. There are long term goals, but I need to get other important functionality in the app first.
9. Hopefully with the annotations rework this will work a little better. I'm going to include a radial menu that can be repositioned easily. Hopefully this will be sufficient by itself, otherwise a toolbar may also be present.
10. It's not easy to just switch out "Song" with "Scores" or some other word because there are hundreds of translation entries that all reference the word "Songs". The app is translated into 11 languages, so in order to make some kind of change like that, it would take getting updates to all 11 translations, and I'm sure the translators would not be too happy about that. Making it configurable so you could use Songs or Scores would be horribly complicated, as every entry would have to be changed so that you could insert one of those words in it, code would have to be changed to dynamically insert the correct word and I don't know if that would work well with every language. I definitely get where you are coming from, and perhaps just a simple switch when the app is first loaded to change what tabs are visible would help. Users can control what tabs are used themselves at the very least (Settings->Library Settings->Tab Order). If the tabs are the more important thing, I think that is something that can be dealt with without too much effort, but if the word "Song" versus "Score" is a big deal, I don't see any easy fix for that one.
I definitely appreciate your feedback, but many of your requests are going to require a fair amount of work and time. Zubersoft is a one-man show and I'm currently only working nights and weekends on MobileSheets, so progress is slower than I would like, but that will hopefully change next year as I'm aiming to go full time. This should help accelerate the handling of feature requests.
Thanks,
Mike