entry transaction not only at bottom

[Jim]

On Thursday 06 November 2003 01:09 am, greg wrote:
> hello gnucasheteers,
>
> i frequently find myself entering transactions from "awhile ago".  so
> first, i'll be up looking to see if it was already there, then i have to
> go to the bottom to enter it, then when it's entered it disappears off
> the top of the window, and i have to scroll up again to find it.
>
> if several such transactions need to be entered, you watch them all
> disappear as you enter them, presuming and hoping they will be there
> when you're done.
>
> so, it would be preferable to have the location of entry be vertically
> located according to the date of the transaction being entered.
>
> i propose that whenever the "blank" or "entry" transaction has a date
> (or whichever field is being sorted) less recent than existing
> transactions, that the "blank" or "entry" transaction be located BOTH at
> the bottom AND vertically whereever it belongs.  both locations would
> show the yellow color and update during typing.  if the upper one was
> selected, when the user changes the date, scrolling should follow the
> transaction as it changes its vertical location.  some of this is
> already what happens anyway when modifying an existing transaction.
>
> or frankly i personally would be just as happy if the entry transaction
> were located only "where it belongs" and not (necessarily) at the
> bottom, since there already is a command to go to it ("blank"), but
> either implementation would make me quite happy.
>
> additionally i propose an "insert transaction" command that, in the
> context of the above, merely changes the date of the entry transaction
> to the date of the current transaction, and locates the cursor on the
> (upper) entry transaction.
>
> my proposal differs from quicken's insert transaction command
> significantly in that the procedure for entering several nonrecent
> transactions would not require repeatedly using the insert transaction
> command.  instead you would always find the cursor ready to go on a new
> transaction, located vertically where it belongs.
>
> what do y'all think?
>
> -greg
>
> _______________________________________________
> gnucash-user mailing list
> gnucash-user at lists.gnucash.org
> https://lists.gnucash.org/mailman/listinfo/gnucash-user
I agree having those transactions jump to the date order is disconcerting.

I just change the sort to date entered when entering transactions from 
non-current dates.  That way what I just entered will be at the bottom.  When 
I want to look at the entries by the transaction date, I change the sort 
order back.

It seems a whole lot simpler.  If you want to see what you entered in the 
order you entered it, sort on date entered.

Showing transactions twice or having a blank transaction show up in the middle 
of the register depending on, I'm not quite sure what, just seems to invite  
confusion.

-- 
Jim