-
-
Notifications
You must be signed in to change notification settings - Fork 270
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Feature Request] increment / decrement all number
and numberSort
in bulk edit
#628
Labels
Comments
number
and numberSort
in bulk edit
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
please unstale |
github-actions bot
pushed a commit
that referenced
this issue
Jan 17, 2023
# [0.159.0](v0.158.0...v0.159.0) (2023-01-17) ### Bug Fixes * **api:** include Z in datetime formats ([bb7b7fd](bb7b7fd)) * **api:** some dates were not returned as UTC ([cdfb8e3](cdfb8e3)) * translated using Weblate ([6ad0188](6ad0188)) ### Features * add links field in series metadata ([f9f02a3](f9f02a3)), closes [#938](#938) * series metadata supports alternate titles ([8e0655f](8e0655f)), closes [#878](#878) * **webui:** display datetime when hovering date on item card ([4d97172](4d97172)) * **webui:** display number of pages left on book details view ([77424b1](77424b1)), closes [#1012](#1012) * **webui:** display read date on book details view ([c30c755](c30c755)), closes [#757](#757) * **webui:** increment/decrement numberSort in bulk ([e7fbe57](e7fbe57)), closes [#628](#628)
🎉 This issue has been resolved in version 0.159.0 🎉 The release is available on:
|
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Is your feature request related to a problem? Please describe.
Extending on #476
Describe the solution you'd like
I really appreciate this has been included in the latest build, much welcome. However, especially with numbering being offset it would be handy to not edit the numbers per field manually, but to be able to multi-select all and also just a range of items (items 20 to 40) and then modify the value by increasing them all or decreasing them all. Reason is, if you've got a manga with 60 chapters and a few of them have extras (e.g. chapter 19 and a chapter 19.5) you would mark 19 and 19.5 as being "number 19" and 19.5 will get the sort number 19.5. However, the next 20 chapters may now falsely have both numbers offset by 1, so you would like to be able to select that range and mass-decrement with the same operation by subtracting 1 from the values for number and sort number.
Hope this makes sense.
As it is now, I still gotta edit every chapter individually, however I do save on not having to open and close a lot of edit dialogues, so that's some improvement already.
Not quite sure on the scarcity of the amount of stuff you can edit in the mass editor, I think iTunes did it best with being able to edit any value, you basically get the same view whether it's for one or many items and if there's fields where there's different values for the range of items you just show that there's various values and values that are the same are displayed in normal text.
Mass-editing rarely means you really wanna change a lot of values individually. Not that I don't appreciate a view where you can do that, in iTunes that'd be the table view. There you can cherrypick any individual item and value and change it.
Yes, I know everyone hates iTunes, but as far as metadata management is concerned I really gotta give it to Apple, they done good on that front. Personally speaking, a shining example for any media library manager out there for metadata presentation (views, general UI, ...), management (bulk edit, single edit, auto-completions, ...) and usage (smart playlists, statistics, ... - really just naming the very first examples that come to mind here)
Describe alternatives you've considered or other apps that can do what you want
n/a
Additional context
Originally wrote this as a comment for issue #476, but thought it'd be better to have it as a new trackable issue. Correct me if I'm wrong and it'd be better to have it in the OG issue.
The text was updated successfully, but these errors were encountered: