When the current drawing is already Mapsforge and a redraw request is made, a check is always made to find the corresponding Mapsforge file from the graph file (.mapgr -> .mapfg).
This test is made even when the Mapsforge drawing already contains a drawing of the current graph. But in this case, the graph is not redrawn due to the optimization (only overlays are removed), and thus the behavior is disconcerting and inconsistent.
Currently, here is what may happen:
the current drawing is "Mapsforge";
the user request a "Mapsforge" redrawing, but the Mapsforge file is not found;
a file chooser asking the user for the Mapsforge file appears;
the user select a file different from the one previously used (either because
the previous one was wrong, or because the user has different versions);
nothing happens...
This is very disconcerting.
This behavior should be changed, either:
always redraw the graph, even when the current drawing and graph match with the requested ones;
do not ask the user for a Mapsforge file when the standard one does not exist.
When the current drawing is already Mapsforge and a redraw request is made, a check is always made to find the corresponding Mapsforge file from the graph file (`.mapgr` -> `.mapfg`).
This test is made even when the Mapsforge drawing already contains a drawing of the current graph. But in this case, the graph is not redrawn due to the optimization (only overlays are removed), and thus the behavior is disconcerting and inconsistent.
Currently, here is what may happen:
1. the current drawing is "Mapsforge";
2. the user request a "Mapsforge" redrawing, but the Mapsforge file is not found;
3. a file chooser asking the user for the Mapsforge file appears;
4. the user select a file different from the one previously used (either because
the previous one was wrong, or because the user has different versions);
5. **nothing** happens...
This is **very** disconcerting.
This behavior should be changed, either:
- always redraw the graph, even when the current drawing and graph match with the requested ones;
- do not ask the user for a Mapsforge file when the standard one does not exist.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
When the current drawing is already Mapsforge and a redraw request is made, a check is always made to find the corresponding Mapsforge file from the graph file (
.mapgr->.mapfg).This test is made even when the Mapsforge drawing already contains a drawing of the current graph. But in this case, the graph is not redrawn due to the optimization (only overlays are removed), and thus the behavior is disconcerting and inconsistent.
Currently, here is what may happen:
the previous one was wrong, or because the user has different versions);
This is very disconcerting.
This behavior should be changed, either: