Please wait until the end of today. I will request a core change regarding
this matter (bug-14386-colormaps-and-luts). we could adapt Matt´s request
on it once merged on the master.
regards,
sebastian
On Wed, Jul 24, 2013 at 11:30 AM,
<[email protected]>wrote:
> Send mitk-users mailing list submissions to
> [email protected]
>
> To subscribe or unsubscribe via the World Wide Web, visit
> https://lists.sourceforge.net/lists/listinfo/mitk-users
> or, via email, send a message with subject or body 'help' to
> [email protected]
>
> You can reach the person managing the list at
> [email protected]
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of mitk-users digest..."
>
>
> Today's Topics:
>
> 1. Logging all user interaction (Clarkson, Matt)
> 2. Question about opacity (Clarkson, Matt)
> 3. Re: Question about opacity (Daniel Maleike)
> 4. Re: Question about opacity (Clarkson, Matt)
> 5. Re: Question about opacity (Daniel Maleike)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Tue, 23 Jul 2013 11:09:54 +0000
> From: "Clarkson, Matt" <[email protected]>
> Subject: [mitk-users] Logging all user interaction
> To: "[email protected]"
> <[email protected]>
> Message-ID: <[email protected]>
> Content-Type: text/plain; charset="us-ascii"
>
> Hi Everyone,
>
> this came up in a recent conversation: Has anyone got a good way of
> tracking and logging all user input, including Qt widget interactions, and
> interactions within a QVTK RenderWindow? This should also include outputing
> things like when a slice number changes in a slice navigation controller,
> so you can tell that the user is viewing a certain image slice or location.
>
> Thanks
>
> Matt
>
>
>
>
>
> ------------------------------
>
> Message: 2
> Date: Wed, 24 Jul 2013 06:45:39 +0000
> From: "Clarkson, Matt" <[email protected]>
> Subject: [mitk-users] Question about opacity
> To: "[email protected]"
> <[email protected]>
> Message-ID: <[email protected]>
> Content-Type: text/plain; charset="Windows-1252"
>
> Hi there,
>
> in bug 10174 i suggested a property so that you could adjust the opacity
> of the lowest value in a lookup table, so that anything that was mapped to
> that lowest value (typically black) could be transparent, or opaque.
>
> Then a whole load of changes were made to the rendering
> framework?..(gratefully received), but I now don't know if the new
> framework supports my suggested behaviour in a different way, or does not
> support it.
>
> Please can someone explain, and especially explain the Image Rendering
> Mode property. Does this affect opacity?
>
> Thanks
>
> Matt
>
>
>
>
>
> ------------------------------
>
> Message: 3
> Date: Wed, 24 Jul 2013 09:46:08 +0200
> From: Daniel Maleike <[email protected]>
> Subject: Re: [mitk-users] Question about opacity
> To: <[email protected]>
> Message-ID: <[email protected]>
> Content-Type: text/plain; charset="windows-1252"; format=flowed
>
> On 24.07.2013 08:45, Clarkson, Matt wrote:
> > Hi there,
> >
> > in bug 10174 i suggested a property so that you could adjust the opacity
> of the lowest value in a lookup table, so that anything that was mapped to
> that lowest value (typically black) could be transparent, or opaque.
> >
> > Then a whole load of changes were made to the rendering
> framework?..(gratefully received), but I now don't know if the new
> framework supports my suggested behaviour in a different way, or does not
> support it.
> >
> > Please can someone explain, and especially explain the Image Rendering
> Mode property. Does this affect opacity?
>
> Dear Matt,
>
> from how I understand your original bug description, I think you want to
> use the "LookupTable_LevelWindow_Color" mode. There is a minimum of
> documentation at
>
> http://docs.mitk.org/nightly-qt4/classmitk_1_1RenderingModeProperty.html
>
> but I agree that this should be much improved (not taking the bug
> documentation as an example). I'll try to bring this to discussion.
>
> Regards,
> Daniel
>
> --
> Dr. Daniel Maleike Telefon: + 49 6221 647976 3
> Mint Medical GmbH, Friedrich-Ebert-Stra?e 2, 69221 Dossenheim/Heidelberg
> Gesch?ftsf?hrer: Dr. Matthias Baumhauer
> Registergericht Mannheim, HRB 709351
>
>
>
> ------------------------------
>
> Message: 4
> Date: Wed, 24 Jul 2013 08:00:02 +0000
> From: "Clarkson, Matt" <[email protected]>
> Subject: Re: [mitk-users] Question about opacity
> To: Daniel Maleike <[email protected]>
> Cc: "<[email protected]>"
> <[email protected]>
> Message-ID: <[email protected]>
> Content-Type: text/plain; charset="windows-1252"
>
> THanks Daniel,
>
> does this mean my LookupTable that I set must have the opacity values set
> as well?.. i.e. RGBA for each entry in the lookup table.
>
> Thanks
>
> M
>
>
>
> On 24 Jul 2013, at 08:46, Daniel Maleike <[email protected]
> <mailto:[email protected]>>
> wrote:
>
> On 24.07.2013 08:45, Clarkson, Matt wrote:
> Hi there,
>
> in bug 10174 i suggested a property so that you could adjust the opacity
> of the lowest value in a lookup table, so that anything that was mapped to
> that lowest value (typically black) could be transparent, or opaque.
>
> Then a whole load of changes were made to the rendering
> framework?..(gratefully received), but I now don't know if the new
> framework supports my suggested behaviour in a different way, or does not
> support it.
>
> Please can someone explain, and especially explain the Image Rendering
> Mode property. Does this affect opacity?
>
> Dear Matt,
>
> from how I understand your original bug description, I think you want to
> use the "LookupTable_LevelWindow_Color" mode. There is a minimum of
> documentation at
>
> http://docs.mitk.org/nightly-qt4/classmitk_1_1RenderingModeProperty.html
>
> but I agree that this should be much improved (not taking the bug
> documentation as an example). I'll try to bring this to discussion.
>
> Regards,
> Daniel
>
> --
> Dr. Daniel Maleike Telefon: + 49 6221 647976 3
> Mint Medical GmbH, Friedrich-Ebert-Stra?e 2, 69221 Dossenheim/Heidelberg
> Gesch?ftsf?hrer: Dr. Matthias Baumhauer
> Registergericht Mannheim, HRB 709351
>
>
> ------------------------------------------------------------------------------
> See everything from the browser to the database with AppDynamics
> Get end-to-end visibility with application monitoring from AppDynamics
> Isolate bottlenecks and diagnose root cause in seconds.
> Start your free trial of AppDynamics Pro today!
> http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk
> _______________________________________________
> mitk-users mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/mitk-users
>
>
> -------------- next part --------------
> An HTML attachment was scrubbed...
>
> ------------------------------
>
> Message: 5
> Date: Wed, 24 Jul 2013 11:29:57 +0200
> From: Daniel Maleike <[email protected]>
> Subject: Re: [mitk-users] Question about opacity
> To: <[email protected]>
> Message-ID: <[email protected]>
> Content-Type: text/plain; charset="windows-1252"; format=flowed
>
> On 24.07.2013 10:00, Clarkson, Matt wrote:
> > THanks Daniel,
> >
> > does this mean my LookupTable that I set must have the opacity values
> > set as well?.. i.e. RGBA for each entry in the lookup table.
>
> No, the opacity property is applied to the complete image after color
> mapping (from what I understand). Actually I tried this by just playing
> with the propery list of mitkWorkbench.
> If you load a CT image and a matching second image above it, just change
> the rendering mode and play with "opacity". If no lookup table is
> defined by the code (as in mitkWorkbench), rendering falls back to a
> default table of rainbow colors..
>
> Regards,
> Daniel
>
> --
> Dr. Daniel Maleike Telefon: + 49 6221 647976 3
> Mint Medical GmbH, Friedrich-Ebert-Stra?e 2, 69221 Dossenheim/Heidelberg
> Gesch?ftsf?hrer: Dr. Matthias Baumhauer
> Registergericht Mannheim, HRB 709351
>
>
>
> ------------------------------
>
>
> ------------------------------------------------------------------------------
> See everything from the browser to the database with AppDynamics
> Get end-to-end visibility with application monitoring from AppDynamics
> Isolate bottlenecks and diagnose root cause in seconds.
> Start your free trial of AppDynamics Pro today!
> http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk
>
> ------------------------------
>
> _______________________________________________
> mitk-users mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/mitk-users
>
>
> End of mitk-users Digest, Vol 86, Issue 27
> ******************************************
>
------------------------------------------------------------------------------
See everything from the browser to the database with AppDynamics
Get end-to-end visibility with application monitoring from AppDynamics
Isolate bottlenecks and diagnose root cause in seconds.
Start your free trial of AppDynamics Pro today!
http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk
_______________________________________________
mitk-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mitk-users
