1) Click track #1
2) CTRL+DownArrowx2
3) SHIFT+UpArrow - #1 + #3 selected
4) SHIFT+UpArrow
Expected: track #3 remains selected.
Observed: track #3 dropped from selection.
EDIT(TC) Tracked at http://www.ventismedia.com/mantis/view.php?id=6810
1299 Tracklist SHIFT+Up/Down arrow can drop tracks [6810]
Moderator: Gurus
Re: 1299 Tracklist SHIFT+Up/Down arrow can drop tracks [---
I can confirm.
Seven Ultimate X64 SP1 / Sansa Clip 2go (with RockBox)
Re: 1299 Tracklist SHIFT+Up/Down arrow can drop tracks [---
Although this does happen I think it's correct that it does. Shift+Arrow is used to select/deselect tracks.
Your sequence should be:
1) Click track #1
2) CTRL+DownArrowx2
3) SHIFT+UpArrow - #1 + #3 selected
4) Ctrl+UpArrow
Your sequence should be:
1) Click track #1
2) CTRL+DownArrowx2
3) SHIFT+UpArrow - #1 + #3 selected
4) Ctrl+UpArrow
Download MediaMonkey ♪ License ♪ Knowledge Base ♪ MediaMonkey for Windows 2024 Help ♪ MediaMonkey for Android Help
Lowlander (MediaMonkey user since 2003)
Lowlander (MediaMonkey user since 2003)
Re: 1299 Tracklist SHIFT+Up/Down arrow can drop tracks [---
Thanks for the confirmation, both.
I see no basis for that. I think the expectation is that it work like standard Windows programs i.e. moving away from the contiguous selection start extends the selection. Instead, in the case reported, moving down does that, but moving up does not. Furthermore I think this is very unlikely to be Devs' intent. Especially considering the many other selection-related bugs I have found, reported here.Lowlander wrote:Although this does happen I think it's correct that it does.
Chris
-
- Posts: 2283
- Joined: Tue Aug 29, 2006 1:09 pm
- Location: Kansas City, Missouri, United States
Re: 1299 Tracklist SHIFT+Up/Down arrow can drop tracks [---
Well with Windows (Vista), Explorer doesn't function like the current MM behavior or your expected behavior. Following your steps, it results in only the originally selected item still selected. As the clicked item is selected, CTRL+Down moves it down twice, SHIFT+Up selects the clicked item and the second item, and SHIFT+Up again returns it to only the original selection. I would agree with Lowlander on this one. Using Shift, the typical behavior is that anything between the original selection and whatever is selected while using Shift is selected (thus, if you select a file, then hold shift and go down twice and up four times, only the original file and the two above it are selected, not all five tracks).
Re: 1299 Tracklist SHIFT+Up/Down arrow can drop tracks [---
Windows Explorer on Windows XP will in Step 4 select all tracks between first highlighted and current selected track (not including the current selected track). This would not achieve what you're looking for. My suggestion would work for you though and is already possible.
Download MediaMonkey ♪ License ♪ Knowledge Base ♪ MediaMonkey for Windows 2024 Help ♪ MediaMonkey for Android Help
Lowlander (MediaMonkey user since 2003)
Lowlander (MediaMonkey user since 2003)
Re: 1299 Tracklist SHIFT+Up/Down arrow can drop tracks [---
I don't expect Windows Explorer to - because unlike MM it (at least in XP) does not support SHIFT-extension of disjoint selections.Mizery_Made wrote:Well with Windows (Vista), Explorer doesn't function like the current MM behavior or your expected behavior.
That is not what MM does. It supports SHIFT-extension of disjoint selections. Except for this failure in just one direction.Mizery_Made wrote:I would agree with Lowlander on this one. Using Shift, the typical behavior is that anything between the original selection and whatever is selected while using Shift is selected
Chris
Re: 1299 Tracklist SHIFT+Up/Down arrow can drop tracks [---
I don't think it's a failure, you need to use Ctrl+key to move to another track in step 4, just like step 2.
Download MediaMonkey ♪ License ♪ Knowledge Base ♪ MediaMonkey for Windows 2024 Help ♪ MediaMonkey for Android Help
Lowlander (MediaMonkey user since 2003)
Lowlander (MediaMonkey user since 2003)
Re: 1299 Tracklist SHIFT+Up/Down arrow can drop tracks [---
chrisjj wrote:in the case reported, moving down does that, but moving up does not
Let's see what the Devs think.Lowlander wrote:I don't think it's a failure
Chris