On Sat, 2005-10-22 at 16:23 +0400, Maxim Udushlivy wrote:
Hello, everybody!
I use gtkmm for almost one year in my project and I want to thank people
behind this library. Despite being a community effort it easily plays on
a par with commercial toolkits. Gtkmm programming is fun (!): it has
On 10/23/05, Murray Cumming [EMAIL PROTECTED] wrote:
On Sat, 2005-10-22 at 16:23 +0400, Maxim Udushlivy wrote: Hello, everybody! I use gtkmm for almost one year in my project and I want to thank people behind this library. Despite being a community effort it easily plays on
a par with commercial
About const functions: widgets are non-constant objects by
their nature.
They can change by outside events, like DND. Aren't these
const
functions misconcept api and bloat documentation?
const means whatever you choose it to
Murray Cumming wrote:
About const functions: widgets are non-constant objects by
their nature.
They can change by outside events, like DND. Aren't these
const
functions misconcept api and bloat documentation?
const means whatever you
On Sunday 23 October 2005 19:09, Maxim Udushlivy wrote:
Hmm... Those non-const counterparts are needed only for getter
functions which return somehow tied objects which should be as const
as widget itself (for example Label::get_layout). Right?
Non-const functions/methods are required for
Hello, everybody!
I use gtkmm for almost one year in my project and I want to thank people
behind this library. Despite being a community effort it easily plays on
a par with commercial toolkits. Gtkmm programming is fun (!): it has
true C++ api, good documentation, builds on strong Gtk
