On Saturday 20 June 2009 13:09:23 Alberto Villa wrote: > On Friday 19 June 2009 22:19:24 [email protected] wrote: > > Revision: 3597 > > m_startPos = infoXml.attribute("position").toInt(); > > - m_zoom = infoXml.attribute("zoom", "7").toInt(); > > - m_zoneStart = infoXml.attribute("zonein", "0").toInt(); > > - m_zoneEnd = infoXml.attribute("zoneout", "100").toInt(); > > > > + QDomElement docproperties = > infoXml.firstChildElement("documentproperties"); > > + QDomNamedNodeMap props = docproperties.attributes(); > > + for (int i = 0; i < props.count(); i++) { > > + m_documentProperties.insert(props.item(i).nodeName(), > props.item(i).nodeValue()); > > + } > > is there a particular reason for position to stay in kdenlivedoc and not in > documentproperties?
Not really, it's just that this property doesn't need to be stored during the document's lifetime, but I just made a commit to move it in the documentproperties, as I also think it is it's place. regards jb ------------------------------------------------------------------------------ Are you an open source citizen? Join us for the Open Source Bridge conference! Portland, OR, June 17-19. Two days of sessions, one day of unconference: $250. Need another reason to go? 24-hour hacker lounge. Register today! http://ad.doubleclick.net/clk;215844324;13503038;v?http://opensourcebridge.org _______________________________________________ Kdenlive-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/kdenlive-devel
