On Feb 21, 2014, at 9:13 PM, Bradley O'Hearne wrote:
> I’ve spent the last hour trying to post an issue to DTS via the Apple Mac
> Developer Program Member Center….no dice. Despite the fact I have all fields
> filled out, I keep getting the error message:
>
> “We are unable to process your re
In the return statement, did you not perhaps mean inputColorProps rather than
inputColor?
Sandy
On Feb 24, 2014, at 12:10 AM, Kevin Meaney wrote:
> inputColor,
___
Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
Please do not post admin reques
I'm developing an app that uses iCloud Core Data in iOS 7, I understand
only lightweight migration is supported for iCloud CD, but at some point a
app may need to migrate to a new model that is different enough where
either custom mapping or migration policy is required. Since that migration
can't
In the CoreImage Programming guide on the discussion about writing a custom
filter one of the steps described it to write a custom attributes method called
"customAttributes". I used as a template of what I needed to do the
customAttributes method implemented in Apple's sample code for
AVGreenS
Apologies for the cross posting from quartz-dev. But it seems these days that
it is hard to work out which forum, lists/devforum and then which of the
discussions to then post.
I've been playing with creating a core image filter for OS X. I've got simple
chroma key filter working as I would lik
From the comments I've seen iOS 7 is slower than iOS 6 which on my iPhone 4 is
already sluggish. I'm not sure I'm happy with the state of affairs Apple has
left me in.
Kevin
On 23 Feb 2014, at 19:27, Clark Smith Cox III wrote:
>
> On Feb 22, 2014, at 6:58 PM, Rick Mann wrote:
>
>> There's
We have run into a number is issues trying to use CIFilters with CALayers:
1. When a layer is hidden, its filters, especially background filters,
should be temporarily removed, or at least bypassed. Hiding the layer
should make if effectively non-existent in the displayed layer stack.
2. The doc
…actually, I will respond to this one last issue, as this was a legit technical
suggestion. We actually looked into this route of detecting screenshots when
they are done, but we shied away from doing this, for a couple of reasons:
- It appeared there would be other kinds of headaches that woul
defaults write com.apple.screencapture location ~/Pictures/
(Putting things on my virtual desktop is as pointless as writing it directly on
my real one - I have so many files/papers open, it's effectively lost. Clutter
is good!)
- Original Message -
From: "Scott Ribe"
To: dangerwillrob
On Feb 22, 2014, at 6:58 PM, Rick Mann wrote:
> There's an update to iOS 6.1 for iPod Touch 4th gen and iPhone 3GS, but none
> for other devices?
iOS 6.1.6 doesn’t exist for any other devices. Those two are the only
devices for which iOS 6.1.6 is the latest available version, all othe
On Feb 22, 2014, at 10:09 PM, dangerwillrobinsondan...@gmail.com wrote:
> There is no Cocoa to this. This is OT.
That is absolutely not true, it is *entirely* a question of Cocoa API, but….
> Thread should end.
…I’ll actually request the thread end, because it has unfortunately been
swallowed
We are applying a custom background filter to a CALayer. It works once,
at installation. However we have been unable to do live control of the
filter parameter. Yes, we are using valueForKey to change parameters, and
have verified that the filter parameters are getting updated. However,
outpu
On Feb 23, 2014, at 11:32, "Kyle Sluder" wrote:
>
> Control-Shift-3 puts the screenshot on the pasteboard
Command-control-shift-3.
Steve via iPad
___
Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
Please do not post admin requests or moderator
On Feb 23, 2014, at 7:34 AM, Scott Ribe wrote:
>
>> On Feb 22, 2014, at 10:09 PM, dangerwillrobinsondan...@gmail.com wrote:
>>
>> How would you know what files to watch for?
>> File extensions are really unreliable means of knowing content types.
>
> Because the built-in screen shot functionali
On 23 Feb 2014, at 14:15, Graham Cox wrote:
> On 23 Feb 2014, at 11:08 pm, jonat...@mugginsoft.com wrote:
>
>>> 1(int) and 1(float) can be represented by the same NSNumber object
>>> perfectly legally.
>> Is that true?
>
> I said "can be", not "is". Certainly my observation in the past was that
An app that deletes files on another persons Mac, blocks certain functions of
the OS, and reports stuff really sounds like a trojan to me. I guess Apple has
done a lot to prohibit this kind of behaviour from apps, so even if the app
made by the thread-starter is legit, the mechanics would be use
On 23.02.2014, at 17:16, Etienne Samson wrote:
> Le 23 févr. 2014 à 16:34, Scott Ribe a écrit :
>
>> On Feb 22, 2014, at 10:09 PM, dangerwillrobinsondan...@gmail.com wrote:
>>
>>> How would you know what files to watch for?
>>> File extensions are really unreliable means of knowing content ty
Le 23 févr. 2014 à 16:34, Scott Ribe a écrit :
> On Feb 22, 2014, at 10:09 PM, dangerwillrobinsondan...@gmail.com wrote:
>
>> How would you know what files to watch for?
>> File extensions are really unreliable means of knowing content types.
>
> Because the built-in screen shot functionality
On Feb 22, 2014, at 10:09 PM, dangerwillrobinsondan...@gmail.com wrote:
> How would you know what files to watch for?
> File extensions are really unreliable means of knowing content types.
Because the built-in screen shot functionality uses a really obvious naming
convention, and drops the fil
On Feb 22, 2014, at 1:28 PM, jonat...@mugginsoft.com wrote:
> On 22 Feb 2014, at 15:32, Ken Thomases wrote:
>>>
>>
>> NSDecimalNumber can represent values that are outside of the range of
>> doubles. So, _some_ NSDecimalNumber instances _may_ return "d" for double,
>> but others definitely w
I create an NSTextView containing RTFD text, with a small image.
The result is ok until I rotate the textView. At 0º, 90º, 180º and 270º the
image within the text looks ok. But if I rotate the textView e.g. by 45º or
22º... the image looks distorted, as slanted, while the text looks good.
What do I
On Feb 23, 2014, at 4:08 AM, jonat...@mugginsoft.com wrote:
>> 1(int) and 1(float) can be represented by the same NSNumber object perfectly
>> legally.
> Is that true?
Yes. As far as NSNumber is concerned, they are equal. They are also both
equal to @(YES) which is initialized with a BOOL. On
On 23 Feb 2014, at 11:08 pm, jonat...@mugginsoft.com wrote:
>> 1(int) and 1(float) can be represented by the same NSNumber object perfectly
>> legally.
> Is that true?
I said "can be", not "is". Certainly my observation in the past was that
NSNumber stored, as an int, a float that could be rep
On 23 Feb 2014, at 10:05, Graham Cox wrote:
>
> You might find it happens to work today but it is not contracted to do so
>
I agree that there is some uncertainty going forward.
Part of the issue I think is in the nature of class clusters.
We rely on the behaviour of an unspecified collection
I don’t like the idea of deleting random files on the user’s computer as it
could cause major problems. You could take the snapchat approach and just send
notifications to the proctor when files are created during a test.
Thanks,
Jon
On Feb 22, 2014, at 1:54 PM, Matt Gough wrote:
> OK,
>
>
On 23 Feb 2014, at 11:20, Uli Kusterer wrote:
> On 23 Feb 2014, at 06:09, dangerwillrobinsondan...@gmail.com wrote:
>> There is no Cocoa to this. This is OT.
>> Thread should end.
>
> What is it with you and this thread?
Sorry, I shouldn’t have written it like that. And particularly not under
On 23 Feb 2014, at 06:09, dangerwillrobinsondan...@gmail.com wrote:
> There is no Cocoa to this. This is OT.
> Thread should end.
What is it with you and this thread? He’s already stated his requirements and
asked for workarounds and solutions. The only people dragging this discussion
kicking
Would an NSNumber subclass be out of the question?
Just store that original type in your own retrievable way?
___
Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
Please do not post admin requests or moderator comments to the list.
Contact the moderat
On 23 Feb 2014, at 8:30 pm, jonat...@mugginsoft.com wrote:
> This dict, when instantiated, will contain 1 key value pair.
>NSDictionary *dict = @{ @((int)1): @"val 1", @((float)1): @"val 2" };
>
> However, this C# Dictionary unit test object will contain two,
>ObjectObjectDictio
On Feb 23, 2014, at 3:30 AM, jonat...@mugginsoft.com wrote:
> 3. For any given object subclass (of which there may be many) I want
> -objCType to be constant.
>
> I think that NSNumber does all of the above. Ken believes that 3. is in doubt.
> If this proves to be the case then I will have to g
On 23 Feb 2014, at 8:30 pm, jonat...@mugginsoft.com wrote:
> Therefore the encoded class of the numeric key is essential.
Another solution would be just to use a string, with some encoding scheme of
your own device, e.g. append a type code to the constant. Category methods on
NSString would a
On 23 Feb 2014, at 8:30 pm, jonat...@mugginsoft.com wrote:
> suppose I think that NSNumber actually is a good fit.
> My usage model requires:
>
> 1. Configure an object with a numeric type: e.g.: @((int)5).
> 2. When I query an object subclass with getValue: I want to receive back an
> instanc
On 23 Feb 2014, at 00:07, Graham Cox wrote:
> NSNumber's can be slippery buggers, in my experience.
Won’t disagree with that.
>
> Why are you so determined that you must use NSNumber, rather than your own
> class? You haven't adequately explained why that isn't a good solution, as it
> certai
I am changing the model of my Core Data app in a big way for the next
update, and custom migration is definitely needed. After reading Apple's
docs on migration policy subclasses, I find it very convoluted and wondered
if there is an easier way. I am thinking, why not just bring up the data in
the
34 matches
Mail list logo