Bug 468626

Summary: Error in the description of the Rename options
Product: [Applications] digikam Reporter: Nicofo <nicofo>
Component: AdvancedRename-dialogAssignee: Digikam Developers <digikam-bugs-null>
Status: RESOLVED FIXED    
Severity: normal CC: metzpinguin, michael2macdonald
Priority: NOR    
Version First Reported In: 8.0.0   
Target Milestone: ---   
Platform: Other   
OS: Linux   
Latest Commit: https://invent.kde.org/graphics/digikam/commit/a15bdcbdc2a1085b18f22eed3e53ed0442975e7b Version Fixed/Implemented In: 8.1.0
Sentry Crash Report:

Description Nicofo 2023-04-17 18:50:33 UTC 
STEPS TO REPRODUCE
1. In the rename tool window, click on the "Show a list of all available options" button
2. Al the options are listed, amongs other;
  #[options,start]    Sequence number (custom start) 
  #[options,step]     Sequence number (custom step) 
3. I suppose that second line is wrong (a unique number in brackets is considered as the custom start and not the custom step: example: #[3])

4. Note: but the following syntax is missing in the description (a sequence number with custom start but without options is valid): 
  #[start]     Sequence number (custom start) 

Note: see image of the error: https://imgur.com/Et6K1BZ
Comment 1 Maik Qualmann 2023-04-17 19:17:07 UTC 
Everything is correct, some options only refer to "c" for example [c,step] others refer to option "f" for example.

Maik
Comment 2 Maik Qualmann 2023-04-17 19:46:39 UTC 
Git commit a15bdcbdc2a1085b18f22eed3e53ed0442975e7b by Maik Qualmann.
Committed on 17/04/2023 at 19:45.
Pushed by mqualmann into branch 'master'.

add possible rename options to the description
FIXED-IN: 8.1.0

M  +1    -1    NEWS
M  +3    -3    core/utilities/advancedrename/parser/options/sequencenumberoption.cpp

https://invent.kde.org/graphics/digikam/commit/a15bdcbdc2a1085b18f22eed3e53ed0442975e7b
Comment 3 Nicofo 2023-04-17 20:19:11 UTC 
Ah, OK, sorry for my misunderstanding.
But it was not so easy to understand I believe --> thank you for the added clarifications.
Comment 4 Maik Qualmann 2023-04-29 04:19:34 UTC 
*** Bug 469118 has been marked as a duplicate of this bug. ***