wxFormBuilder v3.0 - RC6 Released

We are proud to announce another release candidate of wxFormBuilder v3.0. We really appreciate all the users that have been reporting bugs, so please continue. Please test this release and post any problems or concerns on the forum. wxFormBuilder is now feature frozen until the official release comes out. Only bug fixes will be added. This release focuses on bug fixes. Here are the changes:
ChangeLog:

02/01/2008 Version 3.00.54 (RC6)
* FS#308 - Bugs in non-interactive (-g) mode
Note: stderr is not normally available on Windows for GUI apps. If -g is used, all logging goes to stderr and debug output. Either start the process with a pipe for stderr (most IDEs will do this for you), or use a Debug Viewer to watch the output.
* FS#311 - wxFB 3.0 RC5 still generating incorrect wxMenu(item) code


Legend: ‘+’ = Addition, ‘*’ = Bug Fix, ‘-‘ = Removed, ‘~’ = Move, ‘^’ = Updated

2 Responses to “wxFormBuilder v3.0 - RC6 Released”

  1. pavel Says:

    Thanks very for this fantastic tool!!!

    This is quite helpful and easy to work with and even has features which are missing in other tools.

    Possibility to use own controls or derived controls and use them with GUI design is very useful.

    Separation of generated code from code which developer writes is fantastic.

    I hope I will be able to get to the stage I could be helpful for this project, since I miss still some features there.

    Features which I am missing still there:

    * wxContextMenuEvent for every wxWindow

    * Possibility to arrange GUI without sizers with only using window positions. This could be useful in some cases.

    regards,
    pavel

  2. RJP Computing Says:

    Thanks! We love it. :)

    > Features which I am missing still there:
    > * wxContextMenuEvent for every wxWindow
    Please add an issue on the issue tracker for this. All events are suppose to be supported.

    > * Possibility to arrange GUI without sizers with only using window positions. This could be useful in some cases.
    This will most likely never be supported. This not in our plans any time soon. It just goes against our design goals. That doesn’t mean that another developer couldn’t add it, just that the core developers don’t believe in manual layout. :) Not trying to scare you off.

Leave a Reply