Search options (Page 129 of 300)

My goal is to understand why the content of the .qet file always changes when saving, because this makes it difficult for git.
(everything is always different)

Attributes

For some time and over the succeeding versions of Qt, it became obvious that the attributes in the XML definition of the elements were not always be read and saved in the same order on each QET startup.
A Qt class compares attributes to know if a newly dragged/dropped element on the diagram already exists in the project. In this case, the class compares all the attributes.
For some speed reasons, this method compares the whole attributes string: if the position of an attribute is changed, the element is considered as different (new).

Among all possible solutions, the one which seems to us to be the easiest one is the generation of an universal unique identifier (UUID) for each element of the collection. In this way, only the UUID attributes of the files must be compared and not the whole XML attributes strings.
The elements editor generates automaticaly an UUID during the saving of the element file.

The database speeds up the loading of numberous elements by managing changes of element thumbnails in tables. To update the thumbnails cache, the database does no longer compare the modification date of these files, only the UUID attributes.

The official collection was patched to add the new UUID attribute.

Script bash unpretentious, for those on GNU/Linux who want to patch their own collection.