You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Search results to appear nearly instantly while typing
Current Behavior
As of 0.15.0 there appears to be a 350 ms delay after typing is complete before a search is even started.
Possible Solution
With the caveat that I have not experienced the "freeze-like" that the new behavior was meant to address, my preference would be to use a throttle instead of debounce. Also I feel that 350 ms is far too long.
Speaking in terms of lodash's throttle my preference would be 50 ms with leading: false and trailing: true. That means that the first search would not be started until 50 ms after the user started typing, and if they keep typing they will see results every 50 ms.
Another alternative would simply be to make the current debounce behavior configurable.
Steps to Reproduce (for bugs)
Trigger lxqt-runner
Type "firefox" (or another installed program) taking a short pause after each letter
Expected: "firefox" to be displayed as a result while still typing
Actual: no results displayed until after typing is finished
Context
I think this is covered in the possible solution section, but basically I want to launch programs faster.
System Information
Distribution & Version: Arch Linux
Kernel: Linux jdesktop 5.6.13-arch1-1 Update dialog.cpp (for RGBA) #1 SMP PREEMPT Thu, 14 May 2020 06:52:53 +0000 x86_64 GNU/Linux
Qt Version: local/qt4 4.8.7-28
liblxqt Version: local/liblxqt 0.15.0-2
lxqt-build-tools Version: Not sure what package this would be
Expected Behavior
Search results to appear nearly instantly while typing
Current Behavior
As of 0.15.0 there appears to be a 350 ms delay after typing is complete before a search is even started.
Possible Solution
With the caveat that I have not experienced the "freeze-like" that the new behavior was meant to address, my preference would be to use a throttle instead of debounce. Also I feel that 350 ms is far too long.
Speaking in terms of lodash's throttle my preference would be 50 ms with
leading: false
andtrailing: true
. That means that the first search would not be started until 50 ms after the user started typing, and if they keep typing they will see results every 50 ms.Another alternative would simply be to make the current debounce behavior configurable.
Steps to Reproduce (for bugs)
Expected: "firefox" to be displayed as a result while still typing
Actual: no results displayed until after typing is finished
Context
I think this is covered in the possible solution section, but basically I want to launch programs faster.
System Information
The text was updated successfully, but these errors were encountered: