Popup windows will never become the focus window of the application. Meaning that window system events will be send directly to the "main" window, and then forwarded to any potential popup windows, if any. But since popup windows don't become "active", they won't receive the focus in event, and thus never call setFocus on their contentItem. This could cause setFocusInScope() to skip assigning the activeFocusItem to be the new focus item. Effectively breaking keyboard navigation for things like menus that are inside a menubar. Change-Id: Id1345aee09ed4dd31017781f5e0e6f5f925551e6 Reviewed-by: Richard Moe Gustavsen <richard.gustavsen@qt.io>
In cases where a button acts as a view for an action, provide the Action's accessibility information into the visual component so that it can convey the action's information into the accessibility infrastructure. This is done by creating a Accessibility proxy object in the button that will communicate the information from the action's accessibility as part of the button. If the properties of the Accessibility object in the button are modified, these values will prevail. Fixes: QTBUG-123123 Change-Id: Ibeddcc918616d717bb1704177d482ff88bfe99ef Reviewed-by: Mitch Curtis <mitch.curtis@qt.io>
This way you can create them using new and populate them manually (provided you have a way of obtaining type references to them). Task-number: QTBUG-124662 Change-Id: Icceacaefafc311044d519e4af011b078dbf2f1e7 Reviewed-by: Olivier De Cannière <olivier.decanniere@qt.io> Reviewed-by: Fabian Kosmale <fabian.kosmale@qt.io>
Add snippet and description of using QtQuickView in an Android Service. Task-number: QTBUG-124620 Change-Id: I04dcd4d11c810ebdf37bf73bed08a3361751464f Reviewed-by: Nicholas Bennett <nicholas.bennett@qt.io>
When QSHADER_VIEW_COUNT is > 1, then we need to offset the next uniform by the actual view count, even if the projection matrix count is smaller and we therefore do no initialize all matrices. This is a theoretical issue, but makes sense for consistency with how the generic renderer handles this error. Change-Id: Iccda597dac50a6c249df771814958e5f3754a870 Reviewed-by: Laszlo Agocs <laszlo.agocs@qt.io>
- Move snippets into a file so they are tested by tst_quick_examples. - Add snippet that shows how to construct a standalone font, which is useful for sharing fonts among Components, for example. Pick-to: 6.5 6.7 Change-Id: I87ef72c601060b6874d727aa4800f254c62f3eaf Reviewed-by: Ulf Hermann <ulf.hermann@qt.io> Reviewed-by: Fabian Kosmale <fabian.kosmale@qt.io>
Task-number: QTBUG-125291 Change-Id: Ia675c97c296fa1aad1a06b4c4de23b2f803ede7f Reviewed-by: Assam Boudjelthia <assam.boudjelthia@qt.io>
Previously QAndroidViewSignalManager was a direct child of the QQuickView. In JNI calls that we did not have a reference to the signal manager, we had to use findChild to get access to the instance of it. We add QAndroidQuickView as a QQuickView subclass that owns the QAndroidViewSignalManager instance. Task-number: QTBUG-124488 Change-Id: I02ad10756a4af1ac82f130f349e7c8b6f563c70c Reviewed-by: Assam Boudjelthia <assam.boudjelthia@qt.io>
SignalHelper renamed to QAndroidViewSignalManger SignalInfo nested struct renamed to ConnectionInfo And QAndroidViewSignalManger split into new header and source files. Task-number: QTBUG-124488 Change-Id: I77ab8bf995043993224a6c5cafce5ac57dca59d9 Reviewed-by: Assam Boudjelthia <assam.boudjelthia@qt.io>
We obtain pointers to the QQuickView and its root object in various functions of QtQuickView interals. The warning messages used to be scattered in these functions. 1- A functions has been added to get both QQuickView and root object instances in a tuple. 2- An static local message string has been added to be reused when outputting warnings 3- Retouched a few warning messages for consistency. Task-number: QTBUG-124522 Change-Id: I471ce390553e005380df360811ce15bff45c55ed Reviewed-by: Assam Boudjelthia <assam.boudjelthia@qt.io>