Just to note the corruption that xcode sometimes performs (possibly related to kinemecore 0.2's problem), here's a screen shot. Has anyone else seen/experienced this before?
Not really, that's what my code window normally looks like.
Ok, maybe not that bad :D But I've seen nothing like that, and I've been writing a lot of stuff in xcode lately (with 3.1.2). I did see some pretty bad graphical glitches now and then though, like earlier today I had a giant number 2 in the gutter (that sounds disgusting :/ But it was genuinely a huge 2 covering around 10 lines of the gutter!)
The above is a bit exaggerated (I noticed it, so I kept playing with things just to make it obvious what was going on) -- normally it's only a line or two.
Last time I had a giant number 2 in the gutter, I was using Visual Studio ;)
Mine's version 3.1.2 as well... not sure what causes it. :/
(if anyone uses that as an example of what my code looks like, I'll never get another coding job again! :)
I had that happen to me and thought maybe my mother board was going to go bad... glad I'm not the only one.
On another funky note, does anyone ever have the problem where Finder goes whacky and the top menu bar turns black, or doesn't load at all? I have another user account on my computer solely for the purpose of giving Finder a "poke"... as logging out of my usual(actually... usually having to just give the computer a forced shut down), logging into that one, and then back in to my usual, always fixes it. Happens once every couple of months or so.... usually after putting my computer in sleep mode, and taking it out of sleep with a different network config.
I've not really had finder freak out like that, but I do find network/usb configuration changes while the machine's sleeping to be a Really Bad Ideatm. Usually, it renders my machine unloginable (which should be a word :)
(also of note: 140 warnings would also probably get me fired -- I've since dropped it to 4. Using unofficial api hacks tends to make the compiler whiny)
Ok, I just had exactly the same thing happen (looks pretty much the same as your screenshot).
It was just after I did a build (with errors a-plenty!), and I was editing some code with errors displayed (I noticed this is buggy anyway, sometimes the errors are place right over the code you want to edit). It seemed fine until I scrolled down, near the bottom of the document it was like this.
Not really, that's what my code window normally looks like.
Ok, maybe not that bad :D But I've seen nothing like that, and I've been writing a lot of stuff in xcode lately (with 3.1.2). I did see some pretty bad graphical glitches now and then though, like earlier today I had a giant number 2 in the gutter (that sounds disgusting :/ But it was genuinely a huge 2 covering around 10 lines of the gutter!)
The above is a bit exaggerated (I noticed it, so I kept playing with things just to make it obvious what was going on) -- normally it's only a line or two.
Last time I had a giant number 2 in the gutter, I was using Visual Studio ;)
Mine's version 3.1.2 as well... not sure what causes it. :/
(if anyone uses that as an example of what my code looks like, I'll never get another coding job again! :)
I had that happen to me and thought maybe my mother board was going to go bad... glad I'm not the only one.
On another funky note, does anyone ever have the problem where Finder goes whacky and the top menu bar turns black, or doesn't load at all? I have another user account on my computer solely for the purpose of giving Finder a "poke"... as logging out of my usual(actually... usually having to just give the computer a forced shut down), logging into that one, and then back in to my usual, always fixes it. Happens once every couple of months or so.... usually after putting my computer in sleep mode, and taking it out of sleep with a different network config.
I've not really had finder freak out like that, but I do find network/usb configuration changes while the machine's sleeping to be a Really Bad Ideatm. Usually, it renders my machine unloginable (which should be a word :)
(also of note: 140 warnings would also probably get me fired -- I've since dropped it to 4. Using unofficial api hacks tends to make the compiler whiny)
Ok, I just had exactly the same thing happen (looks pretty much the same as your screenshot).
It was just after I did a build (with errors a-plenty!), and I was editing some code with errors displayed (I noticed this is buggy anyway, sometimes the errors are place right over the code you want to edit). It seemed fine until I scrolled down, near the bottom of the document it was like this.