pokeyman posted:

Cookies shouldn't be cleared between builds, so I'm not sure what that's about.

That said, you can grab the cookies from NSHTTPCookieStorage, grab their properties dictionary, and save that. Then you can deserialize them as needed.

DreadCthulhu posted:

Any recommendations for really cheap/free but still effective analytics services? I like the Mixpanel UX, but it gets really expensive really fast. They insist you only track a couple of events, but at my app's really early evolution stage I need to know everything about it.

Doh004 posted:

That doesn't want to work.

I've been reading up, and the cookie we're returning doesn't have an expiration. So I tried setting that manually as supposedly if it doesn't have an expiration it gets destroyed after the session is over (ie the app restarts). However, that doesn't seem to work. When I restart the app (via command + r), there are no cookies.

*edit* Hmm, expiresDate isn't being set when I create the new cookie!

code:

NSDate *tomorrow = [NSDate dateTomorrow];
NSMutableDictionary *properties = [[NSMutableDictionary alloc] initWithDictionary:cookie.properties ];
[properties setObject:tomorrow  forKey:NSHTTPCookieExpires];
NSHTTPCookie *newCookie = [NSHTTPCookie cookieWithProperties:properties];

lord funk posted:

Is there any way to stop autocomplete guessing objects that I have never even used?

UIColor *aColor = [UICollectionElementCategoryCell

THANKS AUTOCOMPLETE THAT'LL DO

Hog Obituary posted:

heh http://www.textfromxcode.com/post/24542673087

I thought the latest Xcode (4.5-ish?) was supposed to be better about that. What version are you on?

lord funk posted:

Is there any way to stop autocomplete guessing objects that I have never even used?

UIColor *aColor = [UICollectionElementCategoryCell

THANKS AUTOCOMPLETE THAT'LL DO

Hog Obituary posted:

heh http://www.textfromxcode.com/post/24542673087

I thought the latest Xcode (4.5-ish?) was supposed to be better about that. What version are you on?

Hog Obituary posted:

Why does Xcode change around my xib files under the covers when all I did was click on an element? (i.e. this)

_{I don't actually expect a real answer.}

edit, well I guess I got one: http://stackoverflow.com/questions/5900245/how-to-avoid-xcode-4s-gratuitous-edits-to-xib-files

lord funk posted:

ManicJason posted:

edit: The easiest way to avoid constantly changing xibs by accident is to manually touch every single xib in Xcode whenever a new Xcode build is installed, then commit all of the phantom changes at once. It never seems to happen more than once per Xcode version per file.

Doc Block posted:

XIBs store the version of IB they were built with. Opening them in a newer version of Xcode updates this, hence the phantom change.

duck pond posted:

Unrelated, I'm trying to do a thing where I subclass UIBezierPath so i can tack a bunch of wacky methods onto it, and I'm having some trouble doing so as it doesn't have any initialisation methods.

in VOBezierPath.h:

code:

@interface VOBezierPath : UIBezierPath
{
    VOBezierPathState state;
}

@property (nonatomic) VOBezierPathState state;

- (id)initWithPoint:(CGPoint)endPoint;

and in VOBezierPath.m:

code:

- (id)initWithPoint:(CGPoint)endPoint
{
    VOBezierPath *path = [super bezierPath];
    if (path) {
        path.state = VOBezierPathNew;
    }
    return path;
}

and I get the warning: No visible @interface for 'UIBezierPath' declares the selector 'bezierPath'.
Even tried VOBezierPath *path = (VOBezierPath *)[super bezierPath]; with no luck.

duck pond posted:

i just wanna say i had this idea for a popover numpad just the other day

HiriseSoftware posted:

I have an iOS app project that has a dependency on a static library project (this is Xcode 4.4). Everything compiles, links and deploys to a device just fine when I go from a clean build, but the problem I have is that if I want to make a change to one of the static library's sources (and not any of the app sources) and then run, it compiles but doesn't deploy to the device again. In order for my changes to deploy, I have go from a clean build. Is there some sort of build setting that I'm not seeing that would allow this to happen? I have "Skip Install" set to No for both the library and app (I do have it set to "Yes" for the app in my Distribution build though). My app project's linker flags are "-ObjC -l<static library>"

If I can get this figured out, there'll be no more compile coffee breaks for me! Actually it's not terribly long it's just still a productivity bottleneck.

Ender.uNF posted:

Uhhh... You certainly can't initialize that way. You are creating a new auto released instance of bezierPath, unrelated to the actual storage alloc created for your subclass. That's a guaranteed path to leakytown if nothing else, plus the storage super created wont be big enough to hold any of your properties so its going to crash sooner or later.

Super has an init method, you should be calling it. I bet if you checked UIBezierPath's super chain you would find the designated initializer in there somewhere.

lord funk posted:

4.5.1. I think when they announced that it was better was exactly when it stopped being nice to me.

Ender.uNF posted:

Anyone have some guides, videos, etc for Mac development, but oriented toward iOS developers? I have only the vaguest grasp of AppKit development and my understanding is that it sucks compared to UIKit.

I know there are plenty of resources for someone trying to learn Mac development, but I just want one that focuses on stuff like "in UIKit you have the App delegate, in AppKit you have X" or "in UIKit, you use storyboards like X, in AppKit use Y or Z instead".

Doc Block posted:

You shouldn't have to manually add them in the linker flags. Add their xcode projects as dependencies, then go into your app target's build settings under the Build Phases tab, and add the libraries in the Link Phase.

That way changing the library sources will also cause your app to be relinked.

pokeyman posted:

That's hardly the only thing that changes seemingly arbitrarily.

What I don't get is why does Xcode re-serialize the nibs and storyboards when you open them? It's one thing if I make a change and Xcode goes "oh hey, while I'm saving this, I'ma bump the version number", or "I'm opening all these nibs and I need to migrate them to the new version". It's the one at a time, only when you open it that strikes me as weird.

At least there's been progress. There used to only be straight-up binary nibs, which were entirely un-diffable. Now it's possible to see the phantom changes, if not do anything about them.

Lando2 posted:

he listed estimated completion at 6 months though, which sucks.