QVTKRenderWindowInteractor bug in Mac OS

classic Classic list List threaded Threaded
13 messages Options
Reply | Threaded
Open this post in threaded view
|

QVTKRenderWindowInteractor bug in Mac OS

take5v
Dear developers and others,

I'd like to visualize grayscale images with python, VTK and PyQt5. So, I've
made this script with Qt Application and embedded
QVTKRenderWindowInteractor. Please have a look into my gist
https://gist.github.com/take5v/1df1e4f4222f49cf05cbf59b1f89a9ea.

The issue is that the vtkPropPicker gives wrong world coordinates while
event coordinates are correct. This bug I could reproduce only on Mac Os,
not on Windows and Ubuntu.

I found probably a workaround that was made for c++ QVTKOpenGLWindow class
which wasn't been wrapped for python:
https://github.com/Kitware/VTK/blob/c6eb8803c44b13947f959aed7b4e551e5e2915db/GUISupport/Qt/QVTKOpenGLWindow.cxx#L266.

My setup:
macOS Mojave 10.14
python 3.6.4
vtk-python 8.1.1
PyQt 5.11.3

Best regards,
Stas





-----
Best regards,
Stanislau Trukhan
--
Sent from: http://vtk.1045678.n5.nabble.com/VTK-Dev-f1251487.html
_______________________________________________
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:
https://public.kitware.com/mailman/listinfo/vtk-developers

Best regards,
Stanislau Trukhan
Reply | Threaded
Open this post in threaded view
|

Re: QVTKRenderWindowInteractor bug in Mac OS

Mathieu Westphal
Hi Stas,

You may want to try with the last development version of VTK, as these class have been reimplemented.

Best Regards,

Mathieu Westphal


On Wed, Oct 31, 2018 at 2:21 PM take5v <[hidden email]> wrote:
Dear developers and others,

I'd like to visualize grayscale images with python, VTK and PyQt5. So, I've
made this script with Qt Application and embedded
QVTKRenderWindowInteractor. Please have a look into my gist
https://gist.github.com/take5v/1df1e4f4222f49cf05cbf59b1f89a9ea.

The issue is that the vtkPropPicker gives wrong world coordinates while
event coordinates are correct. This bug I could reproduce only on Mac Os,
not on Windows and Ubuntu.

I found probably a workaround that was made for c++ QVTKOpenGLWindow class
which wasn't been wrapped for python:
https://github.com/Kitware/VTK/blob/c6eb8803c44b13947f959aed7b4e551e5e2915db/GUISupport/Qt/QVTKOpenGLWindow.cxx#L266.

My setup:
macOS Mojave 10.14
python 3.6.4
vtk-python 8.1.1
PyQt 5.11.3

Best regards,
Stas





-----
Best regards,
Stanislau Trukhan
--
Sent from: http://vtk.1045678.n5.nabble.com/VTK-Dev-f1251487.html
_______________________________________________
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:
https://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:
https://public.kitware.com/mailman/listinfo/vtk-developers

Reply | Threaded
Open this post in threaded view
|

Re: QVTKRenderWindowInteractor bug in Mac OS

Sean McBride
In reply to this post by take5v
On Wed, 31 Oct 2018 06:21:13 -0700, take5v said:

>The issue is that the vtkPropPicker gives wrong world coordinates while
>event coordinates are correct. This bug I could reproduce only on Mac Os,
>not on Windows and Ubuntu.

Is this on a "retina" display?  If so, check if it's correct on a non-Retina display...

Cheers,

--
____________________________________________________________
Sean McBride, B. Eng                 [hidden email]
Rogue Research                        www.rogue-research.com
Mac Software Developer              Montréal, Québec, Canada


_______________________________________________
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:
https://public.kitware.com/mailman/listinfo/vtk-developers

Reply | Threaded
Open this post in threaded view
|

Re: QVTKRenderWindowInteractor bug in Mac OS

