complexlogic
10-second freeze after interaction
I created some sidebar commands that do not launch anything or turn the system on or off, I want to use the sidebar to send request to Home Assistant to toggle some lights.
It works, but I've discovered that big-launcher seems to ignore input for exactly 10 seconds after a menu item is selected. I'm guessing this is by design to prevent accidental duplicate inputs? I'm assuming it does this with all inputs, but I've never noticed before because all my other menu items either launch something else or turn the PC off.
One way to bypass this that I've found is to move focus to another app and then move focus back to big-launcher.
If the input freeze is necessary, could we perhaps have the option to disable it per-menu-item, maybe with an option in layout.xml?
Notes about my setup, I am running big-launcher on NixOS with i3. I tested this with a curl command as well as a simple pwd.
You are correct. The idea is that some applications may take longer to start than others. For some that take longer, the user may get impatient and try to click it a second time, leading to a duplicate launch.
I'll consider adding a disabling option in the future.
The way to do this is with the :fork special command. You use it as :fork [CMD], which will cause [CMD] to be passed through to your system shell. The launcher will not track the new process, and there will be no pause for input.
In your trivial example for pwd, you would implement this as :fork pwd.