bladeracer wrote:I'm glad you mentioned laptops - I was thinking it was only going to be for phone use - which is no good to me.
I understand the need to make it suit lots of different users, but how difficult would it be to have the option of including all those fields or leaving them out? Like a tick box beside each field so the user only has a compact screen of the fields he actually needs. It sucks having to look through fifty items to find the three you use.
Not right now. Layouts are the trickiest things and once it's working on few devices, this is something you want to avoid changing at all costs. That said, this is something I have been thinking about and maybe in the future. However, what you see here in screenshot are prep screens. You won't be looking at them often. The actual cartridge building screens I haven't shared here, but it has exactly what you are thinking. Bare minimum on viewing area and additional pop-up windows if you want to dive deeper into data collection. This is the screen you'd be looking the most at, so it's the smallest...
bladeracer wrote:Maximum Cartridge OAL needs to be included in the load data not the firearm - it's different for each bullet design.
For each cartridge development. Correct. It's in the cartridge development screens. This instance is actually based on Brett's suggestion (who's a walking encyclopaedia of reloading). It's a one off in there. Intended to be recorded for brand new rifle, recorded only once in the beginning. This way you have a baseline record to track throat erosion. There's a note about that but too small to see in the screenshot.
bladeracer wrote:I would rather see the scope listed with the load rather than the rifle. Anything that can be changed on the firearm should be listed with the specific load being developed, not with the firearm data. Otherwise if I change the scope or the bipod then I need to build a new "firearm" for the database.
This my friend is an age old debate of usability vs practicality.
80/20 here... Most shooters don't swap scopes too often. So it's there to reduce data input requirements.
That said, there are few things available to counter that. One, notes areas in all components. So you can track it. Or, lock or archive functions. This is where you want to rebuild something but keep old records... You can archive it or lock it. Depends on your use case, both available, one will lock it and prevent future edits until unlocked. The other will hide but not delete certain data workflows. And you also have a clone facility, where you can duplicate anything into anything new for really small changes. Sort of like setting up templates for common workflows, but better. You can clone a primer batch, a rifle, cartridge batch or entire cartridge batch group... Finally, there's the delete options.
From the box arriving this morning to the first case hitting the bin was under an hour, piece of piss to setup and get running.
And reload for all of them, using different projectiles and charge... It's not like I randomly thought, you know, I am going to stay up late at night doing this, because there is no need lol
