|
Originally Posted by Scylla
|
|
I set up on my Buttons menu for buttons 1-4 to correspond with MortButtons 1-4. I set 3 applications for #1, 3 apps for #2, 1 app for #3, and 1 app for #4.
|
If you're using only one app for a button, it's better to assign it directly. Otherwise all that MortButtons would do is showing a menu with one entry and thus delaying the start of that application.
|
Quote:
|
|
They stop working the second or third time I use them and when I look in the MB settings, no apps are assigned to those keys. What's happening here?
|
Strange... Maybe there's a bug there. It's not too common that there's only one app per button...
|
Quote:
|
|
Also, the setup is confusing. No real direction to it. And the documentation for 1.0 is not clear to me.
|
The principle is quite easy. First of all, you should realize MortButtons is NOT a button manager like VITO or PowerButton (that's why I think about renaming). It's just a menu tool that's optimized for button usage, since it allows to select an entry with multiple presses of an application button (and timeout).
You've got five menus available which you can assign to your application buttons (you can also assing the menu "MortButton1" to the 5th button if you want to...).
Btw, you can lauch the MortButtons menus with any button manager (like VITO), too.
|
Quote:
|
|
What is "MortTasks"?
|
It's a special menu, listing all currently running programs. I.e. if assigned to a button, it allows something like Alt-Tab in Windows.