Yes it's expected right now ... DisplayGroup and model knowledge are
not currently wired into the bindings inspector ... But then, if it
was, it wouldn't be named "Bindings Inspector (Experimental)" :)
ms
On Jun 5, 2008, at 6: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 05 2008 - 18:43:54 EDT