[vtk-developers] VTKWeb support for multiple windows on the client

Sebastien Jourdain sebastien.jourdain at kitware.com
Wed Jul 26 10:04:23 EDT 2017


Hi Dan,

I'll be in KHQ next week. If you want we can talk about it in person.

Seb

On Wed, Jul 26, 2017 at 7:59 AM, Dan Lipsa <dan.lipsa at kitware.com> wrote:

> Thanks Seb,
> I'll have more questions when I get to implementing this.
>
> Dan
>
>
> On Fri, Jul 21, 2017 at 4:29 PM, Sebastien Jourdain <
> sebastien.jourdain at kitware.com> wrote:
>
>> I would rather have one vtkWebMouseListener per div so each listener has
>> its own view id.
>>
>> On Fri, Jul 21, 2017 at 10:17 AM, Dan Lipsa <dan.lipsa at kitware.com>
>> wrote:
>>
>>> Thanks Scott,
>>> I was thinking to go one step further:
>>> - Pass a map between the client elements(divs) and the server window
>>> ids. I already have both the element ids and the server window ids.
>>> - When a mouse event is received in vtkWebMouseListener we can use that
>>> map and send the server window id the event applies too.
>>>
>>> Dan
>>>
>>>
>>>
>>> On Fri, Jul 21, 2017 at 11:40 AM, Scott Wittenburg <
>>> scott.wittenburg at kitware.com> wrote:
>>>
>>>> Hi Dan,
>>>>
>>>> In VtkWebMouseListener, it is the "view" key in the vtk event structure
>>>> that indicates what view to send the event to on the server, and it does
>>>> seem that there is no way to change it from -1, which indicates to send the
>>>> event to the active view.  However, both the paraviewweb and vtkweb server
>>>> protocols have mouse handlers which take the id of the target view as an
>>>> option, so what you want to do seems to be supported on the server side at
>>>> least.  But I agree with you that the VtkWebMouseListener does not seem to
>>>> provide a mechanism to change that view id.  One thing we could do is have
>>>> the VtkWebMouseListener take a view id as an optional 4th argument which
>>>> defaults to -1, then use that in the zoom and drag listeners.
>>>>
>>>> If that makes sense to you, you can put together a PR on paraviewweb,
>>>> and I'll be happy to review it.  Otherwise, get in touch with me offline
>>>> and we can chat about it.  Hope this helps.
>>>>
>>>> Cheers,
>>>> Scott
>>>>
>>>>
>>>>
>>>> On Fri, Jul 21, 2017 at 7:21 AM, Dan Lipsa <dan.lipsa at kitware.com>
>>>> wrote:
>>>>
>>>>> Hi all,
>>>>> We are using VTKWeb + ParaViewWebClient in the browser. We open
>>>>> several VTK windows on the server and put them inside different panels
>>>>> (divs) in the browser.
>>>>>
>>>>> Looking at VtkWebMouseListener/index.js it seems that there is no
>>>>> support for this configuration.
>>>>>
>>>>> It seems that client has not concept of active view, so it always
>>>>> sends mouse events to the server, regardless of the active view on the
>>>>> server.
>>>>>
>>>>> The resulting behavior is that you can move your mouse over a
>>>>> different panel, but the active panel moves. Am I missing something?
>>>>>
>>>>> Thanks,
>>>>> Dan
>>>>>
>>>>>
>>>>> _______________________________________________
>>>>> Powered by www.kitware.com
>>>>>
>>>>> Visit other Kitware open-source projects at
>>>>> http://www.kitware.com/opensource/opensource.html
>>>>>
>>>>> Search the list archives at: http://markmail.org/search/?q=
>>>>> vtk-developers
>>>>>
>>>>> Follow this link to subscribe/unsubscribe:
>>>>> http://public.kitware.com/mailman/listinfo/vtk-developers
>>>>>
>>>>>
>>>>>
>>>>
>>>
>>> _______________________________________________
>>> Powered by www.kitware.com
>>>
>>> Visit other Kitware open-source projects at
>>> http://www.kitware.com/opensource/opensource.html
>>>
>>> Search the list archives at: http://markmail.org/search/?q=
>>> vtk-developers
>>>
>>> Follow this link to subscribe/unsubscribe:
>>> http://public.kitware.com/mailman/listinfo/vtk-developers
>>>
>>>
>>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/vtk-developers/attachments/20170726/5a52bf7b/attachment.html>


More information about the vtk-developers mailing list