Considering the new fire control options, wouldn't it be possible to have it operating similarly to turrets, where you input a specific tracking speed and the game does the math for you? That would be better than seeing a frakkton of 0.01 increments.
I'd argue instead of that, it would be easier to program a pair of boxes that just accept a number between 0.01 and 4.00 for the range/speed modifiers. Which is effectively what's already being done, but would save a lot of scrolling, and needing to code in a bunch of checks for "Did the user enter a range that's too high for their tech... they can only do 480,000km with a max range BFC but they've entered 1,800,000km".
The x1 and x4 (the most common) are already 1st and 2nd in the list, which will cover most of the time. The rest are no different than many other options for different component types.
I have considering re-doing the Create Project screen entirely to allow players to enter values, but that is a much larger change. The dropdowns contain information tagged to each item that is passed directly to the design functions. If I take the values from boxes, I then have to change the design function parameters, which then means updating all the automated design code to use the new parameter types.
I already did that in this case, modifying the beam fire control design function to accept decimals from the dropdowns instead of TechSystem objects. That led to adding new database fields so I could store those choices, because I needed to record them for the ship component code in the class design templates. This is because race-designed components are tagged with the tech systems used to create then, which no longer exist in this case. I also had to change the way NPRs designed ships, to use decimal values instead of tech systems. Because there is a lot of code in Aurora, it is often a lot more complex than simply changing the UI, plus all the changes also lead to increased chances of bugs.
Ultimately, it comes down to the amount of improvement in QoL vs the amount of effort required to achieve it. In this case, I finally found the lack of granularity annoying enough to justify the effort to change it