Report errors

edited February 12 in General
When the RB source deliberately raises errors in code like

raise EInvalidPropertyError.Create(ppLoadStr(342));

in procedure TppStretchable.SetShiftRelativeTo(aStretchable:
TppStretchable); would be great if there could be better info for debugging, e.g.
the rogue aStretchable.Username value.

Just had a customer that managed to parent a DBRichText in a stretchable
region that had its shiftRelativeTo set to the DBRichText. They had
spent hours designing the report and didn't want to lose work. I could
only fix it up by temporarily putting a showmessage in the above routine
to work out which control was faulty.

This discussion has been closed.