Library Folders to multi-drop into Snippets ala Phrase Pools

Posted Wed, 2024-01-24 - 22:35

Hi,

Wonderfully, when we have a Phrase Pool with multiple chunks in it, we can drag it to a Snippets Group and all the chunks roll right into the Group up to the size of the Snippets matrix. I love it!

Sometimes though, the way the source Library was built winds up with individual items which are not Phrase Pools full of chunk. These then have to be dragged one-by-one into Snippets.

Now if we had general multi-select from the Library and could drop the multi-selection onto a Snippets Group for the same result then that would be fine.

Alternatively, if Library Folders, which we do control the creation and contents of, could be dropped on a Snippets Group just like Phrase Pools, that would work well too.

housekeeper

Thu, 2024-01-25 - 08:20 Permalink

A snippet group can only accept a drop of phrases for one instrument at a time. Multiple pools can have different instruments.

sj1

Thu, 2024-01-25 - 14:34 Permalink

A snippet group can only accept a drop of phrases for one instrument at a time. Multiple pools can have different instruments.

OK, I see that dropping phrases containing more than one instrument onto a Snippet Group, as currently implemented, would not make sense.

However, simply assuming that any potential multi-drop may contain that problem and therefore disallowing all multi-drops is quite a limitation!

In my case (so far) all my wished-for multi-drops are from single-instrument libraries, and so would not in-themselves create such a problem.

IOW, I suggest that a better alternative to disallowing all multi-drops would be to have the program check to see that a multi-drop is of a single-instrument nature (and therefore valid/OK) before actually doing it.

One idea would be to allow a Library to be marked as a single-instrument library. In that case, a multi-drop from it onto a Snippet Group would always always valid. The designation of a single-instrument library for this purpose would, I suppose, have to be done by the program so the user's can't lie about it!

unless we also do -

Another idea would be to quickly walk the list of any candidate multi-drops at the time of the drop and either proceed if all the items reference a single instrument, else pop a dialog and explain the issue if they do not.

All this is in service of what seems to the user like it should naturally "just happen". Of course, there's much effort required behind-the-curtain to make that so!