Hi Werner,
On Sat, Oct 2, 2010 at 11:39 AM, Werner Modenbach
werner.modenb...@texion.eu wrote:
This is a snippet from frame (ViewerBase.cpp):
eventTraversal();
updateTraversal();
renderingTraversals();
Yes, I have seen this small sequence :-)
But I have no idea which of the 3
Changing the subject since this is a different topic.
Werner Modenbach writes:
Can you please give a compareable short explanation on how frame() calls are
generated and what happens inside then?
The background of my question is the behaviour and the experience I got with
Qt Adapterwidget.
On Saturday 02 October 2010 11:52:08 Alberto Luaces wrote:
Changing the subject since this is a different topic.
Sorry, was by accident.
Werner Modenbach writes:
Can you please give a compareable short explanation on how frame() calls
are generated and what happens inside then?
The
Werner Modenbach writes:
On Saturday 02 October 2010 11:52:08 Alberto Luaces wrote:
Changing the subject since this is a different topic.
Sorry, was by accident.
Werner Modenbach writes:
Can you please give a compareable short explanation on how frame() calls
are generated and what
Alberto Luaces writes:
In order to have a clearer lecture of what means every OSG traversal, I
recommend you to read the OSG's Quick Start Guide:
Sorry, I meant
http://www.skew-matrix.com/OSGQSG/
--
Alberto
___
osg-users mailing list
Hi Werner,
Alberto said:
This is the common scenario for realtime applications. On the other side
for GUI applications, usually the scene is static until the user does
something. In that case, you only call frame() after keyboard, mouse,
redraw events... and you save all that redundant
6 matches
Mail list logo
