GNOME Bugzilla – Bug 491728
Scheduled Upcoming Calendar highlighting
Last modified: 2018-06-29 21:53:31 UTC
I added three scheduled transactions: Transaction1 | Monthly (x12): 1 | 02/01/2008 Transaction2 | Monthly (x6): 16 | 05/16/2008 Transaction3 | Monthly (x12): 1 | 09/01/2008 But I only see the yellow highlighting in one month. If, I double-click on the 1st transaction the "Edit Schedule Transaction" is displayed, and then I click OK. The calendar displays months Feb-Jan and only Feb 1st and Feb 16th is yellow. If, I double-click on the 2nd transaction the "Edit Schedule Transaction" is displayed, and then I click OK. The calendar displays months May-Apr and only May 1st and May 16th is yellow. If, I double-click on the 3rd transaction the "Edit Schedule Transaction" is displayed, and then I click OK. The calendar displays months Sep-Aug and only Sep 1st and Sep 16th is yellow. Mike
I get the same problem. Using 2.2.2 on Windows XP. The start month of the upcoming calendar appears to be determined by the last scheduled transaction you enter. So if your last entered one is with a start date later than next month you can't see next month on the upcoming calendar. A workaround seems to be to select your earliest scheduled transaction and do an "Edit Schedule Transaction" (you don't need to change anything, just OK it). This resets the upcoming calendar start to the month your transaction starts.
Happens on Linux version 2.2.4 as well.
Also happening on 2.2.8 - Linux
Also happening on 2.2.9 - Linux
Still happening in svn as of today. I ran into this problem after starting to regularly use scheduled transactions, and it's pretty annoying, so I checked out svn and dug in. The starting date is set in gdc_add_tag_markings() in gnc-dense-cal.c. This function takes the first date for a particular "tag" (not sure what that actually means) and sets that as the starting month/year of the calendar. However, this function is being called once for each of my scheduled transactions (there's one scheduled transaction for each "tag"), so the position that the calendar finally gets set at is the date for the last scheduled transaction I've saved. So how do we fix this? 1) Simply remove the calls to setting the calendar's starting position from gdc_add_tag_markings() and use the default of the current month/year. If there's no upcoming transactions in the next month, I don't mind just seeing an empty calendar. That just means I don't have any bills/etc to worry about for awhile. 2) Set the date at the end of gdc_add_markings(), keeping track of the earliest date over all the gdc_add_tag_markings() calls 3) ??? Let me know, and I'd like to put together a patch. Cheers, Jason
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!
Actually 2.4 has the same bug. The good news is that someone provided a patch for this: refer to bug 652193. *** This bug has been marked as a duplicate of bug 652193 ***
GnuCash bug tracking has moved to a new Bugzilla host. This bug has been copied to https://bugs.gnucash.org/show_bug.cgi?id=491728. Please update any external references or bookmarks.