From jpwhiting at kde.org Tue Mar 3 03:16:12 2015 From: jpwhiting at kde.org (Jeremy Whiting) Date: Mon, 2 Mar 2015 19:16:12 -0700 Subject: [Accessibility] OS X QString::fromNSString Message-ID: Hello, Inside QtSpeech in the mac backend we have a method that worked fine with Qt 5.4.0. I've recently upgraded to Qt 5.4.1 and when trying to run the example widget I'm getting an exception thrown when we call QString::fromNSString on the age string we get from the NSSpeechSynthesizer voice's attributes NSDictionary. The backtrace in lldb looks like this: bowser:qtspeech jeremy$ lldb examples/widgets/hello_speak/hello_speak.app/Contents/MacOS/hello_speak (lldb) target create "examples/widgets/hello_speak/hello_speak.app/Contents/MacOS/hello_speak" Current executable set to 'examples/widgets/hello_speak/hello_speak.app/Contents/MacOS/hello_speak' (x86_64). (lldb) r Process 477 launched: '/Users/jeremy/devel/kde/src/qtspeech/examples/widgets/hello_speak/hello_speak.app/Contents/MacOS/hello_speak' (x86_64) Setting voice name to "Agnes" gender is "VoiceGenderFemale" age is 0x2337 2015-03-02 19:08:43.649 hello_speak[477:8289] -[__NSCFNumber length]: unrecognized selector sent to instance 0x2337 2015-03-02 19:08:43.649 hello_speak[477:8289] An uncaught exception was raised 2015-03-02 19:08:43.650 hello_speak[477:8289] -[__NSCFNumber length]: unrecognized selector sent to instance 0x2337 2015-03-02 19:08:43.650 hello_speak[477:8289] ( 0 CoreFoundation 0x00007fff92a7266c __exceptionPreprocess + 172 1 libobjc.A.dylib 0x00007fff93e6276e objc_exception_throw + 43 2 CoreFoundation 0x00007fff92a756dd -[NSObject(NSObject) doesNotRecognizeSelector:] + 205 3 CoreFoundation 0x00007fff929bcaa4 ___forwarding___ + 1028 4 CoreFoundation 0x00007fff929bc618 _CF_forwarding_prep_0 + 120 5 QtCore 0x000000010002742b _ZN7QString12fromNSStringEPK8NSString + 59 6 QtTextToSpeech 0x0000000100013f3e _ZNK23QTextToSpeechPrivateMac15voiceForNSVoiceEP8NSString + 1038 7 QtTextToSpeech 0x000000010001489b _ZNK23QTextToSpeechPrivateMac15availableVoicesEv + 219 8 QtTextToSpeech 0x00000001000155a3 _ZNK13QTextToSpeech15availableVoicesEv + 19 9 hello_speak 0x0000000100004590 _ZN10MainWindow13localeChangedERK7QLocale + 176 10 hello_speak 0x0000000100003dc7 _ZN10MainWindowC2EP7QWidget + 935 11 hello_speak 0x000000010000394e main + 62 12 hello_speak 0x0000000100003904 start + 52 13 ??? 0x0000000000000001 0x0 + 1 ) 2015-03-02 19:08:43.650 hello_speak[477:8289] *** Terminating app due to uncaught exception 'NSInvalidArgumentException', reason: '-[__NSCFNumber length]: unrecognized selector sent to instance 0x2337' *** First throw call stack: ( 0 CoreFoundation 0x00007fff92a7266c __exceptionPreprocess + 172 1 libobjc.A.dylib 0x00007fff93e6276e objc_exception_throw + 43 2 CoreFoundation 0x00007fff92a756dd -[NSObject(NSObject) doesNotRecognizeSelector:] + 205 3 CoreFoundation 0x00007fff929bcaa4 ___forwarding___ + 1028 4 CoreFoundation 0x00007fff929bc618 _CF_forwarding_prep_0 + 120 5 QtCore 0x000000010002742b _ZN7QString12fromNSStringEPK8NSString + 59 6 QtTextToSpeech 0x0000000100013f3e _ZNK23QTextToSpeechPrivateMac15voiceForNSVoiceEP8NSString + 1038 7 QtTextToSpeech 0x000000010001489b _ZNK23QTextToSpeechPrivateMac15availableVoicesEv + 219 8 QtTextToSpeech 0x00000001000155a3 _ZNK13QTextToSpeech15availableVoicesEv + 19 9 hello_speak 0x0000000100004590 _ZN10MainWindow13localeChangedERK7QLocale + 176 10 hello_speak 0x0000000100003dc7 _ZN10MainWindowC2EP7QWidget + 935 11 hello_speak 0x000000010000394e main + 62 12 hello_speak 0x0000000100003904 start + 52 13 ??? 0x0000000000000001 0x0 + 1 ) libc++abi.dylib: terminating with uncaught exception of type NSException Process 477 stopped * thread #1: tid = 0x2061, 0x00007fff94542286 libsystem_kernel.dylib`__pthread_kill + 10, queue = 'com.apple.main-thread', stop reason = signal SIGABRT frame #0: 0x00007fff94542286 libsystem_kernel.dylib`__pthread_kill + 10 libsystem_kernel.dylib`__pthread_kill + 10: -> 0x7fff94542286: jae 0x7fff94542290 ; __pthread_kill + 20 0x7fff94542288: movq %rax, %rdi 0x7fff9454228b: jmp 0x7fff9453dc53 ; cerror_nocancel 0x7fff94542290: retq (lldb) q Quitting LLDB will kill one or more processes. Do you really want to proceed: [Y/n] y Did something change within QString::fromNSString to cause it to throw an exception in some cases? It seems we are trying to send a message to some object that can't respond to that message. thanks, Jeremy -------------- next part -------------- An HTML attachment was scrubbed... URL: From jpwhiting at kde.org Tue Mar 3 03:31:44 2015 From: jpwhiting at kde.org (Jeremy Whiting) Date: Mon, 2 Mar 2015 19:31:44 -0700 Subject: [Accessibility] OS X QString::fromNSString In-Reply-To: References: Message-ID: I love it when I send a question to an e-mail list then find the answer myself. My bad, the NSSpeechSynthesizer documentation at apple was wrong. Filing a bug now. BR, Jeremy On Mon, Mar 2, 2015 at 7:16 PM, Jeremy Whiting wrote: > Hello, > > Inside QtSpeech in the mac backend we have a method that worked fine with > Qt 5.4.0. I've recently upgraded to Qt 5.4.1 and when trying to run the > example widget I'm getting an exception thrown when we call > QString::fromNSString on the age string we get from the NSSpeechSynthesizer > voice's attributes NSDictionary. The backtrace in lldb looks like this: > > bowser:qtspeech jeremy$ lldb > examples/widgets/hello_speak/hello_speak.app/Contents/MacOS/hello_speak > > (lldb) target create > "examples/widgets/hello_speak/hello_speak.app/Contents/MacOS/hello_speak" > > Current executable set to > 'examples/widgets/hello_speak/hello_speak.app/Contents/MacOS/hello_speak' > (x86_64). > > (lldb) r > > Process 477 launched: > '/Users/jeremy/devel/kde/src/qtspeech/examples/widgets/hello_speak/hello_speak.app/Contents/MacOS/hello_speak' > (x86_64) > > Setting voice name to "Agnes" > > gender is "VoiceGenderFemale" > > age is 0x2337 > > 2015-03-02 19:08:43.649 hello_speak[477:8289] -[__NSCFNumber length]: > unrecognized selector sent to instance 0x2337 > > 2015-03-02 19:08:43.649 hello_speak[477:8289] An uncaught exception was > raised > > 2015-03-02 19:08:43.650 hello_speak[477:8289] -[__NSCFNumber length]: > unrecognized selector sent to instance 0x2337 > > 2015-03-02 19:08:43.650 hello_speak[477:8289] ( > > 0 CoreFoundation 0x00007fff92a7266c > __exceptionPreprocess + 172 > > 1 libobjc.A.dylib 0x00007fff93e6276e > objc_exception_throw + 43 > > 2 CoreFoundation 0x00007fff92a756dd > -[NSObject(NSObject) doesNotRecognizeSelector:] + 205 > > 3 CoreFoundation 0x00007fff929bcaa4 > ___forwarding___ + 1028 > > 4 CoreFoundation 0x00007fff929bc618 > _CF_forwarding_prep_0 + 120 > > 5 QtCore 0x000000010002742b > _ZN7QString12fromNSStringEPK8NSString + 59 > > 6 QtTextToSpeech 0x0000000100013f3e > _ZNK23QTextToSpeechPrivateMac15voiceForNSVoiceEP8NSString + 1038 > > 7 QtTextToSpeech 0x000000010001489b > _ZNK23QTextToSpeechPrivateMac15availableVoicesEv + 219 > > 8 QtTextToSpeech 0x00000001000155a3 > _ZNK13QTextToSpeech15availableVoicesEv + 19 > > 9 hello_speak 0x0000000100004590 > _ZN10MainWindow13localeChangedERK7QLocale + 176 > > 10 hello_speak 0x0000000100003dc7 > _ZN10MainWindowC2EP7QWidget + 935 > > 11 hello_speak 0x000000010000394e main + 62 > > 12 hello_speak 0x0000000100003904 start + 52 > > 13 ??? 0x0000000000000001 0x0 + 1 > > ) > > 2015-03-02 19:08:43.650 hello_speak[477:8289] *** Terminating app due to > uncaught exception 'NSInvalidArgumentException', reason: '-[__NSCFNumber > length]: unrecognized selector sent to instance 0x2337' > > *** First throw call stack: > > ( > > 0 CoreFoundation 0x00007fff92a7266c > __exceptionPreprocess + 172 > > 1 libobjc.A.dylib 0x00007fff93e6276e > objc_exception_throw + 43 > > 2 CoreFoundation 0x00007fff92a756dd > -[NSObject(NSObject) doesNotRecognizeSelector:] + 205 > > 3 CoreFoundation 0x00007fff929bcaa4 > ___forwarding___ + 1028 > > 4 CoreFoundation 0x00007fff929bc618 > _CF_forwarding_prep_0 + 120 > > 5 QtCore 0x000000010002742b > _ZN7QString12fromNSStringEPK8NSString + 59 > > 6 QtTextToSpeech 0x0000000100013f3e > _ZNK23QTextToSpeechPrivateMac15voiceForNSVoiceEP8NSString + 1038 > > 7 QtTextToSpeech 0x000000010001489b > _ZNK23QTextToSpeechPrivateMac15availableVoicesEv + 219 > > 8 QtTextToSpeech 0x00000001000155a3 > _ZNK13QTextToSpeech15availableVoicesEv + 19 > > 9 hello_speak 0x0000000100004590 > _ZN10MainWindow13localeChangedERK7QLocale + 176 > > 10 hello_speak 0x0000000100003dc7 > _ZN10MainWindowC2EP7QWidget + 935 > > 11 hello_speak 0x000000010000394e main + 62 > > 12 hello_speak 0x0000000100003904 start + 52 > > 13 ??? 0x0000000000000001 0x0 + 1 > > ) > > libc++abi.dylib: terminating with uncaught exception of type NSException > > Process 477 stopped > > * thread #1: tid = 0x2061, 0x00007fff94542286 > libsystem_kernel.dylib`__pthread_kill + 10, queue = > 'com.apple.main-thread', stop reason = signal SIGABRT > > frame #0: 0x00007fff94542286 libsystem_kernel.dylib`__pthread_kill + 10 > > libsystem_kernel.dylib`__pthread_kill + 10: > > -> 0x7fff94542286: jae 0x7fff94542290 ; __pthread_kill + 20 > > 0x7fff94542288: movq %rax, %rdi > > 0x7fff9454228b: jmp 0x7fff9453dc53 ; cerror_nocancel > > 0x7fff94542290: retq > > (lldb) q > > Quitting LLDB will kill one or more processes. Do you really want to > proceed: [Y/n] y > > > Did something change within QString::fromNSString to cause it to throw an > exception in some cases? It seems we are trying to send a message to some > object that can't respond to that message. > > > thanks, > > Jeremy > -------------- next part -------------- An HTML attachment was scrubbed... URL: From Petri.Jarvenpaa at digia.com Mon Mar 16 13:57:57 2015 From: Petri.Jarvenpaa at digia.com (=?iso-8859-1?Q?J=E4rvenp=E4=E4_Petri?=) Date: Mon, 16 Mar 2015 12:57:57 +0000 Subject: [Accessibility] Qt mailing list migration Message-ID: Hello, We are migrating the mailing list server on Wednesday 18th of March around 09:00 EET. The change should be invisible to the normal user, but maintenance break of some sort is always possible. If you notice problems afterwards or have questions please contact : mika.hiekkamaki at digia.com and petri.jarvenpaa at digia.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From Petri.Jarvenpaa at digia.com Wed Mar 18 09:36:48 2015 From: Petri.Jarvenpaa at digia.com (=?iso-8859-1?Q?J=E4rvenp=E4=E4_Petri?=) Date: Wed, 18 Mar 2015 08:36:48 +0000 Subject: [Accessibility] Qt mailing list migration - UPDATE Message-ID: Hello again. Unfortunately we need to schedule a maintenance break for the Qt-project.org mailing list services for tomorrow (19th of March). Starting 09:00 EET mailing list services will be unavailable and emails sent to the lists will be lost. Break in services is scheduled to last until approx. noon, update to this notification will be sent once normal service resumes. Sorry about the inconvenience. -------------- next part -------------- An HTML attachment was scrubbed... URL: From Mika.Hiekkamaki at digia.com Thu Mar 19 09:42:24 2015 From: Mika.Hiekkamaki at digia.com (=?iso-8859-1?Q?Hiekkam=E4ki_Mika?=) Date: Thu, 19 Mar 2015 08:42:24 +0000 Subject: [Accessibility] Qt mailing list migration - DONE Message-ID: Hi, Qt mailing list server migration is now done. Please let me know if you find some problems. Best regards / Parhain terveisin Hiekkamäki Mika ICT Specialist, BS IT Digia Plc Piippukatu 11, FI-40101 Jyväskylä Finland Email: mika.hiekkamaki at digia.com Gsm: +358 44 5608550 Visit us at: www.digia.com ------------------------------------------------------------------ PRIVACY AND CONFIDENTIALITY NOTICE This message and any attachments are intended only for use by the named addressee and may contain privileged and/or confidential information. If you are not the named addressee you should not disseminate, copy or take any action in reliance on it. If you have received this message in error, please contact the sender immediately and delete the message and any attachments accompanying it. Digia Plc does not accept liability for any corruption, interception, amendment, tampering or viruses occurring to this message. ------------------------------------------------------------------ -------------- next part -------------- An HTML attachment was scrubbed... URL: From leos at uvic.ca Wed Mar 25 23:14:49 2015 From: leos at uvic.ca (Leo Spalteholz) Date: Wed, 25 Mar 2015 22:14:49 +0000 Subject: [Accessibility] VoiceOver support for scrolling QML ListView Message-ID: Does the VoiceOver support on iOS support scrolling in lists? We haven’t been successful in being able to scroll a ListView with the voiceover gesture (three finger swipe). Is there a trick to this or is it not supported? If not, any hints for where to look to add support for this? Thanks, Leo From frederik.gladhorn at theqtcompany.com Fri Mar 27 09:33:57 2015 From: frederik.gladhorn at theqtcompany.com (Frederik Gladhorn) Date: Fri, 27 Mar 2015 09:33:57 +0100 Subject: [Accessibility] VoiceOver support for scrolling QML ListView In-Reply-To: References: Message-ID: <13597879.xhI9I3iTbE@frederik-thinkcentre-m93p> On Wednesday, March 25, 2015 10:14:49 PM Leo Spalteholz wrote: > Does the VoiceOver support on iOS support scrolling in lists? We haven’t > been successful in being able to scroll a ListView with the voiceover > gesture (three finger swipe). Is there a trick to this or is it not > supported? If not, any hints for where to look to add support for this? This is semi-supported, it is missing a bit of glue code. https://bugreports.qt.io/browse/QTBUG-41980 I think the main issue for us is to figure out how much to move the flickable/list. You can work around it for now by moving the list manually. The Accessible property has these signals: void scrollUpAction(); void scrollDownAction(); void scrollLeftAction(); void scrollRightAction(); void previousPageAction(); void nextPageAction(); so you should be able to do something like: MyListView { Accessible.onScrollDownAction: { console.log("move the list around") } } Of course this should have a sensible default implementation, I'm not sure how soon I'll get around to implementing it though. If anyone wants to have a go at it, it should not be very hard to do. Greetings, Frederik > > Thanks, > Leo > > > _______________________________________________ > Accessibility mailing list > Accessibility at qt-project.org > http://lists.qt-project.org/mailman/listinfo/accessibility From vincenzo.rubano at icloud.com Fri Mar 27 12:10:33 2015 From: vincenzo.rubano at icloud.com (Vincenzo Rubano) Date: Fri, 27 Mar 2015 12:10:33 +0100 Subject: [Accessibility] Qt 5.4, improve voiceOver support for QLabel Message-ID: <23450267-7087-4A1E-88C6-8AAF5EF878F2@icloud.com> Hi all, recently, I had to test the mac OS X port of an emulator that we should use for a project at university. I’ve noticed a really annoying bug with QLabel. In fact, after reading the content of a QLabel, voiceOver speaks the word “text”. This is annoying for two reasons: 1. That word is used to announce a read-only text field, which of course is different from a label; 2. It adds an unnecessary information. Is there any fix planned for this bug? If not, is there any workaround we could use in that emulator source code? We’re using Qt 5.4. Thanks in advance for your help. Vincenzo. From leos at uvic.ca Fri Mar 27 22:50:07 2015 From: leos at uvic.ca (Leo Spalteholz) Date: Fri, 27 Mar 2015 21:50:07 +0000 Subject: [Accessibility] VoiceOver support for scrolling QML ListView In-Reply-To: <13597879.xhI9I3iTbE@frederik-thinkcentre-m93p> References: <13597879.xhI9I3iTbE@frederik-thinkcentre-m93p> Message-ID: <3C8DFC99-EB26-4E82-9EC6-078A305A768F@uvic.ca> > On Mar 27, 2015, at 1:33 AM, Frederik Gladhorn wrote: > > On Wednesday, March 25, 2015 10:14:49 PM Leo Spalteholz wrote: >> Does the VoiceOver support on iOS support scrolling in lists? We haven’t >> been successful in being able to scroll a ListView with the voiceover >> gesture (three finger swipe). Is there a trick to this or is it not >> supported? If not, any hints for where to look to add support for this? > > This is semi-supported, it is missing a bit of glue code. > https://bugreports.qt.io/browse/QTBUG-41980 > > I think the main issue for us is to figure out how much to move the > flickable/list. > > You can work around it for now by moving the list manually. > The Accessible property has these signals: > void scrollUpAction(); > void scrollDownAction(); > void scrollLeftAction(); > void scrollRightAction(); > void previousPageAction(); > void nextPageAction(); Thank you very much. This is great and in retrospect I should have found this! The default on iOS is to essentially scroll one page down. However this is often by row and you will get one overlapping row if it is a table view. For example the first page will show Rows 1-10, while one scroll down gesture (3 finger swipe up) will show rows 9-19 (and it will announce this as well “Rows nine to nineteen of forty four”). Will check what happens on Android. Leo