Ticket #141 (closed defect: wontfix)

Opened 2 years ago

Last modified 1 year ago

Volume bounds are not reset upon call to setEmpty

Reported by: cneumann Assigned to: unassigned
Priority: minor Milestone: 1.8 Release
Component: System Version: 1.8
Keywords: Cc:
Completion:

Description

for a non-empty DynamicVolume vol, calling vol.setEmpty(), vol.getBounds(min,max) will give the old min,max values, not the expected (0,0,0), (0,0,0).

Reported on the users list by Josef Grunig, message titled "updateVolume strange behaviour"

Attachments

testVolumeBug.cpp (1.7 kB) - added by cneumann on 12/06/06 07:50:03.
small test to demonstrate the problem

Change History

12/06/06 07:50:03 changed by cneumann

  • attachment testVolumeBug.cpp added.

small test to demonstrate the problem

01/05/07 06:50:16 changed by cneumann

  • status changed from new to closed.
  • resolution set to invalid.

Dirk has clarified that this is intentional, code has to deal with empty volumes by explicitly checking with Volume::isEmpty()

closing as invalid.

(follow-up: ↓ 3 ) 01/05/07 13:23:36 changed by dirk

  • priority changed from major to minor.
  • status changed from closed to reopened.
  • resolution deleted.

Followup: Generally true, an app that wants to handle empty volumes need to check flags. Nonetheless, we could set the bounds to 0 on set empty. I don't like it very much, as setState() would circumvent it…

(in reply to: ↑ 2 ) 01/05/07 13:33:19 changed by cneumann

Replying to dirk:

Followup: Generally true, an app that wants to handle empty volumes need to check flags. Nonetheless, we could set the bounds to 0 on set empty. I don't like it very much, as setState() would circumvent it…

me neither; if we did it, it would be even harder to find the bug next time. So let's close this ticket and open one to add documentation to the volume stuff that explains this ;)

01/31/07 17:40:46 changed by dirk

  • status changed from reopened to closed.
  • resolution set to wontfix.