|
List Info
Thread: code generation (parent . . . )
|
|
| code generation (parent . . . ) |
|
2006-03-20 16:52:53 |
|
--- In anthemion-devtools@yahoogroups.com, "Alan F. Larimer, Jr."
<alarimer ...> wrote:
>
> --- In anthemion-devtools@yahoogroups.com, "ddotedotsdot"
> <dsilvia> wrote:
> >
> > --- In anthemion-devtools@yahoogroups.com, "Alan F. Larimer, Jr."
> > <alarimer> wrote:
> > >
> > > Is there any reason that DB passes "NULL" instead of "this" as the
> > > parameter for parent when creating a dialog? Thanx.
> > >
> > > --Alan
> > >
> >
> > Yes, the reason is contained in the documentation for wxWidgets. If a
> > dialog or a frame is the "Top Window", it has no parent and the ID of
> > the parent is "NULL".
> >
> > HTH,
> > Dave S.
> >
> > P.S. It's also a curious bit of incest to be your own parent!;)
> >
>
> I understand that if it is the top-level widget, but if the top-level
> is calling a user-created dialog, why not pass "this" as the parent?
>
> --Alan
>
Ah, yes! So, actually, your question is "Why does DB only provide for
creation of top level frames and dialogs?". I've posited the same
question in the past, but got no answer.
Yes, to me it makes sense for applications to have child frames and
dialogs, but this seems to be a wxWidgets religious argument, so, for
myself, when using DB or other wxWidgets builders that subscribe to
the restriction, I'm forced to hand code.
Sorry, but that's the best I can advise.
thx,
Dave S.
|
[1]
|
|
|
about | contact Other archives ( Real Estate discussion Medical topics )
|