New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Find a better wx.NewId replacement #896

Closed
RobinD42 opened this Issue Jun 25, 2018 · 1 comment

Comments

Projects
None yet
1 participant
@RobinD42
Member

RobinD42 commented Jun 25, 2018

Operating system: any
wxPython version: 4.0.2
Stock or custom build: any
Python version: any
Stock or custom build: any

Description of the problem:

See discussion starting at https://groups.google.com/d/msg/wxpython-users/QjNaxW0R7uc/j-3cYUCbBQAJ

In a nutshell, the deprecation of wx.NewId has revealed some issues. Mainly that the recommended replacement of wx.Window.NewControlId won't allow the reuse of those IDs after the first widget has been destroyed, and that anything else has the potential for conflicting IDs

@RobinD42

This comment has been minimized.

Member

RobinD42 commented Jun 26, 2018

Fixed by #897

@RobinD42 RobinD42 closed this Jun 26, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment