[vtkusers] Contour slice by slice

[Jonathan Morra]

I don't save the data until the user presses save.  There is
one OrientedGlyphContourRepresentation per contour.

On Tue, Oct 19, 2010 at 8:11 PM, shengwen guo <shengwen.guo at gmail.com>wrote:

> Do you mean that the current contour is stored automatically and
> internally? Was only one OrientedGlyphContourRepresentation used in your
> method and when did you save the current drawing contour to the ploydata
> array?
> But I found there are many slices behind the window if I set contourwidgets
> on and off. For example, if I close the display window, there are other
> slices which were displayed before. Therefore I think these slices havn't
> been cleared really in the background, the side effect seems that the
> contours will added together and it's very slow. I think there must be some
> problems. I need clear other contourwidgets at first and then reload the
> contour from polydata array to initial the current contourwidget.
>
>
> On Wed, Oct 20, 2010 at 10:06 AM, Jonathan Morra <jonmorra at gmail.com>wrote:
>
>> I don't do things this way.  I let the vtkContourWidgets' representations
>> store the appropriate points.  It is only when I need to save the data to
>> disk that I actually look at the vtkPolyData from the widgets.  This let's
>> me not worry about the contents of the contour widgets till it's time to
>> save.  All I have to do is turn on/off the contour widgets themselves.
>>
>>
>> On Tue, Oct 19, 2010 at 6:48 PM, shengwen guo <shengwen.guo at gmail.com>wrote:
>>
>>> Mr. Morra,
>>>    With your great help, I think I will implement the method soon. The
>>> last issue is that I need save the previous contour data before the slice is
>>> changed, and then initialize the new contour using initial points or contour
>>> data from the corresponding polydata array where the contour data is stored.
>>> I use a class vtkSliderCallback : public vtkCommand and refresh window on
>>> function Execute(vtkObject *caller, unsigned long ul, void* vd),  However, I
>>> found I can get the new slice position from the slicer and it's difficult to
>>> get the previous slice position because the Execute() is called after the
>>> slider is changed. Do you have any ideas?
>>>     Thank you again.
>>>
>>>
>>> --
>>> --------------------------------------------------------
>>> Shengwen Guo,Ph.D
>>> Associate Professor
>>> Department of Biomedical Engineering,
>>> South China University of Technology,
>>> Higher Education Mega Center, Guangzhou,510006, P.R.China
>>>
>>>
>>
>
>
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.vtk.org/pipermail/vtkusers/attachments/20101019/9a9f9f0d/attachment.htm>