Migrating from DCEF3, trying again

[salvadordf]

Hi,

I've never done that but I would try to set absolute paths for the CEF binaries in the GlobalCEFApp properties.

Edit : This may be a consequence of using LoadLibraryEx to load the DLLs from custom directories. Another solution would be to register your app in the registry as the default app for a custom file extension or protocol. You would only have to open an empty file with that extension and windows would execute your app without problems.

[thefunkyjoint]

Hi,

I've never done that but I would try to set absolute paths for the CEF binaries in the GlobalCEFApp properties.

Edit : This may be a consequence of using LoadLibraryEx to load the DLLs from custom directories. Another solution would be to register your app in the registry as the default app for a custom file extension or protocol. You would only have to open an empty file with that extension and windows would execute your app without problems.

The 'chdir' really did the trick. Maybe you would consider to do it inside the component source code, to avoid this problem in future versions.

Here is my code :

chdir(extractfiledir(paramstr(0)));

Thanks !

[salvadordf]

Thanks!

I just added your code to TCefApplication.

Your code works in my local tests but I can't test all the possible combinations of library locations so I also added the TCefApplication.SetCurrentDir property to enable the chdir command.

[thefunkyjoint]

Thanks!

I just added your code to TCefApplication.

Your code works in my local tests but I can't test all the possible combinations of library locations so I also added the TCefApplication.SetCurrentDir property to enable the chdir command.

Great ! I'm glad to contribute

[430am]

Thanks!

I just added your code to TCefApplication.

Your code works in my local tests but I can't test all the possible combinations of library locations so I also added the TCefApplication.SetCurrentDir property to enable the chdir command.

I've noticed a small issue with this, it would need to be done in or before the TCefApplication.CheckCEFLibrary function since at least in my case, the check fails when the working directory is different from the file path. I can get around it by disabling the file check but the checking would be nice to keep.

In my case this issue came up because my software can be launched from a custom protocol handler and then the working directory seems to be either system32 or user home directory. Otherwise my migration from DCEF3 has been surprisingly painless

[salvadordf]

I've noticed a small issue with this, it would need to be done in or before the TCefApplication.CheckCEFLibrary function since at least in my case, the check fails when the working directory is different from the file path. I can get around it by disabling the file check but the checking would be nice to keep.
In my case this issue came up because my software can be launched from a custom protocol handler and then the working directory seems to be either system32 or user home directory. Otherwise my migration from DCEF3 has been surprisingly painless

I'm glad all went well in your migration.

Disable the checking and call CheckResources, CheckLocales and CheckDLLs manually with your custom directory.
Those functions are defined in uCEFMiscFunctions.pas

[430am]

I've noticed a small issue with this, it would need to be done in or before the TCefApplication.CheckCEFLibrary function since at least in my case, the check fails when the working directory is different from the file path. I can get around it by disabling the file check but the checking would be nice to keep.
In my case this issue came up because my software can be launched from a custom protocol handler and then the working directory seems to be either system32 or user home directory. Otherwise my migration from DCEF3 has been surprisingly painless

I'm glad all went well in your migration.

Disable the checking and call CheckResources, CheckLocales and CheckDLLs manually with your custom directory.
Those functions are defined in uCEFMiscFunctions.pas

Oh, I didn't see those functions but I have an idea for a PR that'd fix this on the library side. I have my system setup so that the CEF3 resources are always with the binary and I'm trying to avoid specifying any directories in the code since this just means more headaches to separate between development and production.

[salvadordf]

The PR was just merged!

Thanks!!!