Support and General Use > User Interface and Voice

how do you feel about splashes which you can dismiss?

<< < (3/4) > >>

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:

--- Quote from: JdGordon on June 16, 2009, 04:52:35 PM ---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.

--- End quote ---

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.

Navigation

[0] Message Index

[#] Next page

[*] Previous page