-
Notifications
You must be signed in to change notification settings - Fork 6
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Localization Issue with Comma vs Period Based Decimal Separator #2
Comments
Hi Andrew, Excellent work on this app, makes it much easier to create spatial videos. MrLando |
As soon as a I have a spare moment I will fix this. It's at the absolute top of my priority list. |
Great! 👍 |
@mrlando There is a new v1.2 update that addresses the comma vs period localization issue. Please let me know if you try it out and it works for you: https://github.com/Kartaverse/Spatial-Metadata/releases/tag/v1.2 |
Yes! It works! Appreciated thx! |
Ok, well I'll just scroll a bit for now. It is converting to spatial at least. It would be a nice addition sometime in the future. |
Yup. I will enable a progress bar and scrolling console view feature on the next dot update of the Spatial Metadata GUI toolset, along with spatial photo conversions, and a JSON based preset system. :) |
Awesome! |
There is a known localization issue with the current Spatial Metadata GUI's v1.1 release's handling of textfield based number entry in the GUI for users in select regions with non "English US" region settings enabled in their OS. Dev efforts are underway now to solve this. :)
At the moment, you need to set your computer's localization settings to allow a period based separator to be used for the decimal point mark. If you have your number input preferences in your operating system set to use a comma value for the decimal point character there will be an error.
Summary: The GUI wrapper tool is a thin shell that is passing data to the Spatial CLI tool through the command line interface. A North American localized number input setting has to be used until the next dot update is shipped. (Sorry about that!)
The text was updated successfully, but these errors were encountered: