Spam detection software, running on the system "mx.qt-project.org",
has identified this incoming email as possible spam. The original
message has been attached to this so you can view it or label
similar future email. If you have any questions, see
the administrator of that system for details.
Content preview: Hi All, My previous message was flagged as spam for some
reason.
Hopefully this time it goes through, and I Apologize if you receive this
twice. Anyways, I'm trying to reorganize how QT presents QT built-in w [...]
Content analysis details: (4.8 points, 4.6 required)
pts rule name description
---- ---------------------- --------------------------------------------------
0.8 BAYES_50 BODY: Bayes spam probability is 40 to 60%
[score: 0.4972]
1.3 RCVD_ILLEGAL_IP Received: contains illegal IP address
-0.0 RCVD_IN_MSPIKE_H2 RBL: Average reputation (+2)
[40.92.47.65 listed in wl.mailspike.net]
0.0 SPF_HELO_NONE SPF: HELO does not publish an SPF Record
0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail
provider (chigookkim[at]hotmail.com)
0.4 KHOP_HELO_FCRDNS Relay HELO differs from its IP's reverse DNS
2.3 FORGED_MUA_MOZILLA Forged mail pretending to be from Mozilla
--- Begin Message ---
Hi All,
My previous message was flagged as spam for some reason. Hopefully this
time it goes through, and I Apologize if you receive this twice.
Anyways, I'm trying to reorganize how QT presents QT built-in widgets to
VoiceOver on Mac just for accessibility purpose.
What's the best way to reorganize how items appear in accessibility tree
without affecting GUI? For example, I would like to:
1. Relocate an item from current parent to another parent
2. Create a node and Group a number of items under that node as a sub level
It looks like I can change parent and children relationship through
QAccessibleInterface. However, is there a way to change
QAccessibleInterface for QT built-in widgets without modifying QT source
and recompiling?
On a related note, is there a way to modify accessibility properties
without having to subclassing and implementing QAccessibleInterface? For
example QWidget has setAccessibleName, and setAccessibleDescription.
If QWidget had something like removeAccessibleChild and
insertAccessibleChild, it would be pretty easy to modify the tree.
Or, if there was a way to utilize lambda to override member functions
and return different accessibility properties to accessibility clients...
Thanks!
Chi
--- End Message ---
_______________________________________________
Interest mailing list
Interest@qt-project.org
https://lists.qt-project.org/listinfo/interest
