For some controls it's normal, I know that for Combo and Listboxs the frame
work calls PreSubclassWindow no matter how it is created.
AliR.
"AliR (VC++ MVP)" <AliR@online.nospam> wrote in message
news:XFl0i.1672$UU.1304@newssvr19.news.prodigy.net...
Oh I just realized what you were saying. I misunderstood the dynamic
creation part.
It seems as though the combo box doesn't like getting calls to
SetItemHeight for list items in PreSubclassWindow when it is being
created, I doesn't mind SetItemHeight(-1,100).
Anyway, it's not an assert, it's a full blown exception. I tried
catching the excpetion to see what its complaining about couldn't, the
only way I could catch the exception was with catch(...) but I don't know
if there is a way to get execption information with the catch all method.
Anyway I really can think of a solution.
I'm doing two sets
SetItemHeight( 0, abs(lf.lfHeight) + 2 );
SetItemHeight( -1, abs(lf.lfHeight) + 4 );
I guess the first is attempting to set the height of the first element in
the list portion of the combobox. I wonder why this doesn't cause a
problem in the Create method but does in PresubclassWindow? Should
PresubclassWindow be getting called when I'm creating the control outside
of dialog resource?