Building my raft @jdizzle925 - Tumblr Blog

problem with insertItemsAtIndexPaths

I started to implemented pagination in my collection view today. I fetched the objects from parse and tried calling insertItemsAtIndexPaths() and blame!, i get an assertion failure... Error: * Assertion failure in -[UICollectionView _endItemAnimations], /SourceCache/UIKit/UIKit-2903.2/UICollectionView.m:3716 It turns out, the assertion error didn't provide enough details. I implemented @try { [self.collectionView insertItemsAtIndexPaths:indexPaths]; } @catch (NSException *except) { NSLog(@"DEBUG: failure to insertItemsAtIndexPaths. %@", except.description); } And sure enough, I found a simple indexing error when building indexPaths for the new objects.

#uicollectionview #insertItemsAtIndexPaths xcode

Compass complains about $orangelightcolor

$compass watch // then I got all define errors Inserted the lines below in all my sass files @import "compass/reset"; @import "compass/css3"; Error went away // to force rebels of my css files $compass compile -e production --force

#compass sass partials force compile

initWithCoder vs initWIthStyle

So the sample code I have had the tableview dequeue a cell which I had originally laid out using the storyboard. The problem is, the sample code didn't use storyboards and implemented a initWithStyle method which included a lot of setup code for the cell (size of view, buttons, background color, etc.). It confused me for a while how dequeue always ended up with a cell, and thus never calling the [cell initWithStyle] method inside if(cell == nil). To get it to work, I had to reuse initWIthCoder from another object. But then I realized my prototype cell in the storyboard was getting instantiated using initWithCoder, thus initWithStyle never being called. So after deleting my prototype cell, (cell ==nil) after dequeue and initWithStyle gets called. Got rid of the prototype cell and initWIthCoder code. Back to running using initWithStyle...

#initWIthCoder initWithStyle tableview cell dequeue prototype storyboard

BOOL is not an objective-C object

// dont use po as it will return nil. Use p in the debugger instead (lldb) p self.hasActivityImage (BOOL) $0 = NO

#bool debugger print output nil

set a view's background color using an image

[self.mainView setBackgroundColor:[UIColor colorWithPatternImage:[UIImage imageNamed:@"BackgroundNewActivity.png"]]];

How to detect when a textfield changes

First add a target to the textfield [self.joogPriceTextField addTarget:self action:@selector(priceFieldDidChange:) forControlEvents:UIControlEventEditingChanged]; Then add the handler function - (void)priceFieldDidChange:(UITextField *)priceTextField { NSLog(@"Price field is changing!"); }

Still struggled with the armv7s compile error. In the end, I got rid of it by removing $ARCHS_STANDARD_32_BIT and adding armv7. Also set "Build Valid Architectures Only" to YES and "Valid Architectures" to armv7. Now the project is compiling again...

Got rid of armv7s from Valid Architectures too to get rid of the compiler error.

#armv7s compiler error

I kept getting compiler errors related to armv7. Setting "Build Active Architecture Only" to YES solved the problem.

#armv7 compiler ios xcode error

Resolving FFI issues

Set Finder to display hidden files

install and use unrar from command line

Conquering the unknown

A wise man once told me, to do a startup, you must be willing and able to conquer the unknown. This week I'm taking over front-end development for the Moments project. I have one day to ramp up my knowledge of JS and 3 days to finish a working prototype of the app for demo.

Passion + Vision = VISSION

Anyone can build and run a company but great leaders are rare. The world is filled with smart and capable people but a little more than a handful can build and run powerful companies that endure the tests of time. So what makes a great leader? There are long lists out there, but to me great leaders are characterized by both PASSION and VISION. Their passion is so deep, listening to them speak can send chills down your spine. And their vision is so clear, but ordinary people see them as lunatics. Their mere presence can rock your core. My favorite example is Steve Jobs--the beloved tyrant of Silicon Valley. Over the years, and maybe even from the very beginning, he never saw Apple as just another computer company. No, he saw Apple as a company destined to change people's lives. He was so passionate about this idea, he distorted the real world around him and convinced people to drink Apple's proverbial Kool-Aide. Lots of it and it is freaking amazing. Steve's Reality Distortion Field is not made up folks. It really existed. So why is Steve Jobs a great leader? There is not a better testament than the success of the company he built and ran even to very last breath. Apple has dominated a global gadget market where the choices are plenty and the buyers are super picky. How did it get there and what makes Apple employees so much smarter and capable? Maybe, if not more than likely, because of a CEO who was forged by passion and vision. He just saw something other couldn't see and he pursued it relentlessly to the end. People who follow Steve Jobs were inspired to build great things. Thus the smartphones, tablets, and ultra-thin laptops we enjoy today... At Angelhack this past weekend, I met a lot of VERY smart and capable people. There we celebrated our desire to become a great CEOs but yet very few showed the required VISSION--at least not yet. Yes it takes time, and what may not be there today could flare up tomorrow. I see it is a quality that is programmed in some people's DNA and triggered uncontrollably like cancer. If only we can buy it like and give it away to the food people for Christmas then maybe, just maybe, our world would be a much better place.

One of the things that always annoyed me about Xcode that it was packed with tons of feature. So much that little things like figuring out which current branch you are working on is easy to miss. So I created a picture to remind myself moving forward.

Telling your view to dismiss the keyboard

There are times when one of your controllers fire up and you want to get rid of the keyboard. The one liner below provides a quick and dirty solution. // Tell the view to dissmiss keyboard [[self view] endEditing:YES];

#dismiss keyboard

Clean and ready for the ride tomorrow morning... (Taken with Instagram)

Trending Blogs

Recently Viewed Blogs

Building my raft