Re: Please use wxWidgets

In article <EfMCf.8996$NS6.3123@xxxxxxxxxxxxxxxxxxxxxxxxxx>,
phlipcpp@xxxxxxxxx says...
> Gerry Quinn wrote:
>
> > What stops you creating (say) a CButton under the same terms?
>
> I don't know about wxWidgets, but under Tk if you create a button and
> nothing else, the system creates the window to go around it. This is a
> little more than a convenience.
>
> Under the MFC that I remember, you cannot even create a CString unless your
> program includes "afxwin.h", which pulls in a bunch of globals that you must
> satisfy, so you must create a main form, a resource segment, etc. No I have
> never tried CButton but I can't imagine it's better.

You said:
> > Put simply, you can create one wxWidgets object, alone, without creating
> > everything else on the map just to couple to it.

Including headers and globals doesn't create anything. And you don't
need a form or a resource segment to create a CButton. All it needs is
a parent window:

CButton button;
button.Create( "My button", WS_CHILD | WS_VISIBLE, buttonRect,
& parentWnd, buttonID );

Messages relating to the button (e.g. mouse clicks) will now be routed
to the button via its parent, so either or both can handle them.
(Usually the button handles them automatically, for example it displays
different graphics when pressed, while the parent does something about
the fact that the button was clicked by the user.)

Typical uninformed gibberish about MFC.

> These are primarily MS's burdens; they cannot easily upgrade their own
> library without maintaining its endless VendorLockin. So they no longer use
> MFC on their own new projects, despite they invested in it for years.

Would you care to tell us what relevant new projects you mean (they've
obviously been doing some stuff with .NET, though not Vista any more),
and what they use?

- Gerry Quinn

.

Quantcast