Re: EditGrid options

It's rumoured that Andreas Pflug once said:
> Hi Dave,
>
> I just had a look at your recent work, and have some remarks.
>
> - You know I'm not really a fan of popup windows (especially the modal
> ones), can't we implement this in a different way?

I don't think it's an unreasonable use of a modal dialogue - I think it's
more intuitive than using seperate tab on the main form and having an
apply button either update invisible data, or control the tabset.
> - The sort (filter-to-come) options are not visible.

Not sure what you mean. The filter options aren't visible because I
haven't implemented them yet. That's planned for this week, but should be
quicker and easier than sort, even with syntax validation.
> - for very large tables, it's annoying if the query is run immediately
> when starting the EditGrid, without a chance to restrict it. We might
> need a second menu entry to EditGrid like "View filtered data"

Perhaps an 'auto query' option on the form would be appropriate. A toggle
button as per MS Query.
> - Maybe we could use a wxNotebook, first tab is the data, tab text
> shows filter and sort, second tab is "options"

Like I said, I'm not convinced that would be easy to make behave as it
should.
> - The button sizes on the options dlg don't conform to the latest
> design guide.

The OK/Cancel are, the others aren't because the text is too long. It
would probably just fit in English, but there are other less terse
languages as we know.
> Just a hint: when inheriting a dlg from dlgProperty, it will have some
> handy methods for listviews available, supplying DlgUnit sizing,
> headers filling the rest of the control, ...
> Pixels are no legal positioning/sizing units any more.

I didn't use pixels anywhere did I?

Regards, Dave