This does the same thing as a previous post about Swift doing a sort on two dimensions.
https://github.com/mevdev/Two_Dimensional_Sorting_Java
I made this one java file within inline classes to simplify the running of it. It’s really too bad there isn’t something like Playgrounds for Java and Android.
This playground shows sorting of an array of objects by both the name alphabetically and also by a bool.
This showcases Comparator and how it can be used to sort arrays multidimensionally.
https://github.com/mevdev/2d_Sorting_Swift
This was a project of passion and I am happy to say that it is available for Apple Watch.
I made a port of the Apple Sample ‘Sprite Tour’ for iOS (iPhone & iPad). It basically takes the code in the mac delegate file and encapsulates it into an iOS View Controller.
Find it on my github:
https://github.com/mevdev/SpriteTouriOS
NSPredicate is the simplest way to do it.
Given Data like this:
NSArray *theArray = @[@{@"id":1,"name":@"one"},@{@"id":2,"name":@"two"},@{@"id":3,"name":@"three"}]; |
NSPredicate *p = [NSPredicate predicateWithFormat:@"id = 291"]; //fiber NSArray *matchedDicts = [theArray filteredArrayUsingPredicate:p]; |
There is much more to NSPredicate. I used exact matching, but matching with BEGINSWITH, CONTAINS, ENDSWITH, and LIKE. In some examples you’ll also see [c] or [cd] next to these keywords. The ‘c’ means it searches case insensitively and the ‘d’ means that an ‘o’ with an umlaut is still just an ‘o’.
NSString *asterixOnVar; NSString * asterixInAir; NSString* asterixOnTypdef; |
They all declare that it is a pointer to an NSString. There is no difference except readability. I prefer the first version because it shows the type and it is clear that the variable is a pointer.
There are three kinds of segues, push, modal and custom. You’ll probably most often use the ‘push’ method. It is incredibly useful in making storyboards do stuff.
Primarily there are two ways to invoke a segue. One is to rig up a button in Interface Builder that triggers a segue. The other is to invoke the segue on your own. I think that a lot of times I need to validate what’s on the screen before I can release it to the next controller. Therefore I need to do it myself.
Also you need to pass information back and forth, which will be taken care of by setting variables in the method:
-(void) prepareForSegue:(UIStoryBoardSegue *)segue sender:(id)sender { //... } |