next »

[Dotpitch]

Color = pointer = indicator.  I would like only the current track to be indicated.

Get the source of the skin from the Support Site (Neutron). Open skinconfig.txt and change scaler_lit to 1.0 1.0 1.0 (and optionally scaler_pressed as well). Is that better?

[saga]

Color = pointer = indicator.  I would like only the current track to be indicated.

So you never select a bunch of tracks and want to actually see which tracks are selected?

[SmartOne]

It would be better to have a setting that worked with all skins.   Most of the time I don't need to select tracks and would rather see only which track is playing.  "List nav - Jump to current" every time the list advances is a pain.

[Pike84]

Well, I guess it's a reasonable request.

[Cris]

You mean like this (attached)?

Color = pointer = indicator.  I would like only the current track to be indicated.

So you never select a bunch of tracks and want to actually see which tracks are selected?

+1.

What kind of list is that in which you can't actually select items? And I'm talking here about lists that can be edited (such as a media playlist), not about read-only lists (but still, not being able to actually select items in list would make the list useless).

As it was already pointed out, the highlight method/color depends on the skin.

There's no player as far as I know, which doesn't allow you to select items in the list.

[amit]

Theoretically - you could edit the config.txt file and change the scaler_lit in order to change the selected files background  color to differentiate them from the current track.There is a problem though with dark skins with black background. A scaler won't have any affect on zero values. right?

Maybe this issue can be given some thought and solution?

[Cris]

Maybe this issue can be given some thought and solution?

But what exactly is the issue? In my opinion, a good solution can only be offered only once the problem is correctly defined. In this case, what is the problem?

Clearly, the selection marker has to remain, because it's too important to be removed. So completely removing it is not an option.

Keeping the marker, but making it invisible, well... it's basically the same thing as taking it out, because if you can't see what you selected, then you might end up doing something with the playlist items that you didn't want to do. So having an invisible marker is just plain useless.


From my understanding, SmartOne doesn't like seeing the selection marker. But why and when?
A simple solution would be to reset the selection marker once a track change occurs. While it is a very simple solution, and might be very fast to implement, this solution partly breaks the functionality of the playlist. Considering the following scenario: the user wants to select multiple items (in a non-continuous order) to do something with them (doesn't matter what). He selects a few items and wants to select more, but in the meantime the current track changes, so all selections are reset. And the user has to start all over again.

Another solution would be implementing an option to show or hide the selection marker. This might even be combined with another suggestion made sometime ago (can't remember by whom) for an option to make the playlist read-only (so the order cannot be changed accidentally). But again, you can't select multiple items to queue them (for instance).


Another solution, though it might be harder to implement (depending on the way XMPlay's interface internally works right now): show/hide the selection marker depending on weather the playlist is focused or not. Any selected items should remain selected even when the playlist is out-of-focus, but the marker just won't be shown.


And there might be other scenarios and possible solutions to this "issue", but the exact problem (how and why) has to be fully defined so the best solution can be chosen.

[amit]

The regular scaler_lit doesn't affect the black background in neutron skin because it is a multiplier of zeroes (black in RGB=000000). In that case the only way to show selected tracks is to use a different font color.

Maybe with black background the scaler should be culculated for white ie RGB=FFFFFF?

[Pike84]

"Disable selection" or "Lock selection to current track" would be good.  I'm not concerned about the "hover highlighting."

I don't see what's so problematic about this suggestion - it could easily be implemented as an option.

Color = pointer = indicator.  I would like only the current track to be indicated.

So you never select a bunch of tracks and want to actually see which tracks are selected?

I think this quote is misunderstood; he means he wants only the current track to be indicated, as opposed to there being another one during playback, that's just got left there from the initial action. You should still be able to select tracks normally, even while using something like "Disable selection", and I think SmartOne agrees.

Having the selection follow the current track (or making it invisible, as there's already an indicator for the current track) may make it harder to manipulate the playlist during playback, but as an option (especially with a shortcut key) it wouldn't cause any trouble.

[SmartOne]

There's no player as far as I know, which doesn't allow you to select items in the list.

You're right.  I could have used XMPlay for both examples.  This feature would be another reason XMPlay is the best. 

He selects a few items and wants to select more, but in the meantime the current track changes, so all selections are reset. And the user has to start all over again.

User error.  Setting.  Pike84 has the right idea. 

[wrkq]

Sounds to me that "clear selection on doubleclick on entry" ("... on play"?) might be what he needs?

[Jimmy Neutron]

I think some confusion exists with the playlist vs queue vs library and the display in different skins.

It has driven me a bit crazy.  As with other softwares (think of MS-Office for example) I just go to places I understand and ignore the rest.  Not exactly elegant, but it makes me happy.

[wrkq]

Yeah, I'm perfectly happy with just the playlist.

[Dotpitch]

Adding a shortcut like 'List nav - Select none' and optionally hiding the selection indicator at clever moments (when the mouse is not on the playlist, but not when List nav/List track shortcuts are used) should solve most of the issues without losing functionality. It's problem with indicators, not with functionality, so I don't really favour completely disabling track selection.

[amit]

Adding a shortcut like 'List nav - Select none' and optionally hiding the selection indicator at clever moments (when the mouse is not on the playlist, but not when List nav/List track shortcuts are used) should solve most of the issues without losing functionality. It's problem with indicators, not with functionality, so I don't really favour completely disabling track selection.

Maybe a second scaler parameter should be added. One for active window state and the other , to allow a more dimmed color , for inactive window state. 

[Pike84]

Could the speed at which the playlist screen is scrolled when a selected track(/s) is dragged be slowed down a bit, or ideally be made adjustable? As it is, it's difficult to place a track properly by mouse, since the list scrolls so fast.

[SmartOne]

Clear playlist on start.

[Chinese Sausage]

Could the speed at which the playlist screen is scrolled when a selected track(/s) is dragged be slowed down a bit, or ideally be made adjustable? As it is, it's difficult to place a track properly by mouse, since the list scrolls so fast.

+1

[raina]

Clear playlist on start.

Disable writes to xmplay.pls.

[SmartOne]

Seems a bit low-level, but okay.

"XMPlay has stopped working

A problem caused the program to stop working correctly.
Please close the program."

Now I can't get the program to start after reverting the permission change.
EDIT:  I needed CurTrack=-1 in the INI to make the program start.  Could you elaborate on your method?