Flywire,
Have you looked at https://code.gnucash.org/docs/MASTER/group__Options.html?
I guess by "set and use" you mean add a date option to your report. The basic
function is documented at
https://code.gnucash.org/docs/MASTER/group__Options.html#gae207538b13cb19bb68f9b9300743b709
and it has
John,
Seems like an X-Y response. The meaning of a hack is clear, although this
is more of a tweak, and where it occurs hardly matters if it's not part of
a PR. A response in terms of using existing report/module code in a new
report would be fine.
I'm not sure I understand your point. Nothing in the Sample report or the
Custom Reports wiki page suggests changing the code that makes the options
work, just how to use the existing options. Of course you can use GnuCash's
existing code as a starting point just like you might use an existing
Fair enough. The quoted link is not part of a PR, it demonstrates the code, and
the thread from 2021 has extended into getting the functionality working
again following subsequent code changes released in V5.
All scheme reports in GnuCash are internals, interpreted reports, with much
of the
Flywire,
Nope, accounting periods didn't get fixed so everything I said in 2021 about
that is still true.
> https://github.com/flywire/gnucash/blob/Fiscal-year/libgnucash/app-utils/date-utilities.scm#L557-L569
Messing around in GnuCash's internals is only supported if the result gets
Your assumptions are wrong. Clearly, communication from the developer(s)
was ineffective. Full advice of the "major change" quoted in
https://lists.gnucash.org/pipermail/gnucash-user/2023-April/106463.html
with no response to the request for guidance.
On Tue, 18 Apr 2023 at 15:20, Vincent Dawans
My comment was related to custom report creation from an
end-user perspective, which is to say using the given set of options. So
yes the move to c++ makes changing the supporting utility code on the fly
more difficult if that's something required (as in this case). That is a
limitation of going
I can't see how.
Firstly, from previous comments, people don't seem to understand my
workflow. The suggestion it is only a matter of setting the Accounting
Period once per year is so wrong without changing start date of year.
To briefly summarise, I have half a dozen entities and a few extras,
I can certainly see the utility of being able to define various 'start
of year' options for different reports. Though I think this is
essentially what the 'accounting period' option was supposed to
accomplish. (and then the report's generic 'start of accounting period'
will use that date)
Vincent, you seem confident. I posted an example. Can you demonstrate
changing say Start of This Year to 1 July in V5?
Code at
https://github.com/flywire/gnucash/blob/Fiscal-year/libgnucash/app-utils/date-utilities.scm#L557-L569
works in V4 (check cur-year/cal-year). See comments at
10 matches
Mail list logo
