Opened 11 years ago

Closed 10 years ago

#322 closed defect (fixed)

Fusion: ApplicationDefinition.xml files for each template refers to a non-existent map (SheboyganOverview)

Reported by: jng Owned by: pagameba
Priority: medium Milestone: 2.1
Component: Samples Version:
Severity: minor Keywords:
Cc: madair@… External ID: 1054711

Description

If you load the templates using the ApplicationDefinition?.xml file on that folder, fusion will complain about a map called SheboyganOverview? that does not actually exist.

Change History (5)

comment:1 Changed 11 years ago by pagameba

Cc: madair@… added
Milestone: 2.0
Owner: set to pagameba

The ApplicationDefinition? files all need to be updated so that the OverviewMap? doesn't point to a specific map.

comment:2 Changed 10 years ago by tomfukushima

Hi Jackie, can you retest this with MGOS 2.0.0 release.

comment:3 Changed 10 years ago by jng

Just installed the 2.0.0 release.

The ApplicationDefinition?.xml files for each template still has the invalid map resource id. All templates except Slate still complain.

The same xml files in the trunk still have the invalid map references.

Either remove the invalid map reference, or actually have the SheboyganOverview? map definition as part of the sample data.

comment:4 Changed 10 years ago by chrisclaydon

External ID: 1054711

comment:5 Changed 10 years ago by jng

Resolution: fixed
Status: newclosed

I see that the bad mapdefinition was removed in the trunk ApplicationDefinition?.xml files.

Note: See TracTickets for help on using tickets.