I've got a fair number of bugs here, but let me preface my remarks by
saying I think VisualWx might already be the finest wxWidgets program
editor out there. Some others don't build nearly complete programs
including events, such as wxFormBuilder. One or two others can't edit
the contents of notebook panels, not to mention the contents of spiffy
classes like list books. Of the ones I tried, it is the ONLY one I
could just create a frame and start dragging components to where I
thought they should be, like in Visual Studio. VisualWx does NOT
require everything to be in a layout before you can even add a widget,
making layouts what they were intended to be, a handy advancement over
the usual way of doing forms. While I've found a few bugs in it, I've
found nothing that really prevents me from using it. Although I am
quite new to wxWidgets, I don't know of a more intuitive GUI for RAD for
wxWidgets. I may well be missing a better one, but if so, I do not know
what it is. Installation was a breeze under XP - only getting g++ to
run under windows was bey0nd me (so I just used MSVC++ 8, and
encountered very few problems, once the proper lib and header
directories are set). A rich selection of wxWidgets properties are
already supported. I already like it a lot, although it is not yet
vers. 1.0. These remarks pertain to version 0.86.7.0, but should in no
way be interpreted as saying its not already an excellet app, as is.



Bug report for VisualWx

- Sometimes upon creating functions, it does not delete them. As I was

new to VisualWx, and I told it not to delete the function two times,

but it happened with four unrelated functions, it is difficult to

say where these orphaned functions came from. Two were "All" type

event handlers, and I think some might not have been deleted
properly.

Also, it might be nice to have a button to purge orphaned functions
from

the code. These were giving me compile errors in MSVC++ 8 native
mode.

- Build fails, but doesn't tell me why. I installed gc++ and MSYS. It

is also unclear as to whether it needs the bin or the main
directories

for these, although I tried both. I think it is MSYS that it can't
seem

to find. (Does it need the source module too?)

- If I try to put a toolbar in a layout, it leaves room for the toolbar
above

the first layout, in which nothing shows, and still shows the toolbar
in the

layout. I don't know if it is allowable to put a toolbar in a
layout, but if

it is, then the display is handled wrong. If it is not, then this
should be

disallowed in VisualWx as well.

- When I resize a widget in the layout by dragging it, e.g. a
horizontal box

layout doesn't reposition it immediately, although in the final
frame,

it is. In order to see the result, I must save, close and reopen the

frame. It'd be nice to have an always update option, or a redraw
frame

option. I know that you have a ReLayout choice in Environment
Options, but

it forcibly saves the frame, which is not necessarily what one wants.

- When I set the status bar text, it is not enclosed in wxT() or _(),
and

this breaks it when compiling with the Unicode option on.





Feature suggestions:

- Component config file? log file? (Not terribly important, but still
helpful.)

- Taskbar Icon properties, so that it doesn't go in the icon tray all
the time.

- Would prefer redraw of frames while dragging.

- Contributed LED widget will not compile under wxWidgets 2.8.3, and
should

be dropped until it can be.

- Double-click to paste script into code? standard C++ scripts?

- Tool tip info for "A" checkbox (all type functions in events)

- Install with wxWidgets manual (optional?), or just allow a URL to

point to the latest on the wxWidgets site.

- I encourage you to show the menu names and items, and icons in toobar
buttons

during development. (Not terribly important, but still helpful.)

- Minimum size parameters for the main form?

- Something sick is going on with the status bar in the wx code. They
have

a bad fix for when you set the status bar, and have help items on
menus.

The status bar reverts to its initial value after the menus are
destroyed,

but if you e.g. change the status bar text in a button event handler,
it

keeps reverting to the first thing you left the text as after
initialization.

In order to disable it, you need to do a "SetStatusBarPane(-1);" in
able to

disable the menu help. It'd be nice to have an option to disable the

menu help for status bars, and it'd insert this line. I add it in

"MyFrame::initAfter();".

- MSVC++ support!!! Lack of support for it will be an obstacle to
acceptence

to VisualWx. You don't need to build sln files, but at least be able
to use

gnu-make to call it command line style.

- A local chm help manual for VisualWx. One must hack one's way
through to use

it currently. (I know you already know this. I'll quit stating the
obvious now.)

We could especially use a complete walkthrough as to how to add
custom widgets.

- Support for the pie chart widget seems a natural inclusion (although
I think we

ultimately need a wxWidget for gnnPlot or Ploticus, while the latter
still

needs a non-file oriented C++ API). Calc would also be a nice one to
support.

- As you support definition of additional widgets, some ppl probably
have used it.

How can they share their successes with us? How about a way to
export and

import setups for extra widgets?

- How about selecting the frame when the title bar is clicked?
Clicking a tool

only selects the toolbar, not the tool.





[Non-text portions of this message have been removed]