True enough, and I'll probably use that where we're not using an
ERXBatchingDisplayGroup. Where we do, we get bitten because
WODisplayGroup.selectObject() will only select among
WODisplayGroup._displayedObjects, whereas the ERXBatchingDisplayGroup declares
its own _displayedObjects, presumably to support generics. It's going to take
more time than I have right now to track down that interaction but the upshot is
that WODisplayGroup._displayedObjects appears to be always empty, so
selectObject() (and everything in the selectObjectsIdenticalTo() family) does
nothing in that case.
Steve
On 3/24/10 4:19 PM, Ramsey Gurley wrote:
If you want to fire delegate methods, you can call selectObject(obj)
instead of setSelectedObject(obj).
Ramsey
On Mar 24, 2010, at 4:10 PM, Steve Meyer wrote:
Anyone want to posit a theory why among the WODisplayGroup selection
methods, only setSelectedObjects() [and setSelectedObject()*, which
just calls the former with a single object array] calls neither the
WODisplayGroup.Delegate selection-changed methods nor willChange() to
notify observers?
I feel some overriding coming on but wanted thoughts.
Steve
*except if you pass it <null>, because then it calls clearSelection()
which does the notification.
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list ([email protected])
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-dev/ramsey%40xeotech.com
This email sent to [email protected]
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list ([email protected])
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com
This email sent to [email protected]
