ultrajoke - Latest Comments

Re: Premature Completion: An Embarrassing Problem

Brian Nickel — Sun, 21 Apr 2013 01:23:31 -0000

I'm a bit late but I believe the problem you were facing is that animated scrolling does not use CAAnimations, or if it does, not in the sense we're used to.

When a scroll view scrolls, animated or by touch, it fires off a bunch of scrollViewDidScroll: messages. This is critical in cases where you want an element fixed to the top of the scroll view, or in table views where they are constantly shuffling cells around. To do this, scroll views must be doing a sequence of scroll, evaluate, scroll, evaluate...

In the case of animated:NO, the scroll view is saying "scroll X pixels instantly", in the case of animated:YES, it is saying something like scroll 10px, in 0.02 seconds. This is what's tripping you up.

A general rule you could use is: if you don't layout in a scrollview delegate, use animated:NO. If you do, use animated:YES and listen for the appropriate scroll view didFinish events for your next action.

Re: Integrating Asana and Git

Vladimir Kovalskiy — Sun, 24 Mar 2013 16:47:29 -0000

Thanks a lot! That sounds reasonable.

Re: Integrating Asana and Git

foon — Sun, 24 Mar 2013 16:41:25 -0000

Good questions. I usually have Asana open anyway, so I do copy the ticket numbers from the URL. There are several advantages over just closing the ticket from there. One, I get the commit text automatically--so the ticket isn't just closed, but whoever reading it knows about the commit that closed it. Two, I get the commit hash as well--so I'll know where in history to look if it breaks again, or I can cherrypick fixes for a branch. Three, I tend to do a lot of intermediate checkins like "progress on X bug; references #1234566789". Once I've copied the ticket number for the first of these, the rest of the checkins are "free" as long as my git client can remember my last checkin message.

If you want to be able to select which tickets are closed from the command line, check out Bruno Costa's script, which is better suited to a non-gui environment.

Re: Integrating Asana and Git

Vladimir Kovalskiy — Sun, 24 Mar 2013 14:52:34 -0000

Thank a lot for sharing. But you are sampling ticket numbers as 1,2,3 when in real life they can not be remebered and should copy/pasted from the asana url. Cause they look like '4549660050096' And if you are opening ticket to get number, why not close it?

How do you overcome those terrible numbers issue?

Re: Mistakes Were Made: Description Isn’t Enough

Alistair Leszkiewicz — Thu, 14 Mar 2013 23:24:00 -0000

Nice post. The debugging link is broken, can now be found here (OSX) (http://developer.apple.com/lib... and (iOS) (http://developer.apple.com/lib...

Re: Quick Tip: Drawing Right Side Up With Core Text

Jerry Jones — Thu, 14 Mar 2013 11:26:03 -0000

If your lines are drawn in the wrong order, you'll want to apply a transform to your context, and not use the text matrix function. The second snippet of code should sort you out.

CGContextTranslateCTM(context, 0.0f, contextHeight);
CGContextScaleCTM(context, 1.0f, -1.0f);

Re: Quick Tip: Drawing Right Side Up With Core Text

Iosdevpt — Thu, 14 Mar 2013 08:56:59 -0000

Hi Jerry,

in the last screenshot my situation is the third square but i want my text to be like in the fourth square.
can you help me please?

Re: Premature Completion: An Embarrassing Problem

Josh Converse — Sun, 03 Feb 2013 03:23:39 -0000

I'm late to this party, but there's a pretty reasonable workaround to this behavior:

Explicit CATransactions

Since some of the Apple APIs don't provide a completion block for animated methods (the ideal solution), you can cheat with CA a bit. Most/all of these calls will themselves create either an implicit or explicit transaction under the hood. Because transactions are naturally nestable, we can inject a bit of order into the chaos by creating our own explicit CATransaction and adding a completion block. Whatever transactions occur during the Apple-animated method will be a part of our transaction, and we can take advantage of that.

Obviously your mileage may vary, and I haven't tested this on anything but a UIProgressView. Also, in animation-heavy contexts, this probably breaks down. It ought to work for simple enough cases though. I'm using it to wait until my progress view finishes filling up before dismissing the view controller that it lives in.

For example:

#import <quartzcore quartzcore.h="">

[CATransaction begin];
[CATransaction setCompletionBlock:^{
NSLog(@"Got completion block");
}];
[myUIProgressView setProgress:progress animated:YES];
[CATransaction commit];
</quartzcore>

Re: Integrating Asana and Git

Greg Rubin — Wed, 30 Jan 2013 11:04:03 -0000

There is also an Google Chrome Extension to add Time Management to Asana tasks...
https://chrome.google.com/webs...

Re: SMPageControl: UIPageControl’s Fancy One-Upping Cousin

Jerry Jones — Fri, 11 Jan 2013 13:37:50 -0000

I suggest grabbing the sample code from the repo, it's got all the proper assets in place to function properly with the sample code you pasted here. That should help you get started.

Re: SMPageControl: UIPageControl’s Fancy One-Upping Cousin

mars — Tue, 08 Jan 2013 20:28:52 -0000

Im not sure how to use this? I thought I would create a new class with xib, of uiviewcontroller type, load it in the appdelegate instead of the current one, in its viewdidload add the sample code:

SMPageControl *pageControl = [[SMPageControl alloc] init];
pageControl.numberOfPages = 10;
pageControl.pageIndicatorImage = [UIImage imageNamed:@"appleDot"];
pageControl.currentPageIndicatorImage = [UIImage imageNamed:@"currentAppleDot"];
[pageControl sizeToFit];
[self.view addSubview:pageControl];

But then I saw the iPhone xib and saw labels that say drop replacement for UIPageControl. So im confused. Please help. :)

