Minor issue: Custom GUI colors incorrect when launched via command line

English Support for Syncovery on Windows.
Post Reply
» by
Posts: 19
Joined: Mon May 04, 2020 12:42 am

Minor issue: Custom GUI colors incorrect when launched via command line

Post by » by »

I'm currently running Syncovery 9.00e which I know is not the absolute latest, but this issue has been around for a very long time and I highly doubt that it has been corrected over the past couple days.

I have custom colors selected for the main window of Syncovery. When I launch Syncovery the usual way, there is no issue. But when Task Scheduler launches Syncovery, the GUI shows different colors until I interact with the Syncovery window, at which point it begins using my custom colors.

» by
Posts: 19
Joined: Mon May 04, 2020 12:42 am

Re: Minor issue: Custom GUI colors incorrect when launched via command line

Post by » by »

This still occurs in version 9.17.

tobias
Posts: 1639
Joined: Tue Mar 31, 2020 7:37 pm

Re: Minor issue: Custom GUI colors incorrect when launched via command line

Post by tobias »

Hello,
I doubt this will or can be fixed.

You are not supposed to run the Syncovery GUI from Task Scheduler.

You can run Syncovery jobs using the SyncoveryCL.exe command line tool. Please see
https://www.syncovery.com/command-line/

» by
Posts: 19
Joined: Mon May 04, 2020 12:42 am

Re: Minor issue: Custom GUI colors incorrect when launched via command line

Post by » by »

But Syncovery.exe is running under my own user context. All I'm doing is using Task Scheduler to run:

Code: Select all

"C:\Program Files\Syncovery\Syncovery.exe" /O /RUN="1. Windows Images External HDD #1 -> External HDD #2"
When I do the same from a command prompt (parent process cmd.exe) or a Run box (parent process explorer.exe), the same issue occurs. The identity of the parent process does not seem to matter.

tobias
Posts: 1639
Joined: Tue Mar 31, 2020 7:37 pm

Re: Minor issue: Custom GUI colors incorrect when launched via command line

Post by tobias »

Hello,
OK, apparently the /RUN parameter causes this.

I can't fix it very soon, unfortunately. But I will put it on my list.

Post Reply