Qt Creator assumes that WA_AcceptTouchEvents is in the Qt::ApplicationAttribute.
-
Hello,
Before of creating a bug report I should to ask you - is it bug or not?
-
If I call
print(dir(Qt.ApplicationAttribute))
in PyQt6 it doesn't show meWA_AcceptTouchEvents
. Qt Creator should not showWA_AcceptTouchEvents
if I typeQt::ApplicationAttribute::
What PyQt6 shows:
['AA_CompressHighFrequencyEvents', 'AA_CompressTabletEvents', 'AA_DisableNativeVirtualKeyboard', 'AA_DisableSessionManager', 'AA_DisableShaderDiskCache', 'AA_DontCheckOpenGLContextThreadAffinity', 'AA_DontCreateNativeWidgetSiblings', 'AA_DontShowIconsInMenus', 'AA_DontShowShortcutsInContextMenus', 'AA_DontUseNativeDialogs', 'AA_DontUseNativeMenuBar', 'AA_ForceRasterWidgets', 'AA_MacDontSwapCtrlAndMeta', 'AA_NativeWindows', 'AA_PluginApplication', 'AA_SetPalette', 'AA_ShareOpenGLContexts', 'AA_SynthesizeMouseForUnhandledTabletEvents', 'AA_SynthesizeMouseForUnhandledTouchEvents', 'AA_SynthesizeTouchForUnhandledMouseEvents', 'AA_Use96Dpi', 'AA_UseDesktopOpenGL', 'AA_UseOpenGLES', 'AA_UseSoftwareOpenGL', 'AA_UseStyleSheetPropagationInWidgetStyles', '__class__', '__doc__', '__members__', '__module__']
As I already told you on SO it's because you use an unneeded quaification. It's Qt::WA_AcceptToucEvents, not Qt::<WHATEVER>::WA_TouchEvents. So it's ignoring <WHATEVER> and shows you the hint which is wrong but only due to your wrong qualification before. Shit in - shit out.
-
If I call
print(dir(Qt.ApplicationAttribute))
in PyQt6 it doesn't show meWA_AcceptTouchEvents
. Qt Creator should not showWA_AcceptTouchEvents
if I typeQt::ApplicationAttribute::
What PyQt6 shows:
['AA_CompressHighFrequencyEvents', 'AA_CompressTabletEvents', 'AA_DisableNativeVirtualKeyboard', 'AA_DisableSessionManager', 'AA_DisableShaderDiskCache', 'AA_DontCheckOpenGLContextThreadAffinity', 'AA_DontCreateNativeWidgetSiblings', 'AA_DontShowIconsInMenus', 'AA_DontShowShortcutsInContextMenus', 'AA_DontUseNativeDialogs', 'AA_DontUseNativeMenuBar', 'AA_ForceRasterWidgets', 'AA_MacDontSwapCtrlAndMeta', 'AA_NativeWindows', 'AA_PluginApplication', 'AA_SetPalette', 'AA_ShareOpenGLContexts', 'AA_SynthesizeMouseForUnhandledTabletEvents', 'AA_SynthesizeMouseForUnhandledTouchEvents', 'AA_SynthesizeTouchForUnhandledMouseEvents', 'AA_Use96Dpi', 'AA_UseDesktopOpenGL', 'AA_UseOpenGLES', 'AA_UseSoftwareOpenGL', 'AA_UseStyleSheetPropagationInWidgetStyles', '__class__', '__doc__', '__members__', '__module__']
-
If I call
print(dir(Qt.ApplicationAttribute))
in PyQt6 it doesn't show meWA_AcceptTouchEvents
. Qt Creator should not showWA_AcceptTouchEvents
if I typeQt::ApplicationAttribute::
What PyQt6 shows:
['AA_CompressHighFrequencyEvents', 'AA_CompressTabletEvents', 'AA_DisableNativeVirtualKeyboard', 'AA_DisableSessionManager', 'AA_DisableShaderDiskCache', 'AA_DontCheckOpenGLContextThreadAffinity', 'AA_DontCreateNativeWidgetSiblings', 'AA_DontShowIconsInMenus', 'AA_DontShowShortcutsInContextMenus', 'AA_DontUseNativeDialogs', 'AA_DontUseNativeMenuBar', 'AA_ForceRasterWidgets', 'AA_MacDontSwapCtrlAndMeta', 'AA_NativeWindows', 'AA_PluginApplication', 'AA_SetPalette', 'AA_ShareOpenGLContexts', 'AA_SynthesizeMouseForUnhandledTabletEvents', 'AA_SynthesizeMouseForUnhandledTouchEvents', 'AA_SynthesizeTouchForUnhandledMouseEvents', 'AA_Use96Dpi', 'AA_UseDesktopOpenGL', 'AA_UseOpenGLES', 'AA_UseSoftwareOpenGL', 'AA_UseStyleSheetPropagationInWidgetStyles', '__class__', '__doc__', '__members__', '__module__']
As I already told you on SO it's because you use an unneeded quaification. It's Qt::WA_AcceptToucEvents, not Qt::<WHATEVER>::WA_TouchEvents. So it's ignoring <WHATEVER> and shows you the hint which is wrong but only due to your wrong qualification before. Shit in - shit out.
-
8 8Observer8 has marked this topic as solved on
-
As I already told you on SO it's because you use an unneeded quaification. It's Qt::WA_AcceptToucEvents, not Qt::<WHATEVER>::WA_TouchEvents. So it's ignoring <WHATEVER> and shows you the hint which is wrong but only due to your wrong qualification before. Shit in - shit out.
@Christian-Ehrlicher I understand now. Thank you very much!
-
8 8Observer8 referenced this topic on