Replies: 1 comment
-
|
As far as i remember there are many locations with hardcoded information that make it nearly impossible to add anything but simple wxWindow based user elements through plugins. Especially top level elements need special processing in multiple locations, so im afraid your suggestions are not possible in the near feature. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Currently, wxFormBuilder uses hardcoded class name checks to identify top-level windows that support title bars, menu bars, and status bars:
`Cpp
m_form->GetClassName() == wxT("Frame") ||
m_form->GetClassName() == wxT("Dialog") ||
m_form->GetClassName() == wxT("Wizard")
`
This implementation prevents users from working with custom Frame, Dialog, or Wizard classes that inherit from these base classes. I want to extend these base classes to add custom functionality, but wxFormBuilder doesn't recognize them as valid top-level windows.
Suggested Improvement:
It would be more flexible if wxFormBuilder could:
Thanks!
Beta Was this translation helpful? Give feedback.
All reactions