Hi all Please apologize my tone , You don't have to experience my autofrustration. I have a cascade of issues with my "cascaded osgstuffing" and merging with upstream was really a bad idea... Will try to be more self-contained in my comment
Nevertheless, I think you're all understanding why I react to this strange design change...perhaps too roughly as I didn't even test the branch before its merging (i'm lazy), but admit this design rises controversal Have a good weekend robertosfield wrote: > It's really hard to take you seriously when you just head into a > thread with such an obnoxious attitude. > > If you don't understand something ask a polite question, don't dive in > making conclusions about stuff you don't understand yet, let alone be > just plain abrasive and rude about it. > > There may well be bugs in the shader_pipeline work that is now merged > with master, these I'm happy to look into a resolve, though, right now > my focus is getting 3.6.0 out the door, that is the single most > important thing that will happen in the OSG community in the first > half of this year. > > Once 3.6.0 is out my focus will return to master, and completing the > fixed function -> shader pipeline work that started with > shader_pipeline. > > For your own work, please just use the 3.6 branch as base if you are > having problems with master. Once 3.6.0 is out if you still have > problems when using master I can look into and have to explain the > various design choices that I have made. > > Robert. > _______________________________________________ > osg-users mailing list > > http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org > > ------------------ > Post generated by Mail2Forum ------------------ Read this topic online here: http://forum.openscenegraph.org/viewtopic.php?p=73212#73212 _______________________________________________ osg-users mailing list [email protected] http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
