Hmm...ok. Will give it a try and post my findings tomorrow. Thanks, guys. For some reason, our way of rendering stereo (explicitly setting the render action and getting the port) has always been a little "touchy". I hope this little change at least brings it back into the realm of functional code. :)
Thanks again E. Quoting Dirk Reiners <[EMAIL PROTECTED]>: > > Hi Toni, hi Eric, > > Antonio Bleile wrote: >> Hi, >> >> I don't know if I can help here... But I expereinced >> probelms with iterators when porting to VS.NET 2005. >> Especially things like >> >> vec->erase( it+0 ); // althought [0] is valid! >> >> tend to crash. So it could well be something like >> this. So maybe getPort(0) does something like that? > > hm, I doubt it. The only place in 1.8 that uses vector<bool> is the > shadow viewport. > > A quick hack would be to replace the vector<bool> with vector<UInt8> in > Experimental/ShadowViewport and recompile the libs. The used vectors > are fairly > small, so the impact should be negligible. > > Hope it helps > > Dirk > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Splunk Inc. > Still grepping through log files to find problems? Stop. > Now Search log events and configuration files using AJAX and a browser. > Download your FREE copy of Splunk now >> http://get.splunk.com/ > _______________________________________________ > Opensg-users mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/opensg-users > > > ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ Opensg-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/opensg-users
