[Paraview] paraviewweb, linked views, mouse handler

Sgouros, Thomas thomas_sgouros at brown.edu
Thu Jun 21 12:04:28 EDT 2018 

Got it. I had misunderstood that message to only refer to the PVW changes.
I found the protocol.py file and made the change and it seems to work fine
now.

Thank you,

 -Tom


For those who are interested, it involves changing the

/Applications/ParaView-5.5.2.app/Contents/Python/paraview/web/protocols.py
file like this, around line 605:


        if not realViewId in self.trackingViews:
            observerCallback = lambda *args, **kwargs:
self.pushRender(realViewId)
-            startCallback = lambda *args, **kwargs:
self.startViewAnimation()
-            stopCallback = lambda *args, **kwargs: self.stopViewAnimation()
+            startCallback = lambda *args, **kwargs:
self.startViewAnimation(realViewId)
+            stopCallback = lambda *args, **kwargs:
self.stopViewAnimation(realViewId)
            tag = self.getApplication().AddObserver('UpdateEvent',
observerCallback)
            tagStart =
self.getApplication().AddObserver('StartInteractionEvent', startCallback)
            tagStop =
self.getApplication().AddObserver('EndInteractionEvent', stopCallback)


On Thu, Jun 21, 2018 at 11:35 AM, Sebastien Jourdain <
sebastien.jourdain at kitware.com> wrote:

