After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 521505 - Scheduled transaction appears on wrong days on calendar
Scheduled transaction appears on wrong days on calendar
Status: RESOLVED OBSOLETE
Product: GnuCash
Classification: Other
Component: Scheduled Transactions
2.2.x
Other Linux
: Normal normal
: ---
Assigned To: Josh Sled
Josh Sled
Depends on:
Blocks:
 
 
Reported: 2008-03-10 04:56 UTC by G
Modified: 2018-06-29 22:02 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
Example file (4.70 KB, text/plain)
2008-05-13 05:33 UTC, Andreas Köhler
Details

Description G 2008-03-10 04:56:57 UTC
A transaction (A) scheduled to begin two months from now shows up on the calendar (right-click) in the current month if there is another transaction (B) scheduled for the current month. If transaction A is scheduled to occur quarterly (every three months) then it will show up on the wrong month each time.

If I disable transaction B, then transaction A shows up in the correct month.
Comment 1 Andreas Köhler 2008-05-13 05:29:54 UTC
That is true.
It seems that gnc-dense-cal.c:gdc_add_tag_markings() is called for each SX and each time resets the starting month and adds its tags at the calculated offsets.  Old offsets are not recalculated when the month is reset, so tags will appear on wrong positions.
Jsled, do you need more info?  I think I would need a lot more time to resolve this one than you :-)
Comment 2 Andreas Köhler 2008-05-13 05:33:53 UTC
Created attachment 110825 [details]
Example file

SX A: Monthly on the 1st, starting June 1st
SX B: Monthly on the 2nd, starting July 2nd

A's marks are added, B resets starting month to July with A's offsets still active.
-> B's marks are correct
-> A's July 1st is marked on July 31st, as June has only 30 days
Comment 3 Christian Stimming 2011-02-07 10:12:17 UTC
Thank you for taking the time to report this bug. However, you are using a version that is too old and not supported anymore. The GnuCash developers are no longer working on that version, so either this bug has already been fixed or unfortunately there will not be any bug fixes for the version that you use. The current stable version of gnucash is 2.4.0 now.

In the (hopefully unlikely) case you discover the same bug in the very latest stable version, do not hesitate to REOPEN it again. Also, feel free to file other bugs or enhancement requests that you find. Thank you very much!
Comment 4 John Ralls 2018-06-29 22:02:06 UTC
GnuCash bug tracking has moved to a new Bugzilla host. This bug has been copied to https://bugs.gnucash.org/show_bug.cgi?id=521505. Please update any external references or bookmarks.