Jeff Lord
Jeff Lord
> let's rephrase the description of the option as with as it is now users might expect that it'll delay everything 100% agree, something needs to be updated. Here's my...
>Actually, search throttle is supposed to throttle the search for every plugin. It acts like a "wait for more input" before searching. Does this PR change that Yes exactly, that's...
I understand. But if we delay both we are left with the fact that the delay causes this current issue, which seems like somewhat bad side effect. So, if we...
I did a quick test using a fixed 20% ratio (instead of a new setting). So, at the default 150ms for the delay, that would be 150ms throttle for the...
Yes @jaimecbernardo, I agree a setting for each would be best, even though there is more to document/understand. However, I feel like it's a good time to bite the bullet...
@jaimecbernardo I think you nailed it. Yes, debounce is more correct. (We can take that up with the System.Reactive team LOL). We could avoid it all by calling it something...
I am marking this "ready to review" now but I am sure things will need to be change, maybe a lot.
@Aaron-Junker, @crutkas any time to give this PR a look?
> Some ui suggestions Grrrr, xaml updates... my evil nemesis. I did try doing it just about how you suggested, and it did not go well. But you're right, and...
OK, I think the expander just won't work in this case because of how restrictive it is. We have too much that needs to always be there. I will go...