[Uml-devel] umbrello-soc assert

[Ralf Habacker]

Hi,

when loading the following file  
http://websvn.kde.org/*checkout*/trunk/kdesupport/emerge/doc/refactoring.xmi?revision=999553&content-type=text%2Fplain 
on windows umbrello-soc crashes in
   
 >    umbrello-soc.exe!WidgetBase::loadFromXMI(QDomElement & 
qElement={...})  Zeile 502 + 0x23 Bytes    C++
     umbrello-soc.exe!AssociationWidget::loadFromXMI(QDomElement & 
qElement={...}, const QList<UMLWidget *> & widgets={...}, const 
QList<MessageWidget *> * pMessages=0x0000019c)  Zeile 987    C++
     umbrello-soc.exe!AssociationWidget::loadFromXMI(QDomElement & 
element={...})  Zeile 1251    C++
     umbrello-soc.exe!UMLScene::loadAssociationsFromXMI(QDomElement & 
qElement={...})  Zeile 3762 + 0x13 Bytes    C++
     umbrello-soc.exe!UMLScene::loadFromXMI(QDomElement & 
qElement={...})  Zeile 3656 + 0xf Bytes    C++
     umbrello-soc.exe!UMLFolder::loadDiagramsFromXMI(QDomNode & 
diagrams={...})  Zeile 392 + 0x30 Bytes    C++
     umbrello-soc.exe!UMLFolder::load(QDomElement & element={...})  
Zeile 484 + 0xc Bytes    C++
     umbrello-soc.exe!UMLObject::loadFromXMI(QDomElement & 
element={...})  Zeile 1053 + 0x13 Bytes    C++
     umbrello-soc.exe!UMLDoc::loadUMLObjectsFromXMI(QDomElement & 
element={...})  Zeile 2007 + 0x21 Bytes    C++
     umbrello-soc.exe!UMLDoc::loadUMLObjectsFromXMI(QDomElement & 
element={...})  Zeile 2023 + 0xc Bytes    C++
     umbrello-soc.exe!UMLDoc::loadFromXMI(QIODevice & file={...}, short 
encode=1)  Zeile 1857 + 0xc Bytes    C++
     umbrello-soc.exe!UMLDoc::openDocument(const KUrl & url={...}, const 
char * format=0x00000000)  Zeile 550 + 0x15 Bytes    C++
     umbrello-soc.exe!UMLApp::slotFileOpenRecent(const KUrl & 
url={...})  Zeile 1057 + 0x11 Bytes    C++

It runs on the following assert. Any idea how to fix this issue ?

bool WidgetBase::loadFromXMI(QDomElement &qElement)
{
    Q_ASSERT(umlScene());
    // NOTE:
    // The "none" is used by kde3 version of umbrello. The current
    // technique to determine whether a property is being used from
    // the diagram or not is just to compare the same, rather than
    // having flags for them.
    //
    // This way, there is no burden to update the flags and the code
    // is more robust.

Regars
 Ralf