summaryrefslogtreecommitdiffstats
path: root/examples
diff options
context:
space:
mode:
authorNorwegian Rock Cat <qt-info@nokia.com>2009-06-03 13:25:46 (GMT)
committerNorwegian Rock Cat <qt-info@nokia.com>2009-06-03 13:38:23 (GMT)
commit826b2ec2067e725561db2892dd432c01f1d36bc7 (patch)
treedf16e9059dff5be72d944b39ef3b7cb1fbe7656b /examples
parentc9c8742b20c025ad893bdde48cf382267e0b646e (diff)
downloadQt-826b2ec2067e725561db2892dd432c01f1d36bc7.zip
Qt-826b2ec2067e725561db2892dd432c01f1d36bc7.tar.gz
Qt-826b2ec2067e725561db2892dd432c01f1d36bc7.tar.bz2
BT: Fix a crash in the SDI example in Cocoa
This was quite a bug and it showed to some issues that I hadn't taken into account when doing the initial port to Cocoa. The issue was that we weren't "merging" items into the application menu if an item had already been associated with it. Which seems OK for applications that create one window with one menubar, but breaks down horrible when you have multiple windows with each having their own menubar. The result is that items in the application menu potentially go to the wrong window (and the potential crash). Since there can only ever be one "Quit", "About", or "Preferences" menu item in Cocoa, we need to make sure that we keep these items in sync whenever we switch the menubar or remove actions that are being deleted. That's what we do here. FWIW, QActions with "ApplicationSpecificRole" for their menu role have potential to cause memory leaks or other bugs if abused. If you are a happy open source hacker who wants a thankless job, solving them would get you lots of goodwill in my book. Task-number: 255038 Reviewed-by: Richard Moe Gustavsen
Diffstat (limited to 'examples')
0 files changed, 0 insertions, 0 deletions