FYI...It was one of my dependent libraries needed RTTI turned on.
Have to love those Microsoft compilers.
From: Kevin Banks [mailto:kbanks@...]
Sent: Saturday, February 19, 2005 9:40 AM
To: Lyle Johnson
Subject: RE: [Foxgui-users]dynamic_cast popping...
I put the call in an exception handler and it is throwing an exception. In
the debugger it "pops" on the first cast. I assume it is reporting an
invalid cast of some form (I didn't try to catch "bad_cast"). I confirmed
RTTI is turned on (I'm just running out of the box project file). Perhaps I
have a dependent library where RTTI is now required?
All of my 50+ applications have been working for the last three years. This
is the first time I have been broken by an upgrade.
From: Lyle Johnson [mailto:lyle@...]
Sent: Friday, February 18, 2005 9:32 PM
To: Kevin Banks
Subject: Re: [Foxgui-users]dynamic_cast popping...
On Feb 18, 2005, at 8:16 PM, Kevin Banks wrote:
> The child object is of type FXToolBarGrip but the call pops on the
> first dynamic_cast.
> Running VS6 under Windows2K.
I know the question is directed to Jeroen, but I'm curious about what
you mean when you say the "call pops" on the first dynamic_cast<>. The
statement in question:
if (dynamic_cast<FXSeparator*>(child) ||
is an OR, so even if the first dynamic_cast<> fails (and thus returns
zero), if the second one succeeds (and returns a non-zero), it should
still execute the assignment at the end.
What is it that is (or isn't happening) that you were expecting to (or
to not) happen? Did you compile your FOX with RTTI enabled? I know that
this was optional in Visual C++ 6.0, don't know if it's still that way