Hi Klaus, your idea sounds good. Would you be willing to implement it and contribute the code?
Best Regards, Jochen > -----Ursprüngliche Nachricht----- > Von: Klaus Drechsler [mailto:[email protected]] > Gesendet: Samstag, 2. Mai 2009 00:53 > An: [email protected] > Betreff: [mitk-users] TransferFunctions > > Hi, > > I reference the latest svn version of mitk. > > 1. The method 'SetTransferFunctionMode' apears not in the nightly doc > (part of mitkTransferFunction.cpp). > > 2. I don´t like the idea that default transfer function modes are hard > coded in mitkTransferFunction.cpp (in method SetTransferFunctionMode). > This makes it hard to extend. IMO this code is belongs to the > VolumeVisualization Functionality. > > Even better: > mitkTransferFunction.cpp should only manage transfer function modes > that > are set by functionalities (A 'heart' functionality could add a > 'cardiac > ct' mode, a 'liver' functionality could add a 'liver' mode, the volume > vizualization functionality could add a bunch of modes[the ones that > are > hard coded now for example] ...). Then a functionality could request > the 'modes' from mitkTransferFunction.cpp and displays them to the user > (as it is implemented right now in the volume visualization > functionality). API could be (something) like: > > addMode(name, transferFunction) > remMode(name) > setCurrentMode(name) > vector getModes() > > 3. There is a 'MITK default' mode that can be set in the volume > visualization functionality. But this default transfer function is not > set when a dataset is loaded. When I remember correctly this was the > case n revisions ago. Currently I get 'invisible' renderings when I use > my old functionalities that just set the volume rendering property to > 'on'. This is not the case with an older revisions that I used for > development. I suggest: setting 'MITK default' to newly loaded > datasets. > > Or even better: > Change the behaviour of the TransferFunction property so that one can > use the name of a 'mode' instead of a TransferFunction object. So one > can turn volumerendering on and set a TransferFunction with just two > lines of code within a functionality. (The renderer then has to request > the actual TransferFunction from mitkTransferFunction.cpp)) > > Best regards > > Klaus > > ----------------------------------------------------------------------- > ------- > Register Now & Save for Velocity, the Web Performance & Operations > Conference from O'Reilly Media. Velocity features a full day of > expert-led, hands-on workshops and two days of sessions from industry > leaders in dedicated Performance & Operations tracks. Use code vel09scf > and Save an extra 15% before 5/3. http://p.sf.net/sfu/velocityconf > _______________________________________________ > mitk-users mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/mitk-users ------------------------------------------------------------------------------ The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your production scanning environment may not be a perfect world - but thanks to Kodak, there's a perfect scanner to get the job done! With the NEW KODAK i700 Series Scanner you'll get full speed at 300 dpi even with all image processing features enabled. http://p.sf.net/sfu/kodak-com _______________________________________________ mitk-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mitk-users
