On Thu, Oct 15, 2009 at 05:17, Andy Miller
<nzmi...@gmail.com> wrote:
Thanks for this -- I'm planning a refresh on the Mac build (doing a new Windows binary build again Ogre 1.6.4 with latest libraries first) so will take a look at this..
That'll be great!
If the bug isn't fixed in newer Ogre, perhaps you could include the hack in the wrapper somehow; I haven't found another non-hackish solution to the problem, so this will probably appear to everyone using PythonOgre, and not everyone will be willing to dig deep enough and will instead just proclaim the problem unsolvable. So if it fixes the problems for everyone... :-)
I wonder if you can't just use the standard pyobjc interface instead of using pyglet library loader...
I haven't tried; we have to hurry with the port and sadly, I can't look into "real" solutions to the problem. If there's a cleaner way to do things, I'm of course always for it -- except when under pressure to "just get things working" :-)
--
Regards,
Ivan Vučica