vjekob
commented
2 years ago Thanks for the feedback!
Regarding your comments:
- Version 2.9.2 has not yet been released. I got stuck with a few minor issues, then my job got in the way of me being able to work more on this, and then vacation. I'll try to release it as soon as I have a chance, but I won't promise anything.
- Synchronization has merge and replace options, plus there is auto-synchronize. They are all well documented in the documentation, so please check which one of these three will solve your issues. Most of Ninja commands (when you run them) show the "Learn more" option available, so try running synchronization and/or auto-synchronization, reading more about how they work, and then check which one should solve your problems.
- I agree that simply clicking "Synchronize" on the "no more numbers are available" message is bad, and I'll change this behavior to ask you about which kind of synchronization you want to run. However, if you are out of numbers, then either full-synchronization (replace) or auto-synchronization can really help. I'm working on some smooth ways of managing assigned IDs so you can release those you have acquired, but then dropped the objects.
Hope this helps.
First, thank you for this wonderful app!
Not sure if you saw my comment on closed ticket #39 but like I mention there, I don't see 2.9.2 anywhere to be installed.
While doing some testing (2.9.1) I notice that if we get the warning for "no more numbers are available. Do you want to synchronize?" and we press Synchronize, it will REPLACE the back end info. Is this intended? It seems dangerous, if we are using a pool, it will only store that app consumption, and not the whole pool.
Also, on a pool, I need to sync each app individually to have all ID's on the back end. I'm wondering if, when on a pool, the synchronize should sync all apps.
Thank you for your work.