Opened 14 years ago

Closed 14 years ago

Last modified 14 years ago

#1429 closed defect (invalid)

Advanced settings for raster layer seem to do nothing.

Reported by: andrewd Owned by: jng
Priority: low Milestone: Maestro-3.0
Component: Maestro Version: 2.1.0
Severity: trivial Keywords:
Cc: External ID:

Description

It appears that the "advanced" settings for raster layers don't function at all, or don't function as expected.

Attachments (1)

Capture.PNG (26.0 KB ) - added by andrewd 14 years ago.
screen shot from v2.1.1.5078

Download all attachments as: .zip

Change History (8)

comment:1 by jng, 14 years ago

I'm getting a bit lost in all these specialized feature source editors. Can you post some screenshots of the editor in question? I assume it's the GDAL editor, but I don't see anything resembling advanced settings.

by andrewd, 14 years ago

Attachment: Capture.PNG added

screen shot from v2.1.1.5078

comment:2 by jng, 14 years ago

Milestone: Maestro-2.1.x

comment:3 by jng, 14 years ago

Could you be more specific as to which options don't work? The XML document reflects each change I make in the advanced settings.

comment:4 by andrewd, 14 years ago

Well, the main one I was interested was transparency color. The XML doc may have the changes, but are all of those changes actually implemented in MGOS?

comment:5 by jng, 14 years ago

Resolution: invalid
Status: newclosed

Closing as invalid because the issue which I thought ticket relates to (XML content not reflecting values in raster editor UI) is not the case.

comment:6 by andrewd, 14 years ago

Maybe all that is needed is to change the wording in Maestro for a few things. for example, if the wording for "Transparency Color" was changed to "Transparency Color (Monochrome Images)". It's misleading, the way it's written now - unless the transparency color will actually work with the most current MGOS for all types of images.

If the hillshade and surface options are actually doing something in MapGuide, then they're obviously ok - but if those are actually just placeholders for future MapGuide support, I'd consider noting that in Maestro somewhere. Even doing something like "Hillshade (MGOS v2.5)", indicating the supported version.

Anyway - this is what I meant about it not functioning as expected. It may actually be saving the data, but the end result that the user sees is not what is expected. That may or may not be a result of MGOS deficiencies, but I think that Maestro would be well served to let the user know.

comment:7 by jng, 14 years ago

Milestone: Maestro-2.1.xMaestro-3.0

Milestone Maestro-2.1.x deleted

Note: See TracTickets for help on using tickets.