Project

General

Profile

Actions

Bug #3029

closed

Submenus stay open for WPopupMenu deleted from within WPopupMenu::triggered() signal

Added by Jan Lindemann almost 10 years ago. Updated almost 9 years ago.

Status:
Closed
Priority:
Normal
Assignee:
-
Target version:
Start date:
04/29/2014
Due date:
% Done:

0%

Estimated time:

Description

Spawned from http://redmine.emweb.be/boards/2/topics/8918?r=8938#message-8938.

This is with Wt 3.3.2-20140421, commit id 89bd229f7f0aefdfa3d30210edf523aabacd9c9b.

Calling delete on a WPooupMenu instance from within the context of

its triggered() signal closes the menu but not its submenus.

With every newly created popup menu, I also see a growing

group of warning messages in the console log:

"Wt: decodeSignal(): signal 'o5oerc1.cancel' not exposed"

The number of messages in a group grows by one with every new

popup menu.

As Koen already pointed out in the aforementioned forum link,

not deleting the menu instance in the triggered() callback

makes the sticky submenus go away but leaves the problem of

finding another obvious place for deleting the menu instance.

Aminimal application that exhibits this behaviour is attached.


Files

Actions #1

Updated by Jan Lindemann almost 10 years ago

Update: This works fine with current git (54837d1cb3223fac68ac555c2009ea70cc61c15c), i.e. wt 3.3.3 RC1+.

Best regards

Jan

Actions #2

Updated by Koen Deforche almost 9 years ago

  • Status changed from New to Closed
  • Target version set to 3.3.3
Actions

Also available in: Atom PDF