For the record, this works fine if I take the @Property off the
_delete field. It was interfering with setDelete(boolean delete).
Thanks to Uli for pointing this out to me.
This wasted so much of my time I'm pleased to see someone's just added
an issue about @Property. Please have a look
Woah! Indeed, this doesn't work anymore. Evil. How are we supposed to do this
now?
Uli
Geoff Callender schrieb:
No response, so I guess that means we can't add a Delete column to a
Grid any more.
On 14/10/2008, at 8:36 PM, Geoff Callender wrote:
Can anyone tell me if Penyihir's technique
Please ignore my stupidity. I misinterpreted the error message I was getting that had nothing to do
with this.
You can still add a delete column to your model with model.add(delete, null) and add a
deleteCell parameter to your template in order to have a delete column. Works like a charm.
No response, so I guess that means we can't add a Delete column to a
Grid any more.
On 14/10/2008, at 8:36 PM, Geoff Callender wrote:
Can anyone tell me if Penyihir's technique for adding a Delete
column to Grid still works?
Please note this is not the same as editing a flag in the
Uli,
I'm seeing isDelete() called as it renders the display but I'm not
seeing setDelete(boolean delete) being called on submit. Can you
please play spot the obvious error? Here's the code:
html xmlns:t=http://tapestry.apache.org/schema/tapestry_5_0_0.xsd;
body
form t:type=form
