Strange behaviour with prj-folders and nested containers (losing settings)
In our company we are experimenting with SVN-integration (QV11, TurtoiseSVN), therefore I created a prj-folder to store all the XML-Files and syncronizing with our repositiory.
Up to this point everything seems to work like expected.
In one application I have nested Container-objects (one 'inner' Container with 3 Line-Charts, one 'outer' Container with some more Charts and the 'inner' Container).
Now I save&close my application and because the prj-folder exists, QV writes all the objects to XML-Files. If I reopen the application everything seems to work (including possible changes to some XML-files), except the nested Container-Object. While the 'outer' Container seems to work correctly and looks like before saving&closing, the inner Container loses its Objects (the 3 Line-Charts).
If I remove the prj-folder and reopen the application again, the inner Container 'finds' its objects again.
This means, that I can't use the prj-folders to integrate to SVN without losing some (in this case very important) settings!
I think this is a bug - can anyone confirm this behaviour? Is there a workaround?
This is a bug in V11. It will be fixed in the V11 SR1 (Feb/Mar timeframe). To accomodate the fix, please note that we have changed the xml format slightly in SR1.If a prj folder was created with QV 11 IR and has container objects, all containers object will be empty if the user tries to open the prj folder with SR1. The easiest way to migrate prj folders to SR1 is to use the original qvw file and generate a new prj folder.
This is a bug in V11. It will be fixed in the V11 SR1 (Feb/Mar timeframe). To accomodate the fix, please note that we have changed the xml format slightly in SR1.If a prj folder was created with QV 11 IR and has container objects, all containers object will be empty if the user tries to open the prj folder with SR1. The easiest way to migrate prj folders to SR1 is to use the original qvw file and generate a new prj folder.
