Dragon for Mac Forums and Discussion Topic: The Cache

Dragon for Mac Forums and Discussion Topic: The Cache http://www.macspeech.com/extensions/forums/ Dragon for Mac Forums and Discussion Topic: The Cache en Wed, 22 May 2013 03:15:44 +0000 Yakker on "The Cache" http://www.macspeech.com/extensions/forums/topic.php?id=605#post-2643 Sat, 17 Oct 2009 18:10:34 +0000 Yakker 2643@http://www.macspeech.com/extensions/forums/ jayg and endymion: I want to apologize to both of you. My comments were stated much too strongly, endymion, and they are indeed "crosstalk," jayg. I will be careful to refrain from this kind of discourtesy in the future. Ray jayg on "The Cache" http://www.macspeech.com/extensions/forums/topic.php?id=605#post-2616 Fri, 16 Oct 2009 06:55:24 +0000 jayg 2616@http://www.macspeech.com/extensions/forums/ The "Cache" is a reality of MacSpeech Dictate as it stands now. In the context of using the product, we have documented info about the Cache, and have created the Cache-related commands so that you could control things better. In the context of a Feature Request: I don't have a response addressing "alternatives" to how Dictate works. I will point out that not all applications support the Accessibility API. Applications that support the Accessibility API allow MacSpeech Dictate an easier route to keeping track of changes in document made by keyboard, cut/paste, autotext. Because of this, you will find that TextEdit and the Dictate Note Pad do the best job at tolerating a mix of typing and dictation. It is still NOT recommended that you get into the habit of mixing dictation and typing. In addition to Accessibility, it is great when applications support AppleScript so that they can be more easily controlled by voice commands. jayg on "The Cache" http://www.macspeech.com/extensions/forums/topic.php?id=605#post-2615 Fri, 16 Oct 2009 06:43:26 +0000 jayg 2615@http://www.macspeech.com/extensions/forums/ Thank you all for discussing feature requests here for MacSpeech Dictate. I would ask (fairly strongly) that everyone refrain from personal attacks, or "cross-talk" that is addressed to a specific person...unless it is done toward the goal of helping other users with troubleshooting or using the relevant products discussed here. Yakker on "The Cache" http://www.macspeech.com/extensions/forums/topic.php?id=605#post-2607 Fri, 16 Oct 2009 03:00:52 +0000 Yakker 2607@http://www.macspeech.com/extensions/forums/ endymion, I am familiar with this pattern in MacSpeech, and I haven't the slightest problem with it. You want to type text? Fine: type, do a "cache" command, and get on with it. As for where the "arrogance" is to be found: well, the tenor of your many complaints, with their numerous "shoulds" suggest that quality to at least one quite satisfied MacSpeech user: me. (I may be wrong to read them that way, however. I freely acknowledge the possibility.) SO: Do I wish certain things in MSD worked differently? Sure. Am I able to work around its glitches in reasonable comfort? Yep. Do I think I'm getting my money's worth? You bet. I recognize that in your view this message may mark me out as some sort of sucker. So be it: if I am, I'm a happy sucker. Others should be so fortunate. Ray jayg on "The Cache" http://www.macspeech.com/extensions/forums/topic.php?id=605#post-2593 Thu, 15 Oct 2009 01:12:02 +0000 jayg 2593@http://www.macspeech.com/extensions/forums/ endymion wrote: <blockquote> Charlie, he said "not having SOLID word correction feature is just pathetic". MacSpeech Dictate can correct words -- sometimes. It flakes out frequently due to its critical design flaw: the cache. Example of a failure of the word correction feature: Open Mail and create a new message. Now go to the body of the new email message and dictate the words "MacSpeech" (pause) "failure" with MacSpeech. Now press the space bar and type "test" with your hands. MacSpeech thinks that the message says "MacSpeech failure" because it doesn't look at the text. It just attempts (unsuccessfully) to remember what's in the message. That's what they mean when they say "cache". Now say "forget that". When you say "forget that", MacSpeech will attempt to delete the word "failure". It will do that assuming that it knows the current state of that message window, assuming that it contains only "MacSpeech failure". It will delete backwards under that assumption, because the text "MacSpeech failure" is in the MacSpeech cache. But the actual text in the window is "MacSpeech failure test", and when it deletes what it thinks is the word "failure" it will actually delete the word "test" and the last few letters of "failure". You'll be left with "MacSpeech fail". That's not a solid word correction feature. It's not the word correction feature that's broken, it's the fundamental design of MacSpeech. It will never be a useful product as long as it depends on the user to constantly keep it updated as to what text it's currently editing. I've pointed out over and over that the Mac provides all the information that MacSpeech needs for automatically updating its own cache. I'm also left wondering if the root of the problem is ability, funding, or arrogance. </blockquote>