View Issue Details [ Jump to Notes ] | [ Print ] | ||||||||
ID | Project | Category | View Status | Date Submitted | Last Update | ||||
0012799 | VTK | (No Category) | public | 2011-12-16 05:47 | 2016-08-12 09:55 | ||||
Reporter | tomasz | ||||||||
Assigned To | Dave DeMarle | ||||||||
Priority | normal | Severity | minor | Reproducibility | have not tried | ||||
Status | closed | Resolution | moved | ||||||
Platform | OS | OS Version | |||||||
Product Version | 5.6.1 | ||||||||
Target Version | Fixed in Version | ||||||||
Summary | 0012799: VRML Exporter disregards UseLookupTableScalarRangeOn on LookupTables | ||||||||
Description | In its (internal) PolyDataMapper the exporter "copies" ScalarRange from the actor (Get/Set), disregarding UseLookupTableScalarRangeOn if such done. As a result the lookup table (colors) gets reset to the defaout range 0..1. Remark: I do not now if "by design" the GetScalarRange shall (only) return what has been "Sat" (diregarding UseLookupTableScalarRangeOn) OR if any Exporter shall check UseLookupTableScalarRangeOn and go the other (now missing) way. My Code: contourMapper.ScalarVisibilityOn(); contourMapper.SetLookupTable(_LookupTable); contourMapper.UseLookupTableScalarRangeOn(); // otherwise Mapper overwites lut range! and in vtkVRMLExporter: pm = vtkPolyDataMapper::New(); pm->SetInput(pd); pm->SetScalarRange(anActor->GetMapper()->GetScalarRange()); <================?????? pm->SetScalarVisibility(anActor->GetMapper()->GetScalarVisibility()); pm->SetLookupTable(anActor->GetMapper()->GetLookupTable()); pm->SetScalarMode(anActor->GetMapper()->GetScalarMode()); i.e. no check if UseLookupTableScalarRangeOn used instead | ||||||||
Tags | No tags attached. | ||||||||
Project | TBD | ||||||||
Type | incorrect functionality | ||||||||
Attached Files | |||||||||
Relationships | |
Relationships |
Notes | |
(0027825) tomasz (reporter) 2011-12-16 06:03 |
Seems the ALL exporters miss the copy: pm->SetUseLookupTableScalarRange(m->GetUseLookupTableScalarRange()); an more! Looking at vtkMapper::ShallowCopy: this->SetLookupTable(m->GetLookupTable()); this->SetScalarVisibility(m->GetScalarVisibility()); this->SetScalarRange(m->GetScalarRange()); this->SetColorMode(m->GetColorMode()); this->SetScalarMode(m->GetScalarMode()); this->SetScalarMaterialMode(m->GetScalarMaterialMode()); this->SetImmediateModeRendering(m->GetImmediateModeRendering()); this->SetUseLookupTableScalarRange(m->GetUseLookupTableScalarRange());<==== Think adding at least pm->SetUseLookupTableScalarRange(m->GetUseLookupTableScalarRange()); in each exporter would immediately fix it (i'm not involved in VTK project itself, so please fix it). Kind Regards, Tomasz. |
(0031176) Dave DeMarle (administrator) 2013-07-22 16:54 |
Please reopen this report if the bug is still present in 6.0.0. |
(0037262) Kitware Robot (administrator) 2016-08-12 09:55 |
Resolving issue as `moved`. This issue tracker is no longer used. Further discussion of this issue may take place in the current VTK Issues page linked in the banner at the top of this page. |
Notes |
Issue History | |||
Date Modified | Username | Field | Change |
2011-12-16 05:47 | tomasz | New Issue | |
2011-12-16 06:03 | tomasz | Note Added: 0027825 | |
2013-07-22 16:54 | Dave DeMarle | Note Added: 0031176 | |
2013-07-22 16:54 | Dave DeMarle | Status | backlog => expired |
2013-07-22 16:54 | Dave DeMarle | Assigned To | => Dave DeMarle |
2016-08-12 09:55 | Kitware Robot | Note Added: 0037262 | |
2016-08-12 09:55 | Kitware Robot | Status | expired => closed |
2016-08-12 09:55 | Kitware Robot | Resolution | open => moved |
Issue History |
Copyright © 2000 - 2018 MantisBT Team |