KeyWorksRW

### Description: Event names like wxEVT_AUINOTEBOOK_PAGE_CLOSE can be quite long, and when displayed in the property grid, the right side of the event name can be cut off. The user...

### Description: Both gen_python.cpp and gen_ruby.cpp have comments about support persistence for that language. I'm adding this as an issue to make it easier to track. [ ] wxPython does...

### Description: The `cpp_conditional` property available for most forms couild be expanded to support containers and sizers. It could also support an `else_conditional` property. If a custom property dialog was...

### Description: I don't know yet if this is a bug or by design, but even in wxWidgets 3.3, tool bitmaps in a wxAuiToolbar do _not_ get scaled for the...

### Description: While the Insert Widget does list all possible children, it often ends up being a huge alphabetized list. That's sort of okay if the user knows the name...

### Description: wxBitmapComboBox isn't really usable in it's current form, because there isn't any way to add items and associated bitmaps. The prop_contents just displays a normal string -- this...

### Description: Building from CMake is fine for people who are used to building from a command line. On Windows, a _lot_ of people are going to be using either...

### Description: It would make sense both when a project is loaded, created, imported or just the code preference property is changed to also change the order of the code...

Improve the Property Panel description box.

2

### Description: I'm not sure this is possible, but the help panel for properties that have a drop down list have a very odd display. For example, the class access...

### Description: There are actually quite a few widgets that have generic versions. It might make sense to implement a property called "use_generic_version" and only display the property if the...