Running the Code on Mac OS X 10.6

[Nadro]

I don't agree with Hendu this time. If Your team mate which use Mac found some bugs please just report it on bug tracker and we'll fix this. As CuteAlien said Mac have got less users than Windows for example, so number of bug reports is also smaller. Some time I support Windows, Linux and MacOSX for all my projects and from my side I can say that I tested my code under MacOS X very often and I think that this platform is well supported

[mordenkainen]

Access to != good attention, my mac guy has been complaining about a ton of small things that wouldn't be there if it were getting good attention, or a primary platform as you say.

Note that I'm not complaining, I don't particularly care about macs, but you should admit the facts so that new users don't come thinking mac is a first-level supported platform.

It's not a problem. The macintosh is the tool I have, I'll learn to use it. The bug that I mentioned for the first tutorial example comes from this:

cpp Code: Select all

 
IrrlichtDevice *device =
        createDevice( video::EDT_SOFTWARE, dimension2d<u32>(640, 480), 16,
            false, false, false, 0);
 

In order to run properly on the mac, this command needs to be this:

cpp Code: Select all

 
IrrlichtDevice *device =
        createDevice( video::EDT_OPENGL, dimension2d<u32>(640, 480), 16,
            false, false, false, 0);
 

Again, I have no idea if this is intended behavior, it is what it is.

I'm thinking very seriously about going through all of the tutorial examples and making changes and updates that should be more likely to be stable on the macintosh. Of course, riddling tutorial examples with a lot of #ifndef, might damage their purpose as tutorials, at least putting a comment into the source code explaining which options and flags are best for a mac would be an improvement...

[hybrid]

Moreover, we have now fixed all (or almost all) OSX related bugs from the bug tracker. So it should be the best working OS for now But I guess it's often due to the fixes only being in trunk. So let's hope that 1.8 will make the situation better for OSX users.