<div dir="ltr">Cory,<div>Thanks much. It means that except appending all classes by "vtk" nothing needs to be changed and is the crash related to "RequestData" implementation? <div><br></div><div>Chiranjib</div></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Mon, Jul 18, 2016 at 7:44 PM, Cory Quammen <span dir="ltr"><<a href="mailto:cory.quammen@kitware.com" target="_blank">cory.quammen@kitware.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="im HOEnZb">Chiranjib,<br>
<br>
CC'ing the developer's list so that others may benefit.<br>
<br>
Please see my modifications to your code attached. I wouldn't stress<br>
out about crashes until you more fully implement your plugin.<br>
<br>
Thanks,<br>
Cory<br>
<br>
</span><div class="HOEnZb"><div class="h5">On Mon, Jul 18, 2016 at 1:15 AM, Chiranjib Sur <<a href="mailto:sur.chiranjib@gmail.com">sur.chiranjib@gmail.com</a>> wrote:<br>
> Hi Cory,<br>
> Sorry to bother you again.<br>
><br>
> I started with a clear mind this morning. Here is my modified sources<br>
> (prepended the class/file names with vtk ) attached. While building I can<br>
> build the ".so": and can load this as a plugin. However, when I want to<br>
> create the source from the menu, I get a seg fault. I think it's an issue<br>
> with some port. Since I have not implemented "RequestData" i don't expect<br>
> anyting to be displayed in the PV window, however it landed with a crash.<br>
><br>
> You mentioned that by "appending the names with vtk" you could get it<br>
> worked. Could yo you please share the modification you have made it to work<br>
> or have a look at my attachment?<br>
><br>
> Thanks,<br>
> Chiranjib<br>
><br>
> On Fri, Jul 15, 2016 at 12:37 AM, Chiranjib Sur <<a href="mailto:sur.chiranjib@gmail.com">sur.chiranjib@gmail.com</a>><br>
> wrote:<br>
>><br>
>> Yep! I have access now and have the edit privilege. I will start adding<br>
>> things shortly. Let me make a list of things that I have learnt mostly via<br>
>> discussions using the mailing list.<br>
>><br>
>> Chiranjib<br>
>><br>
>><br>
>> On Fri, Jul 15, 2016 at 12:28 AM, Cory Quammen <<a href="mailto:cory.quammen@kitware.com">cory.quammen@kitware.com</a>><br>
>> wrote:<br>
>>><br>
>>> Okay, you should have gotten an email with a randomly generated<br>
>>> password that should get you access to the wiki. You should be able to<br>
>>> edit it - let me know if you can't.<br>
>>><br>
>>> Thanks,<br>
>>> Cory<br>
>>><br>
>>> On Thu, Jul 14, 2016 at 2:53 PM, Cory Quammen <<a href="mailto:cory.quammen@kitware.com">cory.quammen@kitware.com</a>><br>
>>> wrote:<br>
>>> > On Thu, Jul 14, 2016 at 2:46 PM, Chiranjib Sur<br>
>>> > <<a href="mailto:sur.chiranjib@gmail.com">sur.chiranjib@gmail.com</a>> wrote:<br>
>>> >> Hi Cory,<br>
>>> >> Great! I prefer the user name <chiranjib.sur> for the account and<br>
>>> >> atleast<br>
>>> >> for first few posts, I want it to be reviewed by you just to make<br>
>>> >> sure, I am<br>
>>> >> following the standards.<br>
>>> ><br>
>>> > Sure, no problem. I'm not really sure there are standards :-) You give<br>
>>> > us too much credit.<br>
>>> ><br>
>>> >> Do you mind for the wiki and edits if I communicate to you directly<br>
>>> >> bypassing the PV-developer mailing list?<br>
>>> ><br>
>>> > Yes, no problem.<br>
>>> ><br>
>>> > Cory<br>
>>> ><br>
>>> >> Thanks,<br>
>>> >> Chiranjib<br>
>>> >><br>
>>> >> On Fri, Jul 15, 2016 at 12:13 AM, Cory Quammen<br>
>>> >> <<a href="mailto:cory.quammen@kitware.com">cory.quammen@kitware.com</a>><br>
>>> >> wrote:<br>
>>> >>><br>
>>> >>> Chiranjib,<br>
>>> >>><br>
>>> >>> > How do I register to the wiki as an author? And how it works -<br>
>>> >>> > anybody<br>
>>> >>> > reviews the submission before it is published?<br>
>>> >>><br>
>>> >>> The wiki suffered from spam attacks recently, so we had to disable<br>
>>> >>> user registration. I'll work to get you an account and then get you<br>
>>> >>> the login info.<br>
>>> >>><br>
>>> >>> No reviews are needed before publishing, but if you want someone to<br>
>>> >>> take a look after you post the changes, I'm happy to review.<br>
>>> >>><br>
>>> >>> Thanks,<br>
>>> >>> Cory<br>
>>> >>><br>
>>> >>> > Thanks,<br>
>>> >>> > Chiranjib<br>
>>> >>> ><br>
>>> >>> ><br>
>>> >>> ><br>
>>> >>> > On Thu, Jul 14, 2016 at 11:43 PM, Cory Quammen<br>
>>> >>> > <<a href="mailto:cory.quammen@kitware.com">cory.quammen@kitware.com</a>><br>
>>> >>> > wrote:<br>
>>> >>> >><br>
>>> >>> >> > I wish these kind of information is stored in some wiki form<br>
>>> >>> >> > somewhere,<br>
>>> >>> >> > or<br>
>>> >>> >> > posted in your vtk/paraview blog. This will be immensely helpful<br>
>>> >>> >> > to<br>
>>> >>> >> > the<br>
>>> >>> >> > developer community!<br>
>>> >>> >><br>
>>> >>> >> Indeed, though a ParaView developer's guide would likely be<br>
>>> >>> >> several<br>
>>> >>> >> hundred pages long, would no doubt miss an important piece of<br>
>>> >>> >> information someone needs, and would be out of date quite quickly.<br>
>>> >>> >> The<br>
>>> >>> >> ParaView code is itself the authoritative source of information,<br>
>>> >>> >> but I<br>
>>> >>> >> know full well - believe me - that it isn't always fast or easy to<br>
>>> >>> >> go<br>
>>> >>> >> that route.<br>
>>> >>> >><br>
>>> >>> >> The good news is that you are now part of the developer community,<br>
>>> >>> >> so<br>
>>> >>> >> we have one more person to contribute this documentation! It would<br>
>>> >>> >> be<br>
>>> >>> >> great if you could update the ParaView plugins howto page on the<br>
>>> >>> >> wiki<br>
>>> >>> >> for other developers to benefit:<br>
>>> >>> >><br>
>>> >>> >> <a href="http://www.paraview.org/Wiki/Plugin_HowTo" rel="noreferrer" target="_blank">http://www.paraview.org/Wiki/Plugin_HowTo</a><br>
>>> >>> >><br>
>>> >>> >> Best,<br>
>>> >>> >> Cory<br>
>>> >>> >><br>
>>> >>> >><br>
>>> >>> >> > Thanks a lot,<br>
>>> >>> >> > Chiranjib<br>
>>> >>> >> ><br>
>>> >>> >> ><br>
>>> >>> >> > On Thu, Jul 14, 2016 at 7:37 PM, Cory Quammen<br>
>>> >>> >> > <<a href="mailto:cory.quammen@kitware.com">cory.quammen@kitware.com</a>><br>
>>> >>> >> > wrote:<br>
>>> >>> >> >><br>
>>> >>> >> >> Chiranjib,<br>
>>> >>> >> >><br>
>>> >>> >> >> It's not obvious or probably described anywhere, but the<br>
>>> >>> >> >> client/server<br>
>>> >>> >> >> code wrapping mechanism wraps member functions that have VTK<br>
>>> >>> >> >> objects<br>
>>> >>> >> >> as parameters *only* if those VTK objects have names that start<br>
>>> >>> >> >> with<br>
>>> >>> >> >> "vtk". If you prepend vtk to all your sph* classes, it should<br>
>>> >>> >> >> work.<br>
>>> >>> >> >> In<br>
>>> >>> >> >> fact, I tested that locally, and it solves the error you are<br>
>>> >>> >> >> seeing.<br>
>>> >>> >> >><br>
>>> >>> >> >> HTH,<br>
>>> >>> >> >> Cory<br>
>>> >>> >> >><br>
>>> >>> >> >> On Wed, Jul 13, 2016 at 1:57 AM, Chiranjib Sur<br>
>>> >>> >> >> <<a href="mailto:sur.chiranjib@gmail.com">sur.chiranjib@gmail.com</a>><br>
>>> >>> >> >> wrote:<br>
>>> >>> >> >> > Hi,<br>
>>> >>> >> >> > Thanks for your messages the pointers. I still have some<br>
>>> >>> >> >> > issues.<br>
>>> >>> >> >> > Here<br>
>>> >>> >> >> > is<br>
>>> >>> >> >> > the<br>
>>> >>> >> >> > attached code snippets which throws me error messages. I am<br>
>>> >>> >> >> > bit<br>
>>> >>> >> >> > clueless<br>
>>> >>> >> >> > what I am missing here.<br>
>>> >>> >> >> ><br>
>>> >>> >> >> > Thanks,<br>
>>> >>> >> >> > Chiranjib<br>
>>> >>> >> >> ><br>
>>> >>> >> >> > On Tue, Jul 12, 2016 at 8:09 PM, RIVERA ROLDAN, Jorge Orlando<br>
>>> >>> >> >> > <<a href="mailto:Orlando.RIVERA@mtu.de">Orlando.RIVERA@mtu.de</a>> wrote:<br>
>>> >>> >> >> >><br>
>>> >>> >> >> >> Hi,<br>
>>> >>> >> >> >><br>
>>> >>> >> >> >><br>
>>> >>> >> >> >> Also , check if "setVariable" is in the public section<br>
>>> >>> >> >> >> of<br>
>>> >>> >> >> >> your<br>
>>> >>> >> >> >> class<br>
>>> >>> >> >> >><br>
>>> >>> >> >> >> Orlando<br>
>>> >>> >> >> >><br>
>>> >>> >> >> >> -----Ursprüngliche Nachricht-----<br>
>>> >>> >> >> >> Von: Paraview-developers<br>
>>> >>> >> >> >> [mailto:<a href="mailto:paraview-developers-bounces@paraview.org">paraview-developers-bounces@paraview.org</a>]<br>
>>> >>> >> >> >> Im Auftrag von Cory Quammen<br>
>>> >>> >> >> >> Gesendet: Tuesday, 12. July 2016 15:37<br>
>>> >>> >> >> >> An: Chiranjib Sur<br>
>>> >>> >> >> >> Cc: Paraview Developer Mailing list<br>
>>> >>> >> >> >> Betreff: Re: [Paraview-developers] paraview PVSessionCore<br>
>>> >>> >> >> >> error<br>
>>> >>> >> >> >><br>
>>> >>> >> >> >> Chiranjib,<br>
>>> >>> >> >> >><br>
>>> >>> >> >> >> Usually this error means there is a mismatch between the XML<br>
>>> >>> >> >> >> used<br>
>>> >>> >> >> >> to<br>
>>> >>> >> >> >> describe the VTK-side class. Check that your XML name for<br>
>>> >>> >> >> >> the<br>
>>> >>> >> >> >> member<br>
>>> >>> >> >> >> function matches the C++, and that the member function<br>
>>> >>> >> >> >> setVariable()<br>
>>> >>> >> >> >> takes only one value.<br>
>>> >>> >> >> >><br>
>>> >>> >> >> >> Cory<br>
>>> >>> >> >> >><br>
>>> >>> >> >> >> On Tue, Jul 12, 2016 at 1:22 AM, Chiranjib Sur<br>
>>> >>> >> >> >> <<a href="mailto:sur.chiranjib@gmail.com">sur.chiranjib@gmail.com</a>><br>
>>> >>> >> >> >> wrote:<br>
>>> >>> >> >> >> > Hi,<br>
>>> >>> >> >> >> > I am trying to implement a new filter in ParaView and I<br>
>>> >>> >> >> >> > get the<br>
>>> >>> >> >> >> > following<br>
>>> >>> >> >> >> > error while executing.<br>
>>> >>> >> >> >> ><br>
>>> >>> >> >> >> > vtkPVSessionCore (0x162d180): Object type: MyObjectSource,<br>
>>> >>> >> >> >> > could<br>
>>> >>> >> >> >> > not<br>
>>> >>> >> >> >> > find<br>
>>> >>> >> >> >> > requested method: "setVariable"<br>
>>> >>> >> >> >> > or the method was called with incorrect arguments.<br>
>>> >>> >> >> >> ><br>
>>> >>> >> >> >> > while processing<br>
>>> >>> >> >> >> > Message 0 = Invoke<br>
>>> >>> >> >> >> > Argument 0 = vtk_object_pointer<br>
>>> >>> >> >> >> > {MyObjectSource(0x34b3870)}<br>
>>> >>> >> >> >> > Argument 1 = string_value {setVariable}<br>
>>> >>> >> >> >> > Argument 2 = float64_value {0.003}<br>
>>> >>> >> >> >> ><br>
>>> >>> >> >> >> ><br>
>>> >>> >> >> >> > I searched the mailing list and it looks like a very<br>
>>> >>> >> >> >> > similar<br>
>>> >>> >> >> >> > bug<br>
>>> >>> >> >> >> > has<br>
>>> >>> >> >> >> > been<br>
>>> >>> >> >> >> > reported<br>
>>> >>> >> >> >> > <a href="http://www.paraview.org/Bug/view.php?id=15593" rel="noreferrer" target="_blank">http://www.paraview.org/Bug/view.php?id=15593</a><br>
>>> >>> >> >> >> ><br>
>>> >>> >> >> >> ><br>
>>> >>> >> >> >> > People have faced similar problem and here are the details<br>
>>> >>> >> >> >> ><br>
>>> >>> >> >> >> ><br>
>>> >>> >> >> >> ><br>
>>> >>> >> >> >> > <a href="http://public.kitware.com/pipermail/paraview/2016-March/036387.html" rel="noreferrer" target="_blank">http://public.kitware.com/pipermail/paraview/2016-March/036387.html</a><br>
>>> >>> >> >> >> ><br>
>>> >>> >> >> >> > Is there a solution of work-around?<br>
>>> >>> >> >> >> ><br>
>>> >>> >> >> >> > Chiranjib<br>
>>> >>> >> >> >> ><br>
>>> >>> >> >> >> > _______________________________________________<br>
>>> >>> >> >> >> > Powered by <a href="http://www.kitware.com" rel="noreferrer" target="_blank">www.kitware.com</a><br>
>>> >>> >> >> >> ><br>
>>> >>> >> >> >> > Visit other Kitware open-source projects at<br>
>>> >>> >> >> >> > <a href="http://www.kitware.com/opensource/opensource.html" rel="noreferrer" target="_blank">http://www.kitware.com/opensource/opensource.html</a><br>
>>> >>> >> >> >> ><br>
>>> >>> >> >> >> > Search the list archives at:<br>
>>> >>> >> >> >> > <a href="http://markmail.org/search/?q=Paraview-developers" rel="noreferrer" target="_blank">http://markmail.org/search/?q=Paraview-developers</a><br>
>>> >>> >> >> >> ><br>
>>> >>> >> >> >> > Follow this link to subscribe/unsubscribe:<br>
>>> >>> >> >> >> ><br>
>>> >>> >> >> >> > <a href="http://public.kitware.com/mailman/listinfo/paraview-developers" rel="noreferrer" target="_blank">http://public.kitware.com/mailman/listinfo/paraview-developers</a><br>
>>> >>> >> >> >> ><br>
>>> >>> >> >> >><br>
>>> >>> >> >> >><br>
>>> >>> >> >> >><br>
>>> >>> >> >> >> --<br>
>>> >>> >> >> >> Cory Quammen<br>
>>> >>> >> >> >> R&D Engineer<br>
>>> >>> >> >> >> Kitware, Inc.<br>
>>> >>> >> >> >> _______________________________________________<br>
>>> >>> >> >> >> Powered by <a href="http://www.kitware.com" rel="noreferrer" target="_blank">www.kitware.com</a><br>
>>> >>> >> >> >><br>
>>> >>> >> >> >> Visit other Kitware open-source projects at<br>
>>> >>> >> >> >> <a href="http://www.kitware.com/opensource/opensource.html" rel="noreferrer" target="_blank">http://www.kitware.com/opensource/opensource.html</a><br>
>>> >>> >> >> >><br>
>>> >>> >> >> >> Search the list archives at:<br>
>>> >>> >> >> >> <a href="http://markmail.org/search/?q=Paraview-developers" rel="noreferrer" target="_blank">http://markmail.org/search/?q=Paraview-developers</a><br>
>>> >>> >> >> >><br>
>>> >>> >> >> >> Follow this link to subscribe/unsubscribe:<br>
>>> >>> >> >> >><br>
>>> >>> >> >> >> <a href="http://public.kitware.com/mailman/listinfo/paraview-developers" rel="noreferrer" target="_blank">http://public.kitware.com/mailman/listinfo/paraview-developers</a><br>
>>> >>> >> >> >> --<br>
>>> >>> >> >> >> MTU Aero Engines AG<br>
>>> >>> >> >> >> Vorstand/Board of Management: Reiner Winkler,<br>
>>> >>> >> >> >> Vorsitzender/CEO;<br>
>>> >>> >> >> >> Dr.<br>
>>> >>> >> >> >> Rainer<br>
>>> >>> >> >> >> Martens, Michael Schreyoegg<br>
>>> >>> >> >> >> Vorsitzender des Aufsichtsrats/Chairman of the Supervisory<br>
>>> >>> >> >> >> Board:<br>
>>> >>> >> >> >> Klaus<br>
>>> >>> >> >> >> Eberhardt<br>
>>> >>> >> >> >> Sitz der Gesellschaft/Registered Office: Muenchen<br>
>>> >>> >> >> >> Handelsregister/Commercial Register: Muenchen HRB 157206<br>
>>> >>> >> >> >><br>
>>> >>> >> >> >> Diese E-Mail sowie ihre Anhaenge enthalten MTU-eigene<br>
>>> >>> >> >> >> vertrauliche<br>
>>> >>> >> >> >> oder<br>
>>> >>> >> >> >> rechtlich geschuetzte Informationen.<br>
>>> >>> >> >> >> Wenn Sie nicht der beabsichtigte Empfaenger sind,<br>
>>> >>> >> >> >> informieren Sie<br>
>>> >>> >> >> >> bitte<br>
>>> >>> >> >> >> den Absender und loeschen Sie diese<br>
>>> >>> >> >> >> E-Mail sowie die Anhaenge. Das unbefugte Speichern, Kopieren<br>
>>> >>> >> >> >> oder<br>
>>> >>> >> >> >> Weiterleiten ist nicht gestattet.<br>
>>> >>> >> >> >><br>
>>> >>> >> >> >> This e-mail and any attached documents are proprietary to<br>
>>> >>> >> >> >> MTU,<br>
>>> >>> >> >> >> confidential or protected by law.<br>
>>> >>> >> >> >> If you are not the intended recipient, please advise the<br>
>>> >>> >> >> >> sender<br>
>>> >>> >> >> >> and<br>
>>> >>> >> >> >> delete<br>
>>> >>> >> >> >> this message and its attachments.<br>
>>> >>> >> >> >> Any unauthorised storing, copying or distribution is<br>
>>> >>> >> >> >> prohibited.<br>
>>> >>> >> >> ><br>
>>> >>> >> >> ><br>
>>> >>> >> >><br>
>>> >>> >> >><br>
>>> >>> >> >><br>
>>> >>> >> >> --<br>
>>> >>> >> >> Cory Quammen<br>
>>> >>> >> >> R&D Engineer<br>
>>> >>> >> >> Kitware, Inc.<br>
>>> >>> >> ><br>
>>> >>> >> ><br>
>>> >>> >><br>
>>> >>> >><br>
>>> >>> >><br>
>>> >>> >> --<br>
>>> >>> >> Cory Quammen<br>
>>> >>> >> R&D Engineer<br>
>>> >>> >> Kitware, Inc.<br>
>>> >>> ><br>
>>> >>> ><br>
>>> >>><br>
>>> >>><br>
>>> >>><br>
>>> >>> --<br>
>>> >>> Cory Quammen<br>
>>> >>> R&D Engineer<br>
>>> >>> Kitware, Inc.<br>
>>> >><br>
>>> >><br>
>>> ><br>
>>> ><br>
>>> ><br>
>>> > --<br>
>>> > Cory Quammen<br>
>>> > R&D Engineer<br>
>>> > Kitware, Inc.<br>
>>><br>
>>><br>
>>><br>
>>> --<br>
>>> Cory Quammen<br>
>>> R&D Engineer<br>
>>> Kitware, Inc.<br>
>><br>
>><br>
><br>
<br>
<br>
<br>
--<br>
Cory Quammen<br>
R&D Engineer<br>
Kitware, Inc.<br>
</div></div></blockquote></div><br></div>