Amarinder Singh Sethi wrote:
checkstate:
========
The acceleration functions, drawing and blitting flags in the state
structure are passed in CheckState routine to indicate the type of
graphics operation requested, for instance stretchblit with destination
color keying. The CheckState routine of a particular gfx accel driver is
expected to confirm if the operation can be supported in hardware and if
yes, it is expected to set the appropriate drawing or blitting functions
supported in state->accel field. DirectFB compares this with original
acceleration flags requested to check if hardware acceleratrion is
supported or not and follows it with setstate call.
SetState() might not be called, depending on what has changed, e.g.
calling FillRectangle() and FillTriangle() without changing the color
would/could call CheckState() with subsequent primitive.
setstate:
the function gets called to propagate the state changes to the driver.
The gfx accel driver is expected to look at state->modified flags to
check what has been modified and act accordingly and prepare for the
actual operation.
It is state->mod_hw for quite some time now.
--
Best regards,
Denis Oliver Kropp
.------------------------------------------.
| DirectFB - Hardware accelerated graphics |
| http://www.directfb.org/ |
"------------------------------------------"
_______________________________________________
directfb-dev mailing list
directfb-dev@directfb.org
http://mail.directfb.org/cgi-bin/mailman/listinfo/directfb-dev
