Tim,
It's not an objection but a lack of understanding among 'classic,'
'phoenix,' and FB. I need to learn wxPython-4.x and SQLAlchemy to build this
tool.
BTW, I've found so many discrepancies between wxFormBuilder and the 4.0.1
demo code that I've removed the former and am going line-by-line to make my
classes correspond with the demos.
Below is my design for the application. I am completely open to advise and
suggestions by all of you who spend your days developing applications with
wxPython, and I am uncertain of which class methods I should be using to
make the application work the way I've designed it. BTW, if the design
should be modified I'll certainly do this.
The application design:
The application has 6 modules: main, and one for each data catagory.
The main module has the main_frame with menus (File, Add, Edit, View,
Reports, Help), a status bar and a tabbed notebook, one tab for each data
type.
Each data type module has two classes: a grid for displaying data for that
category retrieved from the database back end and a dialog box to add new
data and modify existing data.
Initially, each grid has zero rows and columns with the attribute names for
that database table/SQLAlchemy model. As data are added they are displayed
by adding a row to the grid.
Each dialog has text entry, choice, and spinner widgets. I need to collect
user data from each widget when the user presses the 'Save' button and pass
those value to SQLAlchemy in a method (as a dictionary) for insertion in the
backend database table.
Thanks,
Rich
···
On Thu, 19 Apr 2018, Tim Roberts wrote:
That's just setting the default selection. Why is that inappropriate?
You're always going to need to add a binding to handle the selection
events. wxFormBuilder can add the event handlers.
Maybe I just don't understand your objection.