nanogui: Screen update methods
Subject:
Re: [nanogui] Re: Screen update methods
From:
Junior ####@####.####
Date:
29 May 2007 19:03:42 +0100
Message-Id: <FEF9045C9E8.00000380ejr@inbox.com>
> -----Original Message-----
> From: ####@####.####
> Sent: Mon, 28 May 2007 10:57:48 -0700
> To: ####@####.#### ####@####.####
> Subject: Re: [nanogui] Re: Screen update methods
>
> : But I use GrSetBackgroundPixmap instead of GrCopy, since the server
> calls
> : the blit function for me always when needed.
>
> This is a somewhat tricky method of using blit to update a
> window with changing content, since the applications programmer
> won't know when exactly it happens. Pretty interesting though,
> since this method effectively updates a window area from
> an offscreen pixmap almost automatically. Note that it
> doesn't update the window just because the pixmap
> has changed though... you would need a timer-based
> GrClearWindow call to force redrawing for that case,
> and then the system would redisplay the entire pixmap,
> rather than just the modified portion. It might be better
> to keep an update clip region when the offscreen pixmap
> is updated, to speed the double buffering draws.
>
I have one more question regarding this.
When using GrNewPixmap, the void *pixels argument us not used for client/server, What about when it is Linked into the APP?
I don't see a memory location allocated to draw into, shouldn't there be? If this arg is NULL, it seem to appear that this
seem to draw directly, yes?
Also, does nanox have a way to specifically allocate noncache memory?
Thanks,
Jr.
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: ####@####.####
> For additional commands, e-mail: ####@####.####
____________________________________________________________
PREVENT ACCESSING DANGEROUS WEBSITES - Protect your computer with Free Web Security Guard!
More information at http://www.inbox.com/wsg
