Joe, Could you elaborate a little please? (Or better yet, provide a small example app - but hold off on that for now unless you can put one together without too much effort)
Is an Exception thrown when you load the 'nested panel' BXML file using BXMLSerializer, or possibly when you try to add the serialized Component graph to the your 'main UI panel', or somewhere else again? http://pivot.apache.org/tutorials/bxml-primer.html BXMLSerializer handles a similar situation internally when <bxml:include inline="false"> is used to include additional BXML files into a parent BXML file. This ensures that each included BXML file has its own namespace and therefore avoids clashes. This allows the exact same BXML file to be included multiple times into the same parent BXML file without namespace collisions. I'm pretty sure there will be a way around this, but I'm not at a dev machine, so can't investigate right now. Chris On 19 April 2011 15:21, Joe Minichino - TechFort <[email protected]> wrote: > Hi, > > I am new to Pivot, but I am really impressed by it, well done. > > I have a main UI with a panel that hosts other panels. These nested panels > are simply bxml files dynmically loaded at runtime through user input and > added to the main view (say a user enters the name of the bxml file to load > and that bxml gets added to the view). > > Problem is that if I try to load a bxml file that contains an id that's > already in use the new bxml file won't load. > > I can see how this feature could be by design so my question is if there is > anyway to enforce bxml:id scoping so that I won't have to deal with these > type of id conflicts or keep track of the id's already in use? > > Thanks > Joe > >
