I've got a lot more experience manipulating views in iOS than I do in Mac OS X,
so forgive me if this is a stupid question.
I have a plug-in based app that behaves a lot like IB 3 does. The user can
select one of the instances of a plug-in element in a canvas, and an inspector
window changes it
On Mar 26, 2011, at 20:46, Jeffrey Walton wrote:
> I deleted all connections and actions in Interface Builder. I closed
> IB and Xcode. I cleaned the project (including the two hidden files in
> the xcode.proj director). I reopened the project, and then reconnected
> the NIB in IB.
>
> Everything
On Sat, Mar 26, 2011 at 11:48 PM, Quincey Morris
wrote:
> On Mar 26, 2011, at 20:30, Jeffrey Walton wrote:
>
>> I'm not sure what its being sent to. below, I changed 'delegate' to
>> 'callbackDelegate' in case of a hidden name clash. Then I put in a few
>> NSLogs. The message is clearly not being
On Mar 26, 2011, at 20:30, Jeffrey Walton wrote:
> I'm not sure what its being sent to. below, I changed 'delegate' to
> 'callbackDelegate' in case of a hidden name clash. Then I put in a few
> NSLogs. The message is clearly not being sent to the delegate that was
> init'd in the picker. The deleg
On Sat, Mar 26, 2011 at 11:30 PM, Jeffrey Walton wrote:
> On Sat, Mar 26, 2011 at 10:35 PM, Sherm Pendley
> wrote:
>> On Sat, Mar 26, 2011 at 10:21 PM, Jeffrey Walton wrote:
>>>
>>> 2011-03-26 22:12:50.029 CryptoSandbox[123:707] -[UIView
>>> userSelectedFile:fileSystemObject:suppliedContext:]:
On Sat, Mar 26, 2011 at 10:37 PM, Kyle Sluder wrote:
> On Sat, Mar 26, 2011 at 7:35 PM, Sherm Pendley
> wrote:
>> The delegate message is being sent to an instance of UIView - not to
>> your controller. That would indicate that the first argument you're
>> sending to -initWithDelegate:withContex
On Sat, Mar 26, 2011 at 10:35 PM, Sherm Pendley wrote:
> On Sat, Mar 26, 2011 at 10:21 PM, Jeffrey Walton wrote:
>>
>> 2011-03-26 22:12:50.029 CryptoSandbox[123:707] -[UIView
>> userSelectedFile:fileSystemObject:suppliedContext:]: unrecognized
>> selector sent to instance 0x1dbd00
>
> The delegat
On Sat, Mar 26, 2011 at 11:26 PM, Kyle Sluder wrote:
> I'm on the road so i cant discuss this further right now. One reason it's
> more helpful to keep this discussion on-list. :)
>
> --Kyle Sluder
My Bad. I sometimes forget that GMail does not perform a 'Reply All' by default.
Jeff
>
> On Mar
I'm on the road so i cant discuss this further right now. One reason it's more
helpful to keep this discussion on-list. :)
--Kyle Sluder
(Sent from the road)
On Mar 26, 2011, at 8:23 PM, Jeffrey Walton wrote:
> On Sat, Mar 26, 2011 at 11:01 PM, Jeffrey Walton wrote:
>> On Sat, Mar 26, 2011 at
On Sat, Mar 26, 2011 at 7:35 PM, Sherm Pendley wrote:
> The delegate message is being sent to an instance of UIView - not to
> your controller. That would indicate that the first argument you're
> sending to -initWithDelegate:withContext: is not what it should be.
Or nobody's retaining the delega
On Sat, Mar 26, 2011 at 10:21 PM, Jeffrey Walton wrote:
>
> 2011-03-26 22:12:50.029 CryptoSandbox[123:707] -[UIView
> userSelectedFile:fileSystemObject:suppliedContext:]: unrecognized
> selector sent to instance 0x1dbd00
The delegate message is being sent to an instance of UIView - not to
your co
On Sat, Mar 26, 2011 at 9:56 PM, Kyle Sluder wrote:
> On Sat, Mar 26, 2011 at 6:39 PM, Jeffrey Walton wrote:
>> // FilePicker.m - try both
>> BOOL responds = [delegate respondsToSelector:@selector(userSelectedFile:)];
>> BOOL responds = [delegate
>> respondsToSelector:@selector(userSelectedFile:f
On Sat, Mar 26, 2011 at 9:39 PM, Jeffrey Walton wrote:
>
> I have a protocol and declarations as follows. respondsToSeletor
> returns NO. If I ignore respondsToSeletor (and send the message), I
> get an expeption.
>
> // FilePicker.m - try both
> BOOL responds = [delegate respondsToSelector:@selec
On Sat, Mar 26, 2011 at 6:39 PM, Jeffrey Walton wrote:
> // FilePicker.m - try both
> BOOL responds = [delegate respondsToSelector:@selector(userSelectedFile:)];
> BOOL responds = [delegate
> respondsToSelector:@selector(userSelectedFile:fileSystemObject:suppliedContext:)];
You need to provide co
Hi All,
I have a protocol and declarations as follows. respondsToSeletor
returns NO. If I ignore respondsToSeletor (and send the message), I
get an expeption.
// FilePicker.m - try both
BOOL responds = [delegate respondsToSelector:@selector(userSelectedFile:)];
BOOL responds = [delegate
respondsT
On Fri, 25 Mar 2011 12:08:53 -0700, Laurent Daudelin
said:
>I've been trying to copy items from a local disk to an AFP-mounted volume with
>"copyItemAtPath:toPath:error:" and I found it to be unreliable in the sense
>that it will fail to set the modification date of the item copied to match
>
On 26 Mar 2011, at 01:23, Peter Lübke wrote:
> Thank you, Mike, for showing me I was taken away by my own fantasy about
> hash...
>
> Am 26.03.2011 um 01:22 schrieb Mike Abdullah:
>
>> It sounds like you're rather misunderstanding what -hash does. Cocoa classes
>> are free to cover the full r
On Mar 25, 2011, at 12:43 AM, John Engelhart wrote:
> Again, thanks for your suggestion, it's just some factors that were probably
> non-obvious from my message make this particular approach less desirable
> than it otherwise would be.
Well, if you want to release it to others, making it as simp
18 matches
Mail list logo
