Disclosure Statement: This site contains affiliate links, which means that I may receive a commission if you make a purchase using these links. As an eBay Partner, I earn from qualifying purchases.
If you find these projects useful please consider becoming a sponsor with Patreon, GitHub or Liberapay.
I just uploaded a new version of CEF4Delphi and this is what's new :
Update to CEF 3.3538.1852.gcb937fc.
The issue #139 has been fixed. Read the comments in GitHub for more details. If you have any issue, you can disable this fix by setting the new GlobalCEFApp.DestroyAppWindows property to FALSE. https://github.com/salvadordf/CEF4Delphi/issues/139
Added a LoadHandler in the render process. Now you can use the GlobalCEFApp.OnLoadingStateChange, GlobalCEFApp.OnLoadStart, GlobalCEFApp.OnLoadEnd and GlobalCEFApp.OnLoadError events in the render process.
The fix of issue #139 doesn't work when I try to use External Message Pump. Even if I just create a TCEFWorkScheduler object it's broke Excel starting speed.
For my application very important to use External Message Pump. Is there any way to fix bug and use single EXE file?
P.S. ExternalPumpBrowser demo has same problem.
Last edited by xpert13 on Sun Nov 18, 2018 1:17 pm, edited 1 time in total.
And I don't know why, but Chromium works fine too. As I can see this window created for CEF_PUMPHAVEWORK message but even if it doesn't exist somehow application works.
TCEFWorkScheduler calls AllocateHWnd to receive the CEF_PUMPHAVEWORK message and schedule the calls to DoMessageLoopWork. Commenting the AllocateHWnd line will degrade the browser performance.
I'll try to modify WndProc to reply correctly to the WM_DDE_INITIATE message Excel sends... as soon as I have time...
salvadordf wrote: Mon Nov 19, 2018 6:27 pm
...now that I think of it... perhaps the solution is not creating TCEFWorkScheduler when GlobalCEFApp.ProcessType isn't ptBrowser.
It did not help. I have already tried this option. In this case WndProc didn't receive WM_DDE_INITIATE but Excel still runs slowly.