Let’s say you want to configure some parts of your view rendering directly in your storyboards. Fortunately you can by using @IBInspectable.
|
1 2 |
@IBInspectable var radius: CGFloat = 0 @IBInspectable var strokeColor: UIColor = UIColor.black() |
Here is the project ( Xcode 8, Swift 3) if you want to try it : IBInspectableDemo
That’s it folks, have a good day !
MAB
I recently had a problem with a yellow label on a dynamic background that can sometimes also be yellow. The two common solutions are
NSAttributedString offers everything you need to do it.
|
1 2 3 4 5 6 7 8 9 10 |
var outlinedLabel = UILabel(frame: CGRect(x: 0, y: 0, width: 300, height: 50)) let strokeTextAttributes = [ NSStrokeColorAttributeName : UIColor.blackColor(), NSForegroundColorAttributeName : UIColor.lightGrayColor(), NSStrokeWidthAttributeName : -4.0, NSFontAttributeName : UIFont.boldSystemFontOfSize(52) ] outlinedLabel.attributedText = NSAttributedString(string: "Outlined", attributes: strokeTextAttributes) |
Note that the stroke width attribute is a negative value.
|
1 |
NSStrokeWidthAttributeName : -4.0 |
This is to tell the drawing engine it is a “Stroke & Fill” operation. Otherwise it’ll just ignore the “NSForegroundColorAttributeName” and leave the text transparent like this :
Link to the playground : MABDev.OutlinedText.playground
Documentation : https://developer.apple.com/library/mac/qa/qa1531/_index.html
Cheers,
MAB
Here is one of my favorite extension I created for Array. Very useful shortcut when you use abstraction ( as you should ) and you want to create an array from another one.
Instantiate an Array of type A with an another array of type ( or protocol ) B and fills it with elements from B that can be cast to A.
|
1 2 3 4 5 6 7 8 9 |
init<T>(_ array:[T]) { self.init() for element in array { if let cast_element = element as? Element { self.append(cast_element) } } } |
You could always use .filter but it would take way more lines. I often use it to get a specific subview in my view hierarchy. Here’s the link to the playground file.
MABDev.ArrayExtension.playground
That’s it for today folks ! See you soon. MAB.
So you are working on a UICollectionView and you have to call “reloadData()” a few times in a row because you have data coming in. I know it would be better to insert items or at least reload the section but sometimes for good or bad reasons, like custom layout manager and iOS 9, it’s not always possible. And it’s not the point here anyway. The point is I recently had a problem with my UIImageView flashing like crazy overtime I call “reloadData()” . I found out in your “prepareForReuse()” implementation, rather than setting you imageView.image = nil you’re better off doing imageView.hidden = true and unhide it later when you need to set it again in “cellForItemAtIndexPath”.
|
1 2 3 4 5 |
override func prepareForReuse() { self.titleButton.setTitle(nil, forState: .Normal) <del>self.logoView.image = nil</del> // Causes flashing self.logoView.hidden = true // OK } |
Not much but I thought it could interest some of you guys. Cheers !
Edit: It might not be the best solution after all. It behave poorly in bad / slow network conditions.
