Hi Bruno,
exact the behaviour I do is to create components at a time where they
dont need their markup, as they are later added to (multiple) ListViews
(etc.) and this curently forces me to sync the ListView id's with the
one in the later markup that is also error prone...
Best,
Korbinian
Bruno Borges schrieb:
I'm not sure, but I would guess the reason for this is that if you create a
component with an Id, that component binds to a specific markup. And if it
is allowed to change it's id, it means that you could re-bind it with
another (probably invalid) markkup, creating conflicts.
On Fri, Apr 11, 2008 at 5:18 PM, Korbinian Bachl - privat <
[EMAIL PROTECTED]> wrote:
Hi,
short question: Why isn't it possible to have a setId(String id) on the
components? - Is it really necessary that they know their id at
creation-time?
Regards,
Korbinian
