[wx-dev] Re: CVS: [ABX] wxWidgets/src/univ stdrend.cpp, 1.13, 1.14

[ABX]

Vadim Zeitlin <vadim at wxwindows.org> pisze mi:
> > I'll add longer investigation into my todo.
>
> I strongly suspect there is some real problem elsewhere, this can't be
> due to using ?:.

I think it is somehow related to deeper theory of ?: in C++ which I probably
miss here. My intuition suggested me to test adding copy constructor to
wx/msw/colour.h

    wxColour(const wxColour &clone)
    {
        Set(clone.Red(), clone.Green(), clone.Blue(), clone.Alpha());
    }

and indeed your original code with ?: went fine in the minimal sample startup.
But it again crashed (asserted) in the same place when I opened about dialog
with  probably another route in ?:(?:) taken. Has anyone suggestion what to
test? operator= ? Can we have such copy constructor in
DEFINE_STD_WXCOLOUR_CONSTRUCTORS macro?

ABX