Thank you!
On Feb 16, 2012, at 7:08 PM, Roland King wrote:
> No there's no way to do that
>
> On Feb 16, 2012, at 7:02 PM, Rick C. wrote:
>
>> Hi,
>>
>> My research tells me no, but to be sure is there a way to add additional
>> sharing options in the iOS context menu? So for example if I
As a follow up, it appears that in 10.7.3 Apple have included a further
Console log message along the lines of:
16/02/2012 08:12:28.319 sandboxd: ([23644]) WebProcess(23644) deny
hid-control
It appears that Sandboxed applications do not allow external applications
to run the AXUIElementPostKeybo
Hi,
currently my application supports only English. In the future versions we would
like to have it in around 15 languages.
What is the best practice for having localized nibs.
1) Common approach, different nibs for different languages.
+ve, straight forward.
-ve, Time consuming and maintenanc
I'm quite new Mac OS X programmer. I have to create a project and I'm not
sure what possibilites I have and what mechanism can I use. This is what I
need to do: I need a Cocoa app which send and receive some data (something
similar to the Mail app). I can send for example a pdf document from the
ap
I got an EXC_BAD_ACCESS in objc_msgSend. By probing registers in gdb, I am
able to get the receiver, selector and the single parameter of the offending
message.
(gdb) po *(int*)($ebp+8)
(gdb) po NSStringFromSelector(*(int*)($ebp+12))
updateAgentActivityNow:
(gdb) po *(int*)($ebp+16)
<__NSCFT
On Fri, Feb 17, 2012 at 8:53 AM, Jerry Krinock wrote:
>
> Both the receiver (a window controller) and the method's parameter (a timer)
> both seem to be good, live, valid objects…
>
> (gdb) po 0xcdbf570
>
> (gdb) po [0xcdbf570 window]
>
> (gdb) po 0x9315960
> <__NSCFTimer: 0x9315960>
> (gdb) po
On Feb 16, 2012, at 1:22 AM, Patrick Robertson wrote:
> As a follow up, it appears that in 10.7.3 Apple have included a further
> Console log message along the lines of:
>
> 16/02/2012 08:12:28.319 sandboxd: ([23644]) WebProcess(23644) deny
> hid-control
>
>
> It appears that Sandboxed applica
I've also filed a bug at least 3 months ago, and it appears Apple have been
ignoring it. I have come to the same conclusion as you on the matter Nick.
It seems we must either wait for a new API (which I think is unlikely to
happen) or have to remove features that rely on this from our applications
Actually I read it as set Datasource … LOL
On Feb 16, 2012, at 7:28 PM, Aaron Burghardt wrote:
> Well, I'm glad that worked for you, but I have to admit that I wrote that in
> a hurry and meant to suggest that you set the breakpoint on setDatasource.
> Thanks for following up.
>
> Cheers,
>
>
On 16 Feb 2012, at 3:54 pm, Ken Thomases wrote:
> In other words, you're being silly. It's clear to everyone that -[NSString
> isEqual:] must have semantics built on -[NSString isEqualToString:], which is
> clearly documented.
What value does NSString's isEqualToString: bring to the table over
On 2012 Feb 17, at 09:54, Kyle Sluder wrote:
> All that means is that the storage for the object hasn't been overwritten yet.
Thank you, Kyle, and I see what you mean. But also my tests show that the
object is still able to respond to messages, which means that it shouldn't have
crashed objc_
On 17 Feb 2012, at 20:33, Ben Kennedy wrote:
> On 16 Feb 2012, at 3:54 pm, Ken Thomases wrote:
>
>> In other words, you're being silly. It's clear to everyone that -[NSString
>> isEqual:] must have semantics built on -[NSString isEqualToString:], which
>> is clearly documented.
>
> What valu
Le 17 févr. 2012 à 21:33, Ben Kennedy a écrit :
> On 16 Feb 2012, at 3:54 pm, Ken Thomases wrote:
>
>> In other words, you're being silly. It's clear to everyone that -[NSString
>> isEqual:] must have semantics built on -[NSString isEqualToString:], which
>> is clearly documented.
>
> What v
On Feb 17, 2012, at 2:02 PM, Jerry Krinock wrote:
> On 2012 Feb 17, at 09:54, Kyle Sluder wrote:
>> All that means is that the storage for the object hasn't been overwritten
>> yet.
>
> Thank you, Kyle, and I see what you mean. But also my tests show that the
> object is still able to respond t
I’m trying to take some ordinary single-threaded Cocoa code, and make it
possible to invoke it from multiple threads. At this point I’m not modifying
this code to add thread-safety to it; instead I just want to allow asynchronous
calls into it, which will always run on a single thread at a time.
On Feb 17, 2012, at 2:33 PM, Ben Kennedy wrote:
> On 16 Feb 2012, at 3:54 pm, Ken Thomases wrote:
>
>> In other words, you're being silly. It's clear to everyone that -[NSString
>> isEqual:] must have semantics built on -[NSString isEqualToString:], which
>> is clearly documented.
>
> What va
On Feb 17, 2012, at 2:33 PM, Ben Kennedy wrote:
> What value does NSString's isEqualToString: bring to the table over its
> implementation of isEqual? Is it just a matter of foregoing an 'if ([obj
> isKindOfClass:[NSString class])' construct at the front end? Put another
> way, why does NSStr
On Feb 17, 2012, at 6:22 PM, Jens Alfke wrote:
> The trouble I’m having is that neither GCD dispatch_queues nor
> NSOperationQueues seem to have runloops, so any code that explicitly or
> implicitly uses runloops for scheduling breaks when it’s invoked from a block
> running on a dispatch or op
On Feb 17, 2012, at 8:51 PM, Ken Thomases wrote:
> On Feb 17, 2012, at 2:33 PM, Ben Kennedy wrote:
>
>> On 16 Feb 2012, at 3:54 pm, Ken Thomases wrote:
>>
>>> In other words, you're being silly. It's clear to everyone that -[NSString
>>> isEqual:] must have semantics built on -[NSString isEqua
The root of your problem seems to be your assumption that GCD runs the run loop.
NSURLConnection case: the delegate methods aren't called because
NSURLConnection machinery requires the run loop to be run, which GCD
isn't going to do for you. (Calling -setDelegateQueue: fixes this
because NSURLConn
20 matches
Mail list logo
