Mailing List
Home
Forum Home
Mac Game - Mac game development
Rivers of MUD - a Diku and Merc based multiuser dungeon
SMAUG
Subjects
Getting UDP through NAT/firewalls/whatever for a game
Getting UDP through NAT/firewalls/whatever for a game
QuickTime errors
Python script as stand alone MUD server
Subject: Various sound problems
Fragment Shaders & GL TEXTURE RECTANGLE EXT
Subject: Timers and global variables
Re: Language and platform for Text MUD server
Apparent acquisition of Yantis (mysupersales) by IDE
HID keyboard
Getting UDP through NAT/firewalls/whatever for a game
Microsoft Sparkle
Subject: Director MX
Congratulations Horizons
Yet more problems fullscreen mode
Apple Dev Kitchen Them 's tasty vittles, Maw!
NSOpenGLContext, Pbuffers, and drawables
More DCR "theft " naughtiness
dynamic sprite creation and imaging lingo
Re: Find stuff in Flash array?
Effects of skill imbalances?
QuickTime errors
Rom 2 4/Quickmud Enhancement/Bug fix
Subject: Working with XML files/CFURL
smooth scrolling/subpixel tweening
RE: (Ron help me?) Flash text
Subject: Flash Racing
Subject: MudDev FAQ 2
Browser based games
Installing GLUT
Special character in Flash XML
 
Subject: Re: Thoughts on the Gabe Newell 's Mac comments.

Subject: Re: Thoughts on the Gabe Newell 's Mac comments.

2007-10-05       - By Errol Sayre

 Back
> From my perspective (just personally, not-representing-my-employer,  
> etc.), I can see huge dividends for OpenGL patches separate from OS  
> updates. When we find an OpenGL bug, even if the fix is a simple  
> one-liner for Apple to implement, it has to wait for the next OS  
> update. If the OS has end-of-lifed, then there's no vehicle for the  
> fix at all. Just as one concrete example, there was a problem  
> introduced with the 10.3.9 update affecting Warcraft III on GF2MX,  
> and that was never fixed because there were no future 10.3 updates.  
> We had to tell users to downgrade to 10.3.8 or upgrade to Tiger to  
> solve it (it was fixed early on in 10.4's lifespan, shortly after  
> 10.4.0). Of course there is no official way to downgrade to 10.3.8  
> other than a reinstall, which is difficult for everyone involved.  
> If OpenGL wasn't tied to OS updates, we could have just told the  
> 10.3 users to run Software Update and the next driver release would  
> have fixed it.

What's a shame ?to me at least ?is that these things really aren't a  
part of the OS and could be upgraded independently. QuickTime is a  
prime example of this.

Now, as I said before, if some kernel change, or cocoa change is what  
spurned the fix, I could see why Apple wouldn't release an upgrade  
for an older OS, but I just don't see how a minor bug fix like this  
in OpenGL would be dependent upon any such thing...

I don't see any reason why Apple couldn't release a "Core Graphics  
Update" or "OpenGL Update" for an older version even if those updates  
are included in a "Mac OS X Update" for a later version...

How exactly does one file a bug report about just plain bad  
practices? I guess you could file a bug report that the fix still  
hasn't been applied to an old version but there's nothing stopping  
Apple from marking that as a duplicate of the fixed version...
<HTML><BODY style="word-wrap: break-word; -khtml-nbsp-mode: space; -khtml-line
-break: after-white-space; "><DIV><BLOCKQUOTE type="cite"><DIV style="margin-top
: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">From my
perspective (just personally, not-representing-my-employer, etc.), I can see
huge dividends for OpenGL patches separate from OS updates. When we find an
OpenGL bug, even if the fix is a simple one-liner for Apple to implement, it
has to wait for the next OS update. If the OS has end-of-lifed, then there's no
vehicle for the fix at all. Just as one concrete example, there was a problem
introduced with the 10.3.9 update affecting Warcraft III on GF2MX, and that was
never fixed because there were no future 10.3 updates. We had to tell users to
downgrade to 10.3.8 or upgrade to Tiger to solve it (it was fixed early on in
10.4's lifespan, shortly after 10.4.0). Of course there is no official way to
downgrade to 10.3.8 other than a reinstall, which is difficult for everyone
involved. If OpenGL wasn't tied to OS updates, we could have just told the 10.3
users to run Software Update and the next driver release would have fixed it.<
/DIV></BLOCKQUOTE></DIV><BR><DIV><SPAN class="Apple-style-span">What's a shame
?to me at least ?is that these things really aren't a part of the OS and <I
>could be upgraded</I>?independently. QuickTime is a prime example of this.<
/SPAN></DIV><DIV><BR class="khtml-block-placeholder"></DIV><DIV><SPAN class=
"Apple-style-span">Now, as I said before, if some kernel change, or cocoa change
is what spurned the fix, I could see why Apple wouldn't release an upgrade for
an older OS, but I just don't see how a minor bug fix like this in OpenGL would
be dependent upon any such thing...</SPAN></DIV><DIV><BR class="khtml-block
-placeholder"></DIV><DIV>I don't see any reason why Apple couldn't release a
"Core Graphics Update" or "OpenGL Update" for an older version even if those
updates are included in a "Mac OS X Update" for a later version...</DIV><DIV>
<BR class="khtml-block-placeholder"></DIV><DIV>How exactly does one file a bug
report about just plain bad practices? I guess you could file a bug report that
the fix still hasn't been applied to an old version but there's nothing
stopping Apple from marking that as a duplicate of the fixed version...</DIV><
/BODY></HTML>
__ ____ ____ ____ ____ ____ ____ ____ ____ ____
Do not post admin requests to the list. They will be ignored.
Mac-games-dev mailing list      (Mac-games-dev@(protected))
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/mac-games-dev/junlu%405341.com

This email sent to junlu@(protected)