Opened 11 years ago

Closed 11 years ago

Last modified 11 years ago

#504 closed defect (fixed)

StylizationUtil::GetCompositeSymbolizationBounds doesn't handle expressions

Reported by: waltweltonlair Owned by: waltweltonlair
Priority: medium Milestone: 2.1
Component: General Version: 2.0.0
Severity: major Keywords:
Cc: External ID: 1064832

Description

The StylizationUtil::GetCompositeSymbolizationBounds method computes the bounds of a symbol. It calls GetCompositeSymbolizationBoundsInternal, but passes in NULL for the FdoExpressionEngine. Since the engine is NULL the evaluation of the bounds will fail (an exception is raised) if the symbol has any expressions.

Change History (5)

comment:1 Changed 11 years ago by waltweltonlair

Status: newassigned

comment:2 Changed 11 years ago by waltweltonlair

In Stylization the ExpressionHelper::GetExpressionEngine method is used to obtain an expression engine initialized with the custom stylization functions. As part of this call strings need to be read from the platform resource file. Therefore in order for this call to succeed the platform must have been previously initialized via a call to MgConfiguration::LoadConfiguration (which includes specifying the path to the resource file).

Until recently MapGuide Studio (which calls StylizationUtil::GetCompositeSymbolizationBounds) did not initialize the platform, which is why NULL was being used for the expression engine. But now that Studio does initialize the platform we can change this code to create the engine.

In general, any application which uses the platform must initialize it via a call to MgConfiguration::LoadConfiguration.

comment:3 Changed 11 years ago by waltweltonlair

Resolution: fixed
Status: assignedclosed

comment:4 Changed 11 years ago by waltweltonlair

External ID: 1064832

comment:5 Changed 11 years ago by waltweltonlair

Merged fix into branch stream with submission https://trac.osgeo.org/mapguide/changeset/3127.

Note: See TracTickets for help on using tickets.