En 13/07/2010 13:08:05, Domingo Alvarez Duarte <[email protected]> escribió:
> En 13/07/2010 12:42:25, Domingo Alvarez Duarte <[email protected]> > escribió: > >> Looking at the pattern usage of the functions on fl_vertex.cxx it seems >> that they are a class on itself: >> >> Basically the pattern is: >> >> >> fl_push_matrix(); >> fl_translate(x, y); >> fl_scale(x, y); >> >> do any drawing work with the transformed matrix including any nested >> new transformations >> >> fl_pop_matrix(); // return the stack to it's original state. >> >> I didn't found a cross class usage of the matrix stack, so if the are >> used and restored inside each class (and only few classes use it) it >> seems that turning then into a class tha is instantiated by the class >> or function that will use it makes sense and eliminate this botleneck. > > > In fact most of the pre 1.3 draw functions are already remapped to > fl_graphics_driver->function() it's a matter to extend this mapping to > matrix stack. Also the clip stack should be a member variable of Fl_Graphics_Driver, in this case the functions that manipulate the stack are already mapped but not the clip stack (halfway done and I don't see any reason to complete the other half). _______________________________________________ fltk-dev mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk-dev
