View Issue Details

IDProjectCategoryView StatusLast Update
0021923MMW 5Main Panelpublic2026-01-18 00:21
Reporterlowlander Assigned To 
PriorityurgentSeverityminorReproducibilityalways
Status feedbackResolutionreopened 
Product Version2024.2.1 
Target Version2024.2.1 
Summary0021923: Rating of multiple files via Context Menu triggers modify files confirmation [Regression]
DescriptionWhen you rate multiple files via the Context Menu, the Are you sure you want to modify x files confirmation is triggered. This happens on 2+ files.

This happens with both Confirm modifications to more than 50 files at once enabled and disabled.
Steps To Reproduce1 Select 2 files
2 Right click, Rating, select Stars
--> Confirmation shown
TagsNo tags attached.
Attached Files
image.png (15,766 bytes)   
image.png (15,766 bytes)   
Fixed in build

Relationships

related to 0021880 resolvedrusty Rating albums isn't immediate, and unexpectedly deletes track ratings 
related to 0021930 resolvedLudek Context Menu issues when using Keyboard 

Activities

michal

2026-01-09 18:45

developer   ~0080280

It is by design, because of 0021880.

lowlander

2026-01-16 22:10

developer   ~0080345

This is really annoying and personally I see this 20+ times a day requiring an extra step for just Rating a couple files in the Playing.

It shouldn't be shown when a user adjust Rating on a couple of selected files. It's fine if it's shown on Album Rating, although in that case the message isn't informative on what's happening (Rating in each file will be changed).

rusty

2026-01-18 00:20

administrator   ~0080349

The original issue at 0021880 was related to the case of users rating an _album_. One way to fix this would be to only show the modal dialog for both:
- Rating an album with > 1 track
- (as before) when modifying the rating for > x tracks (I think x is 50 for all mass edits)

If this is technically problematic, an alternative approach could solve the original issue from 0021880 without triggering this problem:
- when the user rates 2-x tracks use a timed toast message: "Updating x files . . . . . . (10s) [OK] [Cancel]"
- when the user rates x+ tracks use the current modal implementation
x should be the same threshold as is used to normally trigger the current modal confirmation dialog.

However, the second approach requires a new string. So if the first approach can't be used, we'd have to defer the second approach to 2026, which may mean that we'd have to revert 0021880.