Page Menu
Home
Phabricator
Search
Configure Global Search
Log In
Files
F311
ChangeRequest.txt
Public
Actions
View File
Edit File
Delete File
View Transforms
Subscribe
Mute Notifications
Award Token
Flag For Later
Authored By
•
schmidts
Sep 11 2009, 10:46 AM
2009-09-11 10:46:30 (UTC+2)
Size
648 B
Referenced Files
None
Subscribers
None
ChangeRequest.txt
View Options
Summary of bug description
* legacy mitkVolumeDataVtkMapper3D had 3 LOD levels, but used the same rendering mode for 2 levels
* modify RenderingManager to set maximum LOD to 1 ( ^= 2 LOD levels)
Cause of the bug
When integrating MIP-Projection Rendering Mode in mitkVolumeDataVtkMapper3D,
it was unsupported in the vtkVolumeTextureMapper2D mapper, and he was disabled,
but still his LOD level was present.
Proposed solution
* modify RenderingManager to set maximum LOD to 1 ( ^= 2 LOD levels)
Affected classes
* mitk::RenderingManager
* mitk::VolumeDataVtkMapper3D
How will the bugfix get tested?
manual test
File Metadata
Details
Attached
Mime Type
text/plain
Storage Engine
blob
Storage Format
Raw Data
Storage Handle
299
Default Alt Text
ChangeRequest.txt (648 B)
Attached To
Mode
T2462: preliminary inclusion of vtk 5.5 vtkVolumeTextureMapper3D in Mitk
Attached
Detach File
Event Timeline
•
schmidts
added a comment.
Sep 11 2009, 10:46 AM
2009-09-11 10:46:30 (UTC+2)
Comment Actions
Change Request
Log In to Comment