how do you feel about splashes which you can dismiss?

[JdGordon]

note to self... dont get into arguments when overtired...

[Llorean]

Just a note - 4 is unlikely to lead to accidental button presses unless you're in the habit of pressing a button several times when you meant to only press it once.

2 and 3, on the other hand, will lead to people trying to dismiss splashes, only to have them disappear right before they tried to press the button, which will lead to accidental button presses. I think you got that footnote mixed up.

[gevaerts]

I mostly like the way splashes behave now.

* I don't want to have to press buttons to make them go away in a reasonable time
* I don't think 3s or 4s is a reasonable time to wait for "normal" splashes
* Allowing variable-length splashes to be dismissed is going to lead to accidental button presses

Also, insulting people who disagree with isn't going to make you many friends.

[pixelma]

I'm with gevaerts on all points.

[nls]

I like the idea of being able to dismiss splashes but maybe we should couple the timeout with some kind of visual indication. Or y'know just make it configurable maybe the following options?
* timeout after X seconds (no dsimissal)
* timeout after X seconds (early dismissal possible)
* don't timeout, wait for user to dismiss (with helpful "press <button> to close" of course)

X could be settable too...

[linuxstb]

Just my "+1" to add to gevaerts and pixelma.

[rasher]

I'm basically with gevaerts, but a visual indication on splashes wouldn't hurt, I guess. Make the bottom line be 3px high, which then gets removed to being 1px high, during the lifetime of the splash.

That's just eyecandy though, and I don't really like the idea of dismissable splashes.

I also don't like getting insulted.

[AlexP]

So if you're not a brain dead monkey you probably find the splashes throughout rockbox to be annoying to some degree....
here are the options:
1) do nothing, leave it how it is and keep being annoyed

This is just bloody stupid.  Why do you feel the need to insult people that don't agree with you?  Ridiculous.

As for the splashes, I agree with gevaerts and all - although a fixed length for splashes would be good.

[Llorean]

I think a fixed length is a somewhat bad idea. Some splashes have more text than others - this generally means they need to stay up longer for voicing (and to give people the ability to read them).

Having single-word splashes need to be displayed the same amount of time as the longest splash is probably unnecessary.

[AlexP]

I think a fixed length is a somewhat bad idea. Some splashes have more text than others - this generally means they need to stay up longer for voicing (and to give people the ability to read them).

Having single-word splashes need to be displayed the same amount of time as the longest splash is probably unnecessary.

Yes, this is a good point.

[JdGordon]

My argument against varying splash timeouts is that currentlys there is no way blind users will know when the splash has gone, if there is a consistant time they are at least more likely to guess when its gone.
Also, the timeouts are completely arbitrary... they rang from .5s to 5s, and its entirely up to whoever added it to choose a number (which may or may not be enough to read/voice the splash).

Also, just because its a single short word in english, doesn't mean it is in all languages... shuffle in german is the usual example... 15 syllables*(maybe exaggerated).

the other point is, splash placement again is completly arbitrary.... *someone* thought it would be a good idea, and they usually are the first time you come across them, but they are not needed after a while.

[gevaerts]

My argument against varying splash timeouts is that currentlys there is no way blind users will know when the splash has gone, if there is a consistant time they are at least more likely to guess when its gone.

I think that if a splash is spoken, it should probably last exactly as long as the spoken text.

[JdGordon]

which leads to fun problems when playback is paused. Also, I dont  even know if its possible to know when a voice smaple is finished talking

[Llorean]

Well, if you wanted to get complex, you could assign each string a value to carry the number of syllables (with spaces possibly counting as one syllable each as well) then just compute the amount of time to display a splash at runtime based on the number of syllables in the string times a set amount of time picked as an average syllable pronunciation time.\

Of course this flies in the exact opposite direction of "reducing complexity."

[GodEater]

+1 to gevaerts, pixelma et al.