<div dir="ltr">Thanks for commenting. In that case, we gonna move forward and integrate Kevin topic into Slicer.<div><br></div><div style>@Kevin: In the commit message and/or doxygen, I would suggest that you write down how it could be done using VTK 6. That way the transition to VTK 6 will be even easier.</div>
<div style><br></div><div style>@David: Do you see anything in the API proposed by Kevin that could be changed to be closer to what is possible in VTK 6 ? </div><div style>See [1]</div><div style><br></div><div style>Jc</div>
<div style><br></div><div style>[1] <a href="https://github.com/kevinwangcanada/Slicer/commit/551c8b7f435b518664eef2917818addf78c853e6">https://github.com/kevinwangcanada/Slicer/commit/551c8b7f435b518664eef2917818addf78c853e6</a></div>
</div><div class="gmail_extra"><br><br><div class="gmail_quote">On Mon, Sep 16, 2013 at 3:38 PM, David Thompson <span dir="ltr"><<a href="mailto:david.thompson@kitware.com" target="_blank">david.thompson@kitware.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi all,<br>
<br>
> I took a quick look at vtkScalarBarActor/vtkScalarsToColors and saw quite a bit changes between 5.10 and 6.0. ...<br>
<br>
Yes, it uses the new matplotlib MathText rendering engine to draw labels and that required a lot of skullduggery to get working with VTK 6's modules. I would advise against trying to backport it.<br>
<span class="HOEnZb"><font color="#888888"><br>
David<br>
</font></span><div class="HOEnZb"><div class="h5"><br>
><br>
> From: Jean-Christophe Fillion-Robin [mailto:<a href="mailto:jchris.fillionr@kitware.com">jchris.fillionr@kitware.com</a>]<br>
> Sent: Monday, September 16, 2013 12:41 PM<br>
> To: Wang, Kevin<br>
> Cc: David Thompson; <a href="mailto:vtk-developers@vtk.org">vtk-developers@vtk.org</a><br>
> Subject: Re: [vtk-developers] Possible vtkScalarBarActor improvement<br>
><br>
> Hi Kevin,<br>
><br>
> I would suggest you a submit a pull request to the SlicerVTK fork backporting the functionality you would like. Then, when we will transition to VTK6, it will go very smoothly.<br>
><br>
> In parallel, you could also submit a patch to the VTK list that would be integrated to the VTK 5.10 maintenance branch.<br>
><br>
> Thanks<br>
> Jc<br>
><br>
><br>
> On Mon, Sep 16, 2013 at 11:24 AM, Wang, Kevin <<a href="mailto:kevin.wang@rmp.uhn.on.ca">kevin.wang@rmp.uhn.on.ca</a>> wrote:<br>
> Thanks David. I think I am ok with switching the vtkStringArrays on the fly.<br>
><br>
> Kevin<br>
><br>
> -----Original Message-----<br>
> From: David Thompson [mailto:<a href="mailto:david.thompson@kitware.com">david.thompson@kitware.com</a>]<br>
> Sent: Monday, September 16, 2013 11:17 AM<br>
> To: Wang, Kevin<br>
> Cc: 'Jean-Christophe Fillion-Robin'; <a href="mailto:vtk-developers@vtk.org">vtk-developers@vtk.org</a><br>
> Subject: Re: [vtk-developers] Possible vtkScalarBarActor improvement<br>
><br>
> Hi Kevin,<br>
><br>
> > The SetAnnotation method in vtkScalarsToColors is what I need in deed. ...<br>
><br>
> Great.<br>
><br>
> > The interface is fine. I wonder if it is possible to add a method to control whether values are used for labels in the vtkScalarBarActor or the annotations are used. ...<br>
><br>
> I would be willing to consider adding something to the vtkScalarsToColors class to switch between sets of strings if we can come up with a clean API that preserves backwards-compatability -- but don't think the class should be responsible for generating a string label for each value; it is very hard to get otherwise-rational people to agree on how to format numbers and vtkVarints as text. :-)<br>
><br>
> David<br>
><br>
><br>
> This e-mail may contain confidential and/or privileged information for the sole use of the intended recipient.<br>
> Any review or distribution by anyone other than the person for whom it was originally intended is strictly prohibited.<br>
> If you have received this e-mail in error, please contact the sender and delete all copies.<br>
> Opinions, conclusions or other information contained in this e-mail may not be that of the organization.<br>
><br>
><br>
><br>
><br>
> --<br>
> <a href="tel:%2B1%20919%20869%208849" value="+19198698849">+1 919 869 8849</a><br>
><br>
> This e-mail may contain confidential and/or privileged information for the sole use of the intended recipient.<br>
> Any review or distribution by anyone other than the person for whom it was originally intended is strictly prohibited.<br>
> If you have received this e-mail in error, please contact the sender and delete all copies.<br>
> Opinions, conclusions or other information contained in this e-mail may not be that of the organization.<br>
<br>
</div></div></blockquote></div><br><br clear="all"><div><br></div>-- <br>+1 919 869 8849<br>
</div>