Paul Fenwick wrote:
> G'day GnuCashers,
>
> On Wed, May 31, 2000 at 12:31:16PM -0700, Dave Peticolas wrote:
>
> > Are you talking about the transfer field on the transaction line in
> > multiline mode? That field wasn't there previously, the space was just
> > blank. The new field (currently called 'transfer to') allows you to
> > move a transaction into another account. The transfer fields on the
> > split lines, and the transfer field in the single and double modes,
> > should work as they always have.
>
> Aha, this is exactly what I'm talking about. However I'm sure that
> the space most certainly had an effect, or at least the way that I
> used it. I'll explain.
>
> I run auto-single mode. Almost all of my transactions are single lines,
> but I like having the current transaction make room for splits so that
> if there are any, I can enter them. In the vast majority of cases,
> I'll enter a transaction exactly as if it were a single transaction.
> Eg (in Assets:Cash)
>
> 01/01/2000 Groceries Expenses:Food $100.00
>
> The Expenses:Food indicates that I've taken $100 from my cash asset,
> and transfered it to the my Expenses:Food account. GnuCash takes
> care of the double entry and all those other good things, and I just
> leave the split lines empty (hit enter on them) because there aren't
> any splits.
>
> However, now (when running in auto-single mode) if I do the same thing,
> the transaction dissapears and moves itself to the Expenses:Food account,
> which is not at all what I want. Now I have to enter ANOTHER line
> of information for the split, which is a lot more keypresses, and a lot
> more work. Alternatively, I can change to use single mode, but that's
> annoying if I ever find myself wanting to enter splits.
>
> To me, it made a lot more sense for GnuCash to allow me to enter both
> single transactions and splits in auto-single mode, and certainly
> provided me with a lot of flexibility and reduced wasted keystrokes.
>
> Using one account's register to enter data into another account's
> register (when not part of double entry) doesn't strike me as a feature
> that would be used very often. There's also the potential for people
> to accidently enter a transaction into another account, and the user
> having to hunt down the rogue transaction. (Scrub does this well if
> you use double-accounting, but not everyone does.)
>
> Cheers,
>
> Paul
>
> --
> Paul Fenwick <[EMAIL PROTECTED]> | "When I see an adult on a bicycle,
> http://www.advogato.net/person/pjf | I have a hope for the human race."
> PGP KeyID: 0xB1479E55 | -- H.G. Wells
>
> ------------------------------------------------------------------------
> Part 1.2Type: application/pgp-signature
I would have to agree - having the ability to transfer a transaction from one
account to another using a field in the transaction entry is going to be very
confusing. You are mixing entry fields for the transaction with actions done
to the transaction.
If you want to accomplish some action on the transation such as deleteing it
or moving it to another account that should not be accomplished using a data
entry field. Currently if I want to delete an entry I can use the mouse and
right click on the entry to bring up a small dialog window. Imagine if one of
the data entry fields caused a transaction to be deleted by entering data in
the field. This would cause great confusion and havoc. Well I think you are
doing the same thing with using a data entry field to cause a transaction to
be moved to another account.
Well I could on and on, but I think you get my point - if we are voting on
this I vote to move this 'function' to the same menu that 'delete' is on and
out of a data entry field.
--
Gnucash Developer's List
To unsubscribe send empty email to: [EMAIL PROTECTED]
