LCDproc development and user support list

Text archives Help


[Lcdproc] bounding box


Chronological Thread 
  • From: Michael.Frase AT gmx.de (Michael Frase)
  • Subject: [Lcdproc] bounding box
  • Date: Fri Aug 1 20:42:02 2003

Hi ...

part of Rene's mail:
> 4. bounding box
> - I still think it's not neccessary.
> - Please, present the reasons that make it neccessary.

If you want frame support you will use a kind of a bounding box !
If a widget moves out of a frame ...it has to be cutted of.
the "cut-positions" are a bounding box. (if you looked at my new render.c
you can find the places where widgets are cutted off !)

The question is: Should the bounding box be realized in drivers or in
rendering code ?
Whats the difference ?
1. bounding box in render.c:
* render code checks widget position and length
* now it compares that info with position, width, height (etc) of frame
* if it is needed the widgets lenght will be cutted
* therefore only the part in the bounding box ( = visible part of the frame
!)
is sended to the driver !

2. bounding box in driver code:
* renderer sends all data (without checking widget position etc)
* driver checks every char whether it is in a defined area (bounding box)
* if this is true ... the char is drawn !

Hope that helps ... Michael





Archive powered by MHonArc 2.6.18.

Top of page