Autobranding via den doesnt work when changing den via cfg file swap
I have tried using the wayk-now.bat to update some settings but apparently disabling passwords, changing the control mode and setting the den didnt work so I gave up and wrote a cfg to just overwrite what was there but apparently the wayk client doesnt seem to load any branding when changing the den by doing so.
you have to go into the settings and click okay once for that to happen, apparently
All Comments (3)
Hello
I'm not sure I completely follow along - but a lot of things won't "apply" when set directly through the .cfg or on command-line without rebooting the application (the Options UI can, in most cases, apply changes directly and prompt you for a restart if it can't). Can you share your wayk-now.bat via PM or email? Are you deploying a standalone .exe or using the .msi? Which .cfg did you update (%appdata% or %programdata%)?
Thanks and best regards,
Richard Markievicz
"but a lot of things won't "apply" when set directly through the .cfg or on command-line without rebooting the application"
I am crazy, I know, but not THAT crazy.
basically it goes as follows:
1) I install wayk (with msi and the following options: complete: icons on both desktop and start menu, usage data and crash reporting are both off, would be awesome to have some msi parameters or whatever, lol)
2) I run a batch file that.
a) gets admin.
b) copy-relaces the global cfg, which doesnt do a lot except disable password and change the den.
3) I start wayk.
I can also close and restart wayk without anything happening in regards to the autobranding.
once I go to options and literally just click OK (which normally should not do much because nothing was changed), I get the "please restart wayk now" and so on notification.
the wayk-now.bat is literally the one that the wayk msi drops into system32 (PATH is a thing, lol) I didnt touch or even look at it, I just went according to the help page to run the wayk-now.bat config and so on.
in my original tries with the wayk-now.bat I also obviously closed the wayk now application (although no idea what the service has been doing in the meantime, no idea whether that thing blocks stuff. there is no output from the bat.
Hello
Ok - when I read wayk-now.bat, I was thinking it was something custom.
If you install with the .msi, and then make changes to the global configuration (either with `wayk-now config --global` or by editing WaykNow.cfg), you'll need to restart the service (i.e. `net stop wayknowservice` and `net start wayknowservice`). The .msi itself does invoke wayk-now to set some configuration, but it does it before the service is started. The Options UI kicks the service to reload certain configuration changes, but any changes made outside the UI you'll need to do that manually.
Thanks and kind regards,
Richard Markievicz