Thread (15 messages) 15 messages, 3 authors, 2003-01-11
  • clipping · Geert Uytterhoeven <geert@linux-m68k.org> · 2002-12-29
  • Re: clipping · Antonino Daplas <hidden> · 2003-01-03
  • Re: clipping · Geert Uytterhoeven <geert@linux-m68k.org> · 2003-01-07
  • Re: clipping · James Simmons <hidden> · 2003-01-07
  • Re: clipping · Geert Uytterhoeven <geert@linux-m68k.org> · 2003-01-08
  • Re: clipping · Antonino Daplas <hidden> · 2003-01-08
  • Re: clipping · James Simmons <hidden> · 2003-01-09
  • Re: clipping · Geert Uytterhoeven <geert@linux-m68k.org> · 2003-01-09
  • Re: [RESEND] clipping · Antonino Daplas <hidden> · 2003-01-10
  • Re: clipping · James Simmons <hidden> · 2003-01-10
  • Re: clipping · Geert Uytterhoeven <geert@linux-m68k.org> · 2003-01-10
  • Re: clipping · Antonino Daplas <hidden> · 2003-01-11
  • Re: clipping · Antonino Daplas <hidden> · 2003-01-10
  • Re: clipping · Geert Uytterhoeven <geert@linux-m68k.org> · 2003-01-10
  • Re: clipping · James Simmons <hidden> · 2003-01-09

Re: clipping

From: James Simmons <hidden>
Date: 2003-01-09 21:24:41

So perhaps, a function something like this:

void fb_clip(struct fb_fillrect *region, struct fb_fillrect *clip);

This should not be difficult to implement, and I'll code it if everyone
agrees.
 
I thought about this. Originally I did have this function but removed it.
WHat do you think Geert?
The other option (which I don't like) is just to check the passed
fb_var_screeninfo in the put_var ioctl against the current console
window size.  But this is not foolproof as we will not be sure of the
resulting window size _after_ the fb_set_var() call.
Yuck!!! The other way is better.



-------------------------------------------------------
This SF.NET email is sponsored by:
SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See!
http://www.vasoftware.com
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help