Re: G2 Testing - Scheduled Transactions[/Register]
When creating a transaction that is being created via the option "Since Last Run" and listed in the "To Create Transaction Preparation" and I am requested to enter a value (i.e. for a utility) clicking the Forward button without entering the required value displays the "To Create Transaction Preparation" window again. However, this time the size of the read-only register at the bottom is increased (by a few pixels). Pressing the Forward button repeatedly increases the register each time by the same amount. :( I was hoping we'd be past this perennial window-resize issue; I notice in other threads your tree was a bit old; does this still occur for you? I do not see this behavior; pressing forward simply selects the next transaction that needs a variable binding and updates the proposed-transaction register, without resizing. I am now running with the tree from 2005-10-31 (just before the switch to subversion) and yes, this problem is still around. The values for 'create NN days in advance' and 'Remind me NN days in advance' can't be modified. These entered values can only be turned on or off but the number of days can not be changed. I've re-layed-out the dialog to deal with this. In gtk 1.x, any widgets in the label of a checkbox were manipulable, but apparently not in gtk2; I've made them two seperate widgets, side by side. OK. The new layout is much better and it works as expected. However, the 'Create Automatically' option has a tool tip, the other options do not. Is this intentional? Also, it appears that none of the options (only the menu options of the Template) have keyboard shortcuts. A new thing I ran into: I'm unable to enter anything into the fields for 'Number of Occurrences' and 'Remaining Occurrences'. I may not be using this properly though since I never did use it myself. - Creating a new SX It appears that the values for the "Days in Advance" for a new SX are being populated from the defaults listed in the preferences for 'Scheduled Transactions' even when the preferences are unchecked. Set the values in the preferences to anything other then '0', then uncheck the options. Now create a new SX. The values from the preferences are being used _and_ the options are checked by default. These are fixed, now. The preferences are respected and populated. Yes, this is OK now. - Creating a new SX I'm setting the frequency of the transaction and the start date. After this I want to specify the transaction and click anywhere in the transaction template. This causes the start date and the displayed calendar view to change to 2004-01-01. I cannot reproduce this; can you find a script to reproduce, please? Sorry, but what exactly do you mean when you say 'a script'? I have no SX (deleted them all), I want to create a new one: Actions --> Scheduled Transactions --> Scheduled Transaction Editor Click 'New' Click in the Register templates and the date jumps back to 2004-01-01. - Saving a new SX crashes GC. I had deleted all of my SX to test these things but now I'm unable to retest any of the other items I reported earlier since GC doesn't allow me to save a scheduled transaction without crashing. Here is the backtrace from such a crash: Continuing. Program received signal SIGSEGV, Segmentation fault. [Switching to Thread -1208235552 (LWP 31484)] 0x00a4b3ed in g_date_valid () from /usr/lib/libglib-2.0.so.0#0 0x00bf0402 in __kernel_vsyscall () #1 0x0080df93 in __waitpid_nocancel () from /lib/libpthread.so.0 #2 0x03738080 in libgnomeui_module_info_get () from /usr/lib/libgnomeui-2.so.0 #3 #4 0x00a4b3ed in g_date_valid () from /usr/lib/libglib-2.0.so.0 #5 0x002a2469 in gnc_sxed_update_cal () from /opt/gnucash2/lib/libgncgnome.so.0 #6 0x002a26ce in gnc_sxed_freq_changed () from /opt/gnucash2/lib/libgncgnome.so.0 #7 0x00af87e7 in g_cclosure_marshal_VOID__VOID () from /usr/lib/libgobject-2.0.so.0 #8 0x00aed285 in g_closure_invoke () from /usr/lib/libgobject-2.0.so.0 #9 0x00afb75b in g_signal_stop_emission () from /usr/lib/libgobject-2.0.so.0 #10 0x00afceb0 in g_signal_emit_valist () from /usr/lib/libgobject-2.0.so.0 #11 0x02958330 in gtk_signal_emit_by_name () from /usr/lib/libgtk-x11-2.0.so.0 #12 0x00fccc85 in freq_option_value_changed () from /opt/gnucash2/lib/gnucash/libgncmod-gnome-utils.so.0 #13 0x00af87e7 in g_cclosure_marshal_VOID__VOID () from /usr/lib/libgobject-2.0.so.0 #14 0x00aed285 in g_closure_invoke () from /usr/lib/libgobject-2.0.so.0 #15 0x00afb75b in g_signal_stop_emission () from /usr/lib/libgobject-2.0.so.0 #16 0x00afceb0 in g_signal_emit_valist () from /usr/lib/libgobject-2.0.so.0 #17 0x00afd223 in g_signal_emit () from /usr/lib/libgobject-2.0.so.0 #18 0x029221b1 in gtk_menu_shell_select_first () from /usr/lib/libgtk-x11-2.0.so.0 #19 0x00af87e7 in g_cclosure_marshal_VOID__VOID () from /usr/lib/libgobject-2.0.so.0 #20 0x00aecd9b in g_cclosure_new_swap () fr
Re: G2 Testing - Scheduled Transactions[/Register]
On Sunday 30 October 2005 9:09 pm, someone claiming to be Josh Sled wrote: > On Thu, 2005-10-27 at 12:04 -0400, Tim Wunder wrote: > > In a related issue: > > It would seem to be a good idea to have the preferences dialog mirror the > > SX creation Options section. > > > > See screenshot > > Fixed; the prefs are closer to the dialog, now, both above and below the > surface. > > ...jsled And it's beautiful :) pgpYHqhT7Ew4Q.pgp Description: PGP signature ___ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel
Re: G2 Testing - Scheduled Transactions[/Register]
Josh Sled wrote: - Saving a new SX crashes GC. The message unknown, but with movement is displayed 50 times on the console. (I had this come up twice but can't recreate it right now) I am, however, able to save a new SX if I don't enter anything in the transaction template. I'm unable to reproduce this, either. The "unknown, but with movement" messages relate to the selection-dragging code in the register, but I'm not sure if they're related to the crash. Per your request the backtrace output: #0 0x0026b402 in __kernel_vsyscall () #1 0x0080df93 in __waitpid_nocancel () from /lib/libpthread.so.0 #2 0x03738080 in libgnomeui_module_info_get () from /usr/lib/libgnomeui-2.so.0 #3 #4 0x00a4b3ed in g_date_valid () from /usr/lib/libglib-2.0.so.0 #5 0x004396dd in gnc_sxed_update_cal () from /opt/gnucash2/lib/libgncgnome.so.0 #6 0x00439942 in gnc_sxed_freq_changed () from /opt/gnucash2/lib/libgncgnome.so.0 #7 0x00af87e7 in g_cclosure_marshal_VOID__VOID () from /usr/lib/libgobject-2.0.so.0 #8 0x00aed285 in g_closure_invoke () from /usr/lib/libgobject-2.0.so.0 #9 0x00afb75b in g_signal_stop_emission () from /usr/lib/libgobject-2.0.so.0 #10 0x00afceb0 in g_signal_emit_valist () from /usr/lib/libgobject-2.0.so.0 #11 0x02958330 in gtk_signal_emit_by_name () from /usr/lib/libgtk-x11-2.0.so.0 #12 0x00d675a9 in freq_option_value_changed () from /opt/gnucash2/lib/gnucash/libgncmod-gnome-utils.so.0 #13 0x00af87e7 in g_cclosure_marshal_VOID__VOID () from /usr/lib/libgobject-2.0.so.0 #14 0x00aed285 in g_closure_invoke () from /usr/lib/libgobject-2.0.so.0 #15 0x00afb75b in g_signal_stop_emission () from /usr/lib/libgobject-2.0.so.0 #16 0x00afceb0 in g_signal_emit_valist () from /usr/lib/libgobject-2.0.so.0 #17 0x00afd223 in g_signal_emit () from /usr/lib/libgobject-2.0.so.0 #18 0x029221b1 in gtk_menu_shell_select_first () from /usr/lib/libgtk-x11-2.0.so.0 #19 0x00af87e7 in g_cclosure_marshal_VOID__VOID () from /usr/lib/libgobject-2.0.so.0 #20 0x00aecd9b in g_cclosure_new_swap () from /usr/lib/libgobject-2.0.so.0 #21 0x00aed285 in g_closure_invoke () from /usr/lib/libgobject-2.0.so.0 #22 0x00afb8e7 in g_signal_stop_emission () from /usr/lib/libgobject-2.0.so.0 #23 0x00afceb0 in g_signal_emit_valist () from /usr/lib/libgobject-2.0.so.0 #24 0x00afd223 in g_signal_emit () from /usr/lib/libgobject-2.0.so.0 #25 0x029222c7 in gtk_menu_shell_cancel () from /usr/lib/libgtk-x11-2.0.so.0 #26 0x0291d2cb in gtk_menu_get_for_attach_widget () from /usr/lib/libgtk-x11-2.0.so.0 #27 0x00af887b in g_cclosure_marshal_VOID__BOOLEAN () from /usr/lib/libgobject-2.0.so.0 #28 0x00aecd9b in g_cclosure_new_swap () from /usr/lib/libgobject-2.0.so.0 #29 0x00aed285 in g_closure_invoke () from /usr/lib/libgobject-2.0.so.0 #30 0x00afb3b0 in g_signal_stop_emission () from /usr/lib/libgobject-2.0.so.0 #31 0x00afceb0 in g_signal_emit_valist () from /usr/lib/libgobject-2.0.so.0 #32 0x00afd223 in g_signal_emit () from /usr/lib/libgobject-2.0.so.0 #33 0x029effe0 in gtk_widget_region_intersect () from /usr/lib/libgtk-x11-2.0.so.0 #34 0x029114d3 in gtk_false () from /usr/lib/libgtk-x11-2.0.so.0 #35 0x02854fab in gtk_bin_get_type () from /usr/lib/libgtk-x11-2.0.so.0 #36 0x028903ee in gtk_container_foreach () from /usr/lib/libgtk-x11-2.0.so.0 #37 0x029115ef in gtk_false () from /usr/lib/libgtk-x11-2.0.so.0 #38 0x029ffd77 in gtk_window_get_position () from /usr/lib/libgtk-x11-2.0.so.0 #39 0x00af87e7 in g_cclosure_marshal_VOID__VOID () from /usr/lib/libgobject-2.0.so.0 #40 0x00aecd9b in g_cclosure_new_swap () from /usr/lib/libgobject-2.0.so.0 #41 0x00aed285 in g_closure_invoke () from /usr/lib/libgobject-2.0.so.0 #42 0x00afb3b0 in g_signal_stop_emission () from /usr/lib/libgobject-2.0.so.0 #43 0x00afceb0 in g_signal_emit_valist () from /usr/lib/libgobject-2.0.so.0 #44 0x00afd223 in g_signal_emit () from /usr/lib/libgobject-2.0.so.0 #45 0x029ee66d in gtk_widget_show () from /usr/lib/libgtk-x11-2.0.so.0 #46 0x028a2839 in gtk_dialog_run () from /usr/lib/libgtk-x11-2.0.so.0 #47 0x00d6946f in gnc_verify_dialog () from /opt/gnucash2/lib/gnucash/libgncmod-gnome-utils.so.0 #48 0x00438eb4 in gnc_sxed_reg_check_close () from /opt/gnucash2/lib/libgncgnome.so.0 #49 0x00434c51 in sxed_close_handler () from /opt/gnucash2/lib/libgncgnome.so.0 #50 0x0024e8f7 in gnc_close_gui_component () from /opt/gnucash2/lib/gnucash/libgncmod-app-utils.so.0 #51 0x0024e975 in gnc_close_gui_component_by_data () from /opt/gnucash2/lib/gnucash/libgncmod-app-utils.so.0 #52 0x00434f84 in editor_ok_button_clicked () from /opt/gnucash2/lib/libgncgnome.so.0 #53 0x00af87e7 in g_cclosure_marshal_VOID__VOID () from /usr/lib/libgobject-2.0.so.0 #54 0x00aed285 in g_closure_invoke () from /usr/lib/libgobject-2.0.so.0 #55 0x00afb75b in g_signal_stop_emission () from /usr/lib/libgobject-2.0.so.0 #56 0x00afceb0 in g_signal_emit_valist () from /usr/lib/libgobject-2.0.so.0 #57 0x00afd223 in g_signal_emit () from /usr/lib/libgobject-2.0.so
Re: G2 Testing - Scheduled Transactions[/Register]
On Mon, 2005-10-24 at 02:23 -0400, Volker Englisch wrote: > I don't know if the scheduled transactions are ready for testing since > they crash GC frequently but here are a few things I noticed: "crash[ing] GC frequently" is generally not my experience with them, currently. If possible, can you attach to the crashed process with gdb when you see the "has crashed" dialog and get a backtrace? Do this by running gdb against '/usr/bin/guile', then attaching to the PID mentioned in the crash dialog: $ gdb /usr/bin/guile gdb> attach <> gdb> bt > When creating a transaction that is being created via the option "Since > Last Run" and listed in the "To Create Transaction Preparation" and I am > requested to enter a value (i.e. for a utility) clicking the Forward > button without entering the required value displays the "To Create > Transaction Preparation" window again. However, this time the size of > the read-only register at the bottom is increased (by a few pixels). > Pressing the Forward button repeatedly increases the register each time > by the same amount. :( I was hoping we'd be past this perennial window-resize issue; I notice in other threads your tree was a bit old; does this still occur for you? I do not see this behavior; pressing forward simply selects the next transaction that needs a variable binding and updates the proposed-transaction register, without resizing. > The values for 'create NN days in advance' and 'Remind me NN days in > advance' can't be modified. These entered values can only be turned on > or off but the number of days can not be changed. I've re-layed-out the dialog to deal with this. In gtk 1.x, any widgets in the label of a checkbox were manipulable, but apparently not in gtk2; I've made them two seperate widgets, side by side. > When I have the option for the 'Since Last Run' to 'Run when data file > opened' GC appears to be crashing frequently - when clicking in the > Scheduled Transactions window; when selecting preferences, when > scrolling, etc. So far, GC only crashed for me when I was working with SX. Yeah, I notice a bunch of console noise when opening the SLR dialog. I don't recall seeing the spewage here before, either. :( I've tried only a few flows through the SLR dialog, and without crashes. I'll take a deeper look. Any reproduction scripts you can offer would be great. > I also was able to crash GC when selecting the the option 'Draw > horizontal lines between cells' of the 'Register' preferences. (I > wanted to see if this option effects the SX window and it did in two > ways. :-) ) > Selecting this option while the 'Since Last Run' window is open appears > to be a certain crasher but I still need to build a good test case. I can reproduce this as well by: - open SX editor - close SX editor - open Register prefs - change either "draw {horiz,vert} lines" option --> crash. This leads me to believe SXes aren't cleaning up their register properly... On Tue, 2005-10-25 at 22:35 -0400, Volker Englisch wrote: > I did some more testing with SX: > > - Creating a new SX >It appears that the values for the "Days in Advance" for a new SX are >being populated from the defaults listed in the preferences for >'Scheduled Transactions' even when the preferences are unchecked. > >Set the values in the preferences to anything other then '0', then >uncheck the options. >Now create a new SX. The values from the preferences are being used >_and_ the options are checked by default. These are fixed, now. The preferences are respected and populated. > - Creating a new SX >I'm setting the frequency of the transaction and the start date. After >this I want to specify the transaction and click anywhere in the >transaction template. >This causes the start date and the displayed calendar view to change >to 2004-01-01. I cannot reproduce this; can you find a script to reproduce, please? > - Saving a new SX crashes GC. The message > unknown, but with movement >is displayed 50 times on the console. >(I had this come up twice but can't recreate it right now) >I am, however, able to save a new SX if I don't enter anything in the >transaction template. I'm unable to reproduce this, either. The "unknown, but with movement" messages relate to the selection-dragging code in the register, but I'm not sure if they're related to the crash. > - Running the 'Since Last Run' I have a single transaction with status > Ready to create >The information for the split for this SX is not displayed in the >Transaction Template. When I click on the transaction to display >the split, GC crashes. I cannot reproduce this; can you after the other register updates you took on? >However, if I click the forward button, the 'Transaction Review' >window appears and the program runs into a loop and the window size >increases. The bottom of the window moves towards the b
Re: G2 Testing - Scheduled Transactions/Register
On Thu, 2005-10-27 at 17:54 -0400, David Hampton wrote: > I think my misunderstanding of the sx settings when I created the > preferences may be contributing to the problem. Can you clarify for me > whether my current understanding is correct. (Line numbers refer to the > sxed dialog options settings in Tim's picture.) > > The "create automatically" seems to be a master setting. If clear, all > the other settings are ignored. If checked, then transactions will be > created on the date of the transaction. If the checkbox in line three > is selected, then transactions will not be created on the actual date of > the transaction, but will be created x days early. If transactions are > being created automatically, the "notify me when created" checkbox seems > obvious. You get a message when a transaction is created. I'm confused > about the final line though. Does this move the creation announcement > forward by x days, or is this an additional reminder that occurs in > advance of creating the transaction. Also is this number of days > calculated from the date of the transaction, or the date that the > transaction will be created. For example, if I have a transaction to be > created on December 1st, marked as create 7 days in advance and a > reminder 10 days in advance, when does the reminder occur? November > 14th (ten days before the transaction is created) or 21st (den days > before the transaction is dated). As per coordination in #gnucash, I've already made these changes, but FTR I'll reply here... "Create automatically" conditionalizes only "notify when (automatically) created" -- if it's not being created automatically you'll be notified by definition in the SX-SLR dialog. The options code-named "notify_days" is really "remind_days"; I've renamed them in the schema and code appropriately to forestall future confusion with the other unrelated "notify [when auto-created]" option. The spinbuttons in this preference dialog behave *slightly* differently than in the editor; in the preferences, "0" is a magic value meaning "don't check the create-/remind-in-advance option *and* make the value 0."; as a corollary: non-zero in the preferences means "check the option and set the spinbutton to be this non-zero value." Thinking about it now, there's no real reason for the editor to have both a checkbox and a spinbutton: 0 can be a sentinel value there too... maybe I'll file an RFE for that later. I don't recall if the create-in-advance and remind-in-advance are cumulative, but they should be, of course. Otherwise, you can end up in a weird state. ...jsled -- http://asynchronous.org/ - `a=jsled; b=asynchronous.org; echo [EMAIL PROTECTED] ___ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel
Re: G2 Testing - Scheduled Transactions/Register
On Thursday 27 October 2005 5:54 pm, someone claiming to be David Hampton wrote: > On Thu, 2005-10-27 at 13:30 -0400, Josh Sled wrote: > > On Thu, Oct 27, 2005 at 12:04:51PM -0400, Tim Wunder wrote: > > | In a related issue: > > | It would seem to be a good idea to have the preferences dialog mirror > > | the SX creation Options section. > > > > True, and that makes sense; I'll need to talk to hampton to see if this > > is readily possible, but I don't see why it wouldn't be. FTR, however, > > there are certainly issues I consider higher severity w.r.t. 2.0. > > Josh, > > I think my misunderstanding of the sx settings when I created the > preferences may be contributing to the problem. Can you clarify for me > whether my current understanding is correct. (Line numbers refer to the > sxed dialog options settings in Tim's picture.) > > The "create automatically" seems to be a master setting. If clear, all > the other settings are ignored. If checked, then transactions will be > created on the date of the transaction. No, create automatically means it gets created without any intervention from the user, whenever the Since Last Run dialog is run to completion within the time frame of to . I use create automatically for payday transactions that don't change week to week. > If the checkbox in line three > is selected, then transactions will not be created on the actual date of > the transaction, but will be created x days early. SX's that are not created automatically are editable from within the Since Last Run dialog (SLRD). If SLRD is run within to , then the transaction is presented to the user for edit/creation. If SLRD is run within and , a reminder is presented, from which it can be selected for creation. > If transactions are > being created automatically, the "notify me when created" checkbox seems > obvious. You get a message when a transaction is created. I'm confused > about the final line though. Does this move the creation announcement > forward by x days, or is this an additional reminder that occurs in > advance of creating the transaction. Also is this number of days > calculated from the date of the transaction, or the date that the > transaction will be created. For example, if I have a transaction to be > created on December 1st, marked as create 7 days in advance and a > reminder 10 days in advance, when does the reminder occur? November > 14th (ten days before the transaction is created) or 21st (den days > before the transaction is dated). > > If you want, I can create some screenies of the whole process (I use SX's extensivley) and post them for your review. (but not tonight -- well, maybe much later tonight...) Tim -- Fedora Core release 4 (Stentz), Linux 2.6.13-1.1532_FC4 KDE: 3.4.3-1.0.fc4.kde, xorg-x11-6.8.2-37.FC4.49.2 18:20:06 up 1 day, 19:51, 4 users, load average: 0.30, 0.32, 0.46 MP3/OGG archive Total playlength : 7 days, 10 hours, 31 mins 30 seconds "It's what you learn after you know it all that counts" John Wooden pgpaJZGgoNdpr.pgp Description: PGP signature ___ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel
Re: G2 Testing - Scheduled Transactions/Register
On Thu, 2005-10-27 at 13:30 -0400, Josh Sled wrote: > On Thu, Oct 27, 2005 at 12:04:51PM -0400, Tim Wunder wrote: > | In a related issue: > | It would seem to be a good idea to have the preferences dialog mirror the > SX > | creation Options section. > > True, and that makes sense; I'll need to talk to hampton to see if this > is readily possible, but I don't see why it wouldn't be. FTR, however, > there are certainly issues I consider higher severity w.r.t. 2.0. Josh, I think my misunderstanding of the sx settings when I created the preferences may be contributing to the problem. Can you clarify for me whether my current understanding is correct. (Line numbers refer to the sxed dialog options settings in Tim's picture.) The "create automatically" seems to be a master setting. If clear, all the other settings are ignored. If checked, then transactions will be created on the date of the transaction. If the checkbox in line three is selected, then transactions will not be created on the actual date of the transaction, but will be created x days early. If transactions are being created automatically, the "notify me when created" checkbox seems obvious. You get a message when a transaction is created. I'm confused about the final line though. Does this move the creation announcement forward by x days, or is this an additional reminder that occurs in advance of creating the transaction. Also is this number of days calculated from the date of the transaction, or the date that the transaction will be created. For example, if I have a transaction to be created on December 1st, marked as create 7 days in advance and a reminder 10 days in advance, when does the reminder occur? November 14th (ten days before the transaction is created) or 21st (den days before the transaction is dated). Thanks. David ___ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel
Re: G2 Testing - Scheduled Transactions/Register
On Thu, 2005-10-27 at 13:30 -0400, Josh Sled wrote: > On Thu, Oct 27, 2005 at 12:04:51PM -0400, Tim Wunder wrote: > | It would seem to be a good idea to have the preferences dialog mirror the > SX > | creation Options section. > > True, and that makes sense; I'll need to talk to hampton to see if this > is readily possible, but I don't see why it wouldn't be. Shouldn't be any problem. The preference definition is just a glade file with callbacks to enable/disable the "days in advance" boxes. Just make sure the widget names don't get changed since that's what keys the infrastructure to update gconf. David ___ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel
Re: G2 Testing - Scheduled Transactions/Register
On Thursday 27 October 2005 12:04 pm, someone claiming to be Tim Wunder wrote: > See screenshot http://www.thewunders.org/files/pics/SX-prefs.jpg > Link shoulda been: http://www.thewunders.org:9000/files/pics/SX-prefs.jpg -- Fedora Core release 4 (Stentz), Linux 2.6.13-1.1532_FC4 KDE: 3.4.3-1.0.fc4.kde, xorg-x11-6.8.2-37.FC4.49.2 13:30:01 up 1 day, 15:01, 3 users, load average: 0.15, 0.09, 0.08 MP3/OGG archive Total playlength : 7 days, 10 hours, 31 mins 30 seconds "It's what you learn after you know it all that counts" John Wooden pgpGR3uEc9kj5.pgp Description: PGP signature ___ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel
Re: G2 Testing - Scheduled Transactions/Register
On Thu, Oct 27, 2005 at 12:04:51PM -0400, Tim Wunder wrote: | In a related issue: | It would seem to be a good idea to have the preferences dialog mirror the SX | creation Options section. True, and that makes sense; I'll need to talk to hampton to see if this is readily possible, but I don't see why it wouldn't be. FTR, however, there are certainly issues I consider higher severity w.r.t. 2.0. Thanks. :) ...jsled -- http://asynchronous.org/jsled/ | a=jsled; b=asynchronous.org; echo [EMAIL PROTECTED] ___ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel
Re: G2 Testing - Scheduled Transactions/Register
On Tuesday 25 October 2005 10:35 pm, someone claiming to be Volker Englisch wrote: > I did some more testing with SX: > > - Creating a new SX >It appears that the values for the "Days in Advance" for a new SX are >being populated from the defaults listed in the preferences for >'Scheduled Transactions' even when the preferences are unchecked. > >Set the values in the preferences to anything other then '0', then >uncheck the options. >Now create a new SX. The values from the preferences are being used >_and_ the options are checked by default. > In a related issue: It would seem to be a good idea to have the preferences dialog mirror the SX creation Options section. See screenshot http://www.thewunders.org/files/pics/SX-prefs.jpg There should be a preference for automatically creating the transaction, and separate preferences for days in advance to create a transaction, and days in advance to remind about a transaction. So the SX preferences screen should look something like: Since Last Run dialog: [ ] Run when data file opened Transaction editor defaults: [ ] Create automatically [ ] Notify me when created (inactive if Create automaticallly is unchecked) [ ] Create [] days in advance [ ] Remind [] days in advance Regards, Tim -- Fedora Core release 4 (Stentz), Linux 2.6.13-1.1532_FC4 KDE: 3.4.3-1.0.fc4.kde, xorg-x11-6.8.2-37.FC4.49.2 11:00:06 up 1 day, 12:31, 3 users, load average: 1.22, 0.41, 0.19 MP3/OGG archive Total playlength : 7 days, 10 hours, 31 mins 30 seconds "It's what you learn after you know it all that counts" John Wooden pgpltxEKeh2z2.pgp Description: PGP signature ___ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel
Re: G2 Testing - Scheduled Transactions/Register
> If you're going to continue testing I'd suggest picking another > subsystem, That's the plan. I'm good at breaking stuff. :-) Please feel free to comment if my explanation is not clear, when I need to be more specific or when a screen shot is needed. Thanks Volker Englisch mailto:[EMAIL PROTECTED](h) ___ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel
Re: G2 Testing - Scheduled Transactions/Register
Volker, This is fantastic! In-depth testing and reporting like this is invaluable. Thank you! I think you've given us a lot to work on here with SX. If you're going to continue testing I'd suggest picking another subsystem, like maybe graphing, or maybe just the register. (or soon hopefully, budgetting.) -chris On Tue, Oct 25, 2005 at 10:35:02PM -0400, Volker Englisch wrote: > I did some more testing with SX: > > - Creating a new SX > It appears that the values for the "Days in Advance" for a new SX are > being populated from the defaults listed in the preferences for > 'Scheduled Transactions' even when the preferences are unchecked. > > Set the values in the preferences to anything other then '0', then > uncheck the options. > Now create a new SX. The values from the preferences are being used > _and_ the options are checked by default. > > - Creating a new SX > I'm setting the frequency of the transaction and the start date. After > this I want to specify the transaction and click anywhere in the > transaction template. > This causes the start date and the displayed calendar view to change > to 2004-01-01. > > - Saving a new SX crashes GC. The message > unknown, but with movement > is displayed 50 times on the console. > (I had this come up twice but can't recreate it right now) > I am, however, able to save a new SX if I don't enter anything in the > transaction template. > > - Running the 'Since Last Run' I have a single transaction with status > Ready to create > The information for the split for this SX is not displayed in the > Transaction Template. When I click on the transaction to display > the split, GC crashes. > However, if I click the forward button, the 'Transaction Review' > window appears and the program runs into a loop and the window size > increases. The bottom of the window moves towards the bottom of the > screen and the window needs to be canceled. The transaction is > applied, though. > > - Display of upcoming transactions > When displaying the upcoming transactions by means of clicking in > the calendar and hovering over the calendar dates, the small window > first gets created in the upper left corner of the screen displaying > the correct information in regards to the mouse position. > As soon as the mouse gets moved, though, the small window follows the > mouse pointer. > The width of the window isn't changing with the dates and appears to > always be the largest window size displayed so far during the current > GC session. > > - Register (SX transaction template) > (I think these are problems with the register and not the SX) > When entering the transaction in the template the pointer is not > visible when I move from one field to the next using the TAB key > or using a mouse click. The pointer becomes visible when I start > typing or when I click in the field a second time. > > - Register (SX transaction template) > When entering the account like this > ex:u: > to jump to > Expenses:Utilities > and then open the account list manually (GC1.8 opens the account list > automatically) I should be able to see the accounts under Utilities. > However, the account list does not display with the > Expenses:Utilities account in view. Instead, the list displayed is > the top of the accounts list. > > - Register (SX transaction template) > Entering a value (e.g. '20.00') without entering an account or a memo > for the first split causes everything else entered so far to be reset > when tabbing to the second split. > > -- > Thanks > > Volker Englisch > > mailto:[EMAIL PROTECTED](h) > ___ > gnucash-devel mailing list > gnucash-devel@gnucash.org > https://lists.gnucash.org/mailman/listinfo/gnucash-devel ___ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel
G2 Testing - Scheduled Transactions/Register
I did some more testing with SX: - Creating a new SX It appears that the values for the "Days in Advance" for a new SX are being populated from the defaults listed in the preferences for 'Scheduled Transactions' even when the preferences are unchecked. Set the values in the preferences to anything other then '0', then uncheck the options. Now create a new SX. The values from the preferences are being used _and_ the options are checked by default. - Creating a new SX I'm setting the frequency of the transaction and the start date. After this I want to specify the transaction and click anywhere in the transaction template. This causes the start date and the displayed calendar view to change to 2004-01-01. - Saving a new SX crashes GC. The message unknown, but with movement is displayed 50 times on the console. (I had this come up twice but can't recreate it right now) I am, however, able to save a new SX if I don't enter anything in the transaction template. - Running the 'Since Last Run' I have a single transaction with status Ready to create The information for the split for this SX is not displayed in the Transaction Template. When I click on the transaction to display the split, GC crashes. However, if I click the forward button, the 'Transaction Review' window appears and the program runs into a loop and the window size increases. The bottom of the window moves towards the bottom of the screen and the window needs to be canceled. The transaction is applied, though. - Display of upcoming transactions When displaying the upcoming transactions by means of clicking in the calendar and hovering over the calendar dates, the small window first gets created in the upper left corner of the screen displaying the correct information in regards to the mouse position. As soon as the mouse gets moved, though, the small window follows the mouse pointer. The width of the window isn't changing with the dates and appears to always be the largest window size displayed so far during the current GC session. - Register (SX transaction template) (I think these are problems with the register and not the SX) When entering the transaction in the template the pointer is not visible when I move from one field to the next using the TAB key or using a mouse click. The pointer becomes visible when I start typing or when I click in the field a second time. - Register (SX transaction template) When entering the account like this ex:u: to jump to Expenses:Utilities and then open the account list manually (GC1.8 opens the account list automatically) I should be able to see the accounts under Utilities. However, the account list does not display with the Expenses:Utilities account in view. Instead, the list displayed is the top of the accounts list. - Register (SX transaction template) Entering a value (e.g. '20.00') without entering an account or a memo for the first split causes everything else entered so far to be reset when tabbing to the second split. -- Thanks Volker Englisch mailto:[EMAIL PROTECTED](h) ___ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel