fix #40641: incorrect import/export of relative-x

[MarcSabatella]

As discussed in issue, I think it makes sense for now to simply not import or export relative-x for chord symbols, since we don't do it for any other elements. There is an existing "todo" note regarding support of offsets and relative-x. I left the relative-x in but commented it out to have for reference if/wehn the time comes to revisit any of this. It seems that is also the approach taken for various other places where relative-x was being used or considered for use at one time.

[timmliu]

@MarcSabatella I'm wondering if you could briefly explain how are the x positions of the chord symbols are calculated without the relative-x value?

[MarcSabatella]

Positions for chord symbols are determined by style settings - the chord symbol text style specifically in this case. Not sure what you are really trying to figure out here, probably better to discuss on IRC or forum.

[timmliu]

Are the chord symbol text style settings available when exported to music XML format? I'm trying to figure out how/where in the XML I can determine the positions of chord symbols. Could you point me to the right forum?

[lasconic]

Not sure if you mean MusicXML or MSCX, and not sure what you mean by the position of Chord Symbols. But if you mean the absolute coordinates from the top left of the page, you will not find this in MusicXML or MSCX. MuseScore doesn't store absolute coordinates for any element. They are all computed on the fly by the layout engine. As @MarcSabatella suggested, it's probably better if your explain your use case in details either on IRC #musescore on freenode.net or on the developer mailing list.