Opened 15 years ago
Closed 13 years ago
#1214 closed enhancement (fixed)
Maestro: consider adding support for CompositeTypeStyle to Layer UI for 1.3 schema
Reported by: | jbirch | Owned by: | jng |
---|---|---|---|
Priority: | low | Milestone: | Maestro-3.5 |
Component: | Maestro | Version: | |
Severity: | trivial | Keywords: | |
Cc: | External ID: |
Description
It would be incredibly useful to be able to add and modify CompositeTypeStyles to the Layer UI.
Currently, this can only be done via XML, so my primary motivation is the fact that in order to preview a layer containing CompositeTypeStyles I have to save the XML document, close it, open the GUI, and click on preview. Issue #1203 would also resolve this particular issue, but this would be a much nicer approach.
Basically, you'd need to allow the user to add a CompositeTypeStyle at each scale range using same kind of check box as existing point/line/area type styles and the same kind of rule definition UI.
Within each rule, you would need to have the ability to add one or more SymbolInstance.
Each SymbolInstance should allow:
- specifying a SymbolDefinition ResourceID via the repository browser
- specifying one or more expression-based Overrides from the parameters exposed in the simple or compound SymbolDefinition
- specifying ScaleX with numeric text entry
- specifying ScaleY with numeric text entry
- specifying a SizeContext from dropdown of DeviceUnits or MappingUnits
- specifying a UsageContext from dropdown of Unspecified, Point, Line, Area
- specifying a GeometryContext from dropdown of Unspecified, Point, LineString, Polygon
Change History (5)
comment:1 by , 15 years ago
Milestone: | → Maestro-2.1 |
---|---|
Status: | new → assigned |
comment:2 by , 15 years ago
Milestone: | Maestro-2.1 → Maestro-2.5 |
---|---|
Owner: | changed from | to
Status: | assigned → new |
comment:3 by , 14 years ago
Milestone: | Maestro-3.0 → Maestro-4.0 |
---|
comment:4 by , 14 years ago
Milestone: | Maestro-4.0 → Maestro-3.5 |
---|
comment:5 by , 13 years ago
Resolution: | → fixed |
---|---|
Status: | new → closed |
This is effectively now implemented.