> So ParaView 5.5.2 still don't have the correct code base, but
> ParaView/master works exactly as expected...
>
> If you look back at our previous email thread, I must have highlighted  to
> you what was the change I had to do on the server side, which you can
> easily pick since it is just Python code with your current ParaView version.
>
> On Wed, Jun 20, 2018 at 9:11 PM Sgouros, Thomas <thomas_sgouros at brown.edu>
> wrote:
>
>> Hi Sebastien:
>>
>> Actually no, that doesn't change this behavior. One view moves with the
>> cursor when I click on it, while the other only moves when the mouse button
>> is lifted. This is true on your example, as well as my code, and I seem
>> unable to control which one is which. Are you saying your example works
>> differently for you?
>>
>> Thanks,
>>
>>  -Tom
>>
>> On Wed, Jun 20, 2018 at 8:53 PM, Sgouros, Thomas <
>> thomas_sgouros at brown.edu> wrote:
>>
>>> Ok, thanks. I'll give that a try.
>>>
>>>  -Tom
>>>
>>> On Wed, Jun 20, 2018 at 5:44 PM, Sebastien Jourdain <
>>> sebastien.jourdain at kitware.com> wrote:
>>>
>>>> You need ParaView 5.5.2 or master as I said last time, I fixed some
>>>> stuff on the python side to properly register animation on a given view.
>>>> Or you may have patched your ParaView. But for sure, you need Python
>>>> code along with the pvw change I made.
>>>>
>>>> On Wed, Jun 20, 2018 at 1:12 PM Sgouros, Thomas <
>>>> thomas_sgouros at brown.edu> wrote:
>>>>
>>>>>
>>>>>
>>>>> On Wed, Jun 20, 2018 at 10:43 AM, Sebastien Jourdain <
>>>>> sebastien.jourdain at kitware.com> wrote:
>>>>>
>>>>>> Hi Tom,
>>>>>>
>>>>>> - The mouse handler seems to listen only to one view...
>>>>>>
>>>>>> I though the example in https://github.com/Kitware/
>>>>>> paraviewweb-examples was taking care of that. Or maybe I don't
>>>>>> understand what you mean here.
>>>>>>
>>>>>
>>>>> I'm not really sure if it is or it isn't. It may be an illusion
>>>>> created by the other problem, but I don't know how to tell for sure which
>>>>> view is listening.
>>>>>
>>>>>
>>>>>
>>>>>> - The behavior I observe is that one of the views moves...
>>>>>>
>>>>>> That could be possible but are you using the latest ParaView/master?
>>>>>> Normally any registered view should receive a stream of images. With the
>>>>>> fix I've done last time for the multi-view.
>>>>>>
>>>>>>
>>>>> The example you wrote behaves this way for me, too, even when I link
>>>>> the views (see patch attached). One moves with the cursor and the other
>>>>> only moves when you lift up the mouse button. Change the sphere to
>>>>> something you can see move better and you'll see. I'm using the ParaViewWeb
>>>>> 3.2.2 that you made. Or are you talking about Paraview itself? That's at
>>>>> 5.5.0rc3. Were there relevant changes since then?
>>>>>
>>>>>
>>>>>
>>>>>> - When I make one of the views invisible...
>>>>>>
>>>>>> Do you still have a css / size issue when you make it available
>>>>>> again? You need to inspect the DOM to see where that component is present
>>>>>> (area of active).
>>>>>> Then does interacting on that area is not enough to get the images, or
>>>>>> interacting does not work because the "active" area has a size 0x0?
>>>>>>
>>>>>>
>>>>> I did fix the css / size issue that was pestering me last week. Your
>>>>> explanation has the air of plausibility, but I don't completely understand
>>>>> how this would work. Can you suggest how I would find the size of the
>>>>> active area?
>>>>>
>>>>> Thanks,
>>>>>
>>>>>  -Tom
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> On Wed, Jun 20, 2018 at 6:38 AM Sgouros, Thomas <
>>>>>> thomas_sgouros at brown.edu> wrote:
>>>>>>
>>>>>>> Hi All:
>>>>>>>
>>>>>>> I'm working on a ParaViewWeb client talking to a pvpython server
>>>>>>> that shows two linked renderviews. The link works, and it all looks great,
>>>>>>> but there remain a couple of oddities I can't seem to squeeze out:
>>>>>>>
>>>>>>>  - The mouse handler seems to listen only to one view, and I can't
>>>>>>> seem to control which one it pays attention to. How can I demand it listen
>>>>>>> to one or the other?
>>>>>>>
>>>>>>>  - The behavior I observe is that one of the views moves with the
>>>>>>> mouse on a click and the other catches up when I release it. They do not
>>>>>>> move together, although this is close enough. Is this the expected behavior?
>>>>>>>
>>>>>>> A possibly relevant data point: On the machine where the pvpython
>>>>>>> server is running, there is a little undecorated window that appears, and
>>>>>>> the view that I see in there is the one that moves with the mouse. But I
>>>>>>> can't seem to control which view is visible there. Most of the time it
>>>>>>> seems to be the one I draw second, but not all the time. What is this
>>>>>>> window and what can it tell me?
>>>>>>>
>>>>>>> One other issue:
>>>>>>>
>>>>>>>  - When I make one of the views invisible (by simply not rendering
>>>>>>> it in the parent React object) I can't get it to render when it reappears.
>>>>>>> The render function is being invoked, but nothing appears. If I refresh the
>>>>>>> whole page, it appears again.
>>>>>>>
>>>>>>>
>>>>>>> Thank you,
>>>>>>>
>>>>>>>  -Tom
>>>>>>> _______________________________________________
>>>>>>> Powered by www.kitware.com
>>>>>>>
>>>>>>> ParaView discussion is moving! Please visit
>>>>>>> https://discourse.paraview.org/ for future posts.
>>>>>>>
>>>>>>> Visit other Kitware open-source projects at http://www.kitware.com/
>>>>>>> opensource/opensource.html
>>>>>>>
>>>>>>> Please keep messages on-topic and check the ParaView Wiki at:
>>>>>>> http://paraview.org/Wiki/ParaView
>>>>>>>
>>>>>>> Search the list archives at: http://markmail.org/search/?q=ParaView
>>>>>>>
>>>>>>> Follow this link to subscribe/unsubscribe:
>>>>>>> https://public.kitware.com/mailman/listinfo/paraview
>>>>>>>
>>>>>>
>>>>>
>>>
>>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://public.kitware.com/pipermail/paraview/attachments/20180621/a1be8594/attachment.html>

More information about the ParaView mailing list