🚀 go-pugleaf

BTW, David I didn't mean any of that below to be negative towards you or
anyone else who voices complaints about CodeWarrior...  It's very
frustrating when your tools aren't behaving like you're used to.

+jon

On 11/15/02 5:10 AM, in article B9FA324B.2D965%jon@rocketnetwork.com, "Jon
Gamble" <jon@rocketnetwork.com> wrote:

>> MW Ron <mwron@metrowerks.com> wrote in message
>> news:<mwron-2E0BF6.17313214112002@enews.newsguy.com>...
>>> In article <drehring-EB3B5F.13160214112002@shawnews.vc.shawcable.net>,
>>>  David Rehring <drehring@shaw.ca> wrote:
>>> 
>>>> Well, for me, this appears to be one of the worst updates from MW in a
>>>> long time.
>>> 
>>> This defintitely is one of the best ever  it is pure gold
> 
> [...]
> 
>> P.P.S I like your bullishness :)
> 
> It is quite remarkable, is it not?  The bullishness, that is...  I'm
> reserving judgement on pure gold.
> 
> So far the update has worked flawlessly for me.  Ran the IDE through a
> brutal window closing session with no problems and reading your post below,
> it really sounds like some old version of the IDE could have been the
> offender.
> 
> OS X does some unexpected stuff when choosing editors for an open document
> event...  It may be well defined at the code level but I think it's safe to
> say there are issues when you put the mechanism live on a user's dirty
> desktop.  A tough problem to be fair, keeping that db mapping coherent.
> 
> It sucks to see MW being vilified there in your post right after this update
> because they sure have taken a beating over the window close crash (and
> rightly so).  I hope your circumstances are isolated.  I have been using 8.3
> for the past 8 hours and it hasn't crashed once.  Things are looking great.
> If it keeps going like this, tomorrow I may even screw up the balls to turn
> on code completion.  I also received a special bug fix from MW to fix a
> linker issue.  I found it incredible that they took time to help me out
> while pounding out something as critical to them as 8.3 - I'm not exactly
> the head of Microsoft's Mac BU or anything, I'm just a frickin guy and they
> gave me a special build of the linkers to address an annoying issue that was
> complicating my build process.
> 
> My point is that Metrowerks cares about the customers that post on this
> newsgroup and that is a very good thing.  I have to pay Apple Computer $195
> before they will even talk to me about an issue.  (yeah there are a few ways
> around that I know).  Whether or not 8.3 is pure gold (so far so good
> though), the support _is_ pure gold and that matters a lot.
> 
> +jon
> 
> On 11/15/02 2:40 AM, in article
> ad65e6c9.0211150240.1f8b63dd@posting.google.com, "EJ" <ec109695@yahoo.com>
> wrote:
> 
>> MW Ron <mwron@metrowerks.com> wrote in message
>> news:<mwron-2E0BF6.17313214112002@enews.newsguy.com>...
>>> In article <drehring-EB3B5F.13160214112002@shawnews.vc.shawcable.net>,
>>>  David Rehring <drehring@shaw.ca> wrote:
>>> 
>>>> Well, for me, this appears to be one of the worst updates from MW in a
>>>> long time.
>>> 
>>> This defintitely is one of the best ever  it is pure gold I don't knwo
>>> why you are having problems.  But there is always ways to foil us so
>>> please do try this again and do a clean install to be sure.
>>> 
>>>> Update 8.2 to 8.3->goes fine
>>>> use installer option to open IDE and update MSL Libs->ok
>>>> rebuild all libraries->fine
>>>> 
>>>> Now, open release notes for 8.3 in Finder
>>>> ->launches new copy of IDE [the same file]
>>>> Most likely, this is just due to how the installer launched the IDE, not
>>>> really a problem
>>> 
>>> You should not have gotten two version of the IDE open unless you happen
>>> to have two versions of the IDE and even then ...
>> 
>> Well I too somehow got two copies of the IDE open. I think it happened
>> when I clicked on CodeWarrior from my dock. I'm not what versions the
>> two copies were. Perhaps the second copy was the old IDE that the
>> installer put into the trash or perhaps the installer opened the IDE
>> in a funky way and confused the Finder. I quickly closed them both,
>> updated my dock shortcut, and haven't had any more problems.
>> 
>> One more thing. What should have opened after the install? I thought
>> the build libraries project was supposed to open. For me, only the IDE
>> launched. After I manually opened the libraries project, everything
>> went very smoothly.
>> 
>> -EJ
>> 
>> P.S. To contact me, please e-mail me at ejc3_at_kagi.com (change the
>> _at_ to an @).
>> P.P.S I like your bullishness :)
>