- Status New
- Percent Complete
- Task Type Patches
- Category User Interface → Themes
- Assigned To No-one
- Operating System All players
- Severity Low
- Priority Very Low
- Reported Version Release 3.6
- Due in Version Undecided
-
Due Date
Undecided
- Votes
- Private
FS#11564 - new tag to talk other tags
This patch reimplements FS#11541 using the skin engine.
new skin tag %Vx(params) will talk whatever is in the params (unlimited….)..
Params can be any string or other skin tag (no conditionals just yet).
if the first option is - it will shutup anything currently talking. otherwise - is a voiced pause.
otherwise the only special string is the word “text” which says to spell the next tag (used when the value of the tag is usable in a conditional, i.e %cP need talk or you will get “1” or “2” :/ ).
quick examples:
%?mh<%Vx(-, %cl,-, %cM, text, %cP)> ← Talk the current hour, minute, am/pm when hold is toggled.
%?pE(15)<%?It<%Tx(-, %Ia, -, %It)» ← untested but should spell the next tracks title and artist when there is 15s left of the current track
voicewps.diff
(5.5 KiB)
Loading...
Available keyboard shortcuts
- Alt + ⇧ Shift + l Login Dialog / Logout
- Alt + ⇧ Shift + a Add new task
- Alt + ⇧ Shift + m My searches
- Alt + ⇧ Shift + t focus taskid search
Tasklist
- o open selected task
- j move cursor down
- k move cursor up
Task Details
- n Next task
- p Previous task
- Alt + ⇧ Shift + e ↵ Enter Edit this task
- Alt + ⇧ Shift + w watch task
- Alt + ⇧ Shift + y Close Task
Task Editing
- Alt + ⇧ Shift + s save task
hi, I think you linked to the wrong patch didn't you?
the one you linked to is something to do with track skipping.
To be honest, I looked at the tags, and it all looked very complicated and not at all easy to understand. Also, they include a lot of punctuation which is obviously extremely important in the wps, but meant I had to arrow through individual letters to read it, and also that it just wasn't very readable.
I read the example tags, and couldn't even hazard a guess at understanding what they would voice.
from a simplicity point of view I prefer
fs#11541 as I wouldn't feel confident about working with the wps tags.
Of course it would be good if the wps eventually does get voiced but I wouldn't feel confident about making changes as at least in my opinion the tags are not very human readable or easy to work with.
sorry, just reread my above comment, to clarify I meant I wouldn't be able to guess at what they would do if you hadn't explained what they do. From a newbies point of view, working with the tags looks very complicated and intimidating.
Like I said in the other patch, this one isnt about accessibility but as a general talking system which the other one could be built on.