I have discovered that all of my page components that were created
with the DisplayGroupComponent wizard in Xcode are broken. The key
path convention that is used by the wizard throws errors in component
editor.
For example, the wizard inserts a button that inserts an entity
(entityDisplayGroup.insert(), which then becomes the display group's
selected entity) and then wires the selected entity to the editing
form fields by using a key path for the value such as
"entityDisplayGroup.selectedEntity.name". This key path is not
recognized. Is this a bug? Or was Xcode doing something inadvisable
and I should be changing all these pages to create variables when an
item in the display group is selected? The issue seems related to my
previous message in this thread.
David
On 5-Jun-08, at 3:25 PM, David Holt wrote:
> In converting a project to WOLips I have discovered that the
> bindings for someDisplayGroup.masterObject or
> someDisplayGroup.selectedObject don't map to the EOs that are
> specified in the DisplayGroup configuration. In WOBuilder if you
> bound to selectedObject() it would expose the variables and methods
> available for that object.
>
> See screenshots for details.
>
> Is this expected behaviour?
>
> <037.jpg>
>
> <038.jpg>
This archive was generated by hypermail 2.0.0 : Thu Jun 12 2008 - 18:17:48 EDT