Bug 571235 – Migrate from GnomeDruid to GtkAssistent

After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.

Bug 571235 - Migrate from GnomeDruid to GtkAssistent


Summary:	Migrate from GnomeDruid to GtkAssistent


Status:	RESOLVED FIXED

Product:	gnome-pilot
Classification:	Other
Component:	general
Version:	unspecified
Hardware:	Other Linux

Importance:	Normal normal
Target Milestone:	---
Assigned To:	gnome-pilot Maintainers
QA Contact:	gnome-pilot Maintainers

URL:
Whiteboard:

Depends on:
Blocks:	590215

Reported:	2009-02-10 22:22 UTC by André Klapper
Modified:	2009-10-22 02:07 UTC

See Also:
GNOME target:	---
GNOME version:	---

Description André Klapper 2009-02-10 22:22:00 UTC

See
http://www.mail-archive.com/evolution-hackers@gnome.org/msg01635.html
http://library.gnome.org/devel/gtk/stable/gtk-migrating-GtkAssistant.html
http://live.gnome.org/LibgnomeMustDie


./gnome-pilot/capplet/gnome-pilot-druid.c:	gnome_druid_set_buttons_sensitive (GNOME_DRUID (arg1), TRUE, ready, TRUE, TRUE);
./gnome-pilot/capplet/gnome-pilot-druid.c:	gnome_druid_set_buttons_sensitive (GNOME_DRUID (priv->druid), TRUE, FALSE, TRUE, TRUE);
./gnome-pilot/capplet/gnome-pilot-druid.c:	gnome_druid_set_buttons_sensitive (GNOME_DRUID (priv->druid), TRUE, ready, TRUE, TRUE);
./gnome-pilot/capplet/gnome-pilot-druid.c:	gnome_druid_set_buttons_sensitive (GNOME_DRUID (priv->druid), TRUE, ready, TRUE, TRUE);
./gnome-pilot/capplet/gnome-pilot-druid.c:	gnome_druid_set_buttons_sensitive (GNOME_DRUID (priv->druid), TRUE, ready, TRUE, TRUE);
./gnome-pilot/capplet/gnome-pilot-druid.c:		gnome_druid_set_buttons_sensitive (
./gnome-pilot/capplet/gnome-pilot-druid.c:	/*	gnome_druid_set_buttons_sensitive (GNOME_DRUID (priv->druid), TRUE, TRUE, TRUE, TRUE);

Comment 1 Matt Davey 2009-10-22 02:07:50 UTC

This problem has been fixed in the development version. The fix will be available in the next major software release. Thank you for your bug report.