On Thu, Dec 12, 2013 at 3:08 PM, Rick Mann wrote:
>
> That's good to know; I thought they were requiring iOS 7.
>
>
https://developer.apple.com/news/index.php?id=12172013a#top
> Even so, does an iOS 6 SDK-based app not get all iOS 7 styling? I'd try
> the experiment myself, but it's a bit of wo
I have formatted text delivered to the app as HTML that I am converting to a
NSAttributedString and then assigning to a UILabel like this:
NSDictionary* options =
@{
NSCharacterEncodingDocumentAttribute: @(NSUTF8StringEncoding),
NSDefaultAttributesDocumentAttribute:
On Dec 17, 2013, at 1:04 PM, Jens Alfke wrote:
> On Dec 17, 2013, at 10:44 AM, Steve Christensen wrote:
>
>> This seems odd to me since there's a perfectly fine Avenir Next Medium
>> Italic available. Is this an expected font choice for italic text given the
>> setup above
>
> That seems wro
On Dec 17, 2013, at 10:44 AM, Steve Christensen wrote:
> This seems odd to me since there's a perfectly fine Avenir Next Medium Italic
> available. Is this an expected font choice for italic text given the setup
> above
That seems wrong to me too.
I just experimented in TextEdit on OS X 10.9
On 12/17/13, Uli Kusterer wrote:
> On 17 Dec 2013, at 00:15, Dan Treiman wrote:
>> The two best solutions (and by best I mean least time-wasting) are
>> CVDisplayLink and NSTimer.
>>
>> CVDisplayLink synchronizes with the display refresh rate and gives you
>> callbacks in a background thread. Th
I have a fairly deep NSView hierarchy which fails to satisfy its vertical
constraints.
The embedded views are generally just embedded within their containers.
To me it seems that the constraints should be viable.
However this is not the case and I have to reduce a bottom constraint from a
priorit
On 17 Dec 2013, at 00:15, Dan Treiman wrote:
> The two best solutions (and by best I mean least time-wasting) are
> CVDisplayLink and NSTimer.
>
> CVDisplayLink synchronizes with the display refresh rate and gives you
> callbacks in a background thread. This somewhat like CADisplayLink on iOS.
My apologies if this question has appeared once already - I'm resending it
because I fear it may have been lost during the Cocoa Dev List outage.
Here's a little oddity that might either be me being foolish (again) or relate
to an open Radar. I'm inclined to the former because (according to my
I have found that if I use
[mImage setCacheMode:NSImageCacheNever];
The trouble never occurs. It occurs when I use
[mImage setCacheMode:NSImageCacheAlways];
I don¹t know whether that¹s a Cocoa¹s bug.
Do you think I have to file a bug to Apple?
Regards
-- Leonardo
Da: "Stephen J. Butl
On 13 Dec 2013, at 10:57 pm, Alex Hall wrote:
> To do so smoothly, though, will require a loop, so I can update the position
> in small increments many times per second.
You probably know this, but it’s a point worth repeating.
Whatever method you use to make the game loop, don’t fall into t
10 matches
Mail list logo
