Hi Aliastair.
Interesting problem, not one I had thought of before. The idea of setting
done to true when all the views are closed is just a mechanism to ensure
exit from the frame loop. When adding views back in it certainly should be
possible to get the frame loop restarted so _done should be
I've only just got round to reading this, but for the sake of clarification, I
think I know what your problem was.
OSG will run perfectly happily at the start with a CompositeViewer but no
views. But after some are created, as soon as they are all destroyed, the
CompositeViewer decides that it'
Hi Chris,
On 13 September 2013 00:09, Chris Stankevitz wrote:
> Thank you. I implemented this and it is rock solid. I had to do some
> head scratching as all my viewers might be running at different
> resolutions but I solved this by 1) making the pbuffer large enough
> and 2) changing the cam
On Wed, Sep 11, 2013 at 10:39 AM, Robert Osfield
wrote:
> First up I'd create a single graphics context, this can would be a pbuffer
> in your case. This graphics context would live for life of the application.
>
> Second I'd have a single CompositeViewer that lives throughout your
> application.
Hi Chris,
Thanks for the explanation.
Rather than answer your questions. I'll dive in make my own suggestion.
First up I'd create a single graphics context, this can would be a pbuffer
in your case. This graphics context would live for life of the application.
Second I'd have a single Composi
On Wed, Sep 11, 2013 at 9:31 AM, Robert Osfield
wrote:
> What stands out is that you are doing stuff that is probably not the best
> way to do it. To find out the best way it would be better to explain what
> you are tying to do with your application w.r.t views, graphics contexts,
> threads, sce
Robert,
Thank you for your reply.
On Wed, Sep 11, 2013 at 8:27 AM, Robert Osfield
wrote:
> Normally one should ever need to worry about constructing or destructing the
> DatabasePager
Thank you. My preference is to never think about the DatabasePager.
Since I use multiple views, at a minimum I
HI Chris,
I am afraid I don't have the time to trying and work out what exactly you
are doing and how to fix it. You are almost certainly tackling things in
the wrong so rather than fix working in a broken way time for us all would
be better spent taking a step back.
What stands out is that you
Hi Chris,
Normally one should ever need to worry about constructing or destructing
the DatabasePager, it should happen behinds the scenes managed by
osgViewer. osgViewer::Scene is used internally by osgViewer to manage one
DatabasePager per scene graph. The Scene object will be shared
automatica
Glenn,
Thank you for your reply.
On Wed, Sep 11, 2013 at 4:22 AM, Glenn Waldron wrote:
> Are you using multiple Viewers, or are you using multiple Views under a
> CompositeViewer?
I am experimenting with both of these techniques. When I use the
CompositeViewer my views turn "purple" after a co
Chris,
Are you using multiple Viewers, or are you using multiple Views under a
CompositeViewer? I'm not sure running 2 Viewers that point at the same
graph is entirely safe.
Anyway, call setUnrefImageDataAfterApplyPolicy() after creating your
View/Viewer but before calling frame().
Glenn Waldron
11 matches
Mail list logo
