No way to tell what file I'm editing in Glade

Bug #158975 reported by Michael Lamothe
0
Affects Status Importance Assigned to Milestone
Glade
Fix Released
Medium
glade-3 (Ubuntu)
Fix Released
Low
Unassigned

Bug Description

Binary package hint: glade-3

If you're a developer (I imagine most people using Glade are) then you've probably got several versions of the same Glade file on your system from different branches. Unfortunately, I can't find a way for Glade to tell me which path/file I'm editing i.e. trunk or branch/0.3.

I'm happy to raise this as a blueprint but I really think this a significant oversight. This is not a "new feature" thing this is a broken thing in Glade, IMHO.

ProblemType: Bug
Architecture: amd64
Date: Wed Oct 31 21:56:25 2007
DistroRelease: Ubuntu 7.10
NonfreeKernelModules: fglrx
Package: glade-3 3.4.0-0ubuntu1
PackageArchitecture: amd64
SourcePackage: glade-3
Uname: Linux sizzles64 2.6.22-14-generic #1 SMP Sun Oct 14 21:45:15 GMT 2007 x86_64 GNU/Linux

Tags: apport-bug
Revision history for this message
Michael Lamothe (lamothe-deactivatedaccount-deactivatedaccount) wrote :
Revision history for this message
Michael Lamothe (lamothe-deactivatedaccount-deactivatedaccount) wrote :

This bug was raised through apport and hence came here. I've also raised this at http://bugzilla.gnome.org/show_bug.cgi?id=503388 which is the bug tracker for Glade in the hope that it gets fixed there and imported in a future upstream release.

The latest release of Glade is 3.4.0 (same as Gutsy) so this hasn't been fixed yet.

Revision history for this message
Pedro Villavicencio (pedro) wrote :

thanks for sending it upstream.

Changed in glade-3:
assignee: nobody → desktop-bugs
importance: Undecided → Low
status: New → Triaged
Revision history for this message
Michael Lamothe (lamothe-deactivatedaccount-deactivatedaccount) wrote :

The response from the glade team is "The absolute filenames can be shown in the statusbar by hovering over the open files in the "Projects" menu."

And yes, that works! However, they agree that this might not be the most intuitive answer and will investigate. But for now, I think that this is not a bug. This is now more of a blueprint/feature.

Changed in glade-3:
status: Triaged → Invalid
Changed in glade-3:
status: Unknown → New
Javier Jardón (jjardon)
Changed in glade-3:
importance: Unknown → Undecided
status: New → Invalid
Changed in glade-3 (Ubuntu):
status: Invalid → New
affects: glade-3 (Ubuntu) → glade (Ubuntu)
Changed in glade (Ubuntu):
status: New → Triaged
Javier Jardón (jjardon)
affects: glade (Ubuntu) → glade-3 (Ubuntu)
Changed in glade-3:
importance: Undecided → Unknown
status: Invalid → Unknown
Javier Jardón (jjardon)
Changed in glade-2.old:
importance: Unknown → Undecided
status: Unknown → New
status: New → Invalid
Changed in glade-3:
importance: Unknown → Medium
status: Unknown → New
Changed in glade-3:
status: New → Fix Released
Revision history for this message
Sebastien Bacher (seb128) wrote :

upstream closed the bug with that comment:

"I'm closing this now as the full path is now quite accessible.

As well as having the fullpath in the statusbar when hovering
the project menu item (which is not very accessible), now the
fullpath is available as a tooltip of the project's notebook
tab label (glade now shows notebook tabs to switch the projects)."

Changed in glade-3 (Ubuntu):
assignee: Ubuntu Desktop Bugs (desktop-bugs) → nobody
status: Triaged → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.