KeyWorksRW
Add custom property dialog for editing multiple pairs of properties
Description:
There are a few places where we use multiple pairs of properties (see issue #600 for an example). Currently, we require the user to enter some kind of separator character -- even when using wxEditableListBox as the property editor.
What we need is a dialog that looks like wxEditableListBox but uses an underlying multi-column wxListView control where we can set column headers, the number of columns, etc. If we provide sufficient methods in the dialog for customizing the wxListView control and possibly the format of the property string, then it should be usable by any property that needs to support multiple parts of a property.
The GridPropertyDlg can be used as a base class that supports multiple fields. See sb_fields_prop.cpp which inherits from this base class and provides bool, choice, date, and text (including number) editors. This should be sufficient to implement most of the property editors described in this issue. For wxBitmapComboBox, we would need to create a custom cell editor.
This dialog might also be a way to implement a dialog for setting custom control parameters if we created a wxGrid editor based on wxCombo rather than wxChoice so that the user could enter in their own values instead of a macro, with the drop-down showing possible macros and/or text. See #360.
I added the 1.3 milestone to move this up in the priority list -- depending on the criterion for releasing 1.3, it might or might not actually be part of that milestone.
I wasn't sure it existed either until I went and looked into the code. If I can't remember what the possible macros are, then I can't expect anyone else to know about them either... 😄
I placed #615 into the 1.3 milestone just so that I remember to take a look at it. The custom parameter dialog would be ideal for displaying the possible macros as well as being able to add them without having to type them in.
#745 and #750 are still open, but they have their own issues, so I don't think we need to leave this issue open since GridPropertyDlg can be used for the remaining two cases.