nanogui: Screen update methods


Previous by date: 27 May 2007 11:47:16 +0100 Re: Screen update methods, Junior
Next by date: 27 May 2007 11:47:16 +0100 Re: Screen update methods, Greg Haerr
Previous in thread: 27 May 2007 11:47:16 +0100 Re: Screen update methods, Junior
Next in thread: 27 May 2007 11:47:16 +0100 Re: Screen update methods, Greg Haerr

Subject: Re: [nanogui] Re: Screen update methods
From: Roberto ####@####.####
Date: 27 May 2007 11:47:16 +0100
Message-Id: <46596199.4090203@tnw2000.org>

>My "active window" or frame buffer I really meant the real memory mapped framebuffer
>and the pixmap area is a memory location that is a "mirror" framebuffer sitting somewhere
>in RAM that I draw into then do a GrCopy (a blit).
>
>My question is if I'm drawing to the "mirror" frame buffer, should the server be writing
>to the actual framebuffer for any reason? I expect no activity to the actual framebuffer until
>I do a copy from the pixmap to that memory. If the latter is true, then drawing horiz lines on the pixmap
>shouldn't have any effect on the actural framebuffer unless they are one and the same. Not so?
>I'll appreciate this clarification.
>  
>
Im using offscreen drawing in tnw2000, too. All activities I do in a 
pixmap allocated
with GrNewPixmap has no effect to the framebuffer.
But I use GrSetBackgroundPixmap instead of GrCopy, since the server calls
the blit function for me always when needed.
Hope this helps you.

>  
>
>>When drawing pixel-by-pixel, or line-by-line, the driver-
>>level drawpixel or drawline (horz or vert) routines are
>>called.  Rectangle fills currently use repeat horz drawline.
>>When copying a bitmap or memory, the blit routine is called.
>>There are not multiple options (routines) to determine when
>>drawing, instead set driver entrypoint(s) are called to
>>effect the required drawing.
>>
>>    
>>
>>>Any drawing I've done I've done on a pixmap
>>>      
>>>
>>so I can do one block copy to the framebuffer.
>>
>>Yes.  Unless you originally filled the pixmap
>>from another image, low-level pixel/line routines were
>>called to draw the pixmap, then the blit driver routine
>>was used to copy it (to the framebuffer or another
>>pixmap, they're just memory addresses).
>>
>>Hope this helps.
>>    
>>
>It did.
>
>Thanks,
>Jr.
>
>____________________________________________________________
>FREE 3D EARTH SCREENSAVER - Watch the Earth right on your desktop!
>Check it out at http://www.inbox.com/earth
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: ####@####.####
>For additional commands, e-mail: ####@####.####
>
>
>  
>


Previous by date: 27 May 2007 11:47:16 +0100 Re: Screen update methods, Junior
Next by date: 27 May 2007 11:47:16 +0100 Re: Screen update methods, Greg Haerr
Previous in thread: 27 May 2007 11:47:16 +0100 Re: Screen update methods, Junior
Next in thread: 27 May 2007 11:47:16 +0100 Re: Screen update methods, Greg Haerr


Powered by ezmlm-browse 0.20.