Should we really hard code this? I’m not sure the GPU would actually be used much, but I really don’t know for sure. It might be, for example, for videos on our website.
I wonder if this should be a runtime config option (if possible), or a command line option.
We can make it configurable by performing the following changes:
Add a switch control in the configure dialog labeled 'Disable GPU hardware acceleration'. By default its value is False.
Will create a config option in "runtime_config.json" like other options port, timeout, etc...
When the user would like to disable the GPU, they will update the switch control and it needs a restart of pgAdmin anyway.
We will update the package.json file like "chromium-args": "--disable-popup-blocking --disable-gpu", and restart the pgAdmin.
If the above seems OK then @Nikhil you can start working on the above changes.
Hmm, no, we can't do that. First, it would invalidate the appbundle signature on macOS, and secondly, on most OS's it would require root privileges to modify an installed file.
Is there no way of setting it from code at startup?
