On Feb 28, 2017, at 3:57 PM, Quincey Morris < email@hidden> wrote:
On Feb 28, 2017, at 11:49 , Daryle Walker < email@hidden> wrote:
On Feb 28, 2017, at 11:35 AM, Andy Lee < email@hidden> wrote:
On Feb 28, 2017, at 2:13 AM, Jens Alfke < email@hidden> wrote: One source of slow down it that the JIT insists on doing the definitions-on-the-side feature for every word you pass by with the cursor. Even if the cursor went by the word in less than a second. I don’t know what you mean by “definitions-on-the-side” … Do you mean the code-completion pop-up? That’s below, not on the side. And it only shows up as you type, not as you move the mouse cursor around.
Maybe Daryle meant the Quick Help Inspector?
Yes. The right-most column (on U.S. installations, at least) above the library of objects you can drag-and-drop onto Interface Builder.
“Doctor, doctor, it hurts when I do *that*.”
You know the rest of this joke, I assume.
The Quick Help inspector isn’t slow on my Mac, so at least it’s not a completely intrinsic fault in the help. If it’s slow for you and you don’t know why, then don’t show that inspector. You can get the exact same information by Option-clicking on a symbol, if you should happen to need it. That should at least help you get on with doing useful stuff.
It’s not just Quick Help; the syntax coloring is also affected. It’s whatever system they both reference. Today, SourceKit (or whatever) decided to not have an exponential-time tantrum, and syntax coloring and Quick Help are at their normal speed.
Also, be careful about assume you know what’s going on when your system misbehaves. You earlier description of how (you thought) SourceKit works is almost certainly very wrong, and as a developer you should already know that symptoms don’t necessarily point in the direction of the bug that causes them. For example (using an example from personal experience), if your Mac gets tied up by the spotlight indexer re-indexing everything on your hard disk, the performance of any I/O-bound process is going to plummet, including Xcode doing things like compiling and analyzing syntax. You’d curse at Xcode, but it wouldn’t be to blame.
You may well have a problem, and it may well be in Xcode, but the correct thing to do is submit a bug report (with a attached sysdiagnose for Xcode if that seems appropriate) and see what comes back.
It happens at random. Sometimes, the freak-out slow down happens for days. Other times, it’s all normal.
— Daryle Walker
Mac, Internet, and Video Game Junkie
darylew AT mac DOT com
|