16
Applications / Re: Test build of dooble with qt5
« on: May 12, 2022, 02:11:09 am »
Hi Doug,
Not using authentication. Testing it earlier showed the best thing was to authenticate right after opening the browser. All it does is encrypt part of your profile.
There are a bunch of command line options for the webengine, linked from the documentation, which IIRC includes an option for different profiles. Simpler might be to change %HOME%, either with a script or using the program properties, could have a couple of program objects.
Hi Remy, the print preview and printing are known issues.
The timing thing sounds like worth opening an issue for, especially if you can reduce it to a small testcase.
Most of my packages are still i686 and Dooble is stable here.
Not using authentication. Testing it earlier showed the best thing was to authenticate right after opening the browser. All it does is encrypt part of your profile.
There are a bunch of command line options for the webengine, linked from the documentation, which IIRC includes an option for different profiles. Simpler might be to change %HOME%, either with a script or using the program properties, could have a couple of program objects.
Hi Remy, the print preview and printing are known issues.
The timing thing sounds like worth opening an issue for, especially if you can reduce it to a small testcase.
Most of my packages are still i686 and Dooble is stable here.