GnuCash
Contact   Instructions
Bug 794990 - Double-click on saved report configuration no longer works
Summary: Double-click on saved report configuration no longer works
Status: RESOLVED FIXED
Alias: None
Product: GnuCash
Classification: Unclassified
Component: User Interface General (show other bugs)
Version: 3.0
Hardware: Other Linux
: Normal normal
Target Milestone: future
Assignee: ui
QA Contact: ui
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-04-04 17:00 EDT by lj618
Modified: 2018-04-27 06:43 EDT (History)
5 users (show)

See Also:


Attachments

Description lj618 2018-04-04 17:00:15 EDT
Using: gnucash-3.0 on 32-bit Slackware Linux 14.2

In gnucash-2.6.x, double-clicking on the name of a saved report configuration in the Saved Report Configurations dialog would load/run the report.  Pressing the enter key or space bar, or clicking on the small button after the name also worked.

In gnucash-3.0, double-clicking on the name no longer does anything. The other ways of loading a report do still work.

Double-clicking to load a report configuration is documented in the GnuCash Help Manual, page 129 "Working with Saved Report Configurations".
Comment 1 Adrien 2018-04-05 01:48:13 EDT
This isn't just linux. It's the same on MacOS. (10.13.4 at least)

I was going to report this as a bug, but I suspected it's due to a change with Gtk3. If not, then yes, it's a bug, otherwise, I suppose as long as we can still run the report via the icon (I didn't know about space/enter) then I suppose it's then a matter of updating the Help Manual.
Comment 2 lj618 2018-04-05 13:59:52 EDT
It could be due to a change with Gtk+3 but still a bug. I see double-click still works in GnuCash-3.0 on rows of Edit Scheduled Transaction, Security Editor, and Price Editor.
Comment 3 Bob 2018-04-08 07:52:34 EDT
I use Gentoo Linux and can double click on the "Saved Report Configurations" and the reports open as expected.
Bob
Comment 4 Bob 2018-04-11 06:37:27 EDT
Just tried this on Windows 10 and it does not work.
Comment 5 Bob 2018-04-19 11:45:12 EDT
I think I have a fix for this and will update soon.
Comment 6 Geert Janssens 2018-04-27 06:43:56 EDT
This problem has been fixed in our software repository. The fix will go into the next software release, 3.1. Once that release is available, you may want to check for a software upgrade provided by your Linux distribution or on our website.

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