Opened 15 years ago
Closed 15 years ago
#54 closed defect (fixed)
Silly way of doing Object3D::getSpatialSize()
Reported by: | MatthewWhiting | Owned by: | MatthewWhiting |
---|---|---|---|
Priority: | normal | Milestone: | |
Component: | Code base | Version: | 1.1.7 |
Severity: | normal | Keywords: | |
Cc: |
Description
The way Object3D::getSpatialSize() works is a bit dumb -- why not just get the size of each Object2D present and add them up?
Check this to see whether that would be quicker and implement it that way!
Change History (2)
comment:1 Changed 15 years ago by
Status: | new → assigned |
---|
comment:2 Changed 15 years ago by
Resolution: | → fixed |
---|---|
Status: | assigned → closed |
Note: See
TracTickets for help on using
tickets.
The suggestion I made there was itself a bit dumb, as it is the spatial size we're after, ie. just the number of distinct (x,y) values.
Better way is to just get the spatial map and find the size of that. Have done that in the refactored code, and it will flow through to the trunk eventually.
Closing ticket.