GnuCash
Contact   Instructions
Bug 798151 - Value entry box not tied to associated transaction in Since Last Run assistant
Summary: Value entry box not tied to associated transaction in Since Last Run assistant
Status: RESOLVED FIXED
Alias: None
Product: GnuCash
Classification: Unclassified
Component: Scheduled Transactions (show other bugs)
Version: 4.4
Hardware: PC Windows
: Normal normal
Target Milestone: ---
Assignee: Bob
QA Contact: core
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2021-03-17 00:14 EDT by David Carlson
Modified: 2021-09-24 18:38 EDT (History)
4 users (show)

See Also:


Attachments
NEED VALUE detatched from SX (5.15 MB, image/jpeg)
2021-03-17 16:10 EDT, David Carlson
no flags Details

Description David Carlson 2021-03-17 00:14:39 EDT

    
Comment 1 John Ralls 2021-03-17 00:23:49 EDT
David, you've been around long enough to know that cryptic one-liners are not sufficient bug reports. Please provide details.
Comment 2 David Carlson 2021-03-17 00:27:58 EDT
when a new instance of the Since Last Run assistant is started, the mouse highlight floats to the first value entry box that needs to be filled, but the list of transactions does not follow, so I cannot see which transaction is missing it's value.  It is necessary to manually scroll down until a transaction that is highlighted finally comes into view.

This issue started in the release 3.x series, and it continues up to at least release 4.4.  

There seems to be another issue in the same program releases that is similar in appearance with report titles floating out of the tabs that they are supposed to be anchored in, but that should have a separate bug number.
Comment 3 David Carlson 2021-03-17 00:29:44 EDT
I am not sure how the bug report was created before I entered my description, I certainly do know better.
Comment 4 David Carlson 2021-03-17 00:52:28 EDT
I was not able to finish searching for duplicates to this bug report or to search for a bug report for the report title floating out of the tab.
Comment 5 Bob 2021-03-17 05:47:14 EDT
Is this not the same as previous bug you reported 798025?
Comment 6 Bob 2021-03-17 05:48:47 EDT
And do you mean this 798151 for the tabs?
Comment 7 Bob 2021-03-17 12:07:54 EDT
Can you provide a screen shot of this, hide any personal data?

I am not seeing this, maybe it is the items I have scheduled none of the rows are highlighted and it just starts at the first entry.

Provide a screen shot of SLR window when it first opens so I can see exactly what you see.
Comment 8 David Carlson 2021-03-17 12:35:04 EDT
I found a bug report for text floating out of tabs - See bug 798129.
It will take a while to regenerate the SLR window screenshot.
Comment 9 David Carlson 2021-03-17 16:10:47 EDT
Created attachment 374029 [details]
NEED VALUE detatched from SX

A prerequisite is to have a file that contains a SX ready to enter that will trigger the NEED VALUE box when the Since Last Run assistant is run.

For my example I also check the Review Created Transactions box, then I click OK.

At this point the NEED VALUE box appears but the SX that it is associated to does not appear behind it.  Thus it is an adventure to figure out what to enter into the box.  I needed to take a picture of the computer screen because the regular screen print methods either failed completely or did not catch the NEED VALUE box while it was on the screen.
Comment 10 Bob 2021-03-17 16:26:08 EDT
Thank you, I now understand what you mean.
I assumed you were navigating the list and updating the value, never occurred to me to let the OK button do the navigating.

From your screen you have some reminders that populate the list first and the first scheduled transaction that requires a value is further down the list which is out of view and hence the confusion.

I will need to setup some reminders that populate the list first to identify possible fix.
Comment 11 Bob 2021-04-13 06:09:48 EDT
I have pushed a change to scroll the tree view so the entry row is visible. This will be in 4.6 and the next nightly. If you can test and confirm OK so we can close the bug that would be great.

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