fore tampering
with its internals.)
Andrea
Message: 10
Date: Thu, 28 Feb 2008 20:14:43 -0600
From: Sam McDonald <[EMAIL PROTECTED]>
Subject: Re: Cannot Debug
To: Philip Bridson <[EMAIL PROTECTED]>
Cc: cocoa-dev@lists.apple.com
Message-ID: <[EMAIL PROTECTED]>
Content-Type: text/plai
He was on a Macbook Pro and I was on a Macbook. We went to a mac lab
at my college and tried it on different computers to see what would
happen. We assumed that my computer was the weird one. We tried it
on iMacs and Power Macs and every single one had the same bug I was
experiencing.
Just a question. Were you both developing on the exact same systems?
I.E MacBooks, same clock speed etc?
I just find it odd that if you both had the same code that the error
would be on one machine not the other. Especially that it would
persist after a full restore and work on one and not
Another solution that I know works, because i've done it a few times,
is to start a new project and import all your files from your old
project into the new one. I don't know why it works but it does. I
always put it down to something I was doing wrong to be honest and
generally that is wha
I had this exact problem. And the crazy thing was that my partner was
running the same code and his computer wasn't affected. I re-
installed my developer tools, and it didn't fix it. I re-installed my
operating system, and still nothing was fixed.
Finally, the other developer and myself
I can't tell you why it happened but it happened to me a few weeks
ago using XC 2.4.1 on Tiger 10.4.11. I couldn't solve it so I
uninstalled the entire Developer folder & Tools then re-installed and
now it works fine.
Phil.
On 29 Feb 2008, at 00:31, Steve Cronin wrote:
Folks;
This is XC