Re: r16077 - gnucash/trunk/src - Add gnc_history_remove_file, call it if the history file cannot be loaded, #388500.
Quoting Dan Widyono <[EMAIL PROTECTED]>: >> Well, I disagree about which is more common. I think almost all users will >> have a 'testing' file in the list. Probably just the one, but it's still >> there. > > My 2 cents: I think most *developers* will have a "testing" file. Everyone I > know who uses finance software does not have a "testing" file; instead, they > have just one file -- the active one. > > Don't least-often-used files simply slip silently off the history list if you > have "too many" entries? You could have a preference setting for how many > are "too many". Yes, it does. The default is '4'. You can set this value through gconf if you want to change it. > You could also have a context-sensitive right-click menu for deleting a > history entry... manually. This is what I suggested. > Dan W. -derek -- Derek Atkins, SB '93 MIT EE, SM '95 MIT Media Laboratory Member, MIT Student Information Processing Board (SIPB) URL: http://web.mit.edu/warlord/PP-ASEL-IA N1NWH [EMAIL PROTECTED]PGP key available ___ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel
Re: r16077 - gnucash/trunk/src - Add gnc_history_remove_file, call it if the history file cannot be loaded, #388500.
On Mon, 2007-05-14 at 11:54 -0400, Ariel wrote: > On Mon, 14 May 2007, Thomas Bushnell BSG wrote: > > > On Sun, 2007-05-13 at 16:53 -0400, Derek Atkins wrote: > >> I dont like this patch. Sometimes I start gnucash before > >> I remember to mount my encrypted partition. GnuCash happily > >> warns me that the file isn't there and I can then quit, mount > >> the partition, and then re-start gnucash. If gnucash > >> automatically removes the entry from the history this no > >> longer works. > > > > I have the same concern; I sometimes start gnucash before I remember to > > start up AFS. Same problem. > > The problem is that there is no obvious way to remove a file from the > history menu. There is gconf, but it's not expected that users will know > how to use it. > > I think it's easier for you to reopen your file, then it is for a user to > figure out which gconf key to remove. Obviously the right fix is to create a way to remove a file from the history menu. Destroying information this way is a habit in many Gnome programs, and it's a disaster. Thomas ___ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel
Re: r16077 - gnucash/trunk/src - Add gnc_history_remove_file, call it if the history file cannot be loaded, #388500.
> Well, I disagree about which is more common. I think almost all users will > have a 'testing' file in the list. Probably just the one, but it's still > there. My 2 cents: I think most *developers* will have a "testing" file. Everyone I know who uses finance software does not have a "testing" file; instead, they have just one file -- the active one. Don't least-often-used files simply slip silently off the history list if you have "too many" entries? You could have a preference setting for how many are "too many". You could also have a context-sensitive right-click menu for deleting a history entry... manually. Dan W. ___ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel
Re: Fedora 6.9
John Newman ([EMAIL PROTECTED]) said: > I had to run yum update, but once that was done GnuCash worked. But > before that is was not even loading. Right, it was a g-wrap packaging bug, since fixed. Bill ___ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel
Re: r16077 - gnucash/trunk/src - Add gnc_history_remove_file, call it if the history file cannot be loaded, #388500.
On Mon, 14 May 2007, Derek Atkins wrote: > Ariel <[EMAIL PROTECTED]> writes: > >> The problem is that there is no obvious way to remove a file from the >> history menu. There is gconf, but it's not expected that users will know >> how to use it. > > That's a completely different issue that automatically removing > an unfound file at startup. I completely support a context menu > option to delete items from the history if there's really a call > for it, but I think automatically removing it is the wrong thing. That's fine with me, as long as there is a way. >> I think it's easier for you to reopen your file, then it is for a user to >> figure out which gconf key to remove. > > How often does a user need to remove an entry from their history? > How often does a user store their datafile on a mounted volume? > I think the latter is MUCH more common than the former, so we should > optimize for the mounted volume, not the removing and entry. Well, I disagree about which is more common. I think almost all users will have a 'testing' file in the list. Probably just the one, but it's still there. >> Perhaps a confirmation dialog? (Carefully stated so that the user doesn't >> think the file itself is being removed.) > > Uggh. I admit that this was my first thought but.. Uggh. Besides, > we already HAVE a confirming dialog.. It says something to the affect > of "Cannot open file". Maybe a checkbox on the error dialog: 'remove history entry'? > I need to go read the original bug report to see what this was > TRYING to fix. Well I wrote it, so I know what it says :) Instead of doing that, search for an email to the user list with subject: 'How to get rid of saved file'. I wrote the bug report for the user who emailed that (since I had the same question). The feature request I wrote was just an idea for an easy way to remove them. But any other method is fine with me, as long as it's possible, I don't specifically need them removed when the file can't be opened. -Ariel ___ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel
Re: r16077 - gnucash/trunk/src - Add gnc_history_remove_file, call it if the history file cannot be loaded, #388500.
Ariel <[EMAIL PROTECTED]> writes: > The problem is that there is no obvious way to remove a file from the > history menu. There is gconf, but it's not expected that users will know > how to use it. That's a completely different issue that automatically removing an unfound file at startup. I completely support a context menu option to delete items from the history if there's really a call for it, but I think automatically removing it is the wrong thing. > I think it's easier for you to reopen your file, then it is for a user to > figure out which gconf key to remove. How often does a user need to remove an entry from their history? How often does a user store their datafile on a mounted volume? I think the latter is MUCH more common than the former, so we should optimize for the mounted volume, not the removing and entry. > Perhaps a confirmation dialog? (Carefully stated so that the user doesn't > think the file itself is being removed.) Uggh. I admit that this was my first thought but.. Uggh. Besides, we already HAVE a confirming dialog.. It says something to the affect of "Cannot open file". I need to go read the original bug report to see what this was TRYING to fix. > -Ariel -derek -- Derek Atkins, SB '93 MIT EE, SM '95 MIT Media Laboratory Member, MIT Student Information Processing Board (SIPB) URL: http://web.mit.edu/warlord/PP-ASEL-IA N1NWH [EMAIL PROTECTED]PGP key available ___ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel
Re: r16077 - gnucash/trunk/src - Add gnc_history_remove_file, call it if the history file cannot be loaded, #388500.
On Mon, 14 May 2007, Thomas Bushnell BSG wrote: > On Sun, 2007-05-13 at 16:53 -0400, Derek Atkins wrote: >> I dont like this patch. Sometimes I start gnucash before >> I remember to mount my encrypted partition. GnuCash happily >> warns me that the file isn't there and I can then quit, mount >> the partition, and then re-start gnucash. If gnucash >> automatically removes the entry from the history this no >> longer works. > > I have the same concern; I sometimes start gnucash before I remember to > start up AFS. Same problem. The problem is that there is no obvious way to remove a file from the history menu. There is gconf, but it's not expected that users will know how to use it. I think it's easier for you to reopen your file, then it is for a user to figure out which gconf key to remove. Perhaps a confirmation dialog? (Carefully stated so that the user doesn't think the file itself is being removed.) -Ariel ___ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel
Re: r16077 - gnucash/trunk/src - Add gnc_history_remove_file, call it if the history file cannot be loaded, #388500.
On Sun, 2007-05-13 at 16:53 -0400, Derek Atkins wrote: > I dont like this patch. Sometimes I start gnucash before > I remember to mount my encrypted partition. GnuCash happily > warns me that the file isn't there and I can then quit, mount > the partition, and then re-start gnucash. If gnucash > automatically removes the entry from the history this no > longer works. I have the same concern; I sometimes start gnucash before I remember to start up AFS. Same problem. Thomas ___ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel
