Bug 149707 - Does not indicate current config file name; "Save As" does not indicate current config file name
Summary: Does not indicate current config file name; "Save As" does not indicate curre...
Alias: None
Product: Red Hat Cluster Suite
Classification: Retired
Component: redhat-config-cluster   
(Show other bugs)
Version: 4
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: Jim Parsons
QA Contact: Cluster QE
Depends On:
TreeView+ depends on / blocked
Reported: 2005-02-25 16:37 UTC by Paul Kennedy
Modified: 2015-04-20 00:46 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2005-04-29 20:37:53 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

Description Paul Kennedy 2005-02-25 16:37:28 UTC
Description of problem:

The GUI window does not indicate the configuration file name of the
configuration displayed. A user could erroneously edit/save a
configuration file because there is no display of the current
configuration file name. In addition, the "Save As" function does not
indicate the name of the file--instead it defaults to

Version-Release number of selected component (if applicable):

How reproducible:
See "Description of problem".

Actual results:
See "Description of problem".

Expected results:
See "Description of problem".

Comment 1 Jim Parsons 2005-03-01 18:13:07 UTC
will fix

Comment 2 Jim Parsons 2005-03-28 11:32:42 UTC
UI now has text field at top of cfg tab that shows file currently being edited,
or  a states that this is a new, unsaved file

Fixed in 0.9.17-1.0

Comment 3 Corey Marthaler 2005-04-18 19:01:09 UTC
partially fixed. 

It now displays the file currently being edited (like
/tmp/my_foobar_cluster.conf) however when I go to 'save as' it still defaults to
"/etc/cluster/cluster.conf", that needs to change as well.

Comment 4 Jim Parsons 2005-04-25 22:04:58 UTC
This bug (I believe) was originally about the UI's lack of a way to tell you
what file you were editing. A text field was added to the top of the UI for this

Now, I *think* you are asking that if a file is open, and 'Save As' is chosen
from the drop down menu, then the file selector box be pre-populated with the
location of the file currently being edited. Is this correct?

I defaulted to always placing /etc/cluster/cluster.conf there, as this tool *is*
about editing that very file.....and expects the file to be saved there for use
by the cluster. That said, I have absolutely no problem having the file selector
dialog be preset to the path and location of the currently edited file -
wherever that may be. Is this what you want?

Comment 5 Paul Kennedy 2005-04-27 21:03:32 UTC
The intent of the original bug description is based on a use case where a user
would configure a file to be used later--not the active configuration file--then
it would be easy for the user to erroneously save to the active file
(etc/cluster/cluster.conf). Therefore, it is necessary to display the file name.
That is addressed with the fix. 

Regarding the "Save As" concern, if a user edits a non-active file and wants to
save again using "Save As" it seems like the file name that is populated should
be the same name as the file that is currently being edited--as a starting
point. I'm not certain if that is a GUI standard, but it seems like expected
behavior compared to other text editing applications. 

Comment 6 Jim Parsons 2005-04-29 19:01:47 UTC
Okee Dokee. Finished in 0.9.44

Comment 7 Corey Marthaler 2005-04-29 20:37:53 UTC
fix verified in -44.

Note You need to log in before you can comment on or make changes to this bug.