i havent hit this usecase myself yet so i wouldnt know. if you guys think its a good idea then go ahead and do it.
my understanding of the property model was that the _expression_ it has
is used for rendering. it has the model of the row object so i dont see
the use for the other _expression_, but
Me neither, but it kind of is Igor's code, right?
Eelco
On 7/22/06, Johan Compagner <[EMAIL PROTECTED]> wrote:
> did you do it already?
> I don't have a problem with it.
>
>
>
> On 7/13/06, Martijn Dashorst <[EMAIL PROTECTED] > wrote:
> > All,
> >
> > I've come across a (minor) limitation of the
did you do it already?I don't have a problem with it.On 7/13/06, Martijn Dashorst <[EMAIL PROTECTED]
> wrote:All,I've come across a (minor) limitation of the PropertyColumn and its
subclasses. I have the need for splitting the currentpropertyExpression into a displayPropertyExpression and amodelPro
All,
I've come across a (minor) limitation of the PropertyColumn and its
subclasses. I have the need for splitting the current
propertyExpression into a displayPropertyExpression and a
modelPropertyExpression.
Sometimes, or possibly often times you want to display an other
property than the value
