[solved]wrong serialization in CXTPControlComboBox

Hi Codejock Team,

the width related code in
void CXTPControlComboBox::DoPropExchange(CXTPPropExchange* pPX)
{
    CXTPControlPopup::DoPropExchange(pPX);

    PX_Bool(pPX, _T("DropDown"), m_bDropDown, TRUE);

    // The Width property is already serialized in CXTPControl
    // so in order to avoid double DPI scaling it must not be read twice (ticket 35575),
    // however the value still must be read out to provide format backward compatibility (ticket 36079).
    int nUnusedWidth = 0;
    PX_DPI_X_Int(pPX, _T("Width"), nUnusedWidth, 0);
    UNUSED(nUnusedWidth);
    ...

is not correct, once again.
In XTP1700
PX_DPI_X_Int(pPX, _T("Width"), m_nWidth, 0) was called twice; the two writes did no harm but the two reads somehow changed the member in case of HighDPI (when XTP_DPI_X returns a modified value)

In XTP1801
PX_DPI_X_Int(pPX, _T("Width"), m_nWidth, 0) was called only once (in the base class) and for us, everything was fine (serializing to XML)

In XTP1820
- PX_DPI_X_Int(pPX, _T("Width"), m_nWidth, 0) is called in the base class
- PX_DPI_X_Int(pPX, _T("Width"), nUnusedWidth, 0) is called again in CXTPControlComboBox::DoPropExchange
Now writing is buggy:
- the base class (CXTPControl) writes e.g. Width=150 into xml
- the derived class (CXTPControlComboBox) writes Width=0 into xml and... gone is the 150

My guess is the code in the derived class should only be called in the read case (IsLoading=true)

I would appreciate it very much if the bug was fixed in the next version.

Thank you and best regards,
Michael

We have seen a similar issue with 18.2.0 where ComboBoxes have almost no width.