I too have worked extensively with Python in a GUI. I have exactly the same
issues.
My approach is thus:
* Python code "registers" an event. Registry consists of the event itself
(eg, the message) and a Python function object.
* C++ code calls "call_object()" on the object itself.
This means that the C++ code never works in terms of Python function names -
just the objects itself. eg, the Python code:
def func( params ):
pass
window.RegisterMessage( MESSAGE_ID, func )
This passes an object itself to the C++ code, which keeps a reference to it.
The C++ code just has an object *, and never needs to know the name of the
function itself. Note that the Python "member -> function " magic also
works, so class methods also work in the same way.
The total Python API I work with consists of probably less than 1 dozen
functions. Thre basic set consists of only about 3 functions "run_command,
call_object", and the others are utilities like "gettuplesize" or "get_repr"
type functions.
As such, some expanded documentation would be nice, but I dont really think
the API itself needs any expanding.
Mark.