On Sep 1, 2013, at 18:26 , Uli Kusterer wrote:
> Honestly, I wouldn’t use non-keyed archiving anymore these days. Either you
> need performance so badly that you create your own file format (or use
> something specialized for a particular need, like sqlite), or you use keyed
> archiving. It’s
Terminate it immediately after launch?
Sent from my iPhone
> On 2013年8月30日, at 20:47, Tony Giaccone wrote:
>
>
>
> Is there a programatic way to prevent the launch of a particular application?
> I want to prevent certain applications under particular situations from
> starting up.
>
>
>
Is there a programatic way to prevent the launch of a particular application? I
want to prevent certain applications under particular situations from starting
up.
Tony
___
Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
Please do not post admi
On Aug 26, 2013, at 7:48 PM, Allan Odgaard wrote:
> On 26 Aug 2013, at 17:35, Ken Thomases wrote:
>
>> On Aug 23, 2013, at 8:17 AM, Leonid Romanov wrote:
>>
>> > Pressing "Command +" results in two -performKeyEquivalent calls […]
>> […] I'm not familiar with this particular one […]
>
> I beli
On Sep 1, 2013, at 6:36 PM, Kyle Sluder wrote:
> On Sep 1, 2013, at 1:41 PM, Greg Parker wrote:
>
>> You're not entirely left up to their whim. A return value whose declared
>> type is immutable imposes restrictions on both sides:
>> 1. You must not mutate the returned object.
>> 2. The returne
On Sep 1, 2013, at 1:41 PM, Greg Parker wrote:
>
> You're not entirely left up to their whim. A return value whose declared type
> is immutable imposes restrictions on both sides:
> 1. You must not mutate the returned object.
> 2. The returned object will not be mutated behind your back by anyo
On Aug 31, 2013, at 7:10 PM, Gerriet M. Denkmann wrote:
> 2. Why did this even occasionally work before I made my veryDeepMutableCopy?
> NSUserDefaults tells me about dictionaryForKey: "The returned dictionary and
> its contents are immutable, even if the values you originally set were
> mutabl
On 01/09/2013, at 5:07 PM, Marcel Weiher wrote:
> Well, archiving in general is pretty convenient, I am just trying to figure
> out how significant the benefits of keyed archiving are in particular (as
> compared to, for example, old style archiving). If you’re on iOS you don’t
> have a choi
On Sep 1, 2013, at 17:07, Marcel Weiher wrote:
> Well, archiving in general is pretty convenient, I am just trying to figure
> out how significant the benefits of keyed archiving are in particular (as
> compared to, for example, old style archiving). If you’re on iOS you don’t
> have a choice,
I use keyed coding with defaults to solve this issue, keys never change meaning
after definition, app should ignore non-recognised keys and missing keys are
defaulted or inferred from existing ones.
On Sep 1, 2013, at 23:07, Marcel Weiher wrote:
> Hi Graham,
>
> thanks for sharing your experi
Hi Graham,
thanks for sharing your experience, that’s really helpful!
On Sep 1, 2013, at 11:54 , Graham Cox wrote:
> On 31/08/2013, at 6:48 PM, Marcel Weiher wrote:
>> So you’ve had good practical experience with forward/backward compatible
>> designs?
>
> Yes.
>
> But let me qualify it :) B
On 31/08/2013, at 6:48 PM, Marcel Weiher wrote:
>
> On Aug 29, 2013, at 11:54 , Graham Cox wrote:
>
>>
>>> So the whole automagic forward/backward compatibility that we’re supposed
>>> to get with keyed archives doesn’t actually pan out. If you want
>>> compatibility, you have to plan and
12 matches
Mail list logo
