Closed frozeman closed 13 years ago
This MAY happen under these conditions: when the directory viewed is near the pagination size.
Scenario/behaviour description: by default, FM performs 'autosensing' with respect to the pagination. This means:
a) change directories
b) hit either the [|<] 'go to start' or [>|] 'go to end' pagination buttons in the top-left bar.
c) change the list mode from 'list' to 'thumb' or vice versa.
When a directory has a number of entries which is close to the actual pagination size, the next 'tuned pagesize' activation MAY be slightly smaller or larger than that number, resulting in the page buttons being shown or not, respectively.
Notw also that rendering a thumb view may take slightly longer than a 'list' view, affecting the 'autotuning' pagination process.
Example: pagination size starts at 100 rows. The dir view is rendered in 'list' view. Assume list render is fast enough that adaptive pagesize is incremented to 110. directory item count is, say, 105. This means the directory will be initially displayed WITH pagination buttons (105 > 100 ==> 2 pages)
After changing from list to thumb view, the new 110 pagesize is activated, producing a thumb render WITHOUT the pagination buttons (110 >= 105). Suppose the thumb render is a little slow, so the autotuning is slightly adjusted downwards.
Next, we enter and view a subdirectory, again in thumb view, and the slower rendering is consistent, resulting in the pagesize being downwards adjusted to, say, 100, again.
Going one directory up, i.e. returning to the 105 items directory, will now render that original thumb view WITH pagination buttons as this time around, pagination size is 100 (100 < 105 ==> 2 pages)
in my case it showed it when going from list to thumb, but when i went back it disapeared
I've seen the same thing myself; matches the scenario described AFAICT. Known feature / side-effect of the autotuning pagesize... hm... this 'effect' should be gone when the frontend options.listPaginationAvgWaitTime is set to zero.
Closing this, known feature unless there's due diligence pointing out the opposite.
the title says it :-)