Jean-Marc Lasgouttes <[EMAIL PROTECTED]> writes:
| >>>>> "Lars" == Lars Gullik Bjønnes <[EMAIL PROTECTED]> writes:
|
| Lars> But that question only shows that you don't know much about
| Lars> Sigc++ yet.
|
| :)
|
| Lars> a "why the hell is it a child of Timeout::base_type?" is IMO a
| Lars> lot worse. And in BufferView: "why the hell is it a child of
| Lars> WorkArea::base_type and not of Timeout::base_type?"
|
| Are signals used in BufferView to do timeouts? If WorkArea uses
Timeouts and Workarea signals.
(What would you like to inherit from?)
| signals in its own way, it would make sense that BufferView is a
| subclass of WorkArea::base_type. This would give a hint about why
| BufferView uses signals. I understand howver that a class could use
| signals for several reasons, but does this happen?
|
| Also base_tye is of course a lame name. It should probably be
| receiver_type or any name that fits with SigC++ philosophy. This way,
| the ifdefs would be only in a few header files, and their intent would
| be clearer to stupid programmers who, as I do, ignore the beauties of
| SigC++.
inheriting from SigC::Object makes the intent very clear. (I want
methods in this class act as slots to connect to some signals)
Lgb
