Re: some shortcomings on assigning events after creation
Posted: Thu May 23, 2019 4:17 pm
Hi,
If you need to assign events after the browser creation create a new class that inherits from TChromium and override the following functions :
CEF applications usually create handlers only when really needed because creating some of them can decrease the performance of your app and in general it's more efficient.
For example, the audio handler triggers its events many times per second even when there's no sound and that means one CPU core is constantly working.
If you need to assign events after the browser creation create a new class that inherits from TChromium and override the following functions :
- MustCreateLoadHandler
- MustCreateFocusHandler
- MustCreateContextMenuHandler
- MustCreateDialogHandler
- MustCreateKeyboardHandler
- MustCreateDisplayHandler
- MustCreateDownloadHandler
- MustCreateJsDialogHandler
- MustCreateDragHandler
- MustCreateFindHandler
- MustCreateAudioHandler
CEF applications usually create handlers only when really needed because creating some of them can decrease the performance of your app and in general it's more efficient.
For example, the audio handler triggers its events many times per second even when there's no sound and that means one CPU core is constantly working.