After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 116565 - don't populate reports at boot time but when user selects the report tab
don't populate reports at boot time but when user selects the report tab
Status: RESOLVED WONTFIX
Product: GnuCash
Classification: Other
Component: User Interface General
unspecified
Other Linux
: Normal enhancement
: ---
Assigned To: David Hampton
Chris Shoemaker
: 343300 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2003-07-02 20:41 UTC by Bob Forsman
Modified: 2018-06-29 20:34 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Bob Forsman 2003-07-02 20:41:00 UTC 
While gnucash boots up it loads all the reports.  As each report is loaded
it is added to the tab stack.  This process overrides the user's selection
of tabs.

I think that the new tabs should be added without changing which tab is
selected/focused.
Comment 1 Lorenzo Cappelletti 2003-10-13 21:18:35 UTC 
Because the report load process may take a while on old computers 
and/or with several reports, I suggest to not update the reports at 
the start-up rather when the user first click on the relative tab.
Comment 2 gnucash 2003-10-14 17:38:28 UTC 
"Lazy evaluation" of reports is not a bad idea.  I have many reports
in my gnucash workbook, and the load is slow, even on a 1GHz machine.
 Sometimes I don't even look at a single report, and even when I do
look at reports, there are usually only 3 or 4 I thumb through.

If the reports were evaluated only when I visited them (or even less
conveniently when I click reload) that would still save me 30 seconds
of start-up time at the cost of 1 click and 4 seconds.  I often need
to regenerate a report anyway after I've entered some transactions.
Comment 3 Chris Shoemaker 2006-03-16 20:56:17 UTC 
somewhat related: 107282
Comment 4 Chris Shoemaker 2006-03-16 20:58:47 UTC 
#107282
Comment 5 Chris Shoemaker 2006-03-16 20:59:24 UTC 
bug#107282
Comment 6 David Hampton 2006-04-19 02:22:59 UTC 
The original problem is fixed in the 1.9 series of beta releases.  I'm re-titling   this entry to match the remaining issue.
Comment 7 Elijah Newren 2006-05-31 00:12:41 UTC 
*** Bug 343300 has been marked as a duplicate of this bug. ***
Comment 8 Christian Stimming 2011-02-07 13:06:17 UTC 
Thank you for taking the time to explain your enhancement request.

The described enhancement is a good proposal and would be an advantage for the software. However, as a volunteer-driven project with limited resources, the GnuCash developers have their own priorities about the features which are most likely being worked on in the near future. In that sense, the current GnuCash developers decided not to work on your proposed feature in the next 4-6 months. In case you would like to have this feature implemented in any case, you have the following option: 1. Start to program in gnucash yourself - see http://wiki.gnucash.org/wiki/Development . 2. Convince someone who is not yet part of the GnuCash team to join the team and implement your feature. 3. Pay some of the GnuCash developers to implement your feature - ask on the mailing list gnucash-devel@gnucash.org in that case. Thank you very much.

Feel free to file other bugs or enhancement requests that you find, though.
Comment 9 John Ralls 2018-06-29 20:34:44 UTC 
GnuCash bug tracking has moved to a new Bugzilla host. This bug has been copied to https://bugs.gnucash.org/show_bug.cgi?id=116565. Please update any external references or bookmarks.