Quote:
Originally Posted by kranu
IMO, the command should be executed as soon as the first statusbar message is shown, not when the success message is shown.
|
the first statusbar message indicates that the hotkey sequence was recognized,
accepted and that the corresponding action/command will be attempted.
The success/failure message indicates the result of this attempt. The moment
when this message gets shown depends on the nature of the action.
For shell commands running in detached mode (xxx = !yyy
&) you'll see this
message immediately. If there's no
& at the end of the action string, then
the success/failure message will be shown only when the 'action' finishes.
Making the status_message/running_action synchronous guarantees that the
status message wouldn't interfere with any other screen output.
And this is the main reason why it is implemented this way.
Quote:
Originally Posted by kranu
I have also suggested to make a binary to change the statusbar message:
|
I think the best solution would be suppressing launchpad status messages and
implementing a standalone "banner generator" which could be run from a command line.
This will allow any custom application (including the launchpad) to effortlessly
show short screen messages, when needed.