What you are experancing is the setting of the q
Quarintene xattr value. This cannot be avoided, as how can the OS know that
your application has no macious intent. The best recomendation I can offer is
provide a pkg installer instead as it
Steve Cronin wrote:
Folks;
My Mac-based Cocoa
This is most likely because you are referencing a Framework that is PPC only.
The code for your application may be universal, but if the system detects that
one of the dependancies is PPC, it will use Rosetta to run the PPC in your fat
binary binding to that framework. Are you using any 3rd pa
at 10:56 AM, Richard Penwell wrote:
>
>> while (([inputStream streamStatus] & [outputStream streamStatus]) ==
>> NSStreamStatusOpening && [[NSRunLoop currentRunLoop]
>> runMode:NSDefaultRunLoopMode beforeDate:[NSDate distantFuture]]);
>
>
> There are a
nts and test that both streams are
open. It should also include a timeout value as well.
On Feb 2, 2010, at 11:38 AM, Richard Penwell wrote:
> Hello Devs,
>
> I'd like some feedback on my design here as I'm building an API that I hope
> will be of use to the community, and
Hello Devs,
I'd like some feedback on my design here as I'm building an API that I hope
will be of use to the community, and some of the finer nuances of Cocoa still
escape me.
I'm building a class called TDSConnection which is part of a object graph
providing connectivity to the Tabular Data
hTarget. then the selector will not be
>> performed.
>>
>> Hope it helps
>>
>> Gustavo
>>
>> On Feb 1, 2010, at 10:44 PM, Richard Penwell wrote:
>>
>>> An alternative technique would be roughly:
>>>
>>> 1. Detect mous
An alternative technique would be roughly:
1. Detect mouse down, set state down
2. Call performSelectorAfterDelay 1 second with a test method
3. If the mouse goes up, set state up
4. In the test method, test if the state is down...
On Feb 1, 2010, at 4:42 PM, Eric Gorr wrote:
> What I am trying
Dear list,
I've been toying around with some problems in the world of dynamic code
loading... (a vast and mythical place). I understand that there is a
fundamental difference between Mach-O executables and Mach-O dynamic libraries
(beyond the obvious Mach-O filetype header). I assume it has t
