Hi Nil,

we're making good progress in the migration towards the VTK OpenGL 2 backend. 
In fact, most things are already working in the branch 
T18922-OpenGLBackend2-kislinsk [1,2]. There's not a specific problem with the 
new backend, but the feature freeze for the current release was already in 
11/2016. Hence the name, by the way. :-)


The macOS rendering bug is probably related. In a first try with the mentioned 
branch, I wasn't able to make things work as they should on macOS. 
Nevertheless, our assumption still is, that macOS makes trouble with shared 
OpenGL contexts of different versions (which is a known issue on macOS 
according to the official OpenGL documentation). The VTK OpenGL 2 backend uses 
OpenGL 3.2 Core Profile. Setting the default surface format for Qt to the same 
version seems not to be the only thing that's necessary. But we still need to 
investigate, as the OpenGL context of the WebEngine, which is causing all the 
trouble, might have ignored our hint in the first try. As a developer, you're 
still able to use the latest version of MITK on macOS, as long as you (a) 
switch off MITK_USE_Qt5_WebEngine in CMake, or alternatively (b) don't open the 
help system and/or the image statistics plugin while the rendering windows are 
visible. That will result in rendering artifacts.


Best,
Stefan


[1] https://phabricator.mitk.org/T18922

[2] 
https://phabricator.mitk.org/source/mitk/browse/T18922-OpenGLBackend2-kislinsk/


________________________________
Von: Nil Goyette <nil.goye...@imeka.ca>
Gesendet: Montag, 6. Februar 2017 16:48
An: mitk-users@lists.sourceforge.net
Betreff: Re: [mitk-users] MITK 2016.11 released


Hi MITK team,

Thank you for this release and for your good work. The changes in the geometry 
system are indeed awesome :)

I have one question about vtk. I was surprised to see that vtk 7.0 didn't make 
it into the list of update even if you updated it. So I checked VTK.cmake and 
realized that you are still using the old OpenGL backend. If I understand 
correctly, the OS X bug is directly caused by this backend.

  1.  What are your plans concerning the new backend? Do you plan to use it on 
the next MITK's version?
  2.  What's the problem with the new backend? I guess that all MITK's mappers 
need to be updated and you didn't have enough time to do it. Anything else? I 
ask because we have our own mappers here and I will probably face the same 
problems :)
  3.  Totally unrelated and not useful question... Why do you name the release 
2016.11 when you release it in 2017.02? :D

Again, thank you for your time.

Nil

Le 2017-02-06 à 08:57, Goch, Caspar Jonas a écrit :

Dear MITK users,



we are happy to announce the release of MITK 2016.11!



New supported versions are CMake 3.5 or newer, Qt 5.6 or 5.7.1  (version 5.8 is 
not yet supported).


------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
_______________________________________________
mitk-users mailing list
mitk-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mitk-users

Reply via email to