[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-bindings
Subject:    [Kde-bindings] Best way to manually connect events in Qyoto?
From:       IBBoard <ibboard () ibboard ! co ! uk>
Date:       2010-01-30 20:37:42
Message-ID: 4B649896.3070100 () ibboard ! co ! uk
[Download RAW message or body]

I'm back with another question - I'm still weighing up whether I'd
rather have GTK#'s non-OO-ness or Qyoto's esoteric "signals".

I know I can now attach delegates to signals using QObject.Connect(),
and I've read the previous discussion about why Qyoto can't have
"normal" C# events (the main point being that signals can be overloaded
with different parameters, but events can't), but I'm not quite sure I
can get used to the SIGNAL("signalName()") method as a good way to do
things. I'm used to TDD and refactoring code, so having a method name in
a string seems like a bad thing anyway. On top of that I don't know what
the signals are for lists, combo boxes, buttons, etc and they're not
available as auto-completes, so I've got to keep going back to the
documentation, reading, copying, remembering the "SIGNAL" wrapper, and
not finding out that I've mistyped something until runtime.

I realise that Qt has its own ways of doing things and that the
signals/slots method is cross-platform and quite flexible, but is there
any easier way to handle this, perhaps in terms of IDE support or some
other method of indicating the signals? The current methods just seems a
bit brittle and difficult for new-comers (what if I'm offline and don't
have access to the documentation, for example?)

Thanks,

IBBoard
_______________________________________________
Kde-bindings mailing list
Kde-bindings@kde.org
https://mail.kde.org/mailman/listinfo/kde-bindings
[prev in list] [next in list] [prev in thread] [next in thread]