Thank you … 
Let me know, when you think it’s ready to be merged
Hard to say.
From what I’m able to test this works fine, and the logic is sound (I think), but I don’t have more cases to test it with.
Since this is an optional addition, the risk is relatively low - so if from your review the conditionals for when it executes are ok and normal flow is not disrupted when it’s disabled, I think it’s mergeable. If something is off with it, people can just leave it disabled until it’s patched.
I’m not sure if we’re going to get some volunteers to test it otherwise…
1 Like
I’ve been running this branch locally this week, and I think it can be merged.
If we could get a build out of it, I could “hint” 
some of our staff to switch to this (on local machines) for further data.
1 Like
Its up here
1 Like
Thanks, will test it next week with our devs from the official build, and if everything will look fine will move it to our citrix-test environment for non-dev testing later.
Weird that I didn’t get a github notification that it was merged, will need to check the settings there.
And sorry for the dumb rename-not-everywhere error, didn’t notice I didn’t commit the last part…
And now the weekend
Also, marking this one as solved, it has gone for long enough 
1 Like
This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.