Re: Time for 2.5.1
Robert Fewell 14ubo...@gmail.com writes: Mike, Yes that was correct, I have had a rethink and made some changes which are in bug 700125 to allow the update on the sub account view. It is dependent on the account selected, if it is a place holder or a placeholder some where below it it will be read only. Also, as I am requiring default account splits in all registers apart from the general ledger, you will only be able to add transactions for the account you selected but I see no issue with that. IMHO the Open Subaccounts should not be read only unless *EVERY* account/subaccount is read-only. When you Open Subaccounts it should act just like the GL in terms of entering transactions, except it's only showing the subset of transactions from the opened set of accounts. The Placeholder bit should only prevent you from selecting that account for a transaction Split, but you shouldn't be limited in the accounts you can select. IMHO when you open subaccounts there does not need to be a default account when you create a new account. I think it's okay to require the user to choose both the credit and debit accounts. And indeed I dont think you should be able to have a basic or event auto split ledger mode in an Open Subaccounts view. -derek -- Derek Atkins, SB '93 MIT EE, SM '95 MIT Media Laboratory Member, MIT Student Information Processing Board (SIPB) URL: http://web.mit.edu/warlord/PP-ASEL-IA N1NWH warl...@mit.eduPGP key available ___ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel
Time for 2.5.1
Mike, Yes that was correct, I have had a rethink and made some changes which are in bug 700125 to allow the update on the sub account view. It is dependent on the account selected, if it is a place holder or a placeholder some where below it it will be read only. Also, as I am requiring default account splits in all registers apart from the general ledger, you will only be able to add transactions for the account you selected but I see no issue with that. What did work, was very limited, any thing to do with the transaction worked but on the splits it would crash. At the moment, they are only there when the general ledger profile is used which as you have seen is for the General Ledger View and certain Sub Account Views. This is the same as existing but it is more visible. The General Ledger is the only view that has the ability to hide the extra columns which are all read only. What columns are visible and the ability to hide them can easily be changed bearing in mind that the profile may be shared across different registers, this can be seen in gnc-tree-view-split-register.c starting at line 671. To resize the columns, you should be able to just double click on the vertical border. This relies on the under lying GktTreeView but will be influenced by the title length and the sort arrow so you may not be able to get them as small as before. Regards, Robert ___ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel
Re: Time for 2.5.1
OK, I've played with this some more and have a few comments. See below. --On May 11, 2013 6:04:52 PM +0100 Robert Fewell 14ubo...@gmail.com wrote: Mike, Yes that was correct, I have had a rethink and made some changes which are in bug 700125 to allow the update on the sub account view. It is dependent on the account selected, if it is a place holder or a placeholder some where below it it will be read only. Also, as I am requiring default account splits in all registers apart from the general ledger, you will only be able to add transactions for the account you selected but I see no issue with that. What did work, was very limited, any thing to do with the transaction worked but on the splits it would crash. At the moment, they are only there when the general ledger profile is used which as you have seen is for the General Ledger View and certain Sub Account Views. This is the same as existing but it is more visible. The General Ledger is the only view that has the ability to hide the extra columns which are all read only. What columns are visible and the ability to hide them can easily be changed bearing in mind that the profile may be shared across different registers, this can be seen in gnc-tree-view-split-register.c starting at line 671. I'm not sure I understand this, but I'll let it go for now. I would really like for these fields to be optionally visible and editable, but there are more important issues. To resize the columns, you should be able to just double click on the vertical border. This relies on the under lying GktTreeView but will be influenced by the title length and the sort arrow so you may not be able to get them as small as before. This sort of works, but only considers the contents of the transaction lines, not the split lines if any transaction is expanded. That makes it much less useful. I also can't get it to work consistently. It seems to sometimes ignore the double click. I tried opening a register for a stock account and entering a new buy transaction. Perhaps I just haven't figured out the correct work-flow yet, but this seems a lot less convenient than the old register. Here are some random thoughts related to this. The arrow keys don't seem to work right. In the old register you can use up and down arrow to move among the lines in a transaction. Now they seem to move to another split (if the transaction is expanded) but nothing is editable. The tab key still works, but only left and right, of course. When I enter an amount and price and then tab out of the price column, it immediately prompts me to recalculate something. In the old register this only happens if I tab out of the Debit or Credit column with inconsistent values. This means I have to switch to the mouse to make this dialog go away (or use a number of inconvenient key strokes) since the default (to recalculate the price I just entered based on the value I haven't entered yet) doesn't make any sense. Autofilling accounts in a split seems less convenient. If you type part of an account name at a given level and hit colon, it autofiles the selected account (which is what I want). However if you type all of a name at a given level and hit colon, it autofills the next level (which is not what I want). It also doesn't seem to be possible to autofill the lowest level account name without using the mouse or arrow keys. For example suppose I have an account abc:def:ghi. If I type ab: it fills abc: and lets me select the next level. If I type abc: it fills abc:def: (assuming def is the first subaccount) and lets me select the third level. If I type abc:def:g there seems to be an easy way to get it to autofill abc:def:ghi. Typing abc:def:g: asks to create an account called abc:def:ghi:. In the old register typing abc:def:g followed by tab autofills abc:def:ghi. Now it asks me to create an account called abc:def:g. Sort of related to this, if I type a bogus account name in a split and then hit the Cancel button to clear out the transaction and start over it asks me to create the account. It shouldn't do that if I'm canceling. Once I've filled the splits in a transaction, I can't enter it using the return or enter keys. Both seem to just open or close the field the cursor is in. Tabbing out of the last field seems to enter it, but this is quite different from before and will likely cause many incorrect transactions to be entered. In the old register I don't think tab ever causes a new transaction to be entered. That's probably enough for now. This does seem to be working reliably and will be fine when some of the rough edges are cleaned off. Mike ___ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel
Re: Time for 2.5.1
On Monday 06 May 2013 08:32:02 David Carlson wrote: On 5/5/2013 3:25 AM, Robert Fewell wrote: Alex, There is only one header row but the titles change depending on which row you are on in the register. This is deliberate to utilises the sort model. I did not think it was necessary to have the extra number on the transaction row, just looked a bit cluttered so have left it out. If you think it is required, then raise a bug and I will add it back. What you have at the moment is my interpretation of the existing register with some subtle changes like you have mentioned but should be close to the existing unless I have made a hash of it. As you say, I think if there is some thing to discuss, get opinions on, then it would be easier on the list and then raise a bug for that item. If there is some thing plain wrong, then raise a bug would be best. Thank you for trying it, Robert. ___ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel I have downloaded 2.5.1 for Windows and so far I think it will be a winner. I do have a couple of comments. Hi David, First of all, thank you for all your testing and feedback. I think that the look and feel of the new register should be visibly different from the old register. I was slightly disappointed when it looked almost the same as before, particularly in bank account and credit card account registers. Why do you want the new register to be visibly different ? Geert ___ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel
Re: Time for 2.5.1
On 5/10/2013 3:31 AM, Geert Janssens wrote: On Monday 06 May 2013 08:32:02 David Carlson wrote: On 5/5/2013 3:25 AM, Robert Fewell wrote: Alex, There is only one header row but the titles change depending on which row you are on in the register. This is deliberate to utilises the sort model. I did not think it was necessary to have the extra number on the transaction row, just looked a bit cluttered so have left it out. If you think it is required, then raise a bug and I will add it back. What you have at the moment is my interpretation of the existing register with some subtle changes like you have mentioned but should be close to the existing unless I have made a hash of it. As you say, I think if there is some thing to discuss, get opinions on, then it would be easier on the list and then raise a bug for that item. If there is some thing plain wrong, then raise a bug would be best. Thank you for trying it, Robert. ___ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel I have downloaded 2.5.1 for Windows and so far I think it will be a winner. I do have a couple of comments. Hi David, First of all, thank you for all your testing and feedback. I think that the look and feel of the new register should be visibly different from the old register. I was slightly disappointed when it looked almost the same as before, particularly in bank account and credit card account registers. Why do you want the new register to be visibly different ? Geert Well, to start off, so that I can tell while testing that I am actually looking at a register2 view, not an old view. I have already mistakenly thought that I was looking at a new register and complained that certain issues had not been fixed, when they actually had been fixed (Thanks, Robert for correcting me). The next reason is that the new view does fix several subtle problems and add some new capabilities. A very important one is that it will actually make GnuCash much easier for newbies to learn and use. This should keep many of the potential users that try GnuCash then give up because they believe that it is not user friendly. You can surely think of other reasons, but I will close with the very standard marketing tactic - New Look! You must have this baby in your garage Greatest invention since sliced bread!!! ;) David C 0xDC7C8BF3.asc Description: application/pgp-keys ___ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel
Re: Time for 2.5.1
On Friday 10 May 2013 07:04:23 David Carlson wrote: On 5/10/2013 3:31 AM, Geert Janssens wrote: Why do you want the new register to bevisibly different ? Geert Well, to start off, so that I can tell while testing that I am actually looking at a register2 view, not an old view. I havealready mistakenly thought that I was looking at a new register andcomplained that certain issues had not been fixed, when theyactually had been fixed (Thanks, Robert for correcting me). That may be useful for testing, but not a valid reason to have a different look in production. The next reason is that the new view does fix several subtleproblems and add some new capabilities. A very important one is that it will actually make GnuCash much easier for newbies to learn and use. This should keep many of the potential users that try GnuCash then give up because they believethat it is not user friendly. I'm not sure which *visual* differences you are referring to that make GnuCash easier for newbies to learn. Note that I don't oppose any improvements, but in the current stage of the new register project I consider the most important thing worry about now is to not have any *regressions* compared to the rich feature set of the old register. It may have had its quirks, but don't underestimate how carefully tuned it was for its task. You can surely think of other reasons, but I will close with thevery standard marketing tactic - New Look! You must have thisbaby in your garage Greatest invention since sliced bread!!! ;) ;) More seriously, I don't think this kind of marketing stragegy matches the average GnuCash user. If the marketing message would have been Even easier/user-friendlier/more efficient than before, finally fixes most of the quirks in the old program for good that might help. I'd expect users of accounting software to prefer a stable/reliable system which they know how it works. Changing the looks too much could actually work backwards on such an audience. Geert ___ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel
Re: Time for 2.5.1
On 5/10/2013 7:48 AM, Geert Janssens wrote: On Friday 10 May 2013 07:04:23 David Carlson wrote: On 5/10/2013 3:31 AM, Geert Janssens wrote: Why do you want the new register to bevisibly different ? Geert Well, to start off, so that I can tell while testing that I am actually looking at a register2 view, not an old view. I havealready mistakenly thought that I was looking at a new register andcomplained that certain issues had not been fixed, when theyactually had been fixed (Thanks, Robert for correcting me). That may be useful for testing, but not a valid reason to have a different look in production. The next reason is that the new view does fix several subtleproblems and add some new capabilities. A very important one is that it will actually make GnuCash much easier for newbies to learn and use. This should keep many of the potential users that try GnuCash then give up because they believethat it is not user friendly. I'm not sure which *visual* differences you are referring to that make GnuCash easier for newbies to learn. Note that I don't oppose any improvements, but in the current stage of the new register project I consider the most important thing worry about now is to not have any *regressions* compared to the rich feature set of the old register. It may have had its quirks, but don't underestimate how carefully tuned it was for its task. You can surely think of other reasons, but I will close with thevery standard marketing tactic - New Look! You must have thisbaby in your garage Greatest invention since sliced bread!!! ;) ;) More seriously, I don't think this kind of marketing stragegy matches the average GnuCash user. If the marketing message would have been Even easier/user-friendlier/more efficient than before, finally fixes most of the quirks in the old program for good that might help. I'd expect users of accounting software to prefer a stable/reliable system which they know how it works. Changing the looks too much could actually work backwards on such an audience. Geert I certainly agree with your point about not regressing and losing any of the existing functionality of the old register view. That is critically important. However, if you sauntered over to your local automobile dealership and saw that the new models looked exactly like the 20 year old models, how could you tell that there was something entirely different under the skin that made them far better and more desirable than the old models. A modest visual change can and often does symbolize improvements that are not visible. I am not referring to Windows 8. As far as user friendliness is concerned, every new user has to struggle with learning how to enter their first few transactions. That puts off a lot of new users. Anything to ease that hurdle would be very welcome. GnuCash is not easy to jump into like Quicken used to be before it got bloated. Maybe if the program were shipped with an example file pre-filled with a few example transactions, that might help too. Or maybe if there were several example files for specific types of transactions available from the FAQ page of the website. Just a thought. David C 0xDC7C8BF3.asc Description: application/pgp-keys ___ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel
Time for 2.5.1
David, Not sure about the schedule problem you have, I have tried it on my XP VM and I am unable to reproduce but will try different options. The opening of an account in the sub-account view should be read only and I have fixed this locally and will upload the patch along with some other changes at the weekend. Once in the schedule Transaction editor, the default options are to open with the old register, you need to have the required schedule highlighted and then use the 'scheduled' menu option at the top which then has 'new 2' and 'edit 2' for the new view. In Basic view, is just like the existing, click on the split button on the tool bar which expand the transaction. Regards, Robert ___ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel
Re: Time for 2.5.1
On 5/9/2013 8:53 AM, Robert Fewell wrote: David, Not sure about the schedule problem you have, I have tried it on my XP VM and I am unable to reproduce but will try different options. The opening of an account in the sub-account view should be read only and I have fixed this locally and will upload the patch along with some other changes at the weekend. Once in the schedule Transaction editor, the default options are to open with the old register, you need to have the required schedule highlighted and then use the 'scheduled' menu option at the top which then has 'new 2' and 'edit 2' for the new view. In Basic view, is just like the existing, click on the split button on the tool bar which expand the transaction. Regards, Robert ___ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel The scheduler is not the only place that the local time vs universal time issue has appeared recently, but I don't want report the other cases unless I can reproduce them. I happened to find it because it was the critical time of day when I tried the SX features. I think that it may also be in certain reports. In any case, I understand that it must either be tested in certain time windows or by using an environment where the clock and local time zone can be easily manipulated. I am sure that most of the register window conflicts between old and new will automatically disappear when old ceases to exist, so I don't expect very many of them to actually be fixed in this testing period. I am trying to help make this testing period short. Regarding use of the SX editor, I did not see the items that you are describing when I was using 2.5.1, highlighting a register transaction in the register2 view and using the right-click drop-down list schedule.. link to open the SX that the register transaction had been created from. Where is the required schedule that I need to highlight? Where is it if I am in the list of scheduled transactions? You can tell that I do not use 'Basic View'. For some reason I did not see the 'Split' icon on the menu-bar when I had release 2.5.1 loaded. I will check next time. That is how I got my flat forehead. There was some issue with reports that use charts not working in release 2.5.1. When I get a better handle on that I will probably be filing another bug report. David C 0xDC7C8BF3.asc Description: application/pgp-keys ___ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel
Re: Time for 2.5.1
On 5/9/2013 12:12 PM, David Carlson wrote: On 5/9/2013 8:53 AM, Robert Fewell wrote: David, Not sure about the schedule problem you have, I have tried it on my XP VM and I am unable to reproduce but will try different options. The opening of an account in the sub-account view should be read only and I have fixed this locally and will upload the patch along with some other changes at the weekend. Once in the schedule Transaction editor, the default options are to open with the old register, you need to have the required schedule highlighted and then use the 'scheduled' menu option at the top which then has 'new 2' and 'edit 2' for the new view. In Basic view, is just like the existing, click on the split button on the tool bar which expand the transaction. Regards, Robert ___ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel The scheduler is not the only place that the local time vs universal time issue has appeared recently, but I don't want report the other cases unless I can reproduce them. I happened to find it because it was the critical time of day when I tried the SX features. I think that it may also be in certain reports. In any case, I understand that it must either be tested in certain time windows or by using an environment where the clock and local time zone can be easily manipulated. I am sure that most of the register window conflicts between old and new will automatically disappear when old ceases to exist, so I don't expect very many of them to actually be fixed in this testing period. I am trying to help make this testing period short. Regarding use of the SX editor, I did not see the items that you are describing when I was using 2.5.1, highlighting a register transaction in the register2 view and using the right-click drop-down list schedule.. link to open the SX that the register transaction had been created from. Where is the required schedule that I need to highlight? Where is it if I am in the list of scheduled transactions? You can tell that I do not use 'Basic View'. For some reason I did not see the 'Split' icon on the menu-bar when I had release 2.5.1 loaded. I will check next time. That is how I got my flat forehead. ;) There was some issue with reports that use charts not working in release 2.5.1. When I get a better handle on that I will probably be filing another bug report. David C ___ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel 0xDC7C8BF3.asc Description: application/pgp-keys ___ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel
Re: Time for 2.5.1
--On May 9, 2013 2:53:50 PM +0100 Robert Fewell 14ubo...@gmail.com wrote: The opening of an account in the sub-account view should be read only and I have fixed this locally and will upload the patch along with some other changes at the weekend. I'm not sure I understand. Do you mean that if you open an account and all of its sub accounts then you can't edit any of the transactions? This certainly isn't true in the old register and it doesn't seem to be true in the new one either. I just tried an experiment where I opened sub accounts in the new register, edited a transaction, then closed the register and reopened it with the old register view. The change I made was there. It would be a step backward if you couldn't edit accounts in the subaccount view. Under what circumstances to you show the Value, Rate and Amount fields? I see that they are there in the subaccount view, but not if a single account is opened. I thought part of the plan was to make it possible to see these fields, at least optionally, in any register. This would make it easier to enter transactions involving multiple currencies. Is there any way to easily resize a column to be just wide enough to contain the data in it? In the old register double clicking the header does this. I understand that this would be harder to do in the new version, but is there any other way? Mike ___ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel
Re: Time for 2.5.1
On 5/9/2013 2:25 PM, Mike Alexander wrote: --On May 9, 2013 2:53:50 PM +0100 Robert Fewell 14ubo...@gmail.com wrote: The opening of an account in the sub-account view should be read only and I have fixed this locally and will upload the patch along with some other changes at the weekend. I'm not sure I understand. Do you mean that if you open an account and all of its sub accounts then you can't edit any of the transactions? This certainly isn't true in the old register and it doesn't seem to be true in the new one either. I just tried an experiment where I opened sub accounts in the new register, edited a transaction, then closed the register and reopened it with the old register view. The change I made was there. It would be a step backward if you couldn't edit accounts in the subaccount view. Under what circumstances to you show the Value, Rate and Amount fields? I see that they are there in the subaccount view, but not if a single account is opened. I thought part of the plan was to make it possible to see these fields, at least optionally, in any register. This would make it easier to enter transactions involving multiple currencies. Is there any way to easily resize a column to be just wide enough to contain the data in it? In the old register double clicking the header does this. I understand that this would be harder to do in the new version, but is there any other way? Mike ___ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel Hi Mike, it's about time another guest showed up to this party. :) David C 0xDC7C8BF3.asc Description: application/pgp-keys ___ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel
Re: Time for 2.5.1
On 5/6/2013 8:32 AM, David Carlson wrote: On 5/5/2013 3:25 AM, Robert Fewell wrote: Alex, There is only one header row but the titles change depending on which row you are on in the register. This is deliberate to utilises the sort model. I did not think it was necessary to have the extra number on the transaction row, just looked a bit cluttered so have left it out. If you think it is required, then raise a bug and I will add it back. What you have at the moment is my interpretation of the existing register with some subtle changes like you have mentioned but should be close to the existing unless I have made a hash of it. As you say, I think if there is some thing to discuss, get opinions on, then it would be easier on the list and then raise a bug for that item. If there is some thing plain wrong, then raise a bug would be best. Thank you for trying it, Robert. ___ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel I have downloaded 2.5.1 for Windows and so far I think it will be a winner. I do have a couple of comments. I think that the look and feel of the new register should be visibly different from the old register. I was slightly disappointed when it looked almost the same as before, particularly in bank account and credit card account registers. Your use of the vertical blue line in future transactions in certain types of registers is one example of something that I really like. Maybe one could argue that it should be in the left hand or right hand border, but I think it really should be there in all registers. In previous versions I used to be frustrated sometimes when editing some multi-line split transactions if a mouse click on a line near the one that had the current focus moved the entire transaction on the screen but it did not put the target field under the mouse pointer with the new focus in the desired field where I had clicked. Then the next keystroke would end up in the wrong field. So far I have not found that here. I will go back to the old version to see if I can find specific examples to test. That is my first 5 minutes of testing this version. David C ___ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel In further testing I found and reported via bug 699790 my findings regarding anomalous behavior under certain circumstances when editing multi-line split transactions. Additionally, I have experienced crashes when attempting to edit scheduled transactions and transactions in the account plus sub-accounts view, which I believe are known issues. The progress to date on this release is very nice to see. I want to see more. David C 0xDC7C8BF3.asc Description: application/pgp-keys ___ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel
Time for 2.5.1
David, Thank you for testing, I am a little confused by your last update. As I have pointed out on the bug mentioned, I am only interested in the new registers which all have the vertical status line and the columns can be moved so you can move it at your pleasure. Sub account registers do not allow changes, the status line is all red so find it perplexing that you are trying to edit one ! In the Schedule editor, the default behaviour is to use the old style register view so to use the new style you need to use the menu option 'scheduled-New2 and Edit2' which also have the vertical status column. This may change in the next release. What problems are you having ? Regards, Robert ___ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel
Re: Time for 2.5.1
On 5/8/2013 10:07 AM, Robert Fewell wrote: David, Thank you for testing, I am a little confused by your last update. As I have pointed out on the bug mentioned, I am only interested in the new registers which all have the vertical status line and the columns can be moved so you can move it at your pleasure. Sub account registers do not allow changes, the status line is all red so find it perplexing that you are trying to edit one ! In the Schedule editor, the default behaviour is to use the old style register view so to use the new style you need to use the menu option 'scheduled-New2 and Edit2' which also have the vertical status column. This may change in the next release. What problems are you having ? Regards, Robert ___ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel I am confused too. Using GnuCash 2.5.1 I opened a file that I have been editing forever with older versions of Gnucash. That file has many register windows left open from previous use. In retrospect I was confused by thinking that all those windows were in the new register view because I no longer saw any option to open then in the new register2 view but there was an option to open in the old view. (When I mention the old behavior my intent is simply to use it as a reference for comparison.) Then, there was a search window created by the since last run assistant, so from there I selected a transaction, right clicked and selected the Schedule option. This opened the scheduled transaction (I think) in the new view. When I tried to edit it GnuCash crashed. I restarted GnuCash, went to the chart of accounts, created a new sub-account of a fixed asset account. Then I opened the fixed asset account in the sub-account view(not Old Sub-account view). There were no red areas other than the highlighted field that alternates between blue and red background depending on whether I am actively editing to show the status of the highlight or focus, or whatever in this particular theme. It was possible to start an edit but again GnuCash crashed. If the vertical line was supposed to be red, it definitely was not. I thought that both of those incidents were artifacts of incomplete code updates to those types of registers in the new view, since this is a work in progress, so I only mentioned them in passing. Now I have re-installed 2.5.1 and re-opened that same file. I returned to the same asset account and re-opened it in the sub-account view. It does appear to be in the register2 view judging by the different titles. there is no red anywhere on the page other than a few negative numbers here and there. It appears that I can edit some fields if I left click on them, but I have not tried to commit an edit yet. Now in a register2 view of a credit card account transaction that has multiple split lines in that account, as you pointed out, the transaction does only appear once in the Auto-split view. However, if I right click on it and select the choice 'Schedule..' the scheduled transaction does open in the register2 view. There is no scheduled-new2 or edit2 option in the right click drop-down list. Attempting an edit again crashed Gnucash. I agree that we need to be on the same page so I am trying to describe my testing as completely as possible. Otherwise we are both spinning our wheels. Is this enough for now? David C 0xDC7C8BF3.asc Description: application/pgp-keys ___ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel
Re: Time for 2.5.1
On 5/8/2013 1:37 PM, David Carlson wrote: On 5/8/2013 10:07 AM, Robert Fewell wrote: David, Thank you for testing, I am a little confused by your last update. As I have pointed out on the bug mentioned, I am only interested in the new registers which all have the vertical status line and the columns can be moved so you can move it at your pleasure. Sub account registers do not allow changes, the status line is all red so find it perplexing that you are trying to edit one ! In the Schedule editor, the default behaviour is to use the old style register view so to use the new style you need to use the menu option 'scheduled-New2 and Edit2' which also have the vertical status column. This may change in the next release. What problems are you having ? Regards, Robert ___ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel I am confused too. Using GnuCash 2.5.1 I opened a file that I have been editing forever with older versions of Gnucash. That file has many register windows left open from previous use. In retrospect I was confused by thinking that all those windows were in the new register view because I no longer saw any option to open then in the new register2 view but there was an option to open in the old view. (When I mention the old behavior my intent is simply to use it as a reference for comparison.) Then, there was a search window created by the since last run assistant, so from there I selected a transaction, right clicked and selected the Schedule option. This opened the scheduled transaction (I think) in the new view. When I tried to edit it GnuCash crashed. I restarted GnuCash, went to the chart of accounts, created a new sub-account of a fixed asset account. Then I opened the fixed asset account in the sub-account view(not Old Sub-account view). There were no red areas other than the highlighted field that alternates between blue and red background depending on whether I am actively editing to show the status of the highlight or focus, or whatever in this particular theme. It was possible to start an edit but again GnuCash crashed. If the vertical line was supposed to be red, it definitely was not. I thought that both of those incidents were artifacts of incomplete code updates to those types of registers in the new view, since this is a work in progress, so I only mentioned them in passing. Now I have re-installed 2.5.1 and re-opened that same file. I returned to the same asset account and re-opened it in the sub-account view. It does appear to be in the register2 view judging by the different titles. there is no red anywhere on the page other than a few negative numbers here and there. It appears that I can edit some fields if I left click on them, but I have not tried to commit an edit yet. Now in a register2 view of a credit card account transaction that has multiple split lines in that account, as you pointed out, the transaction does only appear once in the Auto-split view. However, if I right click on it and select the choice 'Schedule..' the scheduled transaction does open in the register2 view. There is no scheduled-new2 or edit2 option in the right click drop-down list. Attempting an edit again crashed Gnucash. I agree that we need to be on the same page so I am trying to describe my testing as completely as possible. Otherwise we are both spinning our wheels. Is this enough for now? David C ___ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel Now I have another question. If I am in a register2 view and using basic ledger view, how do I edit a transaction? Specifically how do I edit a split transaction, but I also might want to edit a simple transaction. I have not found the secret. David C 0xDC7C8BF3.asc Description: application/pgp-keys ___ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel
Re: Time for 2.5.1
On 5/5/2013 3:25 AM, Robert Fewell wrote: Alex, There is only one header row but the titles change depending on which row you are on in the register. This is deliberate to utilises the sort model. I did not think it was necessary to have the extra number on the transaction row, just looked a bit cluttered so have left it out. If you think it is required, then raise a bug and I will add it back. What you have at the moment is my interpretation of the existing register with some subtle changes like you have mentioned but should be close to the existing unless I have made a hash of it. As you say, I think if there is some thing to discuss, get opinions on, then it would be easier on the list and then raise a bug for that item. If there is some thing plain wrong, then raise a bug would be best. Thank you for trying it, Robert. ___ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel I have downloaded 2.5.1 for Windows and so far I think it will be a winner. I do have a couple of comments. I think that the look and feel of the new register should be visibly different from the old register. I was slightly disappointed when it looked almost the same as before, particularly in bank account and credit card account registers. Your use of the vertical blue line in future transactions in certain types of registers is one example of something that I really like. Maybe one could argue that it should be in the left hand or right hand border, but I think it really should be there in all registers. In previous versions I used to be frustrated sometimes when editing some multi-line split transactions if a mouse click on a line near the one that had the current focus moved the entire transaction on the screen but it did not put the target field under the mouse pointer with the new focus in the desired field where I had clicked. Then the next keystroke would end up in the wrong field. So far I have not found that here. I will go back to the old version to see if I can find specific examples to test. That is my first 5 minutes of testing this version. David C 0xDC7C8BF3.asc Description: application/pgp-keys ___ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel
Re: Time for 2.5.1
Robert Fewell 14ubo...@gmail.com writes: At the moment it is just the Account registers that use the new interface, I am looking at changing the business options to use the same thing. Thanks! Robert -derek -- Derek Atkins, SB '93 MIT EE, SM '95 MIT Media Laboratory Member, MIT Student Information Processing Board (SIPB) URL: http://web.mit.edu/warlord/PP-ASEL-IA N1NWH warl...@mit.eduPGP key available ___ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel
Time for 2.5.1
Alex, There is only one header row but the titles change depending on which row you are on in the register. This is deliberate to utilises the sort model. I did not think it was necessary to have the extra number on the transaction row, just looked a bit cluttered so have left it out. If you think it is required, then raise a bug and I will add it back. What you have at the moment is my interpretation of the existing register with some subtle changes like you have mentioned but should be close to the existing unless I have made a hash of it. As you say, I think if there is some thing to discuss, get opinions on, then it would be easier on the list and then raise a bug for that item. If there is some thing plain wrong, then raise a bug would be best. Thank you for trying it, Robert. ___ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel
Re: Time for 2.5.1
On Friday 03 May 2013 19:37:02 Robert Fewell wrote: I have added a patch on bug 699614 which should change the defaults as requested. Regards, Robert. ___ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel I have applied it. Thank you. As far as I'm concerned we can now release 2.5.1. My GSettings work is not ready yet for inclusion. Geert ___ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel
Re: Time for 2.5.1
On May 4, 2013, at 12:53 AM, Geert Janssens janssens-ge...@telenet.be wrote: On Friday 03 May 2013 19:37:02 Robert Fewell wrote: I have added a patch on bug 699614 which should change the defaults as requested. Regards, Robert. ___ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel I have applied it. Thank you. As far as I'm concerned we can now release 2.5.1. My GSettings work is not ready yet for inclusion. Tagged and tarballs uploaded. Cross your fingers for a successful Windows build tomorrow. Regards, John Ralls ___ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel
Re: Time for 2.5.1
Robert, On Sat, May 4, 2013 at 1:34 AM, Robert Fewell 14ubo...@gmail.com wrote: From: Robert Fewell 14ubo...@gmail.com To: gnucash-devel@gnucash.org Cc: Date: Fri, 3 May 2013 19:37:02 +0100 Subject: Time for 2.5.1 I have added a patch on bug 699614 which should change the defaults as requested. Regards, Robert. I've built the version with your new register and have a few of questions: - In two line mode, yours only has one header line whereas the current gnucash register has two header lines in two line mode and one with one line mode; is this intentional in your design or have you just not yet implemented this functionality? - When a register item is selected with auto-split on, in the current register the debit or credit for the anchor-split is shown on the 'transaction-cursor' line as well as on the 'split-cursor' line, whereas in your new register it is not; is this also intentional in your design or something which you would intend to change if pointed out? - Generally, are you trying to have the general look-and-feel and detailed functionality be the same (but with a different underlying implementation) or are you intending to make any changes in these areas? The feedback you would expect from anyone would depend on this, I think. - How would you like feedback? Bugzilla items might be easier to track but the list would probably be better for general discussion, especially if you intend to change functionality. Perhaps list discussion for any intended changes and bugzilla items for specific items where a change is needed? Look forward to your, and other's, responses. Regards, Alex ___ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel
Re: Time for 2.5.1
On Thursday 02 May 2013 11:41:58 John Ralls wrote: It's a new month and time for a new release of the 2.5 series. I propose to tag on Saturday around noon PDT (1700Z). Is there anything that needs doing to get ready? In particular, is the Win32 build issue fixed? Regards, John Ralls The register 2 code has improved a lot since 2.5.0. So I asked Robert Fewel a few minutes ago to make the new register the default when opening an account. That will make it more prominently present for all potential testers. That would be a patch I'd like to see added for 2.5.1 still. I'll try to make some time to look at the Win32 build issues later today or tomorrow. Geert ___ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel
Re: Time for 2.5.1
On May 3, 2013, at 5:36 AM, Geert Janssens janssens-ge...@telenet.be wrote: On Thursday 02 May 2013 11:41:58 John Ralls wrote: It's a new month and time for a new release of the 2.5 series. I propose to tag on Saturday around noon PDT (1700Z). Is there anything that needs doing to get ready? In particular, is the Win32 build issue fixed? Regards, John Ralls The register 2 code has improved a lot since 2.5.0. So I asked Robert Fewel a few minutes ago to make the new register the default when opening an account. That will make it more prominently present for all potential testers. That would be a patch I'd like to see added for 2.5.1 still. OK ,if he can get it done quickly. Otherwise there's no harm in waiting a month. Actually, less than a month. I'm going on Vacation May 31, so I'm planning to release 2.5.3 the weekend before. I'll try to make some time to look at the Win32 build issues later today or tomorrow. Derek launched a trunk build yesterday and it completed and copied to Code, so maybe it will be OK. Your changes this morning were too late to trip a rebuild, so we'll have to see if it completes on its own tomorrow morning. Derek also set 2.4 back to building only weekly, so it shouldn't block anything until next Thursday. If you can figure out why the scp hangs after completing the transfer by then, that would be great. Regards, John Ralls ___ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel
Re: Time for 2.5.1
On Friday 03 May 2013 07:50:59 John Ralls wrote: Derek launched a trunk build yesterday and it completed and copied to Code, so maybe it will be OK. Your changes this morning were too late to trip a rebuild, so we'll have to see if it completes on its own tomorrow morning. Derek also set 2.4 back to building only weekly, so it shouldn't block anything until next Thursday. If you can figure out why the scp hangs after completing the transfer by then, that would be great. Regards, John Ralls Geert ___ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel
Time for 2.5.1
I have added a patch on bug 699614 which should change the defaults as requested. Regards, Robert. ___ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel
Re: Time for 2.5.1
Robert, Robert Fewell 14ubo...@gmail.com writes: I have added a patch on bug 699614 which should change the defaults as requested. Does this change the Business/Invoice register to use the new register code, too, or just Account registers? (I'm just curious) Regards, Robert. -derek -- Derek Atkins, SB '93 MIT EE, SM '95 MIT Media Laboratory Member, MIT Student Information Processing Board (SIPB) URL: http://web.mit.edu/warlord/PP-ASEL-IA N1NWH warl...@mit.eduPGP key available ___ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel
Time for 2.5.1
Robert, Robert Fewell 14ubobit at gmail.com https://lists.gnucash.org/mailman/listinfo/gnucash-devel writes: * I have added a patch on bug 699614 which should change the defaults as** requested.* Does this change the Business/Invoice register to use the new register code, too, or just Account registers? (I'm just curious) * Regards, Robert.* -derek At the moment it is just the Account registers that use the new interface, I am looking at changing the business options to use the same thing. Robert ___ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel
Time for 2.5.1
It's a new month and time for a new release of the 2.5 series. I propose to tag on Saturday around noon PDT (1700Z). Is there anything that needs doing to get ready? In particular, is the Win32 build issue fixed? Regards, John Ralls ___ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel
