Re: [tree2] TreeStateBase uses "physical node id"

Mario Ivankovits wrote: Ok, no I have seen there are splits on ":" and the ids are used to directly lookup a child entry. s/no/now/ --- Mario

Re: [tree2] TreeStateBase uses "physical node id"

Mario Ivankovits wrote: But no one really relies on its content. Ok, no I have seen there are splits on ":" and the ids are used to directly lookup a child entry. How bad. Though, if I manage to change this, are there chances to get such a patch applied - it might be a rather large patch. -

Re: [tree2] TreeStateBase uses "physical node id"

[EMAIL PROTECTED] wrote: I already proposed this. The problem is, that much of the code in the renderer an the javascript relies on the "physical" node id". But no one really relies on its content. For what I can see is that there is no need to have it somethink like 0:0:0 - I didnt found a spl

Antwort: [tree2] TreeStateBase uses "physical node id"

I already proposed this. The problem is, that much of the code in the renderer an the _javascript_ relies on the "physical" node id". By the way, MYFACES-568 should fix the illogical state problem ... but does not save you from possibly expanding to "wrong" node. [EMAIL PROTECTED] schrieb am 28.0

[tree2] TreeStateBase uses "physical node id"

Hi! I have seen the tree2 component uses a (I will call it) "physical node id" like "0:0:0" to store the expanded/collapsed states. Now if one inserts a new record into say a database and regenerate the tree it might happen that those ids no longer match the data and e.g. a "illogical state"