Oddly enough, I found something in the glibmm CHANGES file that would seem
to help (always happens. Post to the list only to find the answer in the
next few minutes!)
>From glibmm-2.4.7 CHANGES file:
Changes between glibmm 2.2 (previously part of gtkmm) and glibmm 2.4:
* glibmm is now a separat
If you find anything, let me know. I've posted here before and
couldn't get much information on it (afaict, there is no complete
documentation or example/tutorial code for 2.0 yet)
- Jeff
On 7/13/05, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
> I've been searching for information on what I hav
I've been searching for information on what I have to change in my code to
migrate it from libsigc++-1.2 to libgigc++-2.0 (as part of the move from
gtkmm-2.0 to gtkmm-2.4)
Any pointers or web references that I can use to help me accomplish this
would be greatly appreciated.
Thanks in advance!
Er
On Wed, 2005-07-13 at 17:19 +0200, Antonio Coralles wrote:
> Let's say i've an sigc::signal with no slots connected to it. Will
> emit() then return true, or false ?
I guess it will return bool(). For instance, a std::list would
have bool() as the default value for elements. That's probably false.
Let's say i've an sigc::signal with no slots connected to it. Will
emit() then return true, or false ? Is there a way to customize this
behavour ?
[I know that this problem can be easily be circumvented using empty() ... ]
Antonio
___
libsigc-list mailing
On Tue, 2005-07-12 at 22:37 +0200, Antonio Coralles wrote:
> On http://libsigc.sourceforge.net/libsigc2/docs/manual/html/ch01.html
> one can read
> 'To make it easier to construct these, libsigc++ provides 2 the
> sigc::ptr_fun() and sigc::mem_fun() functions ...'
> Antonio
Fixed. Thanks.
--
Mur