maxFetch for short moment visible as 100 when set to custom
Bug #678353 reported by
Adrian Gruntkowski
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Groundhog Usenet Reader |
In Progress
|
Undecided
|
Unassigned | ||
Bug Description
In the first phase "Connecting for download", the progress meter shows "0/100" even thought I've set 300. However, when actual fetching starts, maxFetch goes to 301 (still 1 above the limit but ok otherwise) - of course that's the case when the number of new messages hits the cap.
I've tried to trace it down looking at the code, but I couldn't find anything that would make the app act like that. This may be the case of specific task handling by android, but I have too little experience with the platform to tell.
Revision history for this message
| juanjux (juanjux) wrote | #1 |
| Changed in groundhog: | |
| status: | New → In Progress |
To post a comment you must log in.
Probably I left a 100 hardcoded somewere from the initial prototyping state, should be easy to fix.