List of shortcut functions?

[Reincke]

Hello, is there a textual list of all (generic and specific) shortcut functions? I mean easier than by cut&paste from the dialog? This would ease exploring MuLabs functionality and also allow searching for functions of a specific type.
(I guess there is a bunch of functions only available as shortcut. For example I recently "discovered" the "show clipboard" function.)
JR

[MuTools]

Hello, is there a textual list of all (generic and specific) shortcut functions? I mean easier than by cut&paste from the dialog? This would ease exploring MuLabs functionality and also allow searching for functions of a specific type.

When you add a shortcut then the function list lists all functions, so you can see them all there, right?
Also note that, as in every list, you can type the first characters of an item to quickly jump to that item.
That way you can also implicit search around a bit.

(I guess there is a bunch of functions only available as shortcut. For example I recently "discovered" the "show clipboard" function.)

That's correct. To avoid bloating the context menus too much with very specific functions, some functions are only available via a shortcut.

[Reincke]

When you add a shortcut then the function list lists all functions, so you can see them all there, right?

Thanks Jo for your quick reply. Yes, you're right. But that's what I meant with "easier than by cut&paste from the dialog".

Also note that, as in every list, you can type the first characters of an item to quickly jump to that item. That way you can also implicit search around a bit.

For example I tried to explore what function exist relating to racks. OK, there is the related section below "specific" named "Rack". But here you won't find the (generic) function "Focus Next Rack" (a really interesting function!). And also you won't find it by typing "rack" in the list as suggested. Type "Rack" while the list is open and MuLab suggests "Randomize". For the next "exploration" I have to leave the dialog "Add Shortcut" (cancel) and open it again, cause I cannot delete a suggested function .
Another example: I'm just discovering navigation functions to ease my workflow. I would like to find functions which contains certain words in their namens - words like "focus", "next", "previous", "forward", "in", "out".
Do you know what I mean? It's there, but it could be easier.
JR

[pljones]

Would having suggested shortcuts based on substring match rather than prefix match help? You'd get more suggestions and then "Rack" would get "Focus Next Rack".

[Reincke]

A good approach. And it should search in all sections (generic and specific/...).
But how do I get to the next matching function?
JR

[MuTools]

When you add a shortcut then the function list lists all functions, so you can see them all there, right?

Yes, you're right. But that's what I meant with "easier than by cut&paste from the dialog".

I still don't understand this, the whole list is there. Don't know what you mean with copy-paste in this context.

For example I tried to explore what function exist relating to racks. OK, there is the related section below "specific" named "Rack". But here you won't find the (generic) function "Focus Next Rack" (a really interesting function!).

Because it's not a rack function, it's a session function. Because it's the session that contains the main racks, not the rack itself. Hope u see the technical architecture. Nothing to do about that.

And also you won't find it by typing "rack" in the list as suggested.

Agreed on this point.

Do you know what I mean? It's there, but it could be easier.

I've added a note on the wishlist about exporting the Specific list to a text file so that at least you can have a more relaxed look & search on it. Can't promise anything about implementation timing though, currently focused on other aspects.

[Reincke]

I still don't understand this, the whole list is there. Don't know what you mean with copy-paste in this context.

Sorry, have pointed out as "shortcut". I meant making screenshots and copy&paste them (as images) into a file where I can do a better screening and make annotations for further research in MuLab's depths. Admittedly an old-fashioned method.

Because it's not a rack function, it's a session function. Because it's the session that contains the main racks, not the rack itself. Hope u see the technical architecture. Nothing to do about that.

You're right - from a developer's point of view. I'm just a "user" (although I do see the architecture), and I would like to know strange things like "what the heck can I do with racks?" (just one example).

I've added a note on the wishlist about exporting the Specific list to a text file so that at least you can have a more relaxed look & search on it. Can't promise anything about implementation timing though, currently focused on other aspects.

Jo, thank you for the offer, but I don't want to receive a special treatment. I was just asking for handling possibilities. And obviously nobody else seems to need such a function. So from my point of view you may remove it from the wishlist, cause I'm exploring MuLabs functions now with the on-board means. I understood what's possible now in MuLab and what's not, and that's ok.
Thank you for your reply.
JR

[MuTools]

I still don't understand this, the whole list is there. Don't know what you mean with copy-paste in this context.

Sorry, have pointed out as "shortcut". I meant making screenshots and copy&paste them (as images) into a file where I can do a better screening and make annotations for further research in MuLab's depths. Admittedly an old-fashioned method.

Ah i see now, thx for the clarification.

You're right - from a developer's point of view. I'm just a "user" (although I do see the architecture), and I would like to know strange things like "what the heck can I do with racks?" (just one example).

Of course, i understand your pov. And to avoid confusion: The user is much more important than the developer.

Jo, thank you for the offer, but I don't want to receive a special treatment. I was just asking for handling possibilities. And obviously nobody else seems to need such a function. So from my point of view you may remove it from the wishlist, cause I'm exploring MuLabs functions now with the on-board means. I understood what's possible now in MuLab and what's not, and that's ok. Thank you for your reply.

I'll keep it on the WL cause it may make sense, also towards the docs. I've even extended that note a bit. But we'll see how and when it works out. Currently concentrated on something else, MUX related.