You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The game sometimes bugs and fails to log cartography. Although there's nothing we can directly do about this, instead make the carto fields editable so that the user can manually enter their carto if this happens.
This isn't quite as straightforward as making the on-screen field editable, because the value is abbreviated with e.g. 'k', 'm', 'b' etc. A couple of options:
Make the field directly editable, allow the user to enter abbreviations too (e.g. '3.75m'), then parse it into an integer.
Add an 'Edit' button, which temporarily makes the field directly editable, showing the integer value and then 'save' makes it read-only again and shows the abbreviated value.
When a field is clicked, temporarily make it directly editable, showing the integer value and then clicking away makes it read-only again and shows the abbreviated value.
Add an 'Edit' button which pops up a modal, showing the integer value and allowing a number to be entered. When closed, the value is then updated on the main window.
I like option 3 best, though it needs to be obvious you can click the field (compared to pure read-only values).
The text was updated successfully, but these errors were encountered:
The game sometimes bugs and fails to log cartography. Although there's nothing we can directly do about this, instead make the carto fields editable so that the user can manually enter their carto if this happens.
This isn't quite as straightforward as making the on-screen field editable, because the value is abbreviated with e.g. 'k', 'm', 'b' etc. A couple of options:
I like option 3 best, though it needs to be obvious you can click the field (compared to pure read-only values).
The text was updated successfully, but these errors were encountered: