The setup for this is as follows: * open a register and apply a filter such that a number of splits get hidden (for example hide splits before a certain date) * now go and open a transaction report, filter it to include the account of the above register and some of the splits that were hidden in the register itself (for example include the splits before the chosen date in the register filter) The transaction report will properly show these splits and add hyperlinks to the register. Clicking on a hyperlink to a split that's hidden in the register, that register will open, but the blank split will be selected. While that's a reasonable thing to do (the target split is hidden after all) it is also a source of confusion. Possible improvements would be to 1. inform the user the target split is hidden as the result of a filter and that's why the blank split was selected 2. ask the user to remove the filter to be able to show the target split anyway
Created attachment 373707 [details] target split is hidden Here's a candidate patch. modified gnucash/gnome/gnc-split-reg.c @@ -1795,6 +1795,9 @@ gnc_split_reg_jump_to_split(GNCSplitReg *gsr, Split *split) if (gnc_split_register_get_split_virt_loc(reg, split, &vcell_loc)) gnucash_register_goto_virt_cell( gsr->reg, vcell_loc ); + else + gnc_warning_dialog (GTK_WINDOW (gsr->window), + "target split is currently hidden in this register"); gnc_ledger_display_refresh( gsr->ledger ); }
How about offering the user to remove filters on the register to show the hidden split ?
too difficult! cannot find link from GNCSplitRegister to its owner GncPluginPageRegisterPrivate.
Created attachment 373712 [details] Patch for jumping from reports Chris, give this a spin.
Created attachment 373713 [details] offer to remove filter from report Some cleanup. Would also benefit from similar code with other uses of gnc_split_reg_jump_to_split, e.g. doubleclick from reconcile window. Not sure where to place these functions.
Created attachment 373716 [details] Patch for jumping from reports Try this...
Works well for me!
I have pushed my fix to master so will be in the next version 4.0
