>I think instead of "modified" you should use the word
>"current". Rhys' build required that one use the latest
>versions of Apple's Universal Interfaces, which are
>freely available, and while they do come with
>CodeWarrior, they are something you should update
>anyway. I don't mean to insult you Loren, but I think
>you are the only person who had problems building Rhys'
>version of the code (worked fine for me w/o changing any
>files at all). Also, he explained what was necessary to
>upgrade your UI files several times (not a big deal,
>just d/l the files and replace your Mac OS Support ->
>Universal Headers folder).
actually, in Pro 4 the Universal Headers folder is fairly complicated to
upgrade since it doesn't match the actual structure of the Universal folder
provided by Apple - thus, you had to replace files all over the place. that
was corrected in Pro 5, where it's a lot easier to upgrade the UI.
also, upgrading the UI is not always something you *want* to do. it really
depends on what you're working on. upgrading the UIs is a little like
upgrading your OS - you get the latest features, but you also break a few
programs and have to work a bit to get your system up and running smoothly.
for example, upgrading the UIs will most certainly break PowerPlant
(although this has nothing to do with A1, just an example).
however, it must be said that it's fairly easy to conditionalize the pieces
of code related to a newer version of the UIs, providing there was a way of
doing the same stuff before - a simple #if UNIVERSAL_INTERFACES_VERSION >
... would probably do.
charles lechasseur - danov@...
"The butts of evil are awaiting my bootprints!"