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
{{ message }}
This repository has been archived by the owner on Jul 24, 2021. It is now read-only.
Reporter: CycleStreets [Submitted to the original trac issue database at 2.49pm, Saturday, 2nd April 2011]
Sometimes I've had "Error: Couldn't load the map \n [OK]". Could you include some likely reason for this, i.e. what it actually means?
At present the user has no idea of what went wrong or how they can fix it, which reduces confidence.
If, for instance, it's due to the start zoom being wrong, that should be set as a catchable case with a specific error message.
Naturally, avoid piping through a technical error code directly through to the user. Ideally have a lookup table that converts a technical error code/text to a short user-friendly error message.
The text was updated successfully, but these errors were encountered:
Reporter: CycleStreets
[Submitted to the original trac issue database at 2.49pm, Saturday, 2nd April 2011]
Sometimes I've had "Error: Couldn't load the map \n [OK]". Could you include some likely reason for this, i.e. what it actually means?
At present the user has no idea of what went wrong or how they can fix it, which reduces confidence.
If, for instance, it's due to the start zoom being wrong, that should be set as a catchable case with a specific error message.
Naturally, avoid piping through a technical error code directly through to the user. Ideally have a lookup table that converts a technical error code/text to a short user-friendly error message.
The text was updated successfully, but these errors were encountered: