lord funk posted:

Do multiple UITableViews with the same view classes registered for reuse all pull from the same reusable view pool, or do they each create and pull from their own? If the latter, can they be told to pull from the same pool?

edit: seems like they are separate per instance. That sucks.

Doctor w-rw-rw- posted:

They pull from the same reuse identifier. If you want to reuse the same cells, you have to make the cells themselves configurable for those different modes. That said, hiding a view takes it out of the render tree, so if you're doing a ton of reuse it might be worth it to amortize the really expensive cost of instantiating and adding the views in each cell for all of its states, and hide/unhide as needed.

That, or aggressively bug the AsyncDisplayKit people to open-source their sliding range stuff (not private info; discussed at NSLondon, publicly streamed), which should be particularly useful for smooth tableview operation.

Manic Mongoose posted:

I'm trying to get Game Center working on my simple game and I've been going through Ray Wenderlich's tutorial. So far I'm able to have a person login and authenticate, however I'm unsure how to pull up the gameViewController which I assume holds the matchmaking view.

In his tutorial he has a storyboard that navigates from the navigationcontroller -> gameviewcontroller

However for my sprite kit game, I have no storyboard, and it goes defaultViewController -> firstscene.

I have the code that would you call in the navigationcontroller on the defaultViewController that loads first. After logging in Game Center it transitions to the first scene. However I'm unsure where to or how to transition to the gameViewController (which was a class that I had to create) to start the match making.

http://www.raywenderlich.com/60980/game-center-tutorial-how-to-make-a-simple-multiplayer-game-with-sprite-kit-part-1

This is what I'm following.

Any help would be great!

Doctor w-rw-rw- posted:

That, or aggressively bug the AsyncDisplayKit people to open-source their sliding range stuff (not private info; discussed at NSLondon, publicly streamed), which should be particularly useful for smooth tableview operation.

ultramiraculous posted:

For whoever else cares: http://new.livestream.com/nslondon/anniversary/videos/57840338

I've been eating up this AsyncDisplayKit stuff.

Flobbster posted:

Wtf, Apple

Flobbster posted:

I just spent a couple days on the dumbest loving UICollectionView issue. I have a collection view with a custom layout that displays its contents in a horizontally paged grid. Depending on the number of elements in the whole thing, there might be blank space left over on the last page.

Did you know that if you have a collection view with backgroundColor set to [UIColor clearColor], touching the blank area to start scrolling doesn't work? Only if you touch one of the cells. Likewise, setting a backgroundView with a clear background color causes the same problem.

However, setting the background color to have alpha 0.01 causes scrolling to work again when touching in the empty area.

Wtf, Apple

Flobbster posted:

I just spent a couple days on the dumbest loving UICollectionView issue. I have a collection view with a custom layout that displays its contents in a horizontally paged grid. Depending on the number of elements in the whole thing, there might be blank space left over on the last page.

Did you know that if you have a collection view with backgroundColor set to [UIColor clearColor], touching the blank area to start scrolling doesn't work? Only if you touch one of the cells. Likewise, setting a backgroundView with a clear background color causes the same problem.

However, setting the background color to have alpha 0.01 causes scrolling to work again when touching in the empty area.

Wtf, Apple

This method ignores view objects that are hidden, that have disabled user interactions, or have an alpha level less than 0.01.

Subjunctive posted:

I think it's pretty crappy to tie presentation to event processing, as an API choice. It's not hard to have the owner specify that they want the view to be hit-transparent, and way clearer for that to be the case. It's nice that it's documented (though AFAIK not near the places that control alpha-I-mean-alpha-and-event-targeting), but that's sort of a blame-the-user thing. Too much magic.

Doctor w-rw-rw- posted:

Yeah, I forgot about the alpha-hit-test stuff. It does come in handy, though, when animating things nontrivially from hidden to not hidden or vice versa. I imagine that hits some unhappy corner cases when animating alpha using additive animations - it probably gets tricky to figure out when to call completion blocks and set hidden = YES or NO.

pokeyman posted:

Animating views sets their userInteractionEnabled to NO by default, so that isn't really helped by hit testing considering transparency, but of course everything you mention comes into play when keeping interaction enabled during animation.

Flobbster posted:

Thanks, I'll look into that -- it looks like UIFontDescriptorCharacterSetAttribute and matchingFontDescriptors... do what I need.

