[API] beamPos returns inaccessible QPair

[mnorrisvuw]

Issue type

Other type of issue

Description with steps to reproduce

In the MuseScore API, the property beamPos of a beam returns the x and y coordinates as a QPair. But as far as I can tell, there is no way to access the members of a QPair from within the API.

Currently I have to do the following hack:
var beamPosY = parseFloat(currBeam.beamPos.toString().match(/-?[\d\.]+/g)[1]);

It would be good if there was some native way to access the values (e.g. beamPos returned as a QPoint, rather than a QPair, so that I can then use beamPos.x and beamPos.y)

Supporting files, videos and screenshots

N/A

In which versions of MuseScore Studio is this issue present?

4.6.5

Regression

No.

Operating system

macOS 26.4.1

Additional context

No response

Checklist

• This report follows the guidelines for reporting bugs and issues
• I have verified that this issue has not been logged before, by searching the issue tracker for similar issues
• I have attached all requested files and information to this report
• I have attempted to identify the root problem as concisely as possible, and have used minimal reproducible examples where possible

[XiaoMigros]

does beamPos[0] and beamPos[1] not work?

[mnorrisvuw]

does beamPos[0] and beamPos[1] not work?

No, they return 'undefined'

[mnorrisvuw]

Can we just change:
API_PROPERTY(beamPos, BEAM_POS)

to:
API_PROPERTY_T(QPointF, beamPos, BEAM_POS)

???

[cbjeukendrup]

IIRC, QPointF does not represent the correct semantics here: the first value represents the vertical offset of the left side of the beam, and the second value of the right side. Perhaps the property should be split into two double properties.

[mnorrisvuw]

Good point: perhaps an array of doubles would be good.