Hi,
> The reason for using VS2003 is that we have an existing VS2003 project and
> want to integrate OpenSG 2.
> Probably it could be transfered to 2005 but I would prefer to keep it
> running on 2003. Another reason for sticking at 2003 is that - afaik - the
> current version of OpenSG 2.0 for VS2005 is only compilable in debug mode.
> But thats a minor reason because I think this will be resolved in the
> future.
Migrate! It's time. VS.2008 is already coming.... :-)
> One more issue regarding QT:
> In OpenSG 1.x QT was supported with the WindowQT lib. Are there any plans
> in
> the near future to provide OpenSG 2 with that package as well or is there
> an
> exisiting solution available?
I'd also vote to drop the WindowQT stuff. There's no real reason
that it's there. It causes only problems/dependencies:( You can replace it
with a PassiveWindow with a few more lines of code.....
I can set-up a demo for that, if necessary.
Toni
P.S.: I'm in a radical mood today :)
-------------------------------------------------------------------------
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
