Modify ↓
Opened 7 years ago
Closed 7 years ago
#15487 closed defect (worksforme)
Setting "simplify-way.max-error" has vanished?
Reported by: | bdiscoe | Owned by: | team |
---|---|---|---|
Priority: | normal | Milestone: | |
Component: | Core | Version: | latest |
Keywords: | template_report | Cc: |
Description
What steps will reproduce the problem?
- Open the Settings dialog: Advanced Preferences.
- Look for the setting "simplify-way.max-error"
- It isn't there.
What is the expected result?
It's been there for years, and it's in the documentation at https://josm.openstreetmap.de/wiki/Help/Action/SimplifyWay
What happens instead?
I just downloaded this new JOSM version (12921) and the setting does not appear.
Please provide any additional information below. Attach a screenshot if possible.
URL:http://josm.openstreetmap.de/svn/trunk Repository:UUID: 0c6e7542-c601-0410-84e7-c038aed88b3b Last:Changed Date: 2017-10-03 21:43:00 +0200 (Tue, 03 Oct 2017) Build-Date:2017-10-03 19:50:21 Revision:12921 Relative:URL: ^/trunk Identification: JOSM/1.5 (12921 en) Windows 10 64-Bit OS Build number: Windows 10 Pro 1703 (15063) Memory Usage: 244 MB / 247 MB (49 MB allocated, but free) Java version: 1.8.0_151-b12, Oracle Corporation, Java HotSpot(TM) Client VM Screen: \Display0 1080x1920, \Display1 2560x1440 Maximum Screen Size: 2560x1920 VM arguments: [-Djava.security.manager, -Djava.security.policy=file:<java.home>\lib\security\javaws.policy, -DtrustProxy=true, -Djnlpx.home=<java.home>\bin, -Djnlpx.origFilenameArg=%UserProfile%\AppData\LocalLow\Sun\Java\Deployment\cache\6.0\56\1ee8cfb8-1056c2c6, -Djnlpx.remove=false, -Djava.util.Arrays.useLegacyMergeSort=true, -Djnlpx.splashport=65029, -Djnlp.application.href=https://josm.openstreetmap.de/download/josm.jnlp, -Djnlpx.jvm=<java.home>\bin\javaw.exe] Dataset consistency test: No problems found Plugins: + FastDraw (33583) + buildings_tools (33004) + scripting (30773) + utilsplugin2 (33704) Last errors/warnings: - W: No configuration settings found. Using hardcoded default values for all pools. - W: Region [TMS_BLOCK_v2] Resetting cache - W: java.net.SocketTimeoutException: Read timed out - W: java.net.SocketTimeoutException: Read timed out
Attachments (0)
Note:
See TracTickets
for help on using tickets.
It's still here. It's just that if you did not change it to a custom value, JOSM does not know this parameter until you run the action at least one time. So you can: