>
> Damon Chaplin ([EMAIL PROTECTED]) writes:
> > We do need a better "Signals" page on the property editor.
> > It should be similar to Delphi/VB, i.e. a list of signals with an entry
> > on the right of each one where you type in a signal handler function name.
> > And a button on the right which you click to edit the source code
> > (we'll just emit some kind of Corba signal when it is clicked).
>
> Even better, just emit the Corba signal when a signal is selected.
>
> And, do you really need to allow for user-specified function names?
> Why not just force the function names that glade suggests now?
> on_OBJECT_SIGNAL.
My $0.02: not allowing a user to set the function name is a bad idea, as it
(obviously) precludes connecting signals from different widgets to the same
callback.
Consider writing a GUI that is an input-output client for some hairy
process-control server. A user might want to do something like
connect the clicked signals for many buttons up to the same callback
and within that callback send a message to the server with the widget
name (or some data stored with the widget) as part of the message. If glade
forces the name then each button would have to have a callback that wraps
the real callback, or you have to do some fancy footwork using g_module and
the like, or make a bunch of nearly identical functions ...
all options that make for more work and/or ugly maintenance.
Granted this example isn't terribly common, but why limit the options ... let
glade make name suggestions and the user decide to use or ignore them.
+---------------------------------------------------------------------+
To unsubscribe from this list, send a message to [EMAIL PROTECTED]
with the line "unsubscribe glade-devel" in the body of the message.
