Joshua wrote:
De-Backer wrote:I will first create the doc on my PC and then I will forward it there to you.
I think that can work..it will be plain .txt text.
Whoo it's a hard job, good luck
and thanks in advance
this is a start
The main XML element is therefore the “definition” tag. In case we have more than one type of definition in the future, we use the type attribute to specify that this is an element definition.
definition
* Element dimensions
One of the first things to specify when defining an element is its size: width (width) and height (height), in pixels. These two dimensions must be integers multiples of 10. If this is not the case, QET will round them to the next ten (example: 50 for 42 pixels). They determine the size and the bounding rectangle of the element.
- height
- width
* Element hotspot
The element hooking point designates the point hooked to the mouse cursor during a drag'n drop of the element. They must be full coordinates. “Hotspot_x” is the abscissa, “hotspot_y” is the ordinate. The upper left corner of the rectangle delimiting the element is considered to be the origin. If the values provided exceed the bounding rectangle, they will be limited to the size of the element. The hotspot is also the center of rotation used when changing the orientation of the element.
- hotspot_x
- hotspot_y
* Element orientation
It is then necessary to define what are the possible orientations of the element. Element orientation is used when laying conductors but also to prevent the user from turning an element in a direction that would not make sense. The orientation attribute is defined by a series of 4 characters, each character defining the behavior for an orientation.
+ 1 st character: North
+ 2 nd character: East
+ 3 rd character: South
+ 4 th character: West
Each character can have the following value:
+ d for “default”: indicates that, by default, the element is considered to be oriented in this direction. It is absolutely necessary to indicate a default orientation.
+ y for “yes”: the user can orient the element in this direction.
+ n for “no”: the user cannot orient the element in this direction.
Example: orientation = “ydny” means that the element is drawn facing south and can be turned north and west but not east.
- orientation
- link_type ( grep -w -R 'link_type' sources/* ) info from (/sources/factory/elementfactory.cpp)
-- next_report
-- master
-- slave
-- terminal
- hotspot_x (grep -w -R 'hotspot_x' sources/*)
*
- version
*
- type
uuid
* Uuid used to compare two elements
The code below is used to keep compatibility with previous version of qet
The uuid store in .elmt file, to compare two elements was created at version svn 4032
@TODO remove this code at version 0.6 or 0.7 (all users should already used the version with uuid)
Compare the xml definition transformed in QString. This method can return a false positive (notably with Qt5,
because the attributes of the xml isn't at the same order,with two instance of qet, for the same element)
git ID 557a2eaa878b8e9d48da1c0256bca0dbfd2d849b 2015-06-28
- uuid
names
name
*
- lang
-- be
-- nl
-- fr
-- I have yet to find and link the C ++ code