Rockbox

  • Status Closed
  • Percent Complete
    100%
  • Task Type Patches
  • Category Applications
  • Assigned To No-one
  • Operating System All players
  • Severity Low
  • Priority Very Low
  • Reported Version
  • Due in Version Undecided
  • Due Date Undecided
  • Votes
  • Private
Attached to Project: Rockbox
Opened by mikaelh - 2006-02-24
Last edited by teru - 2010-01-19

FS#4719 - mandelbrot clear button queue after calculation and keep iter setting after zooming

Currently mandelbrot will keep itself busy for a while if you press zoom too many times, so clear the button queue after finishing a calculation. Also, after zooming the iter variable is reset, which is annoying if you lower it to zoom in somewhere faster.

   rockbox-mandelbrot-clear-queu... (1.1 KiB)
Closed by  teru
2010-01-19 07:06
Reason for closing:  Out of Date
Additional comments about closing:   Warning: Undefined array key "typography" in /home/rockbox/flyspray/plugins/dokuwiki/inc/parserutils.php on line 371 Warning: Undefined array key "camelcase" in /home/rockbox/flyspray/plugins/dokuwiki/inc/parserutils.php on line 407

superseded by  FS#10911  which enables to interrupt calculation.

Jaykay commented on 2008-12-20 11:38

i suggest committing. it works well and gevaerts said it can be included but didnt do it because of the 3.1-freeze

Llorean commented on 2009-01-10 16:58

This seems like it could be very annoying if you wanted to zoom in 5 levels, and you pressed it five times quickly, but it cleared so you lose some of them. Is it possibly to lose button presses with this patch?

bluebrother commented on 2009-01-10 17:08

if you want to zoom in 5 levels wouldn't it be better to abort the first 4 calculations (i.e. abort the calculation once the zoom level is changed again) and restart calculating from the top?

Jaykay commented on 2009-01-10 17:12

yes. if you press the zoom-key one time and then four times while calculating, the four key presses are ignored.

i guess it can be closed. its not wanted and the suggested improvements will be done in a few years or never.

kugel. commented on 2009-02-05 15:24

I think it should be committed. Loosing button presses during operations which lead to unresponsiveness isn't annyoing, but safer and should be the common case.

Llorean commented on 2009-02-05 15:31

I 100% disagree. I consider being able to queue "zoom" actions a feature and think having to press the button several more times than necessary because it's intentionally ignoring presses a significant problem.

Fix is as bluebrother suggested possibly, but don't ignore button presses. If someone presses zoom 19 times you should be on the 20th level of zoom, not some unpredictable level depending entirely on how quickly/slowly they pressed it.

bluebrother commented on 2009-02-14 21:12

If you consider it as a problem that you have to wait for all calculations you queued to finish add a dedicated abort button. I still think that zoom levels should be able to get skipped. Dropping the button presses is still the worst solution from my point of view.

Jaykay commented on 2009-02-15 13:45

i suggest closing, since bluebrother and llorean think its the worst solution…

Jaykay commented on 2009-02-15 13:48

imo the abort button plus the first suggestion by bluebrother is the best solution.

Loading...

Available keyboard shortcuts

Tasklist

Task Details

Task Editing