take5v
Sean McBride wrote
> Is this on a "retina" display?  If so, check if it's correct on a
> non-Retina display...

I tested only on a "retina" display.



-----
Best regards,
Stanislau Trukhan
--
Sent from: http://vtk.1045678.n5.nabble.com/VTK-Dev-f1251487.html
_______________________________________________
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:
https://public.kitware.com/mailman/listinfo/vtk-developers

Best regards,
Stanislau Trukhan
Reply | Threaded
Open this post in threaded view
|

Re: QVTKRenderWindowInteractor bug in Mac OS

take5v
When switching off HiDPI all works well. So, apparently, the issue is
concerning HiDPU support in python wrappers.

Best regards,
Stas



-----
Best regards,
Stanislau Trukhan
--
Sent from: http://vtk.1045678.n5.nabble.com/VTK-Dev-f1251487.html
_______________________________________________
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:
https://public.kitware.com/mailman/listinfo/vtk-developers

Best regards,
Stanislau Trukhan
Reply | Threaded
Open this post in threaded view
|

Re: QVTKRenderWindowInteractor bug in Mac OS

David Gobbi
Hi Stas,

An important retina change was made to QVTKRenderWindowInteractor.py since 8.1.1:
You could try adding these same changes to your own QVTKRenderWindowInteractor.py.

Note that QVTKRenderWindowInteractor.py and the vtk GUISupport/Qt classes are
completely independent, so changes to GUISupport/Qt have no impact on the
behaviour of QVTKRenderWindowInteractor.py and vice-versa.  So the changes to
GUISupport/Qt that Mathieu was referring to aren't actually useful to you, since those
classes aren't wrapped (the reason they aren't wrapped is that they are Qt classes,
so they would have to be wrapped with sip, rather than with the VTK wrapper tools).

 - David

On Wed, Oct 31, 2018 at 9:15 AM take5v <[hidden email]> wrote:
When switching off HiDPI all works well. So, apparently, the issue is
concerning HiDPU support in python wrappers.

Best regards,
Stas



-----
Best regards,
Stanislau Trukhan
--
Sent from: http://vtk.1045678.n5.nabble.com/VTK-Dev-f1251487.html
_______________________________________________
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:
https://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:
https://public.kitware.com/mailman/listinfo/vtk-developers

Reply | Threaded
Open this post in threaded view
|

Re: QVTKRenderWindowInteractor bug in Mac OS

take5v
Hi David,

Thank you very much, now it works like a charm! Looking forward to the new
VTK release in pip.

Best regards,
Stas



-----
Best regards,
Stanislau Trukhan
--
Sent from: http://vtk.1045678.n5.nabble.com/VTK-Dev-f1251487.html
_______________________________________________
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:
https://public.kitware.com/mailman/listinfo/vtk-developers

Best regards,
Stanislau Trukhan
Reply | Threaded
Open this post in threaded view
|

Re: QVTKRenderWindowInteractor bug in Mac OS

take5v
Another issue but within the same context of mine toy example (script of
which I posted above) is a slow fps during window/level change on Windows.
This process is slow and laggy even during rendering the super small image
of vtk.png from VTKData.

CPU: GeForce GTX 680
GPU: Intel i7-3770K



-----
Best regards,
Stanislau Trukhan
--
Sent from: http://vtk.1045678.n5.nabble.com/VTK-Dev-f1251487.html
_______________________________________________
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:
https://public.kitware.com/mailman/listinfo/vtk-developers

Best regards,
Stanislau Trukhan
Reply | Threaded
Open this post in threaded view
|

Re: QVTKRenderWindowInteractor bug in Mac OS

David Gobbi
Hi Stas,

Here are a couple things to try to improve fps (no guarantees, though).

With QVTKRenderWindowInteractor, it is best to let Qt handle the
render calls, rather than calling Render() directly.  So try replacing
all of your calls to Render() with calls to self.update(), where 'self' is
the QVTKRenderWindowInteractor.  If you do not do this, then it is
possible that the Render() is hidden because it isn't associated with
a Qt paint operation. By calling update() on a Qt widget, you ensure
that Qt will call Render() synchronously with its paintEvent().