When I said that I didn't want to iterate over all the fonts in the system, I meant that I was hoping to take advantage of whatever tables the OS might have already built internally, instead of iterating over the fonts myself. I think this will do the trick.

Ender.uNF posted:

Are you drawing to the center point of each pixel (x+0.5) or directly on it? My first guess is maybe interpolation artifacts.

Another wild guess, but you could also try drawing to your own backing buffer of fixed resolution then scaling for display to get deterministic behavior. If the display is scaled, are you doing the scaling or is the OS? I wonder if the draw commands are being scaled before drawing (rather than scaling the resulting bitmap). In theory scaling the draw commands would yield better results but I can see that producing some jitter if you're trying to do sub-pixel precise overdraw.

I'm not an expert on this stuff though, so YMMV.

Ninja Rope posted:

Thanks for the help. I was not drawing the center of the pixel. I decided to try drawing into my own buffer as you suggested and then displaying that to the screen and that seems to fix the problem. I started with:

code:

    nsImage = [[NSBitmapImageRep alloc] initWithBitmapDataPlanes:NULL pixelsWide:screenWidth
                                        pixelsHigh:screenHeight bitsPerSample:8 samplesPerPixel:4
                                        hasAlpha:YES isPlanar:NO colorSpaceName:NSCalibratedRGBColorSpace
                                        bitmapFormat:NSAlphaFirstBitmapFormat bytesPerRow:0
                                        bitsPerPixel:32];
    unsigned char *imageData = [nsImage bitmapData];

And then every frame I'd draw new stuff into imageData and then display it:

code:

    NSRect imageRect = NSMakeRect(0, 0, screenWidth, screenHeight);
    [nsImage drawInRect:imageRect];

This works just fine but only for the first frame of animation, it never draws the rest of the frames. Is there something about re-using an NSBitmapImageRep after calling drawInRect that won't work? Can I not just keep updating the buffer returned by bitmapData and calling drawInRect over and over?

The only way I could get it to work is by malloc'ing a persistent buffer I draw into and then creating a new NSBitmapImageRep every frame (with initWithBitmapDataPlanes:NULL because passing my buffer directly causes a crash) and then memcpy my buffer into the one returned by [nsImage bitmapData] for every frame. I'm sure the format of my data is correct because the memcpy method works, so it must be something with how I'm creating or re-using the NSBitmapImageRep.

Ender.uNF posted:

I would have created it with CGImageCreate or CGBitmapContextCreate which is supposed to support modifying the bitmap data via the pointer from CGBitmapContextGetData. I haven't fooled around with Core Graphics drawing in a little while though so someone who has done it more recently would probably have better advice.

Lumpy posted:

code:

K3A73NATW3MW

Lumpy posted:

code:

LXXL7J33AY7P

Doctor w-rw-rw- posted:

Lumpy posted:

Thanks for the feedback! We are having to rush out a fix for some Game Center stuff (it never showed up in testing, honest!) so I will try and sneak in some changes as well based on your suggestions. I was originally going to have the Ready pulse, but every person we had test (including a bunch of 6 year-olds) immediately tapped on it, so I left that out. Certainly wouldn't hurt to add it though!

Lumpy posted:

As for technology, we used the Pop library for animations, and uh, probably some other stuff . I tried hard to *not* code too much on this one, although I did the UI animations and some other bits and pieces. Lessons learned we many, but mostly from a working relationship perspective with my partner on the app.

Lumpy posted:

7LRAPYYMMFYR

Doctor w-rw-rw- posted:

Hmm, good datapoint. Add a 5-second delay before it starts pulsing.

I had a feeling you used pop. Overall, very well-done!

Lumpy posted:

Issues w/ game center is fixed, Ready pulses, and I think I might try my luck at an expedited review.

wwb posted:

Is anyone successfully using CI to build / package release iOS apps? It seems that apple makes it loving impossible. If you are please share any good, recent guides on how you get there.

Lumpy posted:

I used 4.5


Issues w/ game center is fixed, Ready pulses, and I think I might try my luck at an expedited review.

ultramiraculous posted:

Hey, so one bug is you preempt music that's playing on the device. Just starting the app cuts off playback, and your sounds will pause/unpause music. You should be using a different AVAudioSession category like AVAudioSessionCategoryAmbient.

Also seconding reset button somewhere.

Lumpy posted:

What would 'reset' do? Remove the operands, or switch to a new puzzle (in Endless mode)?