Feb-10-2017, 10:26 AM
Thanks to both of you!
I can't say that I understand what's happening with the IDs, but it works.
It guess that I was led into this trap by the "Style Guide" from https://wiki.wxpython.org/wxPython%20Style%20Guide. It's more or less the only site where I could find something about the usage of ids in wxpython at all. There, it's written:
If I use the menu build-up pattern I had in the beginnig, the id seems to be a 'required argument'. Unfortunately, the guide only writes something about the standard menus, but nothing is mentioned for other (own) menu items. So, I did what it writes - I used wx.ID_ANY. I have seen that other people use 'fixed' ids in that case, but I rated the style guide higher. I assume that there is a secret list of 'fixed' ids, and I would prefer to avoid collisions that may lead to hard-to-detect misfunctions if I accidentally hit a predefined id.
And if I understand, Yoritz' code allows to circumvent this by naming the object that is created by the 'Append' and used the id that is 'packed' into it, therefore no more being an (explicit) 'required argument'.
Well, now I wonder more that most of the code was working well, and the misfunction was completely reproducable. I would have guessed that in the case of an assignment of 'random' ids there would be a more 'random' behaviour, too.
And: Does someone know a place where one can learn more about the secrets of ids in wxpython? I searched the docs, but the seem to write nothing at all about ids.
I can't say that I understand what's happening with the IDs, but it works.
It guess that I was led into this trap by the "Style Guide" from https://wiki.wxpython.org/wxPython%20Style%20Guide. It's more or less the only site where I could find something about the usage of ids in wxpython at all. There, it's written:
Quote:Don't use IDs. There is very rarely a good reason to use them.
...
If the id is a required argument, use wx.ID_ANY.
...
EXCEPTION: (there's always an exception!) Use standard IDs for standard menus, buttons, etc. It is useful to use the standard IDs because they may turn on standard functionality, such as menu item remapping for wxMac, automatic Dialog completion or cancellation, using stock button labels and images, etc.
...
By using your own ids you just block this ability to play by the rules.
If I use the menu build-up pattern I had in the beginnig, the id seems to be a 'required argument'. Unfortunately, the guide only writes something about the standard menus, but nothing is mentioned for other (own) menu items. So, I did what it writes - I used wx.ID_ANY. I have seen that other people use 'fixed' ids in that case, but I rated the style guide higher. I assume that there is a secret list of 'fixed' ids, and I would prefer to avoid collisions that may lead to hard-to-detect misfunctions if I accidentally hit a predefined id.
And if I understand, Yoritz' code allows to circumvent this by naming the object that is created by the 'Append' and used the id that is 'packed' into it, therefore no more being an (explicit) 'required argument'.
Well, now I wonder more that most of the code was working well, and the misfunction was completely reproducable. I would have guessed that in the case of an assignment of 'random' ids there would be a more 'random' behaviour, too.
And: Does someone know a place where one can learn more about the secrets of ids in wxpython? I searched the docs, but the seem to write nothing at all about ids.