Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Serializer is not 'stable' #41

Open
pasnox opened this issue Jul 11, 2016 · 4 comments
Open

Serializer is not 'stable' #41

pasnox opened this issue Jul 11, 2016 · 4 comments

Comments

@pasnox
Copy link

pasnox commented Jul 11, 2016

When editing a report, even for small change (by example, just a width change) the saved file is then TOO MUCH different than the previous one while only a width changed.
The xml tags order is not 'stable' ie - it change place from save to save.
This could be easily fixed using a map instead of a hash for the names (if it's what is used), else consider grabbing the keys then sort them (qStableSort) before writing them.
This will a lot help users making diff against edited reports, it's actually a nightmare :)

Thanks,

@fralx
Copy link
Owner

fralx commented Jul 14, 2016

I build XML tree and then save it to a file why during recording tags are written in a different order for me a big mystery :)

@pasnox
Copy link
Author

pasnox commented Jun 14, 2018

Most likely the model hierarchy is changing when loaded from xml in your UI stack then saved with the new stack order.
Any progress on that ?

@fralx
Copy link
Owner

fralx commented Jun 14, 2018

Is it critycal for you ? To be honest i have forget about it :)

@pasnox
Copy link
Author

pasnox commented Jun 14, 2018

It is not critical as I can't live with it ;)
But clearly a problem for reports that are under version control and change frequently.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants