AV caused by TppDesignSelectionController.GetDefaultPropValue
Hi,
while updating from RB9 to RB10 I ran across the following AV which can be
caused by TppDesignSelectionController.GetDefaultPropValue in
ppDesignSelectionController if you select a component in the designer and
that component's default property is an ordinal.
If DefaultPropEditType is etValueList then TraRTTI.GetPropValue is called
passing lOrdValue which is a Byte. The AV is caused because GetPropValue
assigns an Integer to that address and that overwrites the stack, namely the
aValueList parameter. After GetPropValue returns that list is accessed and
the AV is generated. The fix obviously is to declare lOrdValue as Integer
instead of Byte.
Regards
--
Andreas Puhlmann
while updating from RB9 to RB10 I ran across the following AV which can be
caused by TppDesignSelectionController.GetDefaultPropValue in
ppDesignSelectionController if you select a component in the designer and
that component's default property is an ordinal.
If DefaultPropEditType is etValueList then TraRTTI.GetPropValue is called
passing lOrdValue which is a Byte. The AV is caused because GetPropValue
assigns an Integer to that address and that overwrites the stack, namely the
aValueList parameter. After GetPropValue returns that list is accessed and
the AV is generated. The fix obviously is to declare lOrdValue as Integer
instead of Byte.
Regards
--
Andreas Puhlmann
This discussion has been closed.
Comments
Which exact version of ReportBuilder are you currently using? Are you able
to recreate the AV at design time and runtime? If so, please let me know
the exact steps I can take to see the error on my machine and I will work on
a solution.
--
Regards,
Nico Cizik
Digital Metaphors
http://www.digital-metaphors.com
Nico Cizik
Digital Metaphors
http://www.digital-metaphors.com
I'm using RB 10.06 downloaded last night - with D2007.
I saw it at runtime using one of my custom RCL components.
I don't have exact steps especially not ones which don't involve my custom
components.
Have you had a look at the source? I think I described the bogus behaviour
pretty extensively, so even if you can't produce an AV the error in the code
should be obvious.
--
Andreas Puhlmann