To unsubscribe from this group and stop receiving emails from it, send an email to gqrx+unsubscribe@googlegroups.com.
To post to this group, send email to gq...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/gqrx/d7764562-ee9a-4021-b36b-456f0b88f5b0%40googlegroups.com.
To unsubscribe from this group and stop receiving emails from it, send an email to gqrx+unsubscribe@googlegroups.com.
To post to this group, send email to gq...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/gqrx/211a147d-07da-464a-9a84-3eea2d2af7d7%40googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/gqrx/CACopv_jD4SxKr1JL0vo2-Fy1OJ7BzLv9PmGavZmHia%3DwOvCkLw%40mail.gmail.com.
OK, it appears my last message did not go through to responding to this. Yes, I use voice over on a regular basis, right now I am using voice over on my phone. If you would like to see great examples of software that have voiceover implement it beautifully, look at the program Audacity. With voiceover, I tend to use my keyboard exclusively, I can use my mouse, but I prefer to use my keyboard as that is how I was taught on windows. On voiceover, it was always astounding to me that I could use my mouse, but I had always ended up using my keyboard because the Bluetooth mice will die relatively quickly. If you need questions answered about voiceover, get a hold of me and I will try to answer your questions. I hope this message will be a beautiful service, and I hope that I will be hearing from someone soon who may be able to help me, and I may be able to help them. All of you take care
Sent from my iPhone
> On Apr 4, 2017, at 1:52 PM, Alexandru Csete <oz9...@gmail.com> wrote:
>
>> On Tue, Apr 4, 2017 at 4:23 PM, Simon Kennedy <si...@thekennedys.info> wrote:
>> Hi Greg,
>>
>> to take the pressure off Alex(!) I am just tinkering with something that
>> might go someway to providing a solution using the Hamlib type interface
>> that is built into gqrx.
>
> Simon, that would be great.
> I thought of mentioning that as a possibility, just didn't want to
> move the pressure over to others :-)
>
>> Am I correct in assuming that voice over type software reads the tool tip or
>> accessible name and then speaks what it reads?
>
> So, far I have only used tooltips in gqrx and apparently that is
> already some help. Accordign to the documentation, regular widgets
> will have accessibleName and Description populated with e.g. button
> text and and tooltip?
>
> http://doc.qt.io/qt-5/qwidget.html#accessibleName-prop
>
> Alex
>
> --
> You received this message because you are subscribed to the Google Groups "Gqrx SDR" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to gqrx+unsubscribe@googlegroups.com.
> To post to this group, send email to gq...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/msgid/gqrx/CAHG%3DS_dD1gi%2B1OJ8GnubVOg7dzS6UFmt2Qv6%2BPiuCpXtN%2BrErA%40mail.gmail.com.
> For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups "Gqrx SDR" group.
To unsubscribe from this group and stop receiving emails from it, send an email to gqrx+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/gqrx/72000343-DB1E-4AD5-BBB8-2FE9C060277E%40gmail.com.
To unsubscribe from this group and stop receiving emails from it, send an email to gqrx+uns...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/gqrx/CACopv_hpennz--pEnn2E_QMefSJg6RjstccQkFiJ4zNBtqRWBg%40mail.gmail.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/gqrx/CACopv_hpennz--pEnn2E_QMefSJg6RjstccQkFiJ4zNBtqRWBg%40mail.gmail.com.
--
You received this message because you are subscribed to the Google Groups "Gqrx SDR" group.
To unsubscribe from this group and stop receiving emails from it, send an email to gqrx+unsubscribe@googlegroups.com.
To post to this group, send email to gq...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/gqrx/344B51BE-C70C-467B-BFC6-0F1E1CE31D0B%40gmail.com.
--
You received this message because you are subscribed to the Google Groups "Gqrx SDR" group.
To unsubscribe from this group and stop receiving emails from it, send an email to gqrx+uns...@googlegroups.com.
To post to this group, send email to gq...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/gqrx/CACopv_h8weKOSmZgmRqCx4WP36nTaH9ftDtfzva3_xe%2BUoAn0Q%40mail.gmail.com.
Yes, that is a good move but will it work with an actual screen reader software? It might be able to have some speech prompts, and that's good but what about actually implementing with a screen reader as well as your speech promps. That might be problematic but I don't know. I am not a developer, but I do know a little bit about the basics of the screen reader. I've played with Google's screen reader, for example it works but it requires to use your computer's voice that's already on the system. It has its own speech promps but you cannot use your own screen reader with it. When you do try to do that, it goes nuts and freezes and it just completely dies out. I don't know how Google has there's designed, but I'm hoping that your software does not fall prey to that issue. I don't know how they have that set up, by the sound of it it sounds like you at least have a basic if not a very well thought out idea. Keep me posted, and I will help where I can.
Sent from my iPhone
--Update: I want to use the QT Speech module as this is platform independent and will use the native speech engine of the operating system in use. However, as it is brand new the Python libraries that support QT functionality do not support QT speech. Consequently I have changed to writing this in C++ which means I am building it within the QT environment. In the long term this will undoubtedly be a good move.Tonight I have got a basic program producing speech in response to changes in the GUI. The user interface is the the same so there is now quite a lot of copy, paste, convert to C++ syntax to do.Simon.On 6 Apr 2017 23:27, "James Clark - KC3CDV" <james.c...@gmail.com> wrote:Hmm, you said E-speak? You know why thats not working to well? Thats a windows screen reading software, I think voiceover voices would be smoother sense there already intigrated in with the mac.
This might help though I don’t know.
https://www.cbtbc.org/tools/asvo/
This might be useful to.
http://lists.qt-project.org/pipermail/accessibility/2015-March/000072.html
https://developer.apple.com/accessibility/macos/
https://developer.apple.com/library/content/documentation/Accessibility/Conceptual/AccessibilityMacOSX/
You received this message because you are subscribed to the Google Groups "Gqrx SDR" group.
To unsubscribe from this group and stop receiving emails from it, send an email to gqrx+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/gqrx/CACopv_h8weKOSmZgmRqCx4WP36nTaH9ftDtfzva3_xe%2BUoAn0Q%40mail.gmail.com.
--
You received this message because you are subscribed to the Google Groups "Gqrx SDR" group.
To unsubscribe from this group and stop receiving emails from it, send an email to gqrx+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/gqrx/AF7D180B-5F70-48AD-84F4-EDB6D445C594%40gmail.com.
To unsubscribe from this group and stop receiving emails from it, send an email to gqrx+uns...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/gqrx/CACopv_jez2jPj9XNe_hte6wq1zOeFM3uhjHxcTJOkVXtd-BHgQ%40mail.gmail.com.
Is there a way you could get the actual package that Alex made for me. This way you would already have the basic foundation to go off of. It's just an idea as I'm not really technical when it comes to coding. I'll be willing to help when and where I can. If you want someone to test this on the Mac platform with an actual screen reader when it comes time to put in a.DM G file, get a hold of me and I will definitely test it for you.
Sent from my iPhone
Hi James,I get your point. When we test it properly we will have to see if they play nicely together.Simon.
On 10 Apr 2017 23:47, "James Clark" <james.c...@gmail.com> wrote:
Yes, that is a good move but will it work with an actual screen reader software? It might be able to have some speech prompts, and that's good but what about actually implementing with a screen reader as well as your speech promps. That might be problematic but I don't know. I am not a developer, but I do know a little bit about the basics of the screen reader. I've played with Google's screen reader, for example it works but it requires to use your computer's voice that's already on the system. It has its own speech promps but you cannot use your own screen reader with it. When you do try to do that, it goes nuts and freezes and it just completely dies out. I don't know how Google has there's designed, but I'm hoping that your software does not fall prey to that issue. I don't know how they have that set up, by the sound of it it sounds like you at least have a basic if not a very well thought out idea. Keep me posted, and I will help where I can.
Sent from my iPhone
--Update: I want to use the QT Speech module as this is platform independent and will use the native speech engine of the operating system in use. However, as it is brand new the Python libraries that support QT functionality do not support QT speech. Consequently I have changed to writing this in C++ which means I am building it within the QT environment. In the long term this will undoubtedly be a good move.Tonight I have got a basic program producing speech in response to changes in the GUI. The user interface is the the same so there is now quite a lot of copy, paste, convert to C++ syntax to do.Simon.On 6 Apr 2017 23:27, "James Clark - KC3CDV" <james.c...@gmail.com> wrote:Hmm, you said E-speak? You know why thats not working to well? Thats a windows screen reading software, I think voiceover voices would be smoother sense there already intigrated in with the mac.
This might help though I don’t know.
https://www.cbtbc.org/tools/asvo/
This might be useful to.
http://lists.qt-project.org/pipermail/accessibility/2015-March/000072.html
https://developer.apple.com/accessibility/macos/
https://developer.apple.com/library/content/documentation/Accessibility/Conceptual/AccessibilityMacOSX/
You received this message because you are subscribed to the Google Groups "Gqrx SDR" group.
To unsubscribe from this group and stop receiving emails from it, send an email to gqrx+uns...@googlegroups.com.
To post to this group, send email to gq...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/gqrx/CACopv_h8weKOSmZgmRqCx4WP36nTaH9ftDtfzva3_xe%2BUoAn0Q%40mail.gmail.com.
--
You received this message because you are subscribed to the Google Groups "Gqrx SDR" group.
To unsubscribe from this group and stop receiving emails from it, send an email to gqrx+uns...@googlegroups.com.
To post to this group, send email to gq...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/gqrx/AF7D180B-5F70-48AD-84F4-EDB6D445C594%40gmail.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/gqrx/c6b13cb4-ef61-4b91-9912-ee11bf3d584a%40googlegroups.com.
--
You received this message because you are subscribed to the Google Groups "Gqrx SDR" group.
To unsubscribe from this group and stop receiving emails from it, send an email to gqrx+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/gqrx/625cef1e-3f8c-4fd3-a6f5-80057bd44f04%40googlegroups.com.
This should be interesting to see how it works.
Though shift and tab to change freqs, thats going to be different, hey what ever works.
May Peace Be With You. Active skywarn severe weather spotter and Community Collaborative Rain, Hail & Snow Network operative.
@HomefrontHugs Volunteer for our Troops and Families
> On Apr 23, 2017, at 18:31, Simon Kennedy <si...@thekennedys.info> wrote:
>
> Hi Kevin,
>
> Thanks for your email, I am very glad for your input. I will read and digest it fully tomorrow as I am just going to bed now.
>
> In summary, I have the interface to gqrx nearly complete. One piece of functionality I wanted to include has been driving me nuts until this morning and now I think I have fixed it.
>
> Fundamentally my program will allow you to use Tab and shift tab to move between the frequency digits and cursor up and down to change the frequency. I have also included shortcuts to jump to all the ham radio bands from top band to seventy centimetres.
>
> I know it won't be perfect first time and feedback from people like yourself will be essential.
>
> Regards
> Simon.
>
> On 23 Apr 2017 22:21, "Kevin Utter" <kevin.u...@gmail.com> wrote:
> Hi all! I’m Greg’s friend that he’s trying to get hooked on SDR. I’m currently using Gqrx v2.6-84-g4a66a03 - rtl=0. I believe it is the specially modified version. Since there’s a lot of discussion about how the interface might work, I thought I’d chime in.
>
> As far as tones or sounds, that’s a good idea, however, as we’re using a computer rather than an actual receiver, I’d like to suggest that first we might look for ways to identify that buttons are checked or not, or that radio buttons are selected or not. Traditionally, this is done by the screen reader, which identifies those elements and their condition. When those elements are standardized, or their type and condition are relayed to the underlying screen info, the screen reader can automatically identify them. This would save one having to program their own special output of speech or sound for feedback. If one wanted to produce an adapted specialized version, these output optional tones and signals would be fine, but then you’ve got two separate applications to develop, which is going to take a whole lot more work for those involved.
>
> As far as Mac is concerned, they offer a lot of info about how to make things accessible. However, I realize that you’re working on several different platforms. Although the screen readers are different, all of them work in a similar way, e.g., identifying elements and their conditions, whether it be buttons, check boxes, text entry, steppers, etc, then allowing you to manipulate them via the keyboard. I also can’t tell you specifics, but some of the functionality we’re talking about is already done by the screen reader, as long as the screen elements are recognized by it. If Java is being used, it has its own accessibility routines built in, which most screen readers can use. I can’t say about other languages, but think we’re mostly on the same page here by adjusting the interface and screen elements to be more standard things that most screen readers will recognize.
>
> The idea of adjusting the individual digits of the frequency display is excellent, and I understand its already implemented in the program. If one could use the left and right arrows to move between the digits, and the up and down arrows to change them, that would be quite logical, and if done with the appropriate accessibility routines in place, digits will be read, and the beginning or end of the digits is identified so you know you can’t go further right or left.
>
> In this version, some things can be clicked via the VoiceOver controls, and others have to be done with the mouse. VoiceOver does have some control over the mouse, and can be used to move and click some elements, but the consistency and simplicity of being able to use standard keyboard commands, or at least to focus properly on a control so the screen reader can activate it would be helpful.
>
> Please know these aren’t criticisms, but are offered to hopefully help guide any further development. I very much appreciate what’s being done in this area, and will be glad to help by at least bata-testing in the Mac or Windows platforms when needed. I hope this discussion wasn’t either too elementary or complicated for those of you involved in the development, and I apologize to everyone else for its length. If it brings up questions or specifics which might require more discussion than the list needs, I’m willing to be contacted directly as well. Thanks again, and I’m looking forward to exploring more of the airwaves with what looks like a great package.
>
> Kevin
>
>
> --
> You received this message because you are subscribed to the Google Groups "Gqrx SDR" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to gqrx+unsubscribe@googlegroups.com.
> To post to this group, send email to gq...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/msgid/gqrx/625cef1e-3f8c-4fd3-a6f5-80057bd44f04%40googlegroups.com.
>
> For more options, visit https://groups.google.com/d/optout.
>
>
> --
> You received this message because you are subscribed to the Google Groups "Gqrx SDR" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to gqrx+unsubscribe@googlegroups.com.
> To post to this group, send email to gq...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/msgid/gqrx/CACopv_h9pGG85f_rr3h1DCF-Ayi8PHroT14tfVpaoo-ENhPoKQ%40mail.gmail.com.
> For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups "Gqrx SDR" group.
To unsubscribe from this group and stop receiving emails from it, send an email to gqrx+unsubscribe@googlegroups.com.
To post to this group, send email to gq...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/gqrx/1C458A17-E034-40DE-81FE-2DD77D90FDF5%40gmail.com.
--
You received this message because you are subscribed to the Google Groups "Gqrx SDR" group.
To unsubscribe from this group and stop receiving emails from it, send an email to gqrx+unsubscribe@googlegroups.com.
To post to this group, send email to gq...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/gqrx/CAHG%3DS_d__7nz7nueV164fsVAqKjHpAFLoXvreOeR6T0aM0U7VQ%40mail.gmail.com.
Alex
--
You received this message because you are subscribed to the Google Groups "Gqrx SDR" group.
To unsubscribe from this group and stop receiving emails from it, send an email to gqrx+unsubscribe@googlegroups.com.
To post to this group, send email to gq...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/gqrx/CAHG%3DS_fu7MbhL%3DftfG1Uy%2B7ktS9vE9iX5TA%2BveUMLUtfzCtZRw%40mail.gmail.com.
Alex
--
You received this message because you are subscribed to the Google Groups "Gqrx SDR" group.
To unsubscribe from this group and stop receiving emails from it, send an email to gqrx+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/gqrx/CAHG%3DS_dZg7bybc0BkX2G7byt884pRiz1V5UeVutBPx9EWEGbCg%40mail.gmail.com.
This version expects the users own screen reader software to 'do the talking'. Control-X to exit, Control-Y to synchronize the frequency between gqrx and this program (mainly used during debugging)
gqrx must be started with the 'Remote Control via TCP' button clicked and Port used is the default for gqrx
There are basically 4 different areas on the screen:
--
You received this message because you are subscribed to a topic in the Google Groups "Gqrx SDR" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/gqrx/JX3mLZwrvuM/unsubscribe.
To unsubscribe from this group and all its topics, send an email to gqrx+uns...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/gqrx/CACopv_i%3DtORQk9dEBAm_dV03n5H5M5hFyE%3DeLeRL6khmu%2B3-%2BA%40mail.gmail.com.
> To unsubscribe from this group and stop receiving emails from it, send an email to gqrx+unsubscribe@googlegroups.com.
> To post to this group, send email to gq...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/msgid/gqrx/CACopv_jzfqaZN_NRcu6%2BBa5QsJBU6_D2k-gexZjZfHtB2KJPnA%40mail.gmail.com.
> For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups "Gqrx SDR" group.
To unsubscribe from this group and stop receiving emails from it, send an email to gqrx+unsubscribe@googlegroups.com.
To post to this group, send email to gq...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/gqrx/77F88F7B-EAA0-4663-9983-F273E508D40F%40gmail.com.
>>>> an email to gqrx+unsubscribe@googlegroups.com.
>>>> To post to this group, send email to gq...@googlegroups.com.
>>>> To view this discussion on the web visit
>>>> https://groups.google.com/d/msgid/gqrx/CACopv_jzfqaZN_NRcu6%2BBa5QsJBU6_D2k-gexZjZfHtB2KJPnA%40mail.gmail.com.
>>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>> --
>>> You received this message because you are subscribed to the Google Groups
>>> "Gqrx SDR" group.
>>> To unsubscribe from this group and stop receiving emails from it, send an
>>> email to gqrx+unsubscribe@googlegroups.com.
>>> To post to this group, send email to gq...@googlegroups.com.
>>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/gqrx/77F88F7B-EAA0-4663-9983-F273E508D40F%40gmail.com.
>>> For more options, visit https://groups.google.com/d/optout.
>>
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "Gqrx SDR" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to gqrx+unsubscribe@googlegroups.com.
>> To post to this group, send email to gq...@googlegroups.com.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/gqrx/CACopv_huFykRBMEgFSGEp5fLq%2BBC8GcbyAN9UnA7U8j5nv0bUg%40mail.gmail.com.
>>
>> For more options, visit https://groups.google.com/d/optout.
>
> --
> You received this message because you are subscribed to the Google Groups "Gqrx SDR" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to gqrx+unsubscribe@googlegroups.com.
> To post to this group, send email to gq...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/msgid/gqrx/CAHG%3DS_cnmy7jcSwSHBw_d05pwGf2A0%2B8DGUyvb3xsMzoUJKQ_A%40mail.gmail.com.
> For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups "Gqrx SDR" group.
To unsubscribe from this group and stop receiving emails from it, send an email to gqrx+unsubscribe@googlegroups.com.
To post to this group, send email to gq...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/gqrx/E0890FF5-4922-4DF1-B1F1-95D7510BC4D3%40gmail.com.