[AD] [ alleg-Bugs-2931024 ] stop using deprecated interfaces in OSX port

["SourceForge.net" <noreply@xxxxxxxxxx>]

Bugs item #2931024, was opened at 2010-01-12 23:43
Message generated for change (Comment added) made by peterhull90
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=105665&aid=2931024&group_id=5665

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: Mac OSX
Group: 4.9
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Peter Wang (tjaden)
Assigned to: Peter Hull (peterhull90)
Summary: stop using deprecated interfaces in OSX port

Initial Comment:
Evert publically stated we would fix it before 5.0 so I guess we should :)

----------------------------------------------------------------------

>Comment By: Peter Hull (peterhull90)
Date: 2010-01-25 16:18

Message:
OK that's compile-time compatibility but would Allegro compiled on a 10.6
system work on 10.4 at run time?

----------------------------------------------------------------------

Comment By: Evert Glebbeek (eglebbk)
Date: 2010-01-25 13:11

Message:
It should be 10.4, at the very least it worked there up until a couple of
months ago, which is the last time I checked. Obviously, I'll have to do so
again before 5.0 goes life.
Only supporting 10.4 and up is probably not such a bad deal, since 99% of
all Macs will be on 10.4+ anyway.

Note that I've included some code that gets compiled conditionally
depending on the OS X version number that is being targeted. This isn't
actually all that hard (check against MAC_OS_X_VERSION_MIN_REQUIRED) but
the documentation about this is a bit opaque.

----------------------------------------------------------------------

Comment By: Peter Hull (peterhull90)
Date: 2010-01-25 09:40

Message:
That seems like a sensible decision. As Evert says, the documentation is
very poor/non existent, but I believe that the replacement functions are
only supported on the latest OSX versions and would cause problems for
older versions. I don't actually know what is the earliest version that
Allegro will compile for but I would say it needs to be 10.4 at least.

----------------------------------------------------------------------

Comment By: Evert Glebbeek (eglebbk)
Date: 2010-01-25 02:45

Message:
I've fixed a good deal of them. Right now there are still warnings about
CGDisplayBestModeForParametersAndRefreshRate, CGDisplaySwitchToMode,
CGDisplayCurrentMode and CGDisplayBestModeForParameters in osxgl.m.
Unfortunately Apple hasn't bothered to document the replacement functions
yet (the prototypes are visible in the header files though).
I suggest we leave them until Apple documents their new functions.
I also suggest that we don't delay 5.0 because of Apple slacking off. :P

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=105665&aid=2931024&group_id=5665