It's workflow Kevin
And removing that function has broken the workflow. If you have a button on a piece of hardware that says "Press here to activate *an example* "
You then remove that functionality with a software update, you are effectively killing off the hardware use with Spark. What happens when you add new SW features, are you going to further remove hardware functions?
My car has a steering wheel, if I upgrade something on my car, I don't expect that upgrade to remove functionality of my steering wheel and force me to engage the cigarette lighter before I'm able to use the steering wheel.
In order to play live I cannot upgrade to Spark 2 as I no longer have *direct* access to my kits. I don't have time to switch another button before I jog through my kits. I'm not saying that using Shift 7 to get to the library is a bad thing, it's a nice shortcut to have.
I would also expect other shortcuts in order to get through the 4 sub menus, but you're running out of keys as it is.
This would work far better if you were to have a preference that specified the sub menu that the library switches to. Currently, when i hit Shift 7 on my HW, the library will go to the last sub menu page I was on, presuming I make the change first, on start up it always defaults to instruments, meaning I have to dig around in the software to alter it's state. I can now choose the kits I want to show and hide (which is a nice feature) but to be able to specify the sub menu the library lands on is imperative if you are going to run with removing that direct access to the kits.
Stu