Quoting Pierre-Hugues Husson: > Le Samedi 05 Mars 2005 17:43, Denis Oliver Kropp a �crit�: > > It's much better to store the string somewhere in LiteLabel > > and call DrawString() for it each time the button is updated. > I thought it's better about CPU consomation, no?
It's no overhead compared to the disadvantages: - it consumes additional video memory and bandwidth - changing the text color needs to update the image - if the image is blitted without blending, the widget can't be transparent, i.e. showing the text on whatever is shown by parent widgets - blending the image during blit without acceleration is much slower than text rendering > > If you really want to render the string in advance you should > > at least create an offscreen surface for it. > Alright > Thanks > I will try to do this but now my problem is that, while i'm not a graphist i > don't know how to represente both states of the button (for highlight and > normal i know, it's for the others i haven't idea):D disabled - usually gray active - stronger highlight should be fail safe ;) -- Best regards, Denis Oliver Kropp .------------------------------------------. | DirectFB - Hardware accelerated graphics | | http://www.directfb.org/ | "------------------------------------------" _______________________________________________ directfb-users mailing list [email protected] http://mail.directfb.org/cgi-bin/mailman/listinfo/directfb-users
