XXHighEnd

Ultimate Audio Playback => XXHighEnd Support => Topic started by: charliemb on May 19, 2018, 08:16:48 pm



Title: How to Shift-Click in 2.10?
Post by: charliemb on May 19, 2018, 08:16:48 pm
Hi Peter

2.10 sounds great.  Thanks.

I use a traditional keyboard with a track-pad on it as my method of UI.  So the keyboard has mouse-click buttons and I can Ctrl-click on various tracks or alternatively click first on one track and Shift-click on a later track to get a range.

Prior to v2.10,  clicking on track 1 and then Shift-click on track 7 plays tracks 1-7 in order.
Now with 2.10, clicking on track 1 and then Shift-click on track 7 plays tracks in this odd order: 1,7,2,3,4,5,6.

Congratulations!

How do I get the standard behavior back?

Thanks

P.S.  I wouldn't bother you with this except that Ctrl-clicking each individual track in order is hard with my particular keyboard/pad.


Title: Re: How to Shift-Click in 2.10?
Post by: PeterSt on May 20, 2018, 08:11:37 am
Hi there Charlie,

Although I didn't realize that this was the net workout of the new selection mechanism, yes, that is how it technically would work. And I see, not the most convenient for someone with a "normal" keyboard.
Call it a bug as of now.

Why "we" may not notice is because we don't use a keyboard at all (only touch screen) and the changes have been applied for exactly that situation because with a touch screen the whole implied Windows feature isn't available in the first place (but if it is, someone is going to tell me). So this is how the "Select" new option in the context (rightclick) menu on the tracks come in ... (see Release Notes of 2.10). As a work around you can use that just the same, although it surely would be less convenient than the direct shift-click as how you (can) apply it. But for you it may serve as a temporary solution until the next version.

Btw, I thought I covered for this, but the whole application is quite complex, so it probably got undone under way somewhere. Similarly I myself can incur for quite some more bugs in this realm, but this is what I expected (and announced).

Kind regards and thank you for your sharpness (as usual),
Peter