Hi Phillip,
At 19:24 29/06/2006, you wrote:
>First off, I'd like to say that I really like DialogBlocks. It's making
>the project I'm working on much easier.
Good!
> After using it for a while, I've got a few suggestions.
>
>When writing the member variable code, check to make sure there aren't any
>duplicate ID's. I ran into this when I changed a wxStaticText to a
>wxChoice and didn't change the ID from "wxID_STATIC".
Mm, the problem with that is that you might sometimes wish to have some
duplicate ids (such as multiple static controls) but it could
be configurable.
>Also, check to see that there aren't any duplicate member variable
>names. When copying and pasting a control with a member variable name,
>the variable name doesn't change, so you get redefined variables. It
>fails to compile, so it's a little more obvious than the above situation
>which doesn't fail until runtime. 
Good point! I've been thinking about a further tab on the
output/error/debug window
which will show results of checking for these kinds of problems.
>It would be nice to have a setting for a default border size, preferably
>separate ones for sizers and controls. The way I'm laying things out, I'm
>using the sizers, spacers, and the spacing for wxFlexGridSizer to control
>spacing, and I'm setting most of the controls to have a border of 0.
I'll put that on my to-do list.
>One annoying thing in the UI (which I strongly suspect is from wxGrid,
>since I've got the same problem in one of my programs) is that you have to
>click 4 times to change to and modify a value that uses a wxChoice.
Er, yes, this isn't great and yes, I do use wxGrid. I have code in
place to use wxPropertyGrid instead but there are a few things
that need to polishing in wxPropertyGrid so I've not enabled
it just yet. Hopefully when I finally do, it will be an improvement.
>Thanks for making a very useful program!
My pleasure! Thanks a lot for the feedback.
Best regards,
Julian