show and tell,
FAQand so on . See https://github.com/dictation-toolbox/Caster/discussions
I have 2 grammars for people to test that work with all engines.
Eye Tracking with tobii hardware leveraging OCR. # Windows only at the moment
Allows for general text manipulation any programm
Allows you to click on any menu that contains words.
set up assuming tobii software is installed.
pip install screen-ocr[winrt]
Run Caster and
enable tobii rule
"<text> click" To click on an element
Ensure that the dll in files Castor user directory
third_party_integration\tobii\dll are not blocked (right-click Properties, and if there is a "Security" section at the bottom, check the "Unblock" box.)
For those without eye tracking hardware
hunt and peck provides increased navigation for most applications leveraging UI automation accessibility API. # Windows only
enable hunt and peck
hint appor hint
caster alphabetletters as needed when they match they will execute automatically.
also, sometimes when saying eg shin sauce 5 it doesnt mark the first 2 lines
I can't reproduce that locally. if it's going through VM it can have timing issues as mentioned in the issue above.
that one is annoying, but not as much an obstacle as shin sauce 7 just keep spamming UP
Thanks a lot. There's no rush on my part.
Complete in dictation-toolbox/Caster#875
Hi All- I'm new to this group, and am trying to install Caster. I've followed the installation procedure from readthedocs. Natlink is successfully installed (I confirmed it's working with a sample macro outside of Caster). I've set my Caster path as the Natlink User Directory, and Caster does appear to launch when I start Dragon. However, I get a bunch of "Skipping rule...it is enabled but not loaded." messages in the Natlink window, and the "Arch brov char delta" test does not work. I found the quote below from @LexiconCode from earlier this year from their response to this same issue (I think) from @nreith but I'm not sure what to do with it. Thanks in advance!
The issue is resolved. I think switching between Python versions polluted settings.toml. The solution was to regenerate settings.toml. After restart the rules load as expected.