This was actually a fun one to solve. The concept of "orders" makes for
some tricky handling for both model and client layers... I don't know if
this was the best solution but I think it was the least amount of code to
make it work. So getWorkspace is defined on my subkind and it grabs the
appropriate workspace for each order type.


On Thu, May 22, 2014 at 12:10 PM, Travis Webb <notifications@github.com>wrote:

> In lib/enyo-x/source/widgets/relation.js:
>
> > @@ -471,7 +475,7 @@ regexp:true, undef:true, trailing:true, white:true, strict:false */
> >          nameValue = "",
> >          descripValue = "",
> >          additionalValue = "",
> > -        Workspace = this._Workspace,
> > +        Workspace = this._Workspace || (newId ? this._List.prototype.getWorkspace(value) : null),
>
> Whoa. How did you figure this out?
>
> —
> Reply to this email directly or view it on GitHub<https://github.com/xtuple/xtuple/pull/1516/files#r12964957>
> .
>



-- 
Julian Carlin

(US) 612-234-4124