[Bug] chrlauncher not passing commandline arguments to chrome unless in chrlauncher.ini

[FlamingPhoenix40]

Checklist

• [X] I have used the search function to see if someone else has already submitted the same bug report.
• [X] I will describe the problem with as much detail as possible.

App version

2.6

Windows version

Windows 10

Steps to reproduce

1. Open Windows' Run dialogue (win+r)
2. Try to launch chrlauncher with a commandline argument; "patch_to_chrlauncher.exe --incognito" or "patch_to_chrlauncher.exe --app=someurl" for example
3. OR: create shortcut file where target is: "patch_to_chrlauncher.exe --incognito"

Expected behavior

Normally after reading through the documentation, FAQ and other older issues, I would expect Chromium to launch with the commandline arguments active.

Actual behavior

Chromium launches while ignoring the commandline arguments. I.e. incognito and/or app-mode are not started.

It does work if I put said commandline arguments in chrlauncher.ini at the "ChromiumCommandLine=" line. However, I don't want the commandline options to be global and be always used. I want to choose when to use them, and I would prefer to do so with a simple shortcut, and not by having to edit the ini file every time.

Logs

No response