<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
Hi Burlen, <br>
<br>
Thanks for pointing me to the User guide. Very useful.<br>
Im rather new to Paraview/vtk, and I find it it hard to find precise
information how to get started *as a developer*. There is plenty of
material giving a more or less high level description, or it assumes
that all kind of knowlegde is already there ...). I'm not
complaining though, just need the time and the right references.<br>
<br>
Thanks for your help.<br>
Bertwim<br>
<br>
<br>
<div class="moz-cite-prefix">On 10/05/2014 05:26 PM, Burlen Loring
wrote:<br>
</div>
<blockquote cite="mid:54316321.2080000@lbl.gov" type="cite">
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
<div class="moz-cite-prefix">Hi Bertwim,<br>
<br>
I should have explained the cells better. The cells are
descriptions of how points are combined into geometric
primitives that can be rendered by OpenGL (or converted into
those understood by OpenGL). Here is an <a
moz-do-not-send="true"
href="http://www.vtk.org/VTK/img/file-formats.pdf">excerpt</a>
of the User Guide describing VTK's cells, see p9-10.<br>
<br>
Burlen<br>
<br>
On 10/5/2014 8:17 AM, B.W.H. van Beest wrote:<br>
</div>
<blockquote cite="mid:5431610D.2030403@xs4all.nl" type="cite">
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
Hi Burlen, <br>
<br>
Thanks for your reply. On the cell-info: I now (finally)
understood what was there to be. After implementing the cells, I
indeed got the expected display. On the book: what keeps me from
buying is that it seems outdated (because it refers to version
3).<br>
The texture coordinates I had found on Google indeed. What I
needed was how to apply it in Paraview/VTK. I will look into
that again Maybe it becomes clear now.<br>
<br>
Thanks<br>
Bertwim<br>
<br>
<br>
<div class="moz-cite-prefix">On 10/05/2014 05:05 AM, Burlen
Loring wrote:<br>
</div>
<blockquote cite="mid:5430B56C.2090208@lbl.gov" type="cite">
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
<div class="moz-cite-prefix">I assume in your request data you
are generating a vtkPolyData dataset. At the end of request
data call "dataset->Print(cerr);" . That's the one of the
best debug method when you don't see what you think you
should in PV while developing a new filter/source/reader
what ever. The information tab in the GUI gives a subset of
that, also useful.<br>
<br>
texture coordinates are usually for applying an image to the
surface. google it and you'll find volumes of info. In pv
they are optional.<br>
<br>
the cell array I'm afraid is not. when generating poly or
unstructured data. If you have no cells what do you expect
to see?<br>
<br>
normals are per point.<br>
<br>
some of your questions suggest that the book <a
moz-do-not-send="true"
href="http://www.kitware.com/products/books/vtkguide.html">VTK
user guide</a> would be a good investment for you.<br>
<br>
Hope I didn't miss anything. ;-)<br>
<br>
On 10/4/2014 8:30 AM, B.W.H. van Beest wrote:<br>
</div>
<blockquote cite="mid:5430129D.3020508@xs4all.nl" type="cite">
<pre wrap="">Hello,
I need to write a new Source, representing a 'TriPrism",
i.e. a prism where the top and bottom planes are triangles. So far, I
failed.
Being unable to find appropriate documentation, I used the source code
of vtkCubeSource as an example, thinking it would be an easy change.
Wrong! The prism doesn't show on the screen. The
properties panel behaves as expected (and ok, as far I can see).
The member function 'RequestData' seems to be the important method.
But the code of the example (as well as other source examples) is on
closer inspection not clear to me at all.
The following is happening in the vtkCubeSource:
a) The point of the cube are generated. This is straightforward and
easily
translates to the triprism.
The new points are updated via a call "output->setPoints(
newPoints );"
b) The normals (to the side planes of the cube) are being calculated.
The new normals are updated via a call
"output->GetPointData()->SetNormals(newNormals);"
This is also straightforward for the triprism, but:
Q: although calculating the normals is straightforward,
in which order are they supposed to be given?
c) Also, texture coordinates (TCoords) are calculated.
Q: What are these? Are these mandatory?
d) Also, a new vtkCellArray is being created. ('newPolys')
Q: Same question. No clue what I should do here.
As usual, any clue of how to attack this is greatly appreciated.
Bertwim
_______________________________________________
Powered by <a moz-do-not-send="true" class="moz-txt-link-abbreviated" href="http://www.kitware.com">www.kitware.com</a>
Visit other Kitware open-source projects at <a moz-do-not-send="true" class="moz-txt-link-freetext" href="http://www.kitware.com/opensource/opensource.html">http://www.kitware.com/opensource/opensource.html</a>
Please keep messages on-topic and check the ParaView Wiki at: <a moz-do-not-send="true" class="moz-txt-link-freetext" href="http://paraview.org/Wiki/ParaView">http://paraview.org/Wiki/ParaView</a>
Follow this link to subscribe/unsubscribe:
<a moz-do-not-send="true" class="moz-txt-link-freetext" href="http://public.kitware.com/mailman/listinfo/paraview">http://public.kitware.com/mailman/listinfo/paraview</a>
</pre>
</blockquote>
<br>
</blockquote>
<br>
</blockquote>
<br>
</blockquote>
<br>
</body>
</html>