Opened 13 years ago
Closed 13 years ago
#1907 closed defect (wontfix)
Maestro - .SymbolLibrary and .SymbolDefinition
| Reported by: | crispinatime | Owned by: | jng |
|---|---|---|---|
| Priority: | medium | Milestone: | Maestro-5.0 |
| Component: | Maestro | Version: | |
| Severity: | major | Keywords: | |
| Cc: | External ID: |
Description
A few points on incomplete symbol support...
The New Resource allows for creation of a .SymbolDefinition that is really nice, but using MGOS 2.2 the resources lists a 1.0 schema but as soon as I open it I am prompted to update to 1.1 - why is v1.1 not listed in the resource selecter under a MG version?
When editing a point layer for style, there is an option to select a symbol that invokes the resource browser looking for a .SymbolLibrary, however the ability to create a .SymbolLibrary is missing in the new resource selector (old Maestro 2.x at loaded a default XML).
I want to either be able to create a .SymbolLibrary from my .SymbolDefinition or (if allowed) select the .SymbolDefinition directly for my point style. Maybe the drop-down selector needs two symbol options to allow the user to choose from selecting directly or from a library.
Change History (3)
comment:1 by , 13 years ago
comment:2 by , 13 years ago
Isn't is, like 1am on New Years day with you!?...
OK - but there is the ability to create a simple symbol - can the layer point editor be made so that the "Symbol" selection invokes the .SymbolDefinition browser rather than the .SymbolLibrary to allow a user the full cycle of creating an image-based point symbol and associating it with a layer feature style?
comment:3 by , 13 years ago
| Resolution: | → wontfix |
|---|---|
| Status: | new → closed |
There will be no additional SymbolLibrary support due to reasons already stated.
When editing a point layer style, if is not a composite one then you are using basic stylization, where referencing symbols from a SymbolLibrary is the correct and only allowed behaviour.
In short, nothing to do here.
.SymbolLibrary resources are nothing more than DWF blobs. Adding support for .SymbolLibrary resources is basically adding support for manipulating DWF files in pure .net, which is a very tall order. This is why the only support for .SymbolLibrary resources from Maestro is reading and browsing (viewing symbols is a neat hack involving the Drawing Service APIs). Actually writing and updating symbols is a whole different ball game.
As for the missing templates, they already exist. They just haven't been registered with Maestro so they never get picked up.