I have an issue that has me absolutely stumped. I have a custom view
using a custom layer. When 'bind:toObject:withKeyPath:options:' is
called after 'setView' the binding works. When it is called before
'setView' the binding does not work.
// MyCustomView (this version works)
-
On May 18, 2010, at 8:17 AM, Richard Somers wrote:
I have an issue that has me absolutely stumped.
Correction and additional information.
MyCustomOpenGLLayer should be MyCustomLayer.
MyCustomLayer does not implement 'bind:toObject:withKeyPath:options:'
so the standard framework version of
On May 18, 2010, at 07:17, Richard Somers wrote:
I have an issue that has me absolutely stumped. I have a custom view using a
custom layer. When 'bind:toObject:withKeyPath:options:' is called after
'setView' the binding works. When it is called before 'setView' the binding
does not work.
Are you exposing the binding first?
+ (void)exposeBinding:(NSString *)binding
Thanks,
Chaitanya Pandit
Chief Architect
Expersis Software Inc.
On May 18, 2010, at 7:47 PM, Richard Somers wrote:
I have an issue that has me absolutely stumped. I have a custom view using a
custom layer. When
On May 18, 2010, at 9:21 AM, Chaitanya Pandit chaita...@expersis.com
wrote:
Are you exposing the binding first?
This is completely unnecessary.
--Kyle Sluder
+ (void)exposeBinding:(NSString *)binding
Thanks,
Chaitanya Pandit
Chief Architect
Expersis Software Inc.
On May 18, 2010, at
On May 18, 2010, at 10:04 AM, Quincey Morris wrote:
What is foo?
What does not work mean?
Foo is an int.
Does not work means foo is never updated with the value in the user
defaults.
On May 18, 2010, at 10:21 AM, Chaitanya Pandit wrote:
Are you exposing the binding first?
No, but I
On May 18, 2010, at 12:02, Richard Somers wrote:
Foo is an int.
sigh If you want an answer, you're going to have to be a bit more forthcoming
with information.
Is foo an instance variable or a property? If instance variable, what's the
value of accessInstanceVariablesDirectly for its class?
On May 18, 2010, at 1:40 PM, Quincey Morris wrote:
sigh If you want an answer, you're going to have to be a bit more
forthcoming with information.
Is foo an instance variable or a property? If instance variable,
what's the value of accessInstanceVariablesDirectly for its class?
If a
On May 18, 2010, at 15:21, Richard Somers wrote:
I have verified that the setter 'setFoo' is being called in all cases so that
is not the problem as I originally thought.
In 'awakeFromNib' when 'bindFoo' is called before 'setView' the layer frame
is set but never actually changes to the
On May 18, 2010, at 4:44 PM, Quincey Morris wrote:
1. Setting the frame on a layer that doesn't have a view yet doesn't
do anything useful. This happens because the 'bind:...' invocation
is going to cause the setter to be invoked initially, and in your
non-working case, the view's layer
I have a managed object context with two attached NSObjectControllers
in entity mode. Both controllers control the same entity.
managed object model
nib 1
controller
user interface
bind in interface builder
nib 2
controller
user interface (custom view)
On Nov 4, 2009, at 6:04 AM, Richard Somers
rsomers.li...@infowest.com wrote:
I have a managed object context with two attached
NSObjectControllers in entity mode. Both controllers control the
same entity.
Important: do you really mean entity, or do you mean managed object?
managed
On Nov 4, 2009, at 9:40 AM, Kyle Sluder wrote:
Nib 2 only partly works. Changes made in the custom view do not
show up in the managed object model or in the user interface found
in nib 1.
So now we also need to see your custom view code.
Here is the code for nib 2 which only partly
On Wed, Nov 4, 2009 at 12:17 PM, Richard Somers
rsomers.li...@infowest.com wrote:
All code in the custom view that touch the num property use the accessor
methods. The controller in the nib is in entity mode and bound to File's
Owner (MyDocument) managed object context.
Okay, but as I said
On Nov 4, 2009, at 3:17 PM, Richard Somers wrote:
@interface MyView : NSView
{
double num;
}
@end
@implementation MyView
- (double)num
{
return num;
}
- (void)setnum:(double)newNum
{
[self willChangeValueForKey:@num];
num = newNum;
[self didChangeValueForKey:@num];
}
On Nov 4, 2009, at 2:31 PM, Kyle Sluder wrote:
This invokes the default implementation of -
bind:toObject:withKeyPath:options:, which takes care of the model -
view communication. You now need to take care of the view - model
communication. As described in the User Updates a Value in the
On 05/11/2009, at 8:42 AM, Richard Somers wrote:
See mmalc’s Graphics Bindings sample:
http://homepage.mac.com/mmalc/CocoaExamples/controllers.html
Sometimes Cocoa can be overwhelming. This will help. Thank you so
much. :)
You might also find this blog post very helpful:
On Nov 4, 2009, at 5:20 pm, Rob Keniger wrote:
See mmalc’s Graphics Bindings sample:
http://homepage.mac.com/mmalc/CocoaExamples/controllers.html
Sometimes Cocoa can be overwhelming. This will help. Thank you so much. :)
You might also find this blog post very helpful:
on 4/8/08 9:16 PM, [EMAIL PROTECTED] purportedly said:
I'm using bind:toObject:withKeyPath:options: to programmatically set up
bindings from a set of proxy objects (the receiver) to various properties on
a model object, and while changes to the model properties are properly being
reflected in
I'm using bind:toObject:withKeyPath:options: to programmatically set up
bindings from a set of proxy objects (the receiver) to various properties on
a model object, and while changes to the model properties are properly being
reflected in the proxies, changes to the proxy properties are not being
20 matches
Mail list logo
