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 574922 - Cannot edit other pages when apply button is inserted
Cannot edit other pages when apply button is inserted
Status: RESOLVED WONTFIX
Product: glade
Classification: Applications
Component: general
unspecified
Other Linux
: Normal normal
: ---
Assigned To: Glade 3 Maintainers
Glade 3 Maintainers
Depends on:
Blocks:
 
 
Reported: 2009-03-11 11:08 UTC by Lionel Dricot
Modified: 2013-05-20 11:08 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Lionel Dricot 2009-03-11 11:08:59 UTC
From launchpad : https://bugs.edge.launchpad.net/ubuntu/+source/glade-3/+bug/120897


By inserting a gnomedruid widget, and selecting it to have an apply button (show_finish == True), glade draws the Apply button on the first page of the druid widget, making impossible to navigate to the other pages to edit them.

Workaround is to only set the show_finish attribute when the work on the gnomedruid pages is done.

Steps to reproduce:
1. create window widget
2. insert a gnomedruid widget
3. set gnomedruid1 to Show Finish: Yes
4. the first page of gnomedruid displays an Apply button whereas it should not.
Comment 1 Javier Jardón (IRC: jjardon) 2010-01-19 18:57:35 UTC
Gnomedruid is obsolete, could you try GtkAssistant instead?
Comment 2 Tobias Mueller 2010-03-29 11:49:16 UTC
Closing this bug report as no further information has been provided. Please feel free to reopen this bug if you can provide the information asked for.
Thanks!
Comment 3 Tristan Van Berkom 2010-03-29 15:42:40 UTC
Did we ask him for extra info ?

Did you fire up Glade and prove that its not a bug ?

Otherwise, why would you close this bug ?
Comment 4 Tobias Mueller 2010-03-29 16:16:07 UTC
(In reply to comment #3)
> Did we ask him for extra info ?
> 
Yep. In comment #2.
> Did you fire up Glade and prove that its not a bug ?
> 
Nope.
> Otherwise, why would you close this bug ?
Because no further information has been provided and it's our policy to close NEEDINFO bugs after a reasonable amount of time without activity. And in this case I considered >2 month to be reasonable enough.
Comment 5 Tristan Van Berkom 2010-03-29 16:34:30 UTC
Right, except I see no note on this bug about it being NEEDINFO, or
why it would have been marked NEEDINFO in the first place, which I guess
is the initial problem.
Comment 6 André Klapper 2010-03-29 16:50:41 UTC
Comment 7 Paul Eipper 2010-03-30 02:32:58 UTC
Concerning the NEEDINFO thing, I didn't see what extra info was needed, as it was perfectly reproducible with the steps provided.

As far as I'm concerned this bug can be closed as wont fix, seeing that Gnomedruid is obsolete now. It was a small issue anyhow.
Comment 8 Paul Eipper 2010-03-30 02:33:36 UTC
PS: I'm the original reporter of the bug on launchpad.
Comment 9 Tristan Van Berkom 2013-05-20 11:08:05 UTC
(In reply to comment #7)
> Concerning the NEEDINFO thing, I didn't see what extra info was needed, as it
> was perfectly reproducible with the steps provided.
> 
> As far as I'm concerned this bug can be closed as wont fix, seeing that
> Gnomedruid is obsolete now. It was a small issue anyhow.

Thanks for your input, sorry I haven't walked through the bug list
in a couple years.

Closing this since libgnome support is way in the past.