<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Mon, Sep 24, 2018 at 3:22 PM, Andras Lasso <span dir="ltr"><<a href="mailto:lasso@queensu.ca" target="_blank">lasso@queensu.ca</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div link="#0563C1" vlink="#954F72" lang="EN-US">
<div class="m_6706324365005932876WordSection1"><b>Could we create new states, such as VTKIS_PINCH_TRACKPAD / PINCH_TOUCH / PINCH_3D to clearly distinguish these?</b>
<p class="MsoNormal"><u></u> <u></u></p>
<ol style="margin-top:0in" start="2" type="1">
<li class="m_6706324365005932876MsoListParagraph" style="margin-left:0in">Several multi-touch gestures may be active at the same time and some of them share some event properties (e.g., event position) cached in vtkRenderWindowInteractor. Last event position
is corrupted if multiple gestures store their properties in the same variables.<u></u><u></u></li></ol>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal"><b>Should we add more variables to store all event properties that may be changed at the same time?
</b>For example, add new variables for tap position and pinch position (similarly to how translation, rotation, scale are all stored separately).<u></u><u></u></p>
<p class="MsoNormal"><b>Is there a reason why we send only the event ID and retrieve all event properties from vtkRenderWindowInteractor? Would it be possible to pass event properties along with event as callData?</b><span class="HOEnZb"><font color="#888888"><u></u><u></u></font></span></p><span class="HOEnZb"><font color="#888888">
<p class="MsoNormal"><u></u></p></font></span></div></div></blockquote><div><br></div><div>I'm not a huge fan of storing these values in the interactor (although I may be the one at fault for doing it :-). In the Virtual Reality events I started putting much more of the information into the call data for the events. See vtkEventData.h , vtkOpenVRRenderWindowInteractor.cxx and the handling of Button3D event in vtkInteractorStyle.cxx for how the data gets passed down. Related to that I started collapsing more event types into a single event. Button3D includes a wide range of button types as defined in vtkEventData.h My thoughts are that vtkEventData could be extended to handle most existing event types as well such as keyboard and mouse.<br></div><div><br></div><div><br></div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div link="#0563C1" vlink="#954F72" lang="EN-US"><div class="m_6706324365005932876WordSection1"><span class="HOEnZb"><font color="#888888"><p class="MsoNormal"> <u></u></p>
<p class="MsoNormal">Andras<u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
</font></span></div>
</div>
<br>______________________________<wbr>_________________<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 <a href="http://www.kitware.com/opensource/opensource.html" rel="noreferrer" target="_blank">http://www.kitware.com/<wbr>opensource/opensource.html</a><br>
<br>
Search the list archives at: <a href="http://markmail.org/search/?q=vtk-developers" rel="noreferrer" target="_blank">http://markmail.org/search/?q=<wbr>vtk-developers</a><br>
<br>
Follow this link to subscribe/unsubscribe:<br>
<a href="https://public.kitware.com/mailman/listinfo/vtk-developers" rel="noreferrer" target="_blank">https://public.kitware.com/<wbr>mailman/listinfo/vtk-<wbr>developers</a><br>
<br>
<br></blockquote></div><br><br clear="all"><br>-- <br><div class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><div><div dir="ltr"><div>Ken Martin PhD<div>Distinguished Engineer<br><span style="font-size:12.8px">Kitware Inc.</span><br></div><div>101 East Weaver Street<br>Carrboro, North Carolina<br>
27510 USA<br><br><div><span style="font-size:10pt;font-family:Tahoma,sans-serif">This communication,
including all attachments, contains confidential and legally privileged
information, and it is intended only for the use of the addressee. Access to this email by anyone else is
unauthorized. If you are not the intended recipient, any disclosure, copying,
distribution or any action taken in reliance on it is prohibited and may be
unlawful. If you received this communication in error please notify us
immediately and destroy the original message.
Thank you.</span></div></div></div></div></div></div></div>
</div></div>