Opened 13 years ago
Closed 13 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: |
Description
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 by , 13 years ago
comment:2 by , 13 years ago
One more thing. Perhaps the test application could implement some sort of test for this type of error?
- Create object (RuntimeMap, RuntimeMapLayer etc.) with all properties (like map extents) set.
- Serialize it
- Deserialize it again
- Compare the deserialized object properties with the original object (they should be identical).
comment:3 by , 13 years ago
Resolution: | → fixed |
---|---|
Status: | new → closed |
Note:
See TracTickets
for help on using tickets.
Will this bug be corrected both in the Maestro4 branch as well as trunk?