• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: display group madness...
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: display group madness...


  • Subject: Re: display group madness...
  • From: David Holt <email@hidden>
  • Date: Thu, 5 Mar 2009 09:38:02 -0800

Hi Theodore,

The following exchange from the WOLips list answers your question, I think. If you use the component editor to add your WODisplayGroup, it is named displayGroup1 by default which I then rename to "objectDisplayGroup" as XCode used to do. You may want to follow the convention, or rename the filter so that whatever you name your display group is filtered out.

David

On Jun 12, 2008, at 3:16 PM, David Holt wrote:


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.


It is just a validation "error".

It can't validate it as it does not know the type of object returned by selectedObject. Go to the WOLips binding validation rules preferences and tell it to not validate key paths with displayGroup.selectedObject in them


If anyone else wants to add these to their rules I used:

.*.DisplayGroup\.selectedObject\..*
.*.DisplayGroup\.masterObject\..*



On 5-Mar-09, at 7:29 AM, Theodore Petrosky wrote:


I have started using displayGroups for some of my table data... I have a weirdness that is just getting by me.


I have defined a group:   	

public ERXDisplayGroup<Contact> dg;

and I can access it in my WO. I made some change (i don't really remember what because I was finished with the section dealing with the displayGroup) and suddenly I am getting these errors in my WO.

<wo:WOString value = "$dg.selectedObject.companyName"/>
There is no key 'companyName' for the keypath 'dg.selectedObject' in UserMain..


It was fine a yesterday... and the displayGroup is defined and created with

dg = new ERXDisplayGroup<Contact>();
dg.setObjectArray(contactList);

does someone have a clue where I need to look? BTW, my app runs fine. I just have this error (red X) that I would like to get rid of.

Ted



_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
@mac.com


This email sent to email@hidden

_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden


References: 
 >display group madness... (From: Theodore Petrosky <email@hidden>)

  • Prev by Date: Re: Switch from WinXP to MAC OSThursday
  • Next by Date: Re: Reference Lib JARs Not Recognized
  • Previous by thread: display group madness...
  • Next by thread: Re: display group madness...
  • Index(es):
    • Date
    • Thread