KeyWorksRW

Moving to 1.1.x milestone -- I don't want to hold up the 1.1 release for this.

Scintilla decides how keywords get colored, so this is likely to prove very difficult to fix, short of coloring the keywords ourselves.

There isn't time to do this for the 1.1 release, so moving the milestone to 1.1x.

There is support for `wxAuiNotebook` and `wxAuiToolbar`, but **wxUiEditor** does not currently support the main AUI manager. As far as building wxUiEditor, you can use any toolchain supported by CMake....

Glad to hear this got resolved for you. I'm going to leave this issue open because I want to look further into getting something in place that makes it possible...

Unfortunately, I think the only way to fix this would be to subclass the property panel and provide our own implementation. That would allow for adding a command that brings...

The description box is maintained via two wxStaticText controls: `m_pTxtHelpCaption` and `m_pTxtHelpContent`. In the wxPropertyGridManager declaration (manager.h), these variables are `protected:` and there is no `public:` function to get them....

Once the hidden and magnify toolbar buttons become part of the Mockup panel, we could add a dropdown menu that let's the user choose which language to Mockup (C++, Python,...

The problem I see is that FromDIP changes the value based on the current display resolution by calling **GetPPI()**, whereas dialog units call **GetAverageASCIILetterSize()**. If the system font changes either...

I'm leaving the issue open because I do need to separate coordinates for text from coordinates for graphics (including sizes of UI elements like tabs). I want to think more...