b5c3a3fe73
On some platforms the capabilities of a device can change at runtime, and we don't want to model this as a "new device" appearing in place of the old one. We already made the capabilities property non-CONSTANT, but let's add a NOTIFY as well for completeness. I considered making the capabilities member protected, but QXcbConnection's xi2 handling relies on modifying the caps as part of creating the device. Fixes: QTBUG-132281 Change-Id: Ic345475b179f4562cdd39ecf51c7d6738ad47a74 Reviewed-by: Shawn Rutledge <shawn.rutledge@qt.io> (cherry picked from commit d74079873bbbff8701ec9b254647624775ced27a) Reviewed-by: Qt Cherry-pick Bot <cherrypick_bot@qt-project.org>