Closed bgschiller closed 6 years ago
Beyond stories, note that the user can change space properties (e.g., heights), create windows, etc. all before changing units. So more than stories may need to be updated.
It makes me wonder if we simply move the IP vs SI choice to the quick start menu? Or, for the time being, we could remove the ability to change units and require that it be done via the API? @macumber
My thought is that we need to go by the schema here, if there is missing markup in the schema we may have to update the schema for certain fields. As long as @bgschiller detects the ip_units and si_units for a field he can make sure to do the conversion, both for defaults and for user set values, and update those on open if the init units dont match the file units
Sorry, I probably wasn't clear. I'm not referring to a file open action, I'm referring to a new project The app allows you to change the units before you start drawing anything -- but you can still create objects or change object properties before changing the units.
I'm happy to talk this over on Wednesday, but it seems like we have several options:
I won't be able to make the call Wednesday. I don't like deleting existing models or ignoring the unit change. If we do the feature, we should make it work right. I think you could get away with rounding numbers for display only, you could leave them full precision in the data store
I agree with Dan. Of the above options, I like option 2 best. Though I still think there are 2 other possibilities:
convert them to si units when that is the project config setting.
A caveat here is that we're destroying any stories that have already been created (because they are using the defaults for the wrong unit system).
Also, we now use
si
andip
in the schema Project.config.units field, rather thanft
andm
.Addresses #293