Thanks for the feedback. I'm always open to improving the usability of the app. I have plenty of ideas for changes to the Windows 10 version as well. It just comes down to time. Right now, users have made it very clear that changing the annotations functionality is the most important thing (by far). So I'm going to focus most of my attention on that so I can get it done faster. After that, there are very compelling reasons to get the iOS version done as fast as possible, and I'm getting a huge amount of feedback and desire for that. After the iOS version is finished, I have a list of high priority feature requests that have been waiting for awhile that I get feedback on regularly. So those will come next. While working those high priority feature requests, I will slip in small usability enhancements as I can (this is true for any update as long as the usability changes are small). The priority that any change is given depends upon a combination of the complexity involved, the number of users that request it and the number of users that benefit from it.
When I get a chance to modify the code for the pitch/tempo adjustment so that it can be changed without having to exit the dialog, I will do that. This involves having to ensure changes aren't triggered too quickly (when changing the tempo speed, the values can change extremely fast and I don't want to crash the audio player as I'm not sure what that library is capable of when it comes to being hammered like that), that the value is reset properly if the dialog is canceled and adding the necessary code to watch for changes on that dialog in the calling code (right now it doesn't process changes until the dialog is closed). That dialog is used all over the application, so any changes I make could impact other areas, so there may be a lot of other code that needs to be updated depending upon the nature of the changes. I've also been considering changing the dialog based approach with the number entry to something more like a popup window without OK/Cancel that just lets you change the value quickly with arrows and a slider (similar to the existing dialog layout) as it's less jarring on Windows 10. Microsoft's framework only lets you display a single dialog at a time, so if a dialog needs to pop up another dialog, you have to close the first, trigger the second, then when the second closes, trigger the first to show again. It's incredibly annoying and not great from a user standpoint either. So one of my goals is to see if I can switch to popups in various parts of the application where dialogs are being used at the moment.
So as you can see, any change is going to require focus to ensure its done right, and even when it seems small, it can impact a lot of areas of the application. So I can't just work these as I receive them - they will have to be scheduled appropriately. I really do appreciate the feedback, and the changes will be made, but it will require some patience.
As a side note, if you want to restart the track, just press play a second time. That is how the track can be restarted. There is no need to stop and then play again.
Mike
When I get a chance to modify the code for the pitch/tempo adjustment so that it can be changed without having to exit the dialog, I will do that. This involves having to ensure changes aren't triggered too quickly (when changing the tempo speed, the values can change extremely fast and I don't want to crash the audio player as I'm not sure what that library is capable of when it comes to being hammered like that), that the value is reset properly if the dialog is canceled and adding the necessary code to watch for changes on that dialog in the calling code (right now it doesn't process changes until the dialog is closed). That dialog is used all over the application, so any changes I make could impact other areas, so there may be a lot of other code that needs to be updated depending upon the nature of the changes. I've also been considering changing the dialog based approach with the number entry to something more like a popup window without OK/Cancel that just lets you change the value quickly with arrows and a slider (similar to the existing dialog layout) as it's less jarring on Windows 10. Microsoft's framework only lets you display a single dialog at a time, so if a dialog needs to pop up another dialog, you have to close the first, trigger the second, then when the second closes, trigger the first to show again. It's incredibly annoying and not great from a user standpoint either. So one of my goals is to see if I can switch to popups in various parts of the application where dialogs are being used at the moment.
So as you can see, any change is going to require focus to ensure its done right, and even when it seems small, it can impact a lot of areas of the application. So I can't just work these as I receive them - they will have to be scheduled appropriately. I really do appreciate the feedback, and the changes will be made, but it will require some patience.
As a side note, if you want to restart the track, just press play a second time. That is how the track can be restarted. There is no need to stop and then play again.
Mike