discuss-gnustep
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: NSOpenGLView


From: Renaud Molla
Subject: Re: NSOpenGLView
Date: Wed, 8 Nov 2006 14:26:35 +0100

Enrico:
What do you mean by [[self openGLContext] flushBuffer] does the trick?
Will it solve the problem if i remove these calls?
Or do you mean that these make the drawRect: called repeatedly?
And what does the timer if it is created and scheduled, set to repeat, is never invalidated in the code and calls pulseColor which in turn calls setNeedsDisplay: that will then call drawRect:
?

If anybody still thinks about something, let me know

Renaud

On Nov 8, 2006, at 12:27 PM, Enrico Sersale wrote:

On 2006-11-08 12:41:52 +0200 Renaud Molla <renaud.molla@wanadoo.fr> wrote:

Hi,
I'm trying to write an NSOpenGLView application (actually i'm using an example from Stefan Urbanek http://lists.gnu.org/archive/html/discuss-gnustep/2004-11/ msg00191.html
        and corrected the things so it launches and run),
but the NSOpenGLView doesn't display anything although the drawRect method is called regularly
        through the use of a timer.

It seems that, in the Stefan's example, is the "[[self openGLContext] flushBuffer]" at the end of -drawRect: that does the trick, not the timer.

The view 'contains' what was in the background before the window appeared.
        Moving the window don't make it display anything either.
Making the NSOpenGLView the window contentView does not change anything equally.
        The same code works 100% when compiled with cocoa.
        Any help would be appreciated !-)
Renaud Molla

---------------------------------------------------------------------- ----------------- Orange vous informe que cet e-mail a ete controle par l'anti-virus mail. Aucun virus connu a ce jour par nos services n'a ete detecte.









reply via email to

[Prev in Thread] Current Thread [Next in Thread]