Opened 9 years ago

Closed 9 years ago

#1916 closed defect (fixed)

Map extent MaxX incorrectly written in RuntimeMapSerializeExtent

Reported by: hm Owned by: jng
Priority: medium Milestone:
Component: Maestro Version: 2.2.0
Severity: critical Keywords: Serialize Extent MaxX
Cc: External ID:


The RuntimeMap? SerializeExtent? has a bug.

The extents are written as this: s.Write(env.MinX); s.Write(env.MinY); s.Write(env.MaxY); s.Write(env.MaxY);

This should be:

s.Write(env.MinX); s.Write(env.MinY); s.Write(env.MaxX); s.Write(env.MaxY);

Change History (3)

comment:1 Changed 9 years ago by hm

Will this bug be corrected both in the Maestro4 branch as well as trunk?

comment:2 Changed 9 years ago by hm

One more thing. Perhaps the test application could implement some sort of test for this type of error?

  1. Create object (RuntimeMap?, RuntimeMapLayer? etc.) with all properties (like map extents) set.
  2. Serialize it
  3. Deserialize it again
  4. Compare the deserialized object properties with the original object (they should be identical).

comment:3 Changed 9 years ago by jng

Resolution: fixed
Status: newclosed

Fixed 4.0 branch r6432 Fixed trunk r6433

Note: See TracTickets for help on using tickets.