Changeset 18866 in josm for trunk/src/org
- Timestamp:
- 2023-10-12T17:42:13+02:00 (11 months ago)
- Location:
- trunk/src/org/openstreetmap/josm
- Files:
-
- 2 edited
Legend:
- Unmodified
- Added
- Removed
-
trunk/src/org/openstreetmap/josm/data/osm/FilterModel.java
r18571 r18866 440 440 } 441 441 442 for (OsmPrimitive ref: p.getReferrers( )) {442 for (OsmPrimitive ref: p.getReferrers(true)) { 443 443 stack.push(ref); 444 444 } -
trunk/src/org/openstreetmap/josm/gui/tagging/presets/TaggingPreset.java
r18607 r18866 85 85 * read in all predefined presets, either shipped with JOSM or that are 86 86 * in the config directory. 87 * 87 * <p> 88 88 * It is also able to construct dialogs out of preset definitions. 89 89 * @since 294 … … 405 405 /** 406 406 * This hack allows the items to have their own orientation. 407 * 407 * <p> 408 408 * The problem is that 409 409 * {@link org.openstreetmap.josm.gui.ExtendedDialog#showDialog ExtendedDialog} calls 410 410 * {@code applyComponentOrientation} very late in the dialog construction process thus 411 411 * overwriting the orientation the components have chosen for themselves. 412 * 412 * <p> 413 413 * This stops the propagation of {@code applyComponentOrientation}, thus all 414 414 * {@code TaggingPresetItem}s may (and have to) set their own orientation. … … 446 446 447 447 if (selected.size() == 1 && Boolean.TRUE.equals(USE_VALIDATOR.get())) { 448 // Fail early -- validateAsync requires the primitive(s) to be part of a dataset. Failing later in validateAsync ''does not'' give us449 // a usable stack trace. See #21829 for details.450 selected.forEach(OsmPrimitive::checkDataset);451 448 itemGuiSupport.addListener((source, key, newValue) -> 452 449 TaggingPresetValidation.validateAsync(selected.iterator().next(), validationLabel, getChangedTags()));
Note:
See TracChangeset
for help on using the changeset viewer.