Version: (using Devel) Compiler: gcc 4.3.2 OS: Linux Installed from: Compiled sources - Launch Korg - Create one to-do - Go to View menu/To-do list - the to-do that you created is listed in the table - Right click on the column headers and uncheck the check box to remove the 'Description' column - The 'Description' column is removed succesfully - Recheck the 'Description' check box - Nothing happens: the column is not reappearing - Go to the right hand side of the header and the mouse pointer becomes different(two small arrows and a line instead of one arrow) - Drag the pointer to the left while holding the right mouse button to make the 'Description' column visible again. This is not convenient, especially when removing a lot of columns. Would it be possible for the columns to be displayed automatically at the maximum size of what's written in them when they reappear instead? Atm, the user has to know what to do to make the headers visible again and can easily believe that they cannot reappear. Trunk, Svn Rev 1128166
In fact the pb seems to be that the last displayed column takes all the screen space. So when readding column you have to know that they will be displayed outside the screen (hence a scrollbar at the bottom): - Launch KOrg - Right click on the column headers and uncheck the check boxes to remove the 'Description', 'Categories' and 'Due Date/Time' columns - The column are removed succesfully - Recheck the columns check boxes Nothing happens: the columns are not reappearing inside the screen since the 'Complete' column takes up all the screen space unnecessarily. You have to scroll to find them and resize them manually. There is no need for the last column to be displayed to take up all the screen space if there is only a word written in it. I think, it would be more user friendly if the columns were to be displayed at automatically at the maximum size of what's written in them. Trunk, Svn Rev 1128166
This bug has only been reported for versions before 4.14, which have been unsupported for at least two years now. Can anyone tell if this bug still present? If noone confirms this bug for a Framework-based version of korganizer (version 5.0 or later, as part of KDE Applications 15.08 or later), it gets closed in about three months.
Just as announced in my last comment, I close this bug. If you encounter it again in a recent version (at least 5.0 aka 15.08), please open a new one unless it already exists. Thank you for all your input.