I see what you're saying. How about assigning scroll up to both select primary and secondary. I'm not at home atm so I can't test it, its just a thought
@fragnstein wrote:I see what you're saying. How about assigning scroll up to both select primary and secondary. I'm not at home atm so I can't test it, its just a thought
@fragnstein Hmm. I am not sure exactly what would happen (or if it would even allow me to bind both actions to the same input like that), but I am fairly certain it would not resolve the issue I am describing. (It would still leave me with nothing to bind "scroll-down" to.)
Look at it this way: If I just bind "cycle primary" to "scroll-up", it does already continuously swap back & forth between primary/secondary ONLY just by virtue of continuously scrolling up, which is what I want it to do.
But, that's only half the story.
Again, the issue here is that the "cycle secondary" keybind was removed, which means there is nothing for me to bind "scroll-down" to, to allow the same behavior as "scroll-up".
