Wrong value saved for stored number

Bug #1842060 reported by Jean-Pierre Verrue
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Rapid Photo Downloader
Fix Released
Low
Damon Lynch

Bug Description

Since I use the 0.9.x releases (1 or 2 years), I have a problem with the stored number.

The value that is recorded at the end of a loading sequence is the value of the last loaded photo. This was not the case with the 0.4.x releases. With these releases it was the value of the last photo + 1.

The consequence is that when I start a new loading sequence, the first picture of this new sequence is renamed with the same number as the last picture of the previous sequence. So I have two photos with the same number. And of course all the following pictures in the sequence are shifted by -1.

If I don't forget, I correct the stored number manually before starting the loading sequence. Alas, I often forget!

I have this problem on all RPD installations on Opensuse that I have done either with leap or tumbleweed.

Would it be possible to restore the previous functioning?

Translated with www.DeepL.com/Translator

Related branches

Revision history for this message
Damon Lynch (dlynch3) wrote :

Thanks for your bug report. I will look into it after my dissertation is finished late this year. Unfortunately I cannot fix the bug before then, because I do not have time.

Changed in rapid:
status: New → Triaged
assignee: nobody → Damon Lynch (dlynch3)
importance: Undecided → Low
Revision history for this message
Jean-Pierre Verrue (jean-pierre-verrue) wrote : Re: [Bug 1842060] Re: Wrong value saved for stored number

No problem! I myself waited a long time before reporting the bug. I can
still wait a few more months until you have finished your dissertation.

Sincerely, JPV

Le 30/08/2019 à 18:43, Damon Lynch a écrit :
> Thanks for your bug report. I will look into it after my dissertation is
> finished late this year. Unfortunately I cannot fix the bug before then,
> because I do not have time.
>
> ** Changed in: rapid
> Status: New => Triaged
>
> ** Changed in: rapid
> Assignee: (unassigned) => Damon Lynch (dlynch3)
>
> ** Changed in: rapid
> Importance: Undecided => Low
>

Damon Lynch (dlynch3)
Changed in rapid:
status: Triaged → Fix Committed
Damon Lynch (dlynch3)
Changed in rapid:
milestone: none → 0.9.19b3
Revision history for this message
Damon Lynch (dlynch3) wrote :

If you could please test the fix in 0.9.19b3 I would appreciate it. Download it from https://damonlynch.net/rapid/download.html

Changed in rapid:
status: Fix Committed → Fix Released
Revision history for this message
Jean-Pierre Verrue (jean-pierre-verrue) wrote :

Hi, Damon,

It's working very well now. Thank you very much!
I have a wish for a new feature. Where should I express it?

Best regards,
JPV

Le 08/03/2020 à 04:48, Damon Lynch a écrit :
> If you could please test the fix in 0.9.19b3 I would appreciate it.
> Download it from https://damonlynch.net/rapid/download.html
>
> ** Changed in: rapid
> Status: Fix Committed => Fix Released
>

Revision history for this message
Damon Lynch (dlynch3) wrote :

Feature requests can be made here. Give it the importance Wishlist.

Revision history for this message
Damon Lynch (dlynch3) wrote :

By here, I mean in this bug reporting system.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.