A second thing to try is to call Update() on your reader before using
its output.  Most readers will 'stream' which means that they only
read the slices that are requested by the VTK pipeline (possibly
causing the reader to re-execute on future pipeline requests),
unless you specifically call Update() which forces all the slices to be
read into memory at once.  Since your example only has one input
slice, I doubt that this is what is causing a slow-down for you, but it
is still a good habit when working with VTK readers.

  - David


On Wed, Oct 31, 2018 at 10:57 AM take5v <[hidden email]> wrote:
Another issue but within the same context of mine toy example (script of
which I posted above) is a slow fps during window/level change on Windows.
This process is slow and laggy even during rendering the super small image
of vtk.png from VTKData.

CPU: GeForce GTX 680
GPU: Intel i7-3770K



-----
Best regards,
Stanislau Trukhan
--
Sent from: http://vtk.1045678.n5.nabble.com/VTK-Dev-f1251487.html
_______________________________________________
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:
https://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:
https://public.kitware.com/mailman/listinfo/vtk-developers

Reply | Threaded
Open this post in threaded view
|

Re: QVTKRenderWindowInteractor bug in Mac OS

take5v
Hi David!

Thank you for the detailed response. I've changed Render call with
QVTKRenderWindowInteractor update method but I observed no performance
change. But I got lucky twice when changing window/level was real-time
without any lags. I have no idea how to reproduce this behavior again but I
do confirm the same inconsistency in Slicer3D on Windows machine. I found
changing window/level of 2d slices is slow but 3d volume rendering is fast.
There is a thread, apparently, with similar performance issue from Slicer3D:
https://discourse.slicer.org/t/2d-views-in-slicer-extremely-slow-on-windows/782.
I also tried vtkImageViewer2 without qt and got the same laggy behavior.

Nvidia driver: 411.31



David Gobbi wrote

> Hi Stas,
>
> Here are a couple things to try to improve fps (no guarantees, though).
>
> With QVTKRenderWindowInteractor, it is best to let Qt handle the
> render calls, rather than calling Render() directly.  So try replacing
> all of your calls to Render() with calls to self.update(), where 'self' is
> the QVTKRenderWindowInteractor.  If you do not do this, then it is
> possible that the Render() is hidden because it isn't associated with
> a Qt paint operation. By calling update() on a Qt widget, you ensure
> that Qt will call Render() synchronously with its paintEvent().
>
> A second thing to try is to call Update() on your reader before using
> its output.  Most readers will 'stream' which means that they only
> read the slices that are requested by the VTK pipeline (possibly
> causing the reader to re-execute on future pipeline requests),
> unless you specifically call Update() which forces all the slices to be
> read into memory at once.  Since your example only has one input
> slice, I doubt that this is what is causing a slow-down for you, but it
> is still a good habit when working with VTK readers.
>
>   - David
>
>
> On Wed, Oct 31, 2018 at 10:57 AM take5v &lt;

> stas.truhan@

> &gt; wrote:
>
>> Another issue but within the same context of mine toy example (script of
>> which I posted above) is a slow fps during window/level change on
>> Windows.
>> This process is slow and laggy even during rendering the super small
>> image
>> of vtk.png from VTKData.
>>
>> CPU: GeForce GTX 680
>> GPU: Intel i7-3770K
>>
>>
>>
>> -----
>> Best regards,
>> Stanislau Trukhan
>> --
>> Sent from: http://vtk.1045678.n5.nabble.com/VTK-Dev-f1251487.html
>> _______________________________________________
>> 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:
>> https://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:
> https://public.kitware.com/mailman/listinfo/vtk-developers





-----
Best regards,
Stanislau Trukhan
--
Sent from: http://vtk.1045678.n5.nabble.com/VTK-Dev-f1251487.html
_______________________________________________
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:
https://public.kitware.com/mailman/listinfo/vtk-developers

