>> 3. The image generation process is visible to the end user. This is an >> application specific problem. I would have to create a separate 'printing' >> window which is not visible to the application user. > > yup, FBO... *runs and hides* ;)
just to throw in another idea: i once used opensg in combination with mesa to create an arbitrary big rgba-buffer (how big is your ram? :))... could be painfully slow due to software rendering, could be painfully slow due to transfering the geometry from one "opengl-context to another" (aka: create a clone of the graph) ... but the only limit of mesa is your available ram. and it directly renders into your ram, no transferring back pixels from the gpu. just my 2ct, mathias -- [uid] mathias gumz [mail] akira at fluxbox dot org [pgp] 1024D/F6F6B18C [www] http://www.darkshed.net/ [irc] ak|ra (#fluxbox at freenode.org) ------------------------------------------------------------------------------ ThinkGeek and WIRED's GeekDad team up for the Ultimate GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the lucky parental unit. See the prize list and enter to win: http://p.sf.net/sfu/thinkgeek-promo _______________________________________________ Opensg-users mailing list Opensg-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensg-users
