can I get info on quanties from bill splits?

[Shane Litherland]

Hi Derek, list;

now that i'm at end of financial year, i've put some time into fiddling
with a custom report I'd corresponded about months ago.

Some tinkering, but came up with errors. so went back to baby steps:
made a copy of transactions.scm, renamed it quantity.scm and gave it a
new guid (generated from relevant gnucash command in terminal)

so theoretically quantity.scm should work?
Did notice that I'd saved it one-level up in gnucash directory
(under ../report whereas transactions.scm is
under ../report/standard-reports).

Ran a report from gnucash menu - transaction report. changed its name
and saved that (in my home folder/.gnucash/saved-reports-2.4)

then had a look at relevant part of saved-reports-2.4 and tried, one at
a time, substituting the guid that I think related to 'transaction.scm'
for the guid that related to 'quantity.scm' expecting I could at least
get it to spit out the exact same result, but when going back to gnucash
and choosing to run this custom report, I got almost blank page - blank
except for 'error' message at top.
Note, I had re-started gnucash each time I played with the quantity.scm
file.

Also tried three locations of guid changed at once, still error.

Three places I changed were:
(let ((options (gnc:report-template-new-options/report-guid
"8b704744ae8dd94a91826f18952cae80" "Transaction Report")))

'parent-type "8b704744ae8dd94a91826f18952cae80"

'renderer (gnc:report-template-renderer/report-guid
"8b704744ae8dd94a91826f18952cae80" "Transaction Report")))



Any pointers? How about ways to start/run gnucash from command line with
verbose or debug settings to see more info on what it doesn't like? I
did try gnucash --debug and it launched but didn't really seem to spit
anything relevant out in terminal.

ways to run just the report from command/terminal???

I figure until I can understand how to get an identical but new-named
report to work, I shouldn't go tweaking report layout!

Regards,
shane.
PS since earlier correspondence, I figured (once I get over this hurdle)
I could work with either register.scm or transaction.scm to get desired
outcomes. Initially had played with register.scm but hit similar
1st-step errors.

 
On Thu, 2012-02-02 at 10:23 -0500, Derek Atkins wrote:
> Shane Litherland <litherland-farm at bigpond.com> writes:
> 
> > Hi Derek
> >
> > I've looked at some of the .scm files,
> > I am thinking what might work for me, is copying the 'quantity' commands
> > for the invoice.scm into a customised version of the register.scm
> >
> >
> > My first step would naturally be to save a copy of the register.scm with
> > a new name so I can play with it.
> 
> You will need to:
> * rename the file
> * rename the module
> * rename the report
> * give the renamed report a new GUID
> 
> > That means then going through and e.g. changing the define lines from
> > 'register' to 'my-bastardisation-of-an-otherwise-workable-register'
> > or something similar... ;-)
> 
> Yep.
> 
> > Before I crash headlong into that, a quick 'find' shows 'register' in
> > other command pieces such as 
> > register-report-guid
> > gnc:register-report-create-internal
> > and others.
> 
> You will have to make changes in the report.scm.  You shouldn't need to
> make changes outside that report.  The 'create-internal' should possibly
> be removed from the copied report.
> 
> > are these commands/modules defined 'freestanding' (i.e. the register.scm
> > is calling them from elsewhere) and therefore I don't go changing their
> > leading name, or are they all referring back to earlier defines within
> > this register.scm file, in which case if I start changing the filename
> > and main define, I'd have to diligently work through and change any
> > 'children' bits..?
> 
> All the report files should be self sufficient, although sometimes there
> are hooks where others call into the report.  In those hook cases you
> will need to remove the hooks in your duplicated report.
> 
> > I can handle wading through it and slowly deciphering things, just
> > wanted to get some superior advice before I continue.
> 
> No worries!
> 
> > cheers,
> > shane.
> 
> -derek
>