Tk Source Code

View Ticket
Login
2026-10-24
10:14 • Closed ticket [1723059f]: entryconfigure destroys submenus plus 8 other changes artifact: 7696e650 user: nemethi
09:51
Fix for [1723059fff]: entryconfigure destroys submenus check-in: edff8f53 user: csaba tags: core-8-6-branch
09:36
Fix for [1723059fff]: entryconfigure destroys submenus check-in: a3f03a58 user: csaba tags: core-9-0-branch
09:32
Fix for [1723059fff]: entryconfigure destroys submenus check-in: 5f1de6fb user: csaba tags: trunk, main
2026-09-30
17:43
Merge trunk. Renumber the test for [1723059] to menu-45.1, since trunk now has another menu-42.1. closed check-in: 257a67c1 user: serhiy.storchaka tags: menu-clone-cascade-destroy
2026-09-25
15:45 • Ticket [1723059f] Entryconfigure destroys submenus status still Open with 6 other changes artifact: 69068d4d user: jan.nijtmans
2026-09-23
07:36 • Ticket [1723059f]: 3 changes artifact: a6ddabec user: serhiy.storchaka
07:35
Fix [1723059]: entryconfigure of a cascade entry destroys its menu

The entry of a cloned menu points to a clone of the cascade menu, not to the cascade menu itself. If the cascade entry of a menubar menu was configured with the menu which it already had, ConfigureMenuCloneEntries() passed the -menu option to the clones anyway, so their entries pointed to the cascade menu itself, and the next change of the entry deleted it as if it were a clone. Now the -menu option is not passed to the clones if the cascade menu is not changed. Test menu-42.1. check-in: ef4c3587 user: serhiy.storchaka tags: menu-clone-cascade-destroy

2007-05-22
04:29 • Add attachment menutst.tk to ticket [1723059f] artifact: 8a999c12 user: kaitzschu
04:29 • Ticket [1723059f] Entryconfigure destroys submenus status still Open with 4 other changes artifact: 625c9b3b user: kaitzschu
2007-05-21
21:29 • New ticket [1723059f]. artifact: 240ceec4 user: kaitzschu

Ticket UUID: 1723059
Title: entryconfigure destroys submenus
Type: Bug Version: obsolete: 8.5a6
Submitter: kaitzschu Created on: 2007-05-21 21:29:58
Subsystem: 10. Generic Menus Assigned To: jan.nijtmans
Priority: 5 Medium Severity: Minor
Status: Closed Last Modified: 2026-10-24 10:14:56
Resolution: Fixed Closed By: nemethi
    Closed on: 2026-10-24 10:14:56
Description:
When creating a toplevel menubar (. configure -menu ...) and assigning it the same cascade submenu as it has and then replacing submenu with another the previous submenu is destroyed!

Bad explanation, attached script demonstrates behaviour.
User Comments: nemethi (claiming to be Csaba Nemethi) added on 2026-10-24 10:14:56:

Serhiy, many thanks for the fix! Merged into main, core-9-0-branch, and core-8-6-branch by commits [5f1de6fb], [a3f03a58], and [edff8f53]. The relevant test is menu-47.1.


serhiy.storchaka added on 2026-09-23 07:36:25:

The entry of a cloned menu points to a clone of the cascade menu, not to the cascade menu itself. When the entry was configured with the menu which it already had, ConfigureMenuCloneEntries() passed -menu to the clones anyway, so their entries pointed to the cascade menu itself, and the next change of the entry deleted it as a clone.

Fixed on branch menu-clone-cascade-destroy in [ef4c358706]: -menu is not passed to the clones if the cascade menu is not changed. Test menu-42.1.


kaitzschu added on 2007-05-22 04:29:58:

File Added - 230044: menutst.tk

Attachments: