I don't know if this has been brought up before but it has been happening since New Chapter caused the introduction of the toggle solution. I use a recipe that toggle that does not allow me to opt out of filter toggling. I then stop the script when I'm satisfied. Then when I want to run the next recipe or even if I just plain do a manual wiggle (M) or a shake (S), it still toggles!. I don't like toggling in most instances so I then have to close the client and restart to get out of this "locked" toggling function. My only other option is to never run a recipe that does not allow one to opt out of "toggling" (BTW I don't even know if it has been established that you get a lot of time by doing it.
So today I ran GAB Bis Shudder for 3 seconds. And it contaminated my client so that even W and S caused the filters to toggle. So I have to quit the client and start over. A pox on these recipes. Burn them at the stakes.
Recipes. Can't live with em. Can't live without em.
Maybe. But wouldn't it be better to fix the contamination?
It is a bug in how the 'Enable all' and 'Disable all' button code works. If you disable all filters with the X next to them and then re-enable them with the x, the toggle eventually operates as intended again. The bug seems to be in the fact that internally the toggle button does not properly keep track of the state of the X marks.
BUG.
BUMP, this bug (as I describe it above) still persists and is a pain.
@jflat06 tagging you so it gets noticed. I unfortunately cannot change the topic line to '(unresolved) Persistence of "toggling"' @alcor29 maybe you can change this ?
@"Bletchley Park" I can edit the topic name. What would you like me to change it to?
@alcor29 '(unresolved) Persistence of "toggling" '
If you could add '(unresolved)' in front of the original topic then everyone knows it has not been resolved.
Thank you !
