Doh004 posted:

I was under the impression that dequeueReusableCellWithIdentifier:forIndexPath: no longer returned nil, and the checking for nil was just old, leftover practices?

ManicJason posted:

I thought the method with forIndexPath throws an exception if there is no table cell type registered, but the old dequeue method without specifying an index path returns nil if no cell type is registered.

Doc Block posted:

It's not "hard" in the sense that it's no more difficult than creating any other custom view, but in my apps the standard table view cell styles have been perfectly adequate.

Which brings me back to my question: if we aren't supposed to use the old methods that might return nil (the ones that don't require the use of a custom cell that you've already registered), how are we supposed to specify which of the built-in cell styles we want?

Mikey-San posted:

Eschaton might know a simple way to reinstall those pages, but if you have a Time Machine backup, you could do a quick restore of that stuff:

code:

sudo tmutil restore <snapshot_path>/<that_disk>/usr/share/man/man2 /usr/share/man/man2

pliable posted:

Ah that's a good idea...though I haven't done a Time Machine back up in nearly 2 years, haha. My Mac isn't really my primary system anymore.

And, who/what is Eschaton? Google points me to some blog or something?

eschaton posted:

Eschaton is another goon, hi.

I think those man pages are installed as part of the command-line tools, install the latest Xcode command line tools package and you might get them back.

pokeyman posted:

There are some changes to default UIView animations. I don't think that's what you're running in to but I thought I'd mention it anyway. Session 236 has the details.

Kallikrates posted:

If a view already has a non-identity transform I thought the way to apply an additional transform was to construct one with

code:

CGAffineTransformTranslate(self.imageView.transform, 100, 0)

Walked posted:

So I'm trying to get a grasp on pointers in Objective-C and I'm just getting entirely thrown off by passing an NSString as an argument.

code:

@implementation Test
-(void) testMessage(NSString*) s
{
	NSLog(@"%@", s);


}

Why does this work? I would think that since s is an argument that's an NSString* it would need to be dereferenced to get a value out of it? No?
I know this is a really dumb question but I've not dealt with pointers and all my background is in C#/python, so I'm actually trying to understand whats happening here.

I've come across a ton of tutorials that basically cover this secnario:

code:

int *ptr;
int val = 1;
ptr = &val;
 
// print out dereferenced values
printf("dereference *ptr = %d\n", *ptr);
printf("dereference address of val *(&val) = %d\n", *(&val));

But that doesnt cover passing the (NSString *) and why I can simply reference s rather than *s in this case.

Not sure if that makes sense and I may need to take a break, reset, and re-read, but maybe something rather simple if off in my understanding here.

Walked posted:

So I'm trying to get a grasp on pointers in Objective-C and I'm just getting entirely thrown off by passing an NSString as an argument.

code:

@implementation Test
-(void) testMessage(NSString*) s
{
	NSLog(@"%@", s);


}

Why does this work? I would think that since s is an argument that's an NSString* it would need to be dereferenced to get a value out of it? No?
I know this is a really dumb question but I've not dealt with pointers and all my background is in C#/python, so I'm actually trying to understand whats happening here.

I've come across a ton of tutorials that basically cover this secnario:

code:

int *ptr;
int val = 1;
ptr = &val;
 
// print out dereferenced values
printf("dereference *ptr = %d\n", *ptr);
printf("dereference address of val *(&val) = %d\n", *(&val));

But that doesnt cover passing the (NSString *) and why I can simply reference s rather than *s in this case.

Not sure if that makes sense and I may need to take a break, reset, and re-read, but maybe something rather simple if off in my understanding here.

Walked posted:

So I'm trying to get a grasp on pointers in Objective-C and I'm just getting entirely thrown off by passing an NSString as an argument.

code:

@implementation Test
-(void) testMessage(NSString*) s
{
	NSLog(@"%@", s);


}

Why does this work? I would think that since s is an argument that's an NSString* it would need to be dereferenced to get a value out of it? No?
I know this is a really dumb question but I've not dealt with pointers and all my background is in C#/python, so I'm actually trying to understand whats happening here.

I've come across a ton of tutorials that basically cover this secnario:

code:

int *ptr;
int val = 1;
ptr = &val;
 
// print out dereferenced values
printf("dereference *ptr = %d\n", *ptr);
printf("dereference address of val *(&val) = %d\n", *(&val));

