In puttering about with register presentation and my dream of getting GnuCash to grey out reconciled register lines (like Quicken), I've noticed that if a read-only boundary is set in File > Properties, all the transactions that have become read-only have their background colour de-saturated (greyed out).

Furthermore, if I define READONLY_LINES_WITH_CHANGED_FG_COLOR in gnucash-sheet-private.c, the foreground text becomes de-saturated too (after fixing a couple of minor compile errors that were introduced).

Several questions come to mind:

1. Does anyone remember why two different and possibly co-existing mechanisms for identifying read-only transactions were established, of which one was implemented and the other apparently scrapped?

2. Is there any reason not to co-opt the disabled foreground de-saturation logic for reconciled lines instead?

3. Is there a central place where all these conditional compilation directives are documented or discussed (short of doing greps for IFDEFs)?

4. Thoughts about achieving the goal using the above approach vs making a whole new CSS class for a reconciled line style?

Thanks as always,

Paul


_______________________________________________
gnucash-devel mailing list
[email protected]
https://lists.gnucash.org/mailman/listinfo/gnucash-devel

Reply via email to