Hi Gerald, if any pixel in an image has a grey value, that is lower than the lower bound of the level window it is in fact not rendered as black, but as transparent. If you happen to have an image on layer below that has a non black pixel at the same position it will show through.
You can easily observe this by loading the same image twice, setting the colour of the background image to red and changing the level window of the foreground one to a small width in the upper grey value range. Best regards, Caspar Goch Von: Lodron, Gerald [mailto:[email protected]] Gesendet: Freitag, 13. August 2010 10:51 An: '[email protected]' Betreff: [mitk-users] Strange rendering artefacts Hi I found some strange rendering artefacts in the following case: I have two mitk::Image's with different size and spacing loaded, all with opacity = 1, default level window, default lookup table (n/a) and the default transfer function, texture interpolation is set to OFF and both are marked as visible. So normally only the image which is at top layer should be visible (fore sure without border area when the background image is bigger than the foreground image). At the first look that seems to be right but when i look closer (especially at dark regions with zoom) and toggle the visibility of the background image i can see some pixels which change their value. The grayvalue change is only in the Renderer visible, in the lower area where the Position/Index/Time and Pixelvalue is displayed the Pixelvalue stays the same.... I posted some screenshots at my Bugreport 5091 Any ideas where they come from???
------------------------------------------------------------------------------ This SF.net email is sponsored by Make an app they can't live without Enter the BlackBerry Developer Challenge http://p.sf.net/sfu/RIM-dev2dev
_______________________________________________ mitk-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mitk-users
