Hi,
It is common practise to have protected virtual OnEventName methods for all events raised on a non sealed class.
Unfortunately RadControls do not follow this convention, which means that should you want to derive from some RadControl and handle one or more events, you need to subscribe to the events as would a normal consumer of the event.
This is bad practise as it leaves you with no control over when your handling is performed in relation to other event subscribers.
I would hope that RadControls in future versions of the Suite will follow the proper convention.
Thanks,
Thomas Scheelhardt
It is common practise to have protected virtual OnEventName methods for all events raised on a non sealed class.
Unfortunately RadControls do not follow this convention, which means that should you want to derive from some RadControl and handle one or more events, you need to subscribe to the events as would a normal consumer of the event.
This is bad practise as it leaves you with no control over when your handling is performed in relation to other event subscribers.
I would hope that RadControls in future versions of the Suite will follow the proper convention.
Thanks,
Thomas Scheelhardt