Making an element look like a resize grip
Hello, I have made a widget that acts as a resize grip (I had to write one by myself because the resize grip of the statusbar doesn't work on popup windows for some reason). I used an EventBox for that, and manually handled button down, up, motion events. My question is: can I make it look like a resize grip? Is there some way to take the graphic of it (diagonal lines, or dots) and paint it on my widget? Thanks! Noam ___ gtk-app-devel-list mailing list gtk-app-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/gtk-app-devel-list
Re: Making an element look like a resize grip
In expose event handler, use function gtk_paint_resize_grip(). Note that due to GTK's system of skinning/theming the resize grip might look different then the one on statusbar depending on the theme. On 07/11/2010 09:33 AM, Noam Yorav-Raphael wrote: Hello, I have made a widget that acts as a resize grip (I had to write one by myself because the resize grip of the statusbar doesn't work on popup windows for some reason). I used an EventBox for that, and manually handled button down, up, motion events. My question is: can I make it look like a resize grip? Is there some way to take the graphic of it (diagonal lines, or dots) and paint it on my widget? Thanks! Noam ___ gtk-app-devel-list mailing list gtk-app-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/gtk-app-devel-list ___ gtk-app-devel-list mailing list gtk-app-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/gtk-app-devel-list
release of GLib 2.25.11
Hi again,
It's been a couple of weeks, so it's time for another GLib release. I'm
feeling extra creative, so let's call this one 2.25.11.
You can find it in the usual place:
http://download.gnome.org/sources/glib/2.25/
Make sure to check those checksums!
f83cdc74b9a0a8514c496c68f3d4887d38d5de64ffb9b8cdede7e94bb140b16f
glib-2.25.11.tar.bz2
28cbc02036a7f232f23ce56feda3e10bd74fe676902b305bf2a15a8b2c7c9225
glib-2.25.11.tar.gz
This is a development release leading to GLib 2.26.
Note that there have been some more ABI breaks this time around. You
will want to install a new GTK+ and dconf to go with this release of
glib (both of which will be along shortly). See the NEWS section below.
We're going to try to slow it down with the API breaking, but probably
we are not done yet. Particularly, some changes to GApplication are
being considered for the next release.
Notes:
* This is unstable development release. While it has had
a bit of testing, there are certainly plenty of bugs
remaining to be found. This release should not be used
in production.
* Installing this version will overwrite your existing
copy of GLib 2.24. If you have problems, you'll need
to reinstall GLib 2.24.
* GLib 2.26 will be source and binary compatible with
the GLib 2.24 series; however, the new API additions
in GLib 2.25.x are not yet finalized, so there may
be incompatibilities between this release and the final
2.26 release.
* Bugs should be reported to http://bugzilla.gnome.org.
About GLib
==
GLib is the low-level core library that forms the basis for projects
such as GTK+ and GNOME. It provides data structure handling for C,
portability wrappers, and interfaces for such runtime functionality as
an event loop, threads, dynamic loading, and an object system.
More information about GLib is available at:
http://www.gtk.org/
An installation guide for the GTK+ libraries, including GLib, can
be found at:
http://developer.gnome.org/doc/API/2.0/gtk/gtk-building.html
Overview of Changes from GLib 2.25.10 to GLib 2.25.11
=
+---+
| WARNING: There have been minor API changes in GDBus and GVariant. |
| These API changes will not affect many users, but they do require |
| a new version of GTK+ to be installed.|
+---+
Build:
- add a --disable-Bsymbolic configure flag to disable linking with
-Bsymbolic-functions
- this release sees the complete removal of the old 'g*alias' hacks
- honour the NOCONFIGURE environment variable from autogen.sh
- use proper feature test macros for isnan
- use pkg-config to check for zlib
- add ACLOCAL_AMFLAGS to Makefile.am
GDBus:
- hide Class and instance structures for all GDBus types except
GDBusProxy. This breaks API by preventing subclassing, but probably
nobody was doing that.
- add new GDBusConnection call to support flushing all pending
outgoing messages
- change the register_object API to add a reference to the
GDBusInterfaceInfo object so the caller need not keep it alive
themselves
- don't rewrite the serial number when sending messages that already
have a serial number
- better error checking for DBUS_SESSION_BUS_ADDRESS environment
variable
- switch to g_parse_debug_string for G_DBUS_DEBUG and add a lot of new
flags
- add support for temporarily freezing a freshly created
GDBusConnection. Do this until after the ::new-connection signal
has finished running on GDBus services.
- never require non-closed connections (the user is incapable of doing
this due to the obvious race)
- remove weird/misleading redundant check on NameOwnerChanged signal
- emit GDBusProxy::g-properties-changed on NameOwnerChanged
GVariant:
- the 'g_variant_{new,get}_byte_array' APIs have been removed
- g_variant_{new,get,dup}_bytestring has been added, with different
arguments and different behaviour
- g_variant_{new,get,dup}_bytestring_array has been added, doing
essentially the same thing as the 'strv' functions, but with byte
strings instead of utf8 strings
- G_VARIANT_TYPE_BYTESTRING ('ay'), BYTESTRING_ARRAY ('aay') and
STRING_ARRAY ('as') constants have been added
- the undocumented behaviour that g_variant_get_strv() deserialised
arrays of object paths or signature strings has been dropped
- additional varargs support for converting bytestrings or bytestring
arrays with ^ay ^aay ^ay and ^aay
- improved gobject-introspection annotation
- fix a problem with GBuffer calling g_slice_free for the wrong type
- fix leaks in the type inferencing code of the parser
GSettings:
- improved documentation
- updated schema XML DTD, now xincluded into the docs
- added support for schemas that extend other schemas (using the
'extends=' attribute).
Porting a GTK 1.x application to current version
Hi there, I have to port an old GTK 1.x application from around 2000 to a current version. The goal is simply making it work on the current version of Ubuntu. So I searched Google for a general porting guide, but was unable to find anything useful, only a hint that there was one around in 2001. I was finally able to locate this old guid via archive.org, but I'm unsure, if it still applies to current versions of GTK+. Does anyone know if there is a more recent guide on the net, or if the old one from archive.org is still usable? Here is the link: http://web.archive.org/web/20080502161346/http://developer.gnome.org/dotplan/porting/ Thank you in advance for your help, Fabian Schreyer ___ gtk-app-devel-list mailing list gtk-app-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/gtk-app-devel-list
Re: Porting a GTK 1.x application to current version
On Sun, 11 Jul 2010, Fabian Schreyer wrote: I have to port an old GTK 1.x application from around 2000 to a current version. The goal is simply making it work on the current version of Ubuntu. So I searched Google for a general porting guide, but was unable to find anything useful, only a hint that there was one around in 2001. I was finally able to locate this old guid via archive.org, but I'm unsure, if it still applies to current versions of GTK+. The original guide should be some help but (warning: I haven't looked at it lately -- if you get a better-informed comment please disregard this one) I suspect it may not take into account the fact that a fair amount of the API in early GTK+ 2 has since been deprecated, and will disappear in GTK+ 3. Since Ubuntu generally keeps pretty much up to date with GTK, you should probably be looking towards GTK 3 compatibility. I'd recommend referring to the old guide, but cross-checking this against the html API doc for the current GTK release so as to avoid substituting short-lived deprecated code for actually obsolete code. Your situation is a little awkward, since any current guide is likely to focus on porting from (older) GTK 2 to GTK 3. Allin Cottrell ___ gtk-app-devel-list mailing list gtk-app-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/gtk-app-devel-list
release of GLib 2.25.11
Hi again,
It's been a couple of weeks, so it's time for another GLib release. I'm
feeling extra creative, so let's call this one 2.25.11.
You can find it in the usual place:
http://download.gnome.org/sources/glib/2.25/
Make sure to check those checksums!
f83cdc74b9a0a8514c496c68f3d4887d38d5de64ffb9b8cdede7e94bb140b16f
glib-2.25.11.tar.bz2
28cbc02036a7f232f23ce56feda3e10bd74fe676902b305bf2a15a8b2c7c9225
glib-2.25.11.tar.gz
This is a development release leading to GLib 2.26.
Note that there have been some more ABI breaks this time around. You
will want to install a new GTK+ and dconf to go with this release of
glib (both of which will be along shortly). See the NEWS section below.
We're going to try to slow it down with the API breaking, but probably
we are not done yet. Particularly, some changes to GApplication are
being considered for the next release.
Notes:
* This is unstable development release. While it has had
a bit of testing, there are certainly plenty of bugs
remaining to be found. This release should not be used
in production.
* Installing this version will overwrite your existing
copy of GLib 2.24. If you have problems, you'll need
to reinstall GLib 2.24.
* GLib 2.26 will be source and binary compatible with
the GLib 2.24 series; however, the new API additions
in GLib 2.25.x are not yet finalized, so there may
be incompatibilities between this release and the final
2.26 release.
* Bugs should be reported to http://bugzilla.gnome.org.
About GLib
==
GLib is the low-level core library that forms the basis for projects
such as GTK+ and GNOME. It provides data structure handling for C,
portability wrappers, and interfaces for such runtime functionality as
an event loop, threads, dynamic loading, and an object system.
More information about GLib is available at:
http://www.gtk.org/
An installation guide for the GTK+ libraries, including GLib, can
be found at:
http://developer.gnome.org/doc/API/2.0/gtk/gtk-building.html
Overview of Changes from GLib 2.25.10 to GLib 2.25.11
=
+---+
| WARNING: There have been minor API changes in GDBus and GVariant. |
| These API changes will not affect many users, but they do require |
| a new version of GTK+ to be installed.|
+---+
Build:
- add a --disable-Bsymbolic configure flag to disable linking with
-Bsymbolic-functions
- this release sees the complete removal of the old 'g*alias' hacks
- honour the NOCONFIGURE environment variable from autogen.sh
- use proper feature test macros for isnan
- use pkg-config to check for zlib
- add ACLOCAL_AMFLAGS to Makefile.am
GDBus:
- hide Class and instance structures for all GDBus types except
GDBusProxy. This breaks API by preventing subclassing, but probably
nobody was doing that.
- add new GDBusConnection call to support flushing all pending
outgoing messages
- change the register_object API to add a reference to the
GDBusInterfaceInfo object so the caller need not keep it alive
themselves
- don't rewrite the serial number when sending messages that already
have a serial number
- better error checking for DBUS_SESSION_BUS_ADDRESS environment
variable
- switch to g_parse_debug_string for G_DBUS_DEBUG and add a lot of new
flags
- add support for temporarily freezing a freshly created
GDBusConnection. Do this until after the ::new-connection signal
has finished running on GDBus services.
- never require non-closed connections (the user is incapable of doing
this due to the obvious race)
- remove weird/misleading redundant check on NameOwnerChanged signal
- emit GDBusProxy::g-properties-changed on NameOwnerChanged
GVariant:
- the 'g_variant_{new,get}_byte_array' APIs have been removed
- g_variant_{new,get,dup}_bytestring has been added, with different
arguments and different behaviour
- g_variant_{new,get,dup}_bytestring_array has been added, doing
essentially the same thing as the 'strv' functions, but with byte
strings instead of utf8 strings
- G_VARIANT_TYPE_BYTESTRING ('ay'), BYTESTRING_ARRAY ('aay') and
STRING_ARRAY ('as') constants have been added
- the undocumented behaviour that g_variant_get_strv() deserialised
arrays of object paths or signature strings has been dropped
- additional varargs support for converting bytestrings or bytestring
arrays with ^ay ^aay ^ay and ^aay
- improved gobject-introspection annotation
- fix a problem with GBuffer calling g_slice_free for the wrong type
- fix leaks in the type inferencing code of the parser
GSettings:
- improved documentation
- updated schema XML DTD, now xincluded into the docs
- added support for schemas that extend other schemas (using the
'extends=' attribute).
release of GLib 2.25.11
Hi again,
It's been a couple of weeks, so it's time for another GLib release. I'm
feeling extra creative, so let's call this one 2.25.11.
You can find it in the usual place:
http://download.gnome.org/sources/glib/2.25/
Make sure to check those checksums!
f83cdc74b9a0a8514c496c68f3d4887d38d5de64ffb9b8cdede7e94bb140b16f
glib-2.25.11.tar.bz2
28cbc02036a7f232f23ce56feda3e10bd74fe676902b305bf2a15a8b2c7c9225
glib-2.25.11.tar.gz
This is a development release leading to GLib 2.26.
Note that there have been some more ABI breaks this time around. You
will want to install a new GTK+ and dconf to go with this release of
glib (both of which will be along shortly). See the NEWS section below.
We're going to try to slow it down with the API breaking, but probably
we are not done yet. Particularly, some changes to GApplication are
being considered for the next release.
Notes:
* This is unstable development release. While it has had
a bit of testing, there are certainly plenty of bugs
remaining to be found. This release should not be used
in production.
* Installing this version will overwrite your existing
copy of GLib 2.24. If you have problems, you'll need
to reinstall GLib 2.24.
* GLib 2.26 will be source and binary compatible with
the GLib 2.24 series; however, the new API additions
in GLib 2.25.x are not yet finalized, so there may
be incompatibilities between this release and the final
2.26 release.
* Bugs should be reported to http://bugzilla.gnome.org.
About GLib
==
GLib is the low-level core library that forms the basis for projects
such as GTK+ and GNOME. It provides data structure handling for C,
portability wrappers, and interfaces for such runtime functionality as
an event loop, threads, dynamic loading, and an object system.
More information about GLib is available at:
http://www.gtk.org/
An installation guide for the GTK+ libraries, including GLib, can
be found at:
http://developer.gnome.org/doc/API/2.0/gtk/gtk-building.html
Overview of Changes from GLib 2.25.10 to GLib 2.25.11
=
+---+
| WARNING: There have been minor API changes in GDBus and GVariant. |
| These API changes will not affect many users, but they do require |
| a new version of GTK+ to be installed.|
+---+
Build:
- add a --disable-Bsymbolic configure flag to disable linking with
-Bsymbolic-functions
- this release sees the complete removal of the old 'g*alias' hacks
- honour the NOCONFIGURE environment variable from autogen.sh
- use proper feature test macros for isnan
- use pkg-config to check for zlib
- add ACLOCAL_AMFLAGS to Makefile.am
GDBus:
- hide Class and instance structures for all GDBus types except
GDBusProxy. This breaks API by preventing subclassing, but probably
nobody was doing that.
- add new GDBusConnection call to support flushing all pending
outgoing messages
- change the register_object API to add a reference to the
GDBusInterfaceInfo object so the caller need not keep it alive
themselves
- don't rewrite the serial number when sending messages that already
have a serial number
- better error checking for DBUS_SESSION_BUS_ADDRESS environment
variable
- switch to g_parse_debug_string for G_DBUS_DEBUG and add a lot of new
flags
- add support for temporarily freezing a freshly created
GDBusConnection. Do this until after the ::new-connection signal
has finished running on GDBus services.
- never require non-closed connections (the user is incapable of doing
this due to the obvious race)
- remove weird/misleading redundant check on NameOwnerChanged signal
- emit GDBusProxy::g-properties-changed on NameOwnerChanged
GVariant:
- the 'g_variant_{new,get}_byte_array' APIs have been removed
- g_variant_{new,get,dup}_bytestring has been added, with different
arguments and different behaviour
- g_variant_{new,get,dup}_bytestring_array has been added, doing
essentially the same thing as the 'strv' functions, but with byte
strings instead of utf8 strings
- G_VARIANT_TYPE_BYTESTRING ('ay'), BYTESTRING_ARRAY ('aay') and
STRING_ARRAY ('as') constants have been added
- the undocumented behaviour that g_variant_get_strv() deserialised
arrays of object paths or signature strings has been dropped
- additional varargs support for converting bytestrings or bytestring
arrays with ^ay ^aay ^ay and ^aay
- improved gobject-introspection annotation
- fix a problem with GBuffer calling g_slice_free for the wrong type
- fix leaks in the type inferencing code of the parser
GSettings:
- improved documentation
- updated schema XML DTD, now xincluded into the docs
- added support for schemas that extend other schemas (using the
'extends=' attribute).
Re: Why GtkFontSelectionDialog doesn't implements GtkFontSelection?
Hi all, Unstable here means that it maybe will not be part of stable version of GTK+ or that it will be part of a stable version and is just on a beta version? 2010/6/28 Javier Jardón jjar...@gnome.org: 010/6/29 Tadej Borovšak tadeb...@gmail.com: There has been some work going on to bring font chooser widgets into 21st century, but nothing has come out of that yet (and I lost the link to the page with some mockups). This is the link: [1] [1] http://live.gnome.org/Design/GTKFontDialog/MockupSet1 -- Javier Jardón Cabezas ___ gtk-list mailing list gtk-list@gnome.org http://mail.gnome.org/mailman/listinfo/gtk-list
signal apparently missing on gtkcalendar
Hi all, I am reading the documentation of GtkCalendar, more precisely at the signals. There are the month-changed and day-selected signal, but why not a signal to represent the year changing? Maybe something like year-changed, why it doesn't exist? Thanks ___ gtk-list mailing list gtk-list@gnome.org http://mail.gnome.org/mailman/listinfo/gtk-list
Re: Why GtkFontSelectionDialog doesn't implements GtkFontSelection?
Hi. Unstable here means that it maybe will not be part of stable version of GTK+ or that it will be part of a stable version and is just on a beta version? Unstable means it'll be part of next GTK+ release, due to be out in October 2010. Tadej -- Tadej Borovšak tadeboro.blogspot.com tadeb...@gmail.com tadej.borov...@gmail.com ___ gtk-list mailing list gtk-list@gnome.org http://mail.gnome.org/mailman/listinfo/gtk-list
