Hello,
I have made local developments on gnucash, mainly introducing the exact time up
to the second in each date, and arranging colors and font sizes of gnucash
window to have white text on dark background.
I can tell you, José, that there are in the .gnucash xml file some details that
may be us
My patchset is not ready yet.
After three weeks of intensive testing (without any crash :-), I
finally stumbled on a bug.
That bug is that, when editing a transaction done when the daylight
settings is not the same as the time of edition, the date is going
earlier and earlier. To enter a correct
2016-01-28 19:54 UTC+01:00, John Ralls :
> You removed the code for the auto-read-only threshold.
This is because my version of gnc_tree_util_split_reg_parse_date delegated to
qof_scan_date_internal, and I did not know that qof_scan_date_internal does not
honor that auto-read-only threshold.
I wi
t; On Feb 1, 2016, at 1:50 AM, gLETTERyYuMEANSj LETTERyOt
>> wrote:
>>
>> Dear everyone,
>>
>> Can someone help me, by showing the right Gnucash-compatible way to
>> recover the
>> time difference due to the timezone settings at a given UTC date, in
>&g
Dear everyone,
Can someone help me, by showing the right Gnucash-compatible way to recover the
time difference due to the timezone settings at a given UTC date, in
C++ and in C?
This is blocking any progress from my part :-/
2016-01-29 15:49 UTC+01:00, Geert Janssens :
>
Dear Geert,
Thank you for your very helpful input !
>> 2016-01-28 19:54 UTC+01:00, John Ralls :
>> > Don't remove function description comments; do make them Doxygen
>> > markup.
> On Friday 29 January 2016 11:44:53 I wrote:
>> I did that because some function description comments were removed
>
Dear John,
Thank you very much for the help your comments provide to me !
I accept without additionnal question all of your comments that are not quoted
below, and will work on them.
2016-01-28 19:54 UTC+01:00, John Ralls :
> Don't remove function description comments; do make them Doxygen marku
2015-05-28 17:15 UTC+02:00, John Ralls :
> Please don't submit patches to the mailing list. Open a bug in
> Bugzilla.gnome.org or fork our repo on Github, create a branch with your
> patch, and make a pull request. Patches should be written against HEAD in
> the branch you're working on -- which sh
2015-05-29 12:05 UTC+02:00, Christoph Holtermann :
> I vote for keeping the times and making them visible.
Thank you.
I have created a github fork. I am trying to upload my patches there, but I am
in a busy period. Then I will switch to 1100Z.
Daniel
_
Thank you very much to discuss with me.
> That changes the way the database is interpreted
I disagree.
If the user loads a .gnucash file then edits it and saves it, the date field of
a preexisting transaction only changes if:
- the date field used another timezone than + (gnucash-2.4), in w
2015-05-28 20:02 UTC+02:00, Michael Ferrara :
> I see how noting transaction times down to the fraction of a second could
> be useful for quantitative analysis of a stock market.
Among the multiple date format used (from memory: struct tm, Timespec, time64,
GDate, GDateTime, {int day, month, year}
> Daniel,
>
> Please don't submit patches to the mailing list. Open a bug in
> Bugzilla.gnome.org or fork our repo on Github, create a branch with your
> patch, and make a pull request.
I'll choose the buzgilla bug. I'll then ask my boss if I can take time for a
github account (would be my first
12 matches
Mail list logo
