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 308332 - File chooser resets file name entry when using type ahead
File chooser resets file name entry when using type ahead
Status: RESOLVED FIXED
Product: gtk+
Classification: Platform
Component: Widget: GtkFileChooser
2.6.x
Other All
: Urgent major
: Medium fix
Assigned To: gtk-bugs
gtk-bugs
: 309638 312053 314219 315849 316303 316869 323193 324271 330519 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2005-06-19 20:47 UTC by Jürg Billeter
Modified: 2006-02-09 15:52 UTC
See Also:
GNOME target: ---
GNOME version: 2.9/2.10


Attachments
Fix attempt (791 bytes, patch)
2005-07-06 18:43 UTC, Jürg Billeter
committed Details | Review

Description Jürg Billeter 2005-06-19 20:47:45 UTC
Version details: 2.6.8
Distribution/Version: paldo testing

Since gtk+ 2.6.8 the file chooser resets the file name entry when using type
ahead (to choose folder) in save mode. It also happens when deselecting the
currently selected folder by ctrl+clicking but the latter probably doesn't
happen often in normal use cases.

The patch
http://cvs.gnome.org/viewcvs/gtk%2B/gtk/gtkfilechooserdefault.c?r1=1.265&r2=1.266
(in 2.6.8 and HEAD) seems to have introduced this behaviour.
Comment 1 Matthias Clasen 2005-07-06 17:28:00 UTC
Looks like its not easy to fix. The treeview currently does not have a way to
find out that a selection change was during typeahead.
Comment 2 Jürg Billeter 2005-07-06 18:43:34 UTC
Created attachment 48738 [details] [review]
Fix attempt

I don't know the file chooser code at all but perhaps the attached simple patch
can solve the problem. Very possible that I've overlooked something but it may
be worth an attempt...
Comment 3 Federico Mena Quintero 2005-07-19 20:20:53 UTC
*** Bug 309638 has been marked as a duplicate of this bug. ***
Comment 4 Federico Mena Quintero 2005-07-19 20:21:49 UTC
As noted in the duplicate, this interferes with the "Create Folder" button ---
hitting it clears the filename entry, which is definitely wrong.
Comment 5 Sebastien Bacher 2005-07-31 12:14:21 UTC
*** Bug 312053 has been marked as a duplicate of this bug. ***
Comment 6 Rodd Clarkson 2005-08-15 00:25:53 UTC
I'm a little fascinated that this wasn't fixed before 2.8.0 was released.

This is a regression on previous file-chooser behaviour and it's quite annoying,
making saving of files very complicated if you want to retain the file name that
was supplied (which most people would I would think).
Comment 7 Reinout van Schouwen 2005-08-23 20:54:11 UTC
*** Bug 314219 has been marked as a duplicate of this bug. ***
Comment 8 Matthias Clasen 2005-09-09 21:56:09 UTC
*** Bug 315849 has been marked as a duplicate of this bug. ***
Comment 9 Daniel Holbach 2005-09-20 06:53:54 UTC
How is the fix attempt coming on?
Comment 10 Federico Mena Quintero 2005-09-27 21:33:24 UTC
I just committed the patch from comment #2 to HEAD and gtk-2-8.  Sorry for
taking so long in reviewing it.  Thanks for the patch, Jürg!

2005-09-27  Federico Mena Quintero  <federico@ximian.com>

	Merged from HEAD:

	* gtk/gtkfilechooserdefault.c (update_chooser_entry): If the
	selection is empty, clear the file name entry only if we are in
	CREATE_FOLDER mode.  In SAVE mode, nothing will be selected when
	the user starts typeahead in the treeview, and we don't want to
	clear the file name entry in that case --- the user could be
	typing-ahead to look for a folder name.  Fixes bug #308332, patch
	by Jürg Billeter.
Comment 11 Janis Blechert 2005-09-28 13:59:24 UTC
Thanks a lot!
Comment 12 oll 2005-09-28 15:15:22 UTC
Is there a chance the patch will be commit to 2.6.x too ?
Comment 13 Matthias Clasen 2005-09-28 15:21:38 UTC
Why ? There will not be any further 2.6.x releases
Comment 14 oll 2005-09-28 15:38:55 UTC
Here in my coporate environment, gnome 2.10 is quite stable now (latest release
with latest few cvs 2.10 patches).
I know "by experiment" that migrating to gtk 2.8  (at least now) will bring some
other problems.
Comment 15 Matthias Clasen 2005-09-28 15:47:54 UTC
Yes, but we lack the manpower to maintain three branches in parallel. So if you
need that patch in 2.6, you need to patch your installation, or ask your
distribution to patch their package.
Comment 16 oll 2005-09-28 19:57:12 UTC
I deeply understand and agrre with you,but that's more political than technical.
I'm a big fan of gnome/gtk since the begining and your everyday's hard work
proves I'm right.
But since I migrated all my users -from Windows,Sun CDE,even KDE (but no flame
there), to gnome, I have to justify my choice.
And it's easier to say 
"Look, you have this bug, there's already a patch in cvs"
than
"OK, huum, let's migrate to 2.12..."

In a coorporate environment , that's not so easy ... I can't, technically and
politically, migrate everyone every 6 months.

I check for every patches applied by RedHat (Fedora) , but this is far from
being as useful as checking bugzilla, or cvs.

Comment 17 Federico Mena Quintero 2005-10-31 18:18:18 UTC
*** Bug 316303 has been marked as a duplicate of this bug. ***
Comment 18 Federico Mena Quintero 2005-11-01 18:11:19 UTC
*** Bug 316869 has been marked as a duplicate of this bug. ***
Comment 19 Federico Mena Quintero 2005-12-06 21:16:37 UTC
*** Bug 323193 has been marked as a duplicate of this bug. ***
Comment 20 Sven Neumann 2005-12-16 17:06:13 UTC
*** Bug 324271 has been marked as a duplicate of this bug. ***
Comment 21 Reinout van Schouwen 2006-02-09 15:52:50 UTC
*** Bug 330519 has been marked as a duplicate of this bug. ***