bug - applying change to smart stack parameters
When you make a change to the smart stack parameters and hit Save, it will save the new parameters, but it does not apply them to the results displayed. .
To get the changes to apply, after saving a change, I then go back into the parameters editing panel and just click Cancel. Then the changes you made before will be applied to the results displayed. Or you can change a filter to get the displayed notes to update, but that is not as convenient if you don't really want to change your filter (two steps, to change it, and then change it back).
Could you just fix it so that the results of the new saved parameters are immediately applied to the displayed notes?
|?||Show this help|
|ESC||Blurs the current field|
|r||Focus the comment reply box|
|^ + ↩||Submit the comment|
You can use
Command ⌘ instead of
Control ^ on Mac
Support Staff 1 Posted by drewmccormack on 06 Feb, 2020 09:59 AM
It's possible it is taking a few seconds to "clear" the displayed notes. If you wait 10 seconds, switch to another stack, and back again, do the correct notes display?
2 Posted by zeppo on 06 Feb, 2020 02:01 PM
Waiting 10 seconds, or even 30, doesn't make any difference.
Switching to another stack and back can be done without waiting 10 seconds to accomplish the application of the changes to what is displayed. It typically works just as well as going back in and clicking Cancel, but after using the app for a while (and with something else running) it starts to slow down, and moving in and out of stacks becomes slower, so my method of hitting Cancel was a little quicker for me. But on a fresh boot of the 2015 macbook (8 DDR3) changing stacks is a step quicker approach.
Odd thing is that occasionally it does refresh the display upon hitting Save. Maybe one out of 7 times. Haven't figured out why that might be. Although, this morning as I test it, its not doing this at all. Something to do with a buffer?
At any rate, maybe there's some reason why you don't want to have the changes applied when hitting Save?
Support Staff 3 Posted by drewmccormack on 06 Feb, 2020 02:07 PM
I think it is very likely caching, ie buffering. A smart stack is quite slow, in the sense that it has to search the whole library with your rules each time. So we store what is found, and only update that occasionally. Maybe the update is not going through when the rules change. Clearly that is a time when it should throw away the cache.
4 Posted by zeppo on 06 Feb, 2020 02:36 PM
So you can add a fix so that it throws away the cache?
Support Staff 5 Posted by drewmccormack on 06 Feb, 2020 02:52 PM
Sure. If that is the problem, we can do that.