1. Messages
  2. ClipSpeak doesn't seem as reliable as

Re: ClipSpeak doesn't seem as reliable as

Damien Garwood <damien@...>
 

Hi Gene,
Time isn't an issue for me. The problem is finding beginner-friendly resources. That's also an issue because people learn in different ways, program in different ways, and experts are generally unaware of what or how to teach beginners unless they are qualified teachers and/or course organisers (I speak from experience). One of the biggest hurdles is discovering exactly what the beginner does or doesn't know (and that goes for any area of study).
Personally, I'm rubbish at learning through pre-existing material or class-based courses. I learn ten times quicker and better through personal tuition. Unfortunately, where that causes a problem is, money.
Again, I speak from experience. I did a course that taught how to use Reaper three years ago, and I couldn't get to grips with it. Two months of personal tuition, and I'm doing things I would have never dreamed of before then.
Anyway, I am glad you find use for it, but it's doubly clear to me now that it definitely could be improved.
Cheers,
Damien.

On 07/07/2020 10:41 am, Gene wrote:
It may have faults or defects but I've been using it for years and I find it useful and almost always reliable.  I'm very pleased you created it, though from what you say, it may have taken so much time that maybe it wasn't worth it from your standpoint of time and work.  But I have believed since the issue came up, that this feature should be in the NVDA code itself and I very much a[ppreciate your attempting to make NVDA do what System Access and JAWS both do and saving me work and aggrevation because I usually know when, even if I issue the command correctly, it fails and then I can make sure it is done correctly.
Gene
-----Original Message----- From: Damien Garwood
Sent: Tuesday, July 07, 2020 2:24 AM
To: nvda@nvda.groups.io
Subject: Re: [nvda] ClipSpeak doesn't seem as reliable as
Hi Joseph,
Trust me, I wouldn't take it badly if you did.
I guess that's what happens when a beginner tries to code something
useful without knowing how the infrastructure around it works.
Having said that, nobody can say I didn't read the dev docs. I just
didn't understand most of them. But I was determined not to throw in the
towel at that point. If I'd known what an embarrassing piece of junk I
was going to spew forth...
Three years of hard study, a few months of coding, and three years of
reflection. Yup. I think we can safely say I definitely failed that test!
If it's any consolation, I don't even use Clipspeak myself anymore.
Cheers,
Damien.
On 06/07/2020 11:19 pm, Joseph Lee wrote:
Hi,

Okay, a few things for everyone:

  * Is this related to NVDA language: actually, no. If it was, then it
    would be something NVDA translators would have been aware of. A key
    piece of information translators need is add-on gestures, and for
    this one, there is none for languages other than English. How we
    ended up with this is beyond the scope of this forum – all I can say
    is that ClipSpeak wasn’t registered with translations workflow, and
    it won’t be made translatable for some time (due to another work
    that’s being researched, which is again beyond the scope of this list).
  * Is NVDA supposed to announce “cut” all the time: no. If the
    currently focused control does allow you to cut or copy text using
    how NVDA does it (say, in browse mode), it is supposed to use
    whatever facility NVDA provides. If not, it is supposed to send the
    command to the program you are using.
  * Clipboard content matters: even if you do cut something, NVDA won’t
    announce things you have just cut. ClipSpeak supports text, parts of
    text 9such as words), and files and folders. Also, item must be
    selected (for example, text must be selected) before NVDA can say
    things.
  * Where you are located matters: even though you are working with a
    file, not all edit fields will tell ClipSpeak to announce clipboard
    messages. This is more so if the text field is read-only.

Based on this, I think one or more of the following might be happening:

  * No text selected
  * Jarte does not support operations necessary for ClipSpeak add-on to
    speak the appropriate clipboard message
  * Wrong command was sent to the application
  * NVDA didn’t recognize that the clipboard contains text

For resident geeks here: I must say ClipSpeak add-on source code is quite an interesting read. It isn’t up for me to critique the author of this add-on, but I think folks may wish to work on improving this add-on somehow.

Cheers,

Joseph

*From:* nvda@nvda.groups.io <nvda@nvda.groups.io> *On Behalf Of *Gerardo Corripio
*Sent:* Monday, July 6, 2020 2:58 PM
*To:* nvda@nvda.groups.io
*Subject:* Re: [nvda] ClipSpeak doesn't seem as reliable as

Joseph and lister

Just tried the Control+x command on Jart, but no go! It doesn’t say Cut text. I again went into NVDA+n; p for Options, and N to get into the Input Gestures area; from there into Clipboard. I arrow down to where it says Cut, and it says one of one Control+x, thus I can’t get why isn’t it saying Cut text if the option is set up right? Any other ideas aside from deleting and reassigning Control+x?


Enviado desde Correo <https://go.microsoft.com/fwlink/?LinkId=550986> para Windows 10

*De: *Joseph Lee <mailto:joseph.lee22590@gmail.com>
*Enviado: *lunes, 6 de julio de 2020 04:51 p. m.
*Para: *nvda@nvda.groups.io <mailto:nvda@nvda.groups.io>
*Asunto: *Re: [nvda] ClipSpeak doesn't seem as reliable as

Hi,

Hmmm, I think I know why. Can you tell us exactly how you are doing this – that is, tell us how to reproduce the issue? Only then I will tell you what’s happened.

Cheers,

Joseph

*From:* nvda@nvda.groups.io <mailto:nvda@nvda.groups.io> <nvda@nvda.groups.io <mailto:nvda@nvda.groups.io>> *On Behalf Of *Gerardo Corripio
*Sent:* Monday, July 6, 2020 2:43 PM
*To:* nvda@nvda.groups.io <mailto:nvda@nvda.groups.io>
*Subject:* Re: [nvda] ClipSpeak doesn't seem as reliable as

And which is what I have as well installed since yesterday. Remember I use Windows in Spanish, thus I went into check within the Clipboard subsection ofInput Gestures, and the Control+x is as it should.


Enviado desde Correo <https://go.microsoft.com/fwlink/?LinkId=550986> para Windows 10

*De: *Brian Vogel <mailto:britechguy@gmail.com>
*Enviado: *lunes, 6 de julio de 2020 04:36 p. m.
*Para: *nvda@nvda.groups.io <mailto:nvda@nvda.groups.io>
*Asunto: *Re: [nvda] ClipSpeak doesn't seem as reliable as

Gene,

         I omitted that the version currently downloading from the official add-on page you supplied, https://addons.nvda-project.org/addons/clipspeak.en.html, is ClipSpeak 1.1, which is what Luke stated he just downloaded in an earlier post.
--

Brian *-*Windows 10 Pro, 64-Bit, Version 1909, Build 18363

/*Science has become just another voice in the room; it has lost its platform.  Now, you simply declare your own truth.*/

~ Dr. Paul A. Offit, in /New York Times/ article, /How Anti-Vaccine Sentiment Took Hold in the United States/ <https://www.nytimes.com/2019/09/23/health/anti-vaccination-movement-us.html>/,/September 23, 2019
Join nvda@nvda.groups.io to automatically receive all group messages.