But that doesnt cover passing the (NSString *) and why I can simply reference s rather than *s in this case.

Not sure if that makes sense and I may need to take a break, reset, and re-read, but maybe something rather simple if off in my understanding here.

pokeyman posted:

How does this work

C code:

const char *s = "I am a C string";
printf("pointer %p points to %s", s, s);

? I can simply reference s rather than *s.

Walked posted:

This is really helpful. I assume that the %@ in the NSLog is the same principle? Still wrapping my head around it but that example is exceedingly helpful.

edit: And yes that was a typo to leave out the colon; transcription error between two computers

pokeyman posted:

There are some changes to default UIView animations. I don't think that's what you're running in to but I thought I'd mention it anyway. Session 236 has the details.

Walked posted:

So I'm trying to get a grasp on pointers in Objective-C and I'm just getting entirely thrown off by passing an NSString as an argument.

code:

@implementation Test
-(void) testMessage(NSString*) s
{
	NSLog(@"%@", s);


}

Why does this work? I would think that since s is an argument that's an NSString* it would need to be dereferenced to get a value out of it? No?
I know this is a really dumb question but I've not dealt with pointers and all my background is in C#/python, so I'm actually trying to understand whats happening here.

quote:

I've come across a ton of tutorials that basically cover this secnario:

code:

int *ptr;
int val = 1;
ptr = &val;
 
// print out dereferenced values
printf("dereference *ptr = %d\n", *ptr);
printf("dereference address of val *(&val) = %d\n", *(&val));

But that doesnt cover passing the (NSString *) and why I can simply reference s rather than *s in this case.

Not sure if that makes sense and I may need to take a break, reset, and re-read, but maybe something rather simple if off in my understanding here.

Doc Block posted:

Just wanna say that PaintCode is awesome. No more having to create a bunch of variations of the same toolbar icons and such. Gonna have to see about finding the best way to make it work with different image sizes due to different size classes and whatnot, but still.

It's a vector drawing app, except it can export your drawings as Core Graphics draw calls in Objective-C, Swift, and C#, both for iOS and OS X.

Doctor w-rw-rw- posted:

You can set the matrix such that you can scale the coordinates to whatever size you wish. I did this (also tried PaintCode, it's pretty okay, but I preferred to rewrite it a little). I'll pull the code up later tonight - remind me via PM?

Excerpt:

Objective-C code:

+ (UIImage *)foobarIconWithSize:(CGSize)size
    UIGraphicsBeginImageContextWithOptions(size, NO, 0.0);

    // Scale to 80x80 coordinate space
    CGContextScaleCTM(UIGraphicsGetCurrentContext(), size.width / 80.0, size.height / 80.0);

    // all that drawing jazz

    UIImage *image = UIGraphicsGetImageFromCurrentImageContext();
    UIGraphicsEndImageContext();
    return image;

Come to think of it, you probably want to change that CGContextScaleCTM to account for screen scale. You can also run this on a background thread, btw, because UIImage is (as far as I know) threadsafe since it doesn't deal with views or have state.

UIGraphicsGetImageFromCurrentImageContext

This function may be called from any thread of your app.

pokeyman posted:

I think screen scale is handled by the third parameter of UIGraphicsBeginImageContextWithOptions isn't it? Assuming main screen.

pokeyman posted:

edit: CocoaPods is so frustrating. Presumably for the people who work on it too.

Doctor w-rw-rw- posted:

Agreed. My coworker is one of the CocoaPods devs. What about it is frustrating? I can pass it on.

Doctor w-rw-rw- posted:

Oh yeah, when I say rewrite, I mean extracting things into constants, and using core graphics calls instead of UIBezierCurve. But that's just because I'm a neckbeard and like C APIs. Also, see above edit.

Doc Block posted:

I don't know how long it's been since you used PaintCode, but now they have this thing they introduced in PaintCode 2 called StyleKit, where you can have drawing colors and such be split off so that you can change them for all your images at once. So it's like having that stuff broken out into constants, but also works in the PaintCode UI. (I'm not a big fan of modifying generated code).

pokeyman posted:

I long for a pseudo-fork of CocoaPods that does away with workspaces and static libraries and instead just downloads some code and wires it into your target(s).