Improve Capture One
Request a new feature, or support for a camera/lens that you would like to use in Capture One.
Request a new feature, or support for a camera/lens that you would like to use in Capture One.
What problem do you see this solving?
Capture One always becomes unresponsive when searching, and with 'search as you type' turned on permanently, it's impossible to finish typing a search term without the application becoming unresponsive. If 'search as you type' could be made optional, or if it could be turned off permanently, the search function would be more useful that it currently is.
If Capture One didn't become unresponsive when searching, having 'search as you type' turned on permanently wouldn't be a problem.
When was the last time you were affected by this lack of functionality, or specific tool?
Every time I use the search function.
|
Current workaround
Are you using any workarounds or other solutions to achieve your goals in Capture One? One possible workaround is to type the search term elsewhere, copy it and then paste it into the search field in Capture One, but it would be more convenient not having to do this. |
Indeed, the basic problem is unresponsiveness when searching, but I doubt that this will be fixed any time soon. Turning off 'search as you type' would at least limit the number of times Capture One becomes unresponsive when searching.
You explain it's not due to multiple substrings being searched simultaneously that searching leads to unresponsiveness. Even a single search apparently already does this. Then it's the search operation in of itself causing the issue, not the search as you type implementation. (Of course pausing halfway typing your phrase is problematic). Turning off this feature would not make the single search perform any better.
But I agree it also doesn't really add anything useful unless search performance (or at least ui blocking behaviour) is improved.
How do you mean?
True, but conversely being able to turn it off would also not solve it.
Capture One appears to have a timeout already. If I type "input" fast, I can type the whole word before Capture One becomes unresponsive.
In any case, as long as every search operation causes Capture One to become unresponsive, it makes no sense to have 'search as you type' enabled.
I think this can be fixed by adding a timeout to the search. Only start a search after no keypress has occurred for 500ms. This would prevent searches being started for every substring of the complete string being entered.
Instead of searching for I & In & Inp & Inpu & Input, it would only do a search for Input. This prevents wasting resources on (parallel?) search operations that return data that is never used.