[From the dev list] Is there a major reason why the column widths behave the way they do? It doesn't seem very logical to me at the moment, or in fact ever. A slight silly, but not untypical, example is that if I choose to use a complex system for check numbers, such that the whole number is not visible, the only way I have available is to stretch the whole window. However, even that doesn't help, as the whole of the increase is grabbed by the Details column. I accept that it is likely that that column is going to need to be the widest. Then, why are the Payment and Deposit columns twice the width of the Balance column, when that column may be likely to have the greatest value? Ditto for the Date. Why not allow the user to set the column widths according to *his* needs? Alvaro Soliverez <asoliverez@kde.org> wrote: > From when I had to work on it during the porting days, I can tell the > ledger view is full of weird widgets. It needs a revamp to remove all > the crust (we even found KDE 2.x code in there). > But... it is the most complicated view in the app, so it will take a > lot of dev time that we don't have at the moment. No, I understand that, but before posting last night, I changed the horizontalHeader()->setResizeMode() to Interactive, which seemed helpful. I wanted to check that there wasn't an obscure reason for it to be that way. The change to KDE4 was a massive undertaking, and it would be understandable if some elements weren't optimal. Reproducible: Always Steps to Reproduce: 1.Open a new transaction in a checking account. 2.Enter a silly long number field entry, say "12345678901". 3.The number field cannot display the full number. 4.Try stretching the window width. 5.The number field remains unaltered and the extra width is grabbed by the Details column. Actual Results: As above. The example is perhaps unrealistic, but it serves to illustrate the issue. Expected Results: It would be helpful if the user were able to adjust column widths to suit his needs.
Very similar to bug 312816 *** This bug has been marked as a duplicate of bug 312816 ***