Re: Feedback about 2.7.8

2018-03-28 Thread David Carlson
Neither of those sample .css file addresses Adreien's question " Is there a class/id list for the GnuCash UI so we can know what’s available to style? Or are those listed in the sample file the only ones available? (I’m also assuming other properties can be set, for example font-size in addition

Re: Feedback about 2.7.8

2018-03-28 Thread Robert Fewell
I do not think that is the right file to link to, I would of thought this one was the correct one... https://github.com/Gnucash/gnucash/blob/unstable/doc/gtk-3.0.css Bob On 28 March 2018 at 21:13, Adrien Monteleone wrote: > Christop, > > A general guide to CSS(in

Re: Feedback about 2.7.8

2018-03-28 Thread Adrien Monteleone
Christop, A general guide to CSS(in the context of web pages) is available here: https://www.w3schools.com/css/ A more specific guide with respect to CSS usage in GTK3 is here: https://developer.gnome.org/gtk3/stable/chap-css-overview.html Regards, Adrien > On Mar 28, 2018, at 2:20 PM,

Re: Feedback about 2.7.8

2018-03-28 Thread Adrien Monteleone
Geert, I just noticed in the sample file linked in the FAQ that the following rules are repeated at the top and bottom of the file: /* Change font color by mixing with grey */ .lighter-grey-mix { color: mix (currentColor, grey, 0.8); } .darker-grey-mix { color: mix (currentColor, grey, 0.2); }

Re: Feedback about 2.7.8

2018-03-28 Thread Christoph R
Hi Geert, > Am 28.03.2018 um 17:24 schrieb Geert Janssens : > > Op woensdag 28 maart 2018 15:46:26 CEST schreef Christoph R: > >> It choked on one of my files, which worked fine with 2.6 and was probably >> created with 2.4 or even earlier. There was an out-of range

Re: Feedback about 2.7.8

2018-03-28 Thread Geert Janssens
Op woensdag 28 maart 2018 15:46:26 CEST schreef Christoph R: > Hi, > > since 2.7.8 is deemed a release candidate I am giving it a try on MacOS High > Sierra. > > here is my feedback so far: Thanks for your feedback. > It choked on one of my files, which worked fine with 2.6 and was probably >

Re: Feedback about 2.7.8

2018-03-28 Thread Christoph R
Hi Alen, > The description is something for me (the user) to add notes about the > transaction and is basically irrelevant for anyone else we might argue about that. I find it at least inconsistent since the transaction description is in fact protected by the reconciliation of a single

Re: Feedback about 2.7.8

2018-03-28 Thread Christoph R
> Does changing the description of a reconciled split line unreconcile the > transaction or does it leave the split reconciled but simply have no warning? It leaves the split reconciled. Cheers, Christoph > Am 28.03.2018 um 16:03 schrieb David Carlson : > > Does

Re: Feedback about 2.7.8

2018-03-28 Thread David Carlson
Does changing the description of a reconciled split line unreconcile the transaction or does it leave the split reconciled but simply have no warning? David C On Wed, Mar 28, 2018 at 8:54 AM, Alen Siljak wrote: > > > Sent: Wednesday, March 28, 2018 at 3:46 PM > > From:

Re: Feedback about 2.7.8

2018-03-28 Thread Alen Siljak
> Sent: Wednesday, March 28, 2018 at 3:46 PM > From: "Christoph R" > To: gnucash-devel > Subject: Feedback about 2.7.8 > But I can change the description of a reconciled split without a warning. I > need to file a bug report on that.

Feedback about 2.7.8

2018-03-28 Thread Christoph R
Hi, since 2.7.8 is deemed a release candidate I am giving it a try on MacOS High Sierra. here is my feedback so far: It choked on one of my files, which worked fine with 2.6 and was probably created with 2.4 or even earlier. There was an out-of range date in the price database which I

Re: Unstable Imap Editor

2018-03-28 Thread Geert Janssens
Op woensdag 28 maart 2018 12:09:33 CEST schreef Robert Fewell: > Could some one explain the following, trying to fix the 2nd problem as I > thought was the simpler one... > If I try this ... > > std::vector path {IMAP_FRAME}; > if (category) > path.emplace_back (category); > >

Re: Unstable Imap Editor

2018-03-28 Thread Robert Fewell
Could some one explain the following, trying to fix the 2nd problem as I thought was the simpler one... If I try this ... std::vector path {IMAP_FRAME}; if (category) path.emplace_back (category); if (qof_instance_has_path_slot (QOF_INSTANCE (acc), path)) I have a slot but