Re: SMPageControl: UIPageControl’s Fancy One-Upping Cousin

Jerry Jones — Fri, 09 Nov 2012 19:06:01 -0000

I suspect it doesn't handle variably sized dots very well right now - I remember thinking of this part way through, and I never came back to it.

Do me a favor, open an issue on the GitHub repo (https://github.com/Spaceman-La..., and I'd be happy to get that added.

Re: SMPageControl: UIPageControl’s Fancy One-Upping Cousin

sebastian — Fri, 09 Nov 2012 07:38:51 -0000

How about using dots of different sizes. Say currentDot is bigger than other dots? I get problems with distances. Seems dots are not placed as centered in its own place but left aligned.

Re: SMPageControl: UIPageControl’s Fancy One-Upping Cousin

Thomas Hempel — Tue, 06 Nov 2012 05:24:02 -0000

This is awesome! Thank you very very much!!!

Re: SMPageControl: UIPageControl’s Fancy One-Upping Cousin

Jerry Jones — Mon, 05 Nov 2012 17:54:17 -0000

Honestly, it's pretty flexible - whatever best suits your app's appearance. We're using it in a project right now at about 12pt x 12pt, and I'm quite happy with it.

Re: Cancel dispatch_after

Mark — Sun, 04 Nov 2012 01:12:21 -0000

Thanks, ran into this problem myself and this helped!

Re: SMPageControl: UIPageControl’s Fancy One-Upping Cousin

Colin Pierse — Thu, 01 Nov 2012 07:19:55 -0000

Just awesome dude. Was wondering what size is best for the page bot. 12x12?

Re: US States in an NSArray

ultrajoke — Tue, 30 Oct 2012 17:45:03 -0000

Thanks, Leo! You rock.

Re: US States in an NSArray

Leo — Tue, 30 Oct 2012 17:39:47 -0000

And here's the state abbreviations matching that array:

[NSArray arrayWithObjects:@"AL", @"AK", @"AZ", @"AR", @"CA", @"CO", @"CT", @"DE", @"FL", @"GA", @"HI", @"ID", @"IL", @"IN", @"IA", @"KS", @"KY", @"LA", @"ME", @"MD", @"MA", @"MI", @"MN", @"MS", @"MO", @"MT", @"NE", @"NV", @"NH", @"NJ", @"NM", @"NY", @"NC", @"ND", @"OH", @"OK", @"OR", @"PA", @"RI", @"SC", @"SD", @"TN", @"TX", @"UT", @"VT", @"VA", @"WA", @"WV", @"WI", @"WY", nil];

Re: SMPageControl: UIPageControl’s Fancy One-Upping Cousin

Jerry Jones — Thu, 18 Oct 2012 11:40:44 -0000

No, not at all. In fact, I'm 99% sure that most of the API used in the class has been around since iOS 2.0. This should be safe to use with any version of iOS.

However, I'm not sure if the classes will _compile against_ an SDK earlier than 5.0, given the use of UI_APPEARANCE_SELECTOR in the interface.

Re: SMPageControl: UIPageControl’s Fancy One-Upping Cousin

Jeffrey Moran — Wed, 17 Oct 2012 13:32:41 -0000

Is this for iOS 6 only?

Re: Premature Completion: An Embarrassing Problem

foon — Wed, 29 Aug 2012 13:11:14 -0000

Whoops, I seem to be switching between disqus users. Foon and ultrajoke are both the author :)

Re: Premature Completion: An Embarrassing Problem

ultrajoke — Wed, 29 Aug 2012 13:09:30 -0000

Not synchronization, just UI timing. I disagree that the word "completion" should be read so strictly, but I see your point. For me it's just about what the user of the API will expect. I think people won't necessarily think through all the implications of "completion", but I could certainly be wrong.

Re: Premature Completion: An Embarrassing Problem

Johann Fradj — Wed, 29 Aug 2012 13:05:07 -0000

Hahaha,

I'll argue that creating software making synchronisation based on timer is really bad ;-)

Also I want to say that it is a completion block and as it's name supposed it's a block that has to be called when the animation complete. And for me - and apparently for Apple too -, when there is nothing to animate, the job is already done ;-) so the animation duration is useless. That parameter as a good name too: animationDuration, so if there is nothing to animate it should take no time to do it ;-)
(Just a note: if you use the delay parameter, you'll see that the animation block is called after the delay, which is completely logic.)

Re: Premature Completion: An Embarrassing Problem

foon — Wed, 29 Aug 2012 12:53:13 -0000

The other option--and I would argue, the more reasonable option--is to fire the completion block after the duration passed to the UIView method, whether or not an animation has been created.
Consider a situation where the user animates a view that may or may not be onscreen. Is it better to do what the user expects, and run the completion after the animation duration regardless? Or should he have to special case and set up his own dispatch_after only if the view won't animate due to implementation details in CA?