Marc Portier wrote:
don't fully understand what you are saying here, but if you have
investigated more and have more detail to present the issue I'll do a
best effort to get into it
(next week I'll have limited online time though, so be patient)
No, I haven't investigated it fully. I will
Marc Portier wrote:
nope, current binding doesn't do this.
That's clear now. From the sample, I was under the impression that the
binding would set the id attribute equal to the index of the row in
the repeater. My wrong.
you can: make the id visible so the user can provide it though
I've tried
Ugo Cei wrote:
Marc Portier wrote:
nope, current binding doesn't do this.
That's clear now. From the sample, I was under the impression that the
binding would set the id attribute equal to the index of the row in
the repeater. My wrong.
you can: make the id visible so the user can provide
I'm trying to do something similar to Woody's form2 sample, adding nodes
to an XML document using the repeater. The problem with form2 (and also
with my code) is that the new nodes' id attribute is null, and I
cannot see an obvious way to set it's value. What I'd like is to set it
to the
nope, current binding doesn't do this.
you can: make the id visible so the user can provide it though
and you can also: loop through your form-model and set this stuff (with
the same API the binding is using internally)
but what you describe here seems to be quite a specific kind of business
