Getting "QAccessibleWidget...does not support subelements" error

[gobbldygook]

I've successfully worked with MO for a considerable number of hours over the past few months. This morning, after having successfully installed STEP 2.2.9, I was working on setting up REGS. I can only figure I clicked on something wrong, or tried to drag & drop something incorrectly, because I started getting an error saying "QAccessibleWidget::rect: This implementation does not support subelements! (ID __ unknown for QWidget)". The __ is a number that changes depending on what I click on. The error pops up when I click in the log area, in the plugin list area, and in the mod list area, as well as the category area. When I click on the right-hand tabs, it will change and say "(ID __ unknown for QTabBar)". ((If my memory serves, I was dragging and dropping something from overwrite, wanted to cancel it, found a place where there was a circle-with-a-bar sign, and let go there. I thiiiink this may be when the error started popping up??))

 

I thought perhaps this was a glitch in my MO install - uninstalled it, leaving mods/profiles/etc intact, and reinstalled it. Still getting the same problem, however.

 

Haven't found any thing about it on the STEP forums, and only thing I saw through googling was this link: https://bugreports.qt-project.org/browse/QTBUG-20969 . Neither it nor google's cached version are loading for me, though, so I have no idea if it's relevent.

 

So, my first question would be - is it possible to keep modding despite this error/is it having any effect on me installing/positioning mods? And secondly, suggestions on how to fix?

 

Thanks a bunch!

[Tannin]

The warning shouldn't do anything.

the qaccessible stuff is for supporting accessibility for users with disabilities (i.e. high-contrast ui or special keyboard shortcuts)

This subsystem seems to be incompatible with certain input devices, most prominently wacom tablets and mice.

There appear to be some high-precision mice from other vendors that also don't play well with qt.

 

This is something I could fix on my side only by updating to qt 5 and that unfortunately brings along new problems.

[DoubleYou]

Never heard of this error. The bug report you link to indicates that the problem is fixed, so unless you have an old version of QT installed, I can't see how that would be relevant. Try posting on the Mod Organizer Bug Tracker. https://issue.tannin.eu/tbg/modorganizer/issues/open

[gobbldygook]

I've continued modding and not noticed anything messing up in-game due to the messages, so I figured it wasn't doing anything. Thanks for the confirmation that I don't have to worry about it!

 

I think it's rather strange that it only just started happening, but it's easily ignorable and it would seem not many others have had this problem. I totally understand that you don't want to make more problems for yourself by updating to qt 5!