How can I disable spell checking for an NSTextView? In particular, the red lines that are automatically drawn. I know about the "Continuous Spell Checking" option in Xcode, and every option I have found in the documentation related to spell checking doesn't seem to take the red lines away.
Select NSTextView (doubleClick in IB on it because NSTextView is in NSScrollView by default or select it in Document Outline) and go to Attributes Inspector -> Linguistics -> and uncheck Continous Spell Checking here:
Result:
I don't know what you tried, but [self.textView setContinuousSpellCheckingEnabled:NO]; worked for me.
After unsetting continuousSpellCheckingEnabled clean your build folder and run again. Seems as though it is holding onto the setting between builds (quite surprisingly!). Your observation that changing the property name solved the issue led me to this solution -- still an issue almost five years after you asked.
Related
Everything I have found, every one says this cant be done.
I studied in fullsail university and they taught me how to do this so I know without a doubt it can be done. No one just knows how and assumes it can't.
Basically, when in XCode-story board, I would add constraints to a view and everything is all blue and perfect. From there, if you click, hold a drag, the view to another position then all of the constraints will turn orange. (Not RED because the constraints are still good it just simply needs to snap back into place..)
When in school my teacher taught me a quick key short cut that you press and everything snaps back into place and its all blue again. It has been a while since I have coded and i am just now getting back into it again and i just cant remember what that shortcut was.
I hope someone out there knows how to do this. Maybe any fullsail graduates?
Your responses are greatly appreciated.
I figured it out.
option + CMND + '='
What you're looking to do is referred to as "Update(ing) Frames."
The quick command is indeed option-command-equals
The command can also be reached from the bottom menu of a storyboard.
This link may change in the future but check out the Auto Layout Guide. Specifically reference the "Resolve Auto Layout Issues Tool" section.
I'm facing a problem with this 2 ScrollBox, one is TVertScrollBox which display whole screen and it have a THorzScrollBox in it, my problem is if i want to touch to the HorzScrollbox item and move up and down, my VertScrollBox have to scroll same as. Are there any ways to solve this issue? Thanks in advance
//Edit 1 : I'm using a gesture and ScrollBy(x,y) function to do with this issue. But it seem a bit laggy(not smooth) and still the HorzitonScrollBox scroll it own. A image for this(http://i.imgur.com/weOqW0R.gifv). Still watting another solution to do this
You can do it using UICollectionView as given in below example project.
http://damir.me/implementing-uicollectionview-layout
Source code link: http://bascarsija.s3.amazonaws.com/CollectionView.zip
After downloading this source code, In build settings change the value of the "Compiler for C/C++/Objective-C" to Default Compiler and run the app.
OK, I have found a simple answer.
When you have a THorzScrollBox inside of a TVertScrollBox, set THorzScrollBox.Touch.InteractiveGestures.Pan to False.
Assume you've selected an object and you have the Size Selector in the Utilities panel open. You can see the list of constraints applied to the object. In the list of constraints you could click on the little gear and pick delete. You can't in Xcode 6.
There are still several ways to delete constraints in IB:
Find the constraint in the Document Outline and delete it that way (but it can be hard to find).
Click on the little bar in the storyboard and delete it that way (which can be hard to click on).
Double click on the constraint in the Size Selector which will open Attribute Inspector and highlight the constraint in the Document Outline. This can be a nuisance when you want to delete several.
Still, I miss ease of use of the gear delete feature and I'm wondering if it's still there in a similar fashion and I just can find it. While the other ways work, I find myself wasting lots of time especially when playing with the new Size Classes feature. So, find a easier way to delete them?
In Xcode6 (Beta5) when I click on a particular constraint in the Size inspector, it acquires a thin blue border. The constraint can then be deleted using the backspace.
The accepted answer is right, but there is so much frustration with selecting constraints that lay outside of selected view that I decided to add this tips as another answer.
I found incredible list of tips that helped me to solve this problem.
The problem:
You select the view and Xcode shows related constraints.
You try to choose the one that is outside of selected view.
You fail (end with selecting the view beneath the constraint)
Soulution:
Click it with Shift+Ctrl pressed and you'll see a menu of all the views that exist where you've clicked.
To delete selected constraint press delete key.
The selected answer is incomplete. When you delete the constraint from the Size Inspector, you are leaving behind the constraint object in the Document Outline pane. It is greyed out, meaning it is not used, but still exists and, what's worse, will affect auto layout with errors, warnings or conflicting constraints and you will go crazy until you also delete them from the Document Outline pane.
So:
1. Delete the constraint from the Size Inspector as in the accepted answer
2. Delete any greyed out constraints from the Document Outline
Live a happy, constraint-free life.
This answer from #wayne chi is the simplest, and spares you from hunting down constraints in Document Outline:
Double click the grayed out constraint (switches focus to the constraint) then press delete. This will delete the constraint.
Sometimes, the easiest way is to close the file in Xcode and edit it with a text editor. :-/
If you want to delete ALL constraints from a viewController simply turn off auto layout and then reenable it (or don't) and all of the constraints will be gone.
I can't be the only one that finds Xcode's method of "pointing out" where your mistakes are - ridiculous. As helpful and essential as the feature is.. it does not help to make the line I need to fix virtually impossible to read or edit... let alone see...
And don't get me started on the constant struggle to find a "selection" color that is visible, yet retains one's sanity/ability to see what the selected text actually IS!
What am I missing here? I know how to futz with the colors in xCode, I know how to mess with the Appearance "Control Panel", but it all just results in different configurations - of varying aesthetic quality - that are all hard to read... I don't have this issue in TextMate... Is that my answer?
UPDATE: Thanks to the brilliant work, and answer by #amadillu, here is what the remarkably more usable Xcode looks like after installing his Xcode 4 "Fix-Ins"
I've made an Xcode Plugin by using davekeck's "fixins" that allows you to customize the colors of the inline error and warning messages. This really helps if you use a dark scheme / background . See here.
I have two basic practical problems:
1) The first one is really stupid. I receive a message saying: "Method definition for 'aIncreasedSelection' not found, together with an "Incomplete Implementation".
Well, that is quite strange, because I don't have this method in neither my .m or .h file (and the class name is mentioned in the remark).
I used to implement this method, but I deleted it because it was redundant. In a certain way, it appears as if my Xcode project can't let go of the method...
2) The second question is also a very mysterious one. I have a couple of viewControllers in which I have put the identical same background, and the identical same buttons. It's really identical in size and position in the screen as well (I defined the pixels). For an unknown reason, when I switch between the views, one of the buttons changes very slightly its color (it is a Photoshop created button with mirror effect on the bottom, it's the mirror that becomes lighter). That is really annoying because it's supposed to be identical; when the user switches views now, he can see that there is a color difference in the button (supposed to be planted as a button in a dock, which should be identical over the entire app)...
Very frustrating as I cannot solve these small mistakes... Any ideas? Thanks!
Regarding your first problem, if you have verified that it no longer exists in your .h or .m file, try to cmd+shift+k and clean your project, then rebuild. This should update everything and in theory solve that issue for you.
As for the second problem, it sounds strange indeed. Is there any chance you could provide pictures somehow? Are you statically loading the image into similar buttons, or are you doing something differently?
Re - opening my project solved my first problem (unlike the refresh - cmd + shift + k, which didn't work). The color problem is not solved despite :-/
It was definitely a bug since I didn't change anything. It is in fact - very confusing!