Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Groups
  • Search
  • Get Qt Extensions
  • Unsolved
Collapse
Brand Logo
  1. Home
  2. Qt Development
  3. General and Desktop
  4. Disabling accessibility support on Mac
Forum Updated to NodeBB v4.3 + New Features

Disabling accessibility support on Mac

Scheduled Pinned Locked Moved Unsolved General and Desktop
2 Posts 2 Posters 442 Views 1 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • Thuan_FirelightT Offline
    Thuan_FirelightT Offline
    Thuan_Firelight
    wrote on last edited by
    #1

    We are using Qt 5.4.1 and accessibility support on Mac seems pretty flaky. For starters, our app would crash if if Voice Over is enabled (looking at the callstack it seems to hit a recursive code and resulted in a stack overflow)?

    Instead of trying to fix this, is there any way an application can opt out of accessibility altogether? I tried setting the QAccessible::setRootObject but that didn't work. Would implementing a custom InterfaceFactory and returning a dummy accessibility interface work? If so, what is the best thing to do for the dummy? I tried just returning null or 0, false, etc but they all eventually crash at some point (related to accessibility).

    J.HilkJ 1 Reply Last reply
    0
    • Thuan_FirelightT Thuan_Firelight

      We are using Qt 5.4.1 and accessibility support on Mac seems pretty flaky. For starters, our app would crash if if Voice Over is enabled (looking at the callstack it seems to hit a recursive code and resulted in a stack overflow)?

      Instead of trying to fix this, is there any way an application can opt out of accessibility altogether? I tried setting the QAccessible::setRootObject but that didn't work. Would implementing a custom InterfaceFactory and returning a dummy accessibility interface work? If so, what is the best thing to do for the dummy? I tried just returning null or 0, false, etc but they all eventually crash at some point (related to accessibility).

      J.HilkJ Offline
      J.HilkJ Offline
      J.Hilk
      Moderators
      wrote on last edited by J.Hilk
      #2

      @Thuan_Firelight I can't help you with disabling the accessibility support, but have you considert increasing the stack size?
      http://doc.qt.io/qt-5/qthread.html#setStackSize

      IIRC MacOS limits all non mainthreads to 100 or 200k (BYTES!). In my opinion that is so < (year)2000 but, it is what it is. Thankfully we have ways to increase that on the go. I've run into stackoverflow on mac during recursive calculations before and the only thing put on the stack was the return adress for when the functions returns.


      Be aware of the Qt Code of Conduct, when posting : https://forum.qt.io/topic/113070/qt-code-of-conduct


      Q: What's that?
      A: It's blue light.
      Q: What does it do?
      A: It turns blue.

      1 Reply Last reply
      1

      • Login

      • Login or register to search.
      • First post
        Last post
      0
      • Categories
      • Recent
      • Tags
      • Popular
      • Users
      • Groups
      • Search
      • Get Qt Extensions
      • Unsolved