Best regards,
Stanislau Trukhan
Reply | Threaded
Open this post in threaded view
|

Re: QVTKRenderWindowInteractor bug in Mac OS

Steve Pieper-2
Hi Stas - 

We think the Slicer display issues have all been resolved since the thread you linked - can you try the latest 4.10 release (from just a few days ago) and see if you still see the issue?  We tracked some issues to the graphics drivers, but others had to do with optimizing the reslice theading and render compression settings.

Best,
Steve

On Wed, Oct 31, 2018 at 6:57 PM take5v <[hidden email]> wrote:
Hi David!

Thank you for the detailed response. I've changed Render call with
QVTKRenderWindowInteractor update method but I observed no performance
change. But I got lucky twice when changing window/level was real-time
without any lags. I have no idea how to reproduce this behavior again but I
do confirm the same inconsistency in Slicer3D on Windows machine. I found
changing window/level of 2d slices is slow but 3d volume rendering is fast.
There is a thread, apparently, with similar performance issue from Slicer3D:
https://discourse.slicer.org/t/2d-views-in-slicer-extremely-slow-on-windows/782.
I also tried vtkImageViewer2 without qt and got the same laggy behavior.

Nvidia driver: 411.31



David Gobbi wrote
> Hi Stas,
>
> Here are a couple things to try to improve fps (no guarantees, though).
>
> With QVTKRenderWindowInteractor, it is best to let Qt handle the
> render calls, rather than calling Render() directly.  So try replacing
> all of your calls to Render() with calls to self.update(), where 'self' is
> the QVTKRenderWindowInteractor.  If you do not do this, then it is
> possible that the Render() is hidden because it isn't associated with
> a Qt paint operation. By calling update() on a Qt widget, you ensure
> that Qt will call Render() synchronously with its paintEvent().
>
> A second thing to try is to call Update() on your reader before using
> its output.  Most readers will 'stream' which means that they only
> read the slices that are requested by the VTK pipeline (possibly
> causing the reader to re-execute on future pipeline requests),
> unless you specifically call Update() which forces all the slices to be
> read into memory at once.  Since your example only has one input
> slice, I doubt that this is what is causing a slow-down for you, but it
> is still a good habit when working with VTK readers.
>
>   - David
>
>
> On Wed, Oct 31, 2018 at 10:57 AM take5v &lt;

> stas.truhan@

> &gt; wrote:
>
>> Another issue but within the same context of mine toy example (script of
>> which I posted above) is a slow fps during window/level change on
>> Windows.
>> This process is slow and laggy even during rendering the super small
>> image
>> of vtk.png from VTKData.
>>
>> CPU: GeForce GTX 680
>> GPU: Intel i7-3770K
>>
>>
>>
>> -----
>> Best regards,
>> Stanislau Trukhan
>> --
>> Sent from: http://vtk.1045678.n5.nabble.com/VTK-Dev-f1251487.html
>> _______________________________________________
>> 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:
>> https://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:
> https://public.kitware.com/mailman/listinfo/vtk-developers





-----
Best regards,
Stanislau Trukhan
--
Sent from: http://vtk.1045678.n5.nabble.com/VTK-Dev-f1251487.html
_______________________________________________
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:
https://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:
https://public.kitware.com/mailman/listinfo/vtk-developers

Reply | Threaded
Open this post in threaded view
|

Re: QVTKRenderWindowInteractor bug in Mac OS

Andras Lasso
In reply to this post by take5v
Initially, when 3D Slicer switched to VTK8/Qt5/OpenGL2 backend, image reslice speed was about 5-10x slower than using the old VTK7/Qt4/OpenGL backend.

We could achieve acceptable performance by:
1. Switching to TBB SMP backend in VTK. This primarily helped on Windows computers with i7 CPU and strong NVidia GPU (https://github.com/Slicer/Slicer/pull/930).
2. Tuning strategy how ScheduleRender() calls are converted to Render() calls. This helped in particular in getting consistent frame rates on MacOSX. (https://github.com/commontk/CTK/blob/master/Libs/Visualization/VTK/Widgets/ctkVTKAbstractView.h)

Still, image reslicing is about 10-20% slower with VTK8/Qt5/OpenGL2, especially on laptops and computers with combined integrated+discrete GPU. It seems most time is spent in the OpenGL driver, mainly due to calls made from vtkOpenGLTexture::Load (https://issues.slicer.org/view.php?id=4496).

Andras

-----Original Message-----
From: vtk-developers <[hidden email]> On Behalf Of take5v
Sent: Wednesday, October 31, 2018 6:58 PM
To: [hidden email]
Subject: Re: [vtk-developers] QVTKRenderWindowInteractor bug in Mac OS

Hi David!

Thank you for the detailed response. I've changed Render call with QVTKRenderWindowInteractor update method but I observed no performance change. But I got lucky twice when changing window/level was real-time without any lags. I have no idea how to reproduce this behavior again but I do confirm the same inconsistency in Slicer3D on Windows machine. I found changing window/level of 2d slices is slow but 3d volume rendering is fast.
There is a thread, apparently, with similar performance issue from Slicer3D:
https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdiscourse.slicer.org%2Ft%2F2d-views-in-slicer-extremely-slow-on-windows%2F782&amp;data=02%7C01%7Classo%40queensu.ca%7C60be52993c6448c59bbb08d63f844891%7Cd61ecb3b38b142d582c4efb2838b925c%7C1%7C0%7C636766234722688008&amp;sdata=z%2F85pd7WeC8GI7%2FmnMlNsUcx3JRogc5sJfByit0kA0Q%3D&amp;reserved=0.
I also tried vtkImageViewer2 without qt and got the same laggy behavior.

Nvidia driver: 411.31



David Gobbi wrote

> Hi Stas,
>
> Here are a couple things to try to improve fps (no guarantees, though).
>
> With QVTKRenderWindowInteractor, it is best to let Qt handle the
> render calls, rather than calling Render() directly.  So try replacing
> all of your calls to Render() with calls to self.update(), where
> 'self' is the QVTKRenderWindowInteractor.  If you do not do this, then
> it is possible that the Render() is hidden because it isn't associated
> with a Qt paint operation. By calling update() on a Qt widget, you
> ensure that Qt will call Render() synchronously with its paintEvent().
>
> A second thing to try is to call Update() on your reader before using
> its output.  Most readers will 'stream' which means that they only
> read the slices that are requested by the VTK pipeline (possibly
> causing the reader to re-execute on future pipeline requests), unless
> you specifically call Update() which forces all the slices to be read
> into memory at once.  Since your example only has one input slice, I
> doubt that this is what is causing a slow-down for you, but it is
> still a good habit when working with VTK readers.
>
>   - David
>
>
> On Wed, Oct 31, 2018 at 10:57 AM take5v &lt;

> stas.truhan@

> &gt; wrote:
>
>> Another issue but within the same context of mine toy example (script
>> of which I posted above) is a slow fps during window/level change on
>> Windows.
>> This process is slow and laggy even during rendering the super small
>> image of vtk.png from VTKData.
>>
>> CPU: GeForce GTX 680
>> GPU: Intel i7-3770K
>>
>>
>>
>> -----
>> Best regards,
>> Stanislau Trukhan
>> --
>> Sent from:
>> https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fvtk.1
>> 045678.n5.nabble.com%2FVTK-Dev-f1251487.html&amp;data=02%7C01%7Classo
>> %40queensu.ca%7C60be52993c6448c59bbb08d63f844891%7Cd61ecb3b38b142d582
>> c4efb2838b925c%7C1%7C0%7C636766234722688008&amp;sdata=EOxcLPZE4jDzrxX
>> k0KOIf9RqXouukZgL7HC46iwz6NU%3D&amp;reserved=0
>> _______________________________________________
>> Powered by
>> https://na01.safelinks.protection.outlook.com/?url=www.kitware.com&am
>> p;data=02%7C01%7Classo%40queensu.ca%7C60be52993c6448c59bbb08d63f84489
>> 1%7Cd61ecb3b38b142d582c4efb2838b925c%7C1%7C0%7C636766234722688008&amp
>> ;sdata=iZoyvIzvUo3wwXD0sMcGmJaw2kRTyRVktar3DnBYOFM%3D&amp;reserved=0
>>
>> Visit other Kitware open-source projects at
>> https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.k
>> itware.com%2Fopensource%2Fopensource.html&amp;data=02%7C01%7Classo%40
>> queensu.ca%7C60be52993c6448c59bbb08d63f844891%7Cd61ecb3b38b142d582c4e
>> fb2838b925c%7C1%7C0%7C636766234722688008&amp;sdata=f%2BKMU0xm65TMwdPj
>> TMLZwBorIQ7cwgA8mjdrNIHYCQg%3D&amp;reserved=0
>>
>> Search the list archives at:
>> https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fmarkm
>> ail.org%2Fsearch%2F%3Fq%3Dvtk-developers&amp;data=02%7C01%7Classo%40q
>> ueensu.ca%7C60be52993c6448c59bbb08d63f844891%7Cd61ecb3b38b142d582c4ef
>> b2838b925c%7C1%7C0%7C636766234722688008&amp;sdata=sHi5aRgy7vD%2BLy%2B
>> dcLgAfMntvGLyfl3ZhHdddq270ow%3D&amp;reserved=0
>>
>> Follow this link to subscribe/unsubscribe:
>> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpubl
>> ic.kitware.com%2Fmailman%2Flistinfo%2Fvtk-developers&amp;data=02%7C01
>> %7Classo%40queensu.ca%7C60be52993c6448c59bbb08d63f844891%7Cd61ecb3b38
>> b142d582c4efb2838b925c%7C1%7C0%7C636766234722688008&amp;sdata=fQsqBZg
>> 8c8fc2sL4duw2325P8PnFuE75a%2BowRhAFWcQ%3D&amp;reserved=0
>>
>>
>
> _______________________________________________
> Powered by
> https://na01.safelinks.protection.outlook.com/?url=www.kitware.com&amp
> ;data=02%7C01%7Classo%40queensu.ca%7C60be52993c6448c59bbb08d63f844891%
> 7Cd61ecb3b38b142d582c4efb2838b925c%7C1%7C0%7C636766234722688008&amp;sd
> ata=iZoyvIzvUo3wwXD0sMcGmJaw2kRTyRVktar3DnBYOFM%3D&amp;reserved=0
>
> Visit other Kitware open-source projects at
> https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.ki
> tware.com%2Fopensource%2Fopensource.html&amp;data=02%7C01%7Classo%40qu
> eensu.ca%7C60be52993c6448c59bbb08d63f844891%7Cd61ecb3b38b142d582c4efb2
> 838b925c%7C1%7C0%7C636766234722688008&amp;sdata=f%2BKMU0xm65TMwdPjTMLZ
> wBorIQ7cwgA8mjdrNIHYCQg%3D&amp;reserved=0
>
> Search the list archives at:
> https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fmarkma
> il.org%2Fsearch%2F%3Fq%3Dvtk-developers&amp;data=02%7C01%7Classo%40que
> ensu.ca%7C60be52993c6448c59bbb08d63f844891%7Cd61ecb3b38b142d582c4efb28
> 38b925c%7C1%7C0%7C636766234722688008&amp;sdata=sHi5aRgy7vD%2BLy%2BdcLg
> AfMntvGLyfl3ZhHdddq270ow%3D&amp;reserved=0
>
> Follow this link to subscribe/unsubscribe:
> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpubli
> c.kitware.com%2Fmailman%2Flistinfo%2Fvtk-developers&amp;data=02%7C01%7
> Classo%40queensu.ca%7C60be52993c6448c59bbb08d63f844891%7Cd61ecb3b38b14
> 2d582c4efb2838b925c%7C1%7C0%7C636766234722688008&amp;sdata=fQsqBZg8c8f
> c2sL4duw2325P8PnFuE75a%2BowRhAFWcQ%3D&amp;reserved=0





-----
Best regards,
Stanislau Trukhan
--
Sent from: https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fvtk.1045678.n5.nabble.com%2FVTK-Dev-f1251487.html&amp;data=02%7C01%7Classo%40queensu.ca%7C60be52993c6448c59bbb08d63f844891%7Cd61ecb3b38b142d582c4efb2838b925c%7C1%7C0%7C636766234722688008&amp;sdata=EOxcLPZE4jDzrxXk0KOIf9RqXouukZgL7HC46iwz6NU%3D&amp;reserved=0
_______________________________________________
Powered by https://na01.safelinks.protection.outlook.com/?url=www.kitware.com&amp;data=02%7C01%7Classo%40queensu.ca%7C60be52993c6448c59bbb08d63f844891%7Cd61ecb3b38b142d582c4efb2838b925c%7C1%7C0%7C636766234722688008&amp;sdata=iZoyvIzvUo3wwXD0sMcGmJaw2kRTyRVktar3DnBYOFM%3D&amp;reserved=0

Visit other Kitware open-source projects at https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.kitware.com%2Fopensource%2Fopensource.html&amp;data=02%7C01%7Classo%40queensu.ca%7C60be52993c6448c59bbb08d63f844891%7Cd61ecb3b38b142d582c4efb2838b925c%7C1%7C0%7C636766234722688008&amp;sdata=f%2BKMU0xm65TMwdPjTMLZwBorIQ7cwgA8mjdrNIHYCQg%3D&amp;reserved=0

Search the list archives at: https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fmarkmail.org%2Fsearch%2F%3Fq%3Dvtk-developers&amp;data=02%7C01%7Classo%40queensu.ca%7C60be52993c6448c59bbb08d63f844891%7Cd61ecb3b38b142d582c4efb2838b925c%7C1%7C0%7C636766234722688008&amp;sdata=sHi5aRgy7vD%2BLy%2BdcLgAfMntvGLyfl3ZhHdddq270ow%3D&amp;reserved=0

Follow this link to subscribe/unsubscribe:
https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpublic.kitware.com%2Fmailman%2Flistinfo%2Fvtk-developers&amp;data=02%7C01%7Classo%40queensu.ca%7C60be52993c6448c59bbb08d63f844891%7Cd61ecb3b38b142d582c4efb2838b925c%7C1%7C0%7C636766234722688008&amp;sdata=fQsqBZg8c8fc2sL4duw2325P8PnFuE75a%2BowRhAFWcQ%3D&amp;reserved=0

_______________________________________________
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:
https://public.kitware.com/mailman/listinfo/vtk-developers

Reply | Threaded
Open this post in threaded view
|

Re: QVTKRenderWindowInteractor bug in Mac OS

take5v
Hi all,

I uploaded a video of my screen to confirm the inconsistent performance
behavior during window/level changing, please have a look. I tested
completely the same script and on the same environment.

https://www.dropbox.com/s/jresoj5tf2fumpt/vtk_window_level_performance_inconsistency.mp4?dl=0

Environment:
Windows 10
Python 3.6.4
PyQt5 5.10.1
vtk-python 8.1.1
CPU Intel i7-3770K
GPU GeForce GTX 680
Nvidia driver 411.31
Display LG IPS277L

Best regards,
Stas




-----
Best regards,
Stanislau Trukhan
--
Sent from: http://vtk.1045678.n5.nabble.com/VTK-Dev-f1251487.html
_______________________________________________
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:
https://public.kitware.com/mailman/listinfo/vtk-developers

Best regards,
Stanislau Trukhan