Page MenuHomePhabricator
Create Task
Maniphest T10245

Is transparent background still reasonable?
Closed, DuplicatePublic
Actions

Description

In order to ensure a correct rendering of PET images with enabled "Inverted Black to White" lookup table we need to remove this line in the deprecated class/method mitkImageMapperGL2D::ApplyProperties() :

LookupTableProp->GetLookupTable()->ChangeOpacity(0, 0.0); (line 1102)

Removing this line prevents that the background (value 0) is fully transparent if a lookup table is applied.

The question is: Is this in the new version of the ImageMapper class still reasonable to change the opacity of the background? Which use cases need a transparent background (e.g. binary images?)?

Related Objects

Event Timeline

kast added projects: MITK, Bugzilla.Nov 25 2011, 9:22 AM
ivo added a subscriber: ivo.Nov 25 2011, 10:07 AM

(In reply to comment #0)

Which use cases need a transparent background (e.g. binary images?)?

This was probably the original use case. A solution could be to use transparent backgrounds for binary images (identified by checking whether the binary property is true) only.

Another problem is decribed in T10174 comment 2:

The background of the image with the smaller dimension will also become visible
and you cannot see the second image anymore.

kislinsk closed this task as a duplicate of T10174: Provide opacity property for first color in Lookup Table.Aug 1 2016, 10:47 PM
MITK · MIC · IMSY · DKFZ