FActiveDefaultControl points at destroyed control
Original Reporter info from Mantis: djenkins @dfjenkins
-
Reporter name: David Jenkins
Original Reporter info from Mantis: djenkins @dfjenkins
- Reporter name: David Jenkins
Description:
FActiveDefaultControl management.
For buttons the SetActiveDefaultControl is only nil'd with a call to WMKillFocus. Carbon does not pass a KillFocus event back when control is destroyed. So we were seeing a case where FActiveDefaultControl was pointing to a destroyed TButton.
Suggested fix is connecting the Form and FActiveDefaultControl with a FreeNotification to make sure that FActiveDefaultControl is set to nil if control it is pointing at is destroyed.
Patch against 36681 is attached
Mantis conversion info:
- Mantis ID: 21735
- Version: 0.9.30.5 (SVN)
- Fixed in version: 1.1 (SVN)
- Fixed in revision: 36806 (#a34725fc)
- Monitored by: » luizamerico (Luiz Americo), » @dfjenkins (David Jenkins)