Version: 3.0 (using KDE KDE 3.2.0) Installed from: Compiled From Sources The listview columns in the watch window resize automaticly to fit the largest text entry in them. This is very annoying, especially when dealing with variables which are instances of template classes. When for example you click at the "expand(+)" button in the "Variable" column and the class name is very long, you have to scroll 2 minutes to reach the "Value" column and actually to see the value.
CVS commit by dagerbo: Don't autoresize watch window columns. CCMAIL: 78113-done@bugs.kde.org M +3 -3 variablewidget.cpp 1.37 --- kdevelop/languages/cpp/debugger/variablewidget.cpp #1.36:1.37 @@ -150,7 +150,7 @@ VariableTree::VariableTree(VariableWidge QListView::setSelectionMode(QListView::Single); - addColumn(i18n("Variable")); - addColumn(i18n("Value")); - addColumn(i18n("Type")); + addColumn(i18n("Variable"), 100 ); + addColumn(i18n("Value"), 100 ); + addColumn(i18n("Type"), 100 ); connect( this, SIGNAL(contextMenu(KListView*, QListViewItem*, const QPoint&)),
It seems that is partially fixed - I attach two screenshots which show that problem still occurs. I think this now happens only if a subitem of some of the entries in the list view is expanded. It also only happens once for a particular list view entry.
Created attachment 7858 [details] State before auto-resize This shows the state of the list view before clicking on the expand icon of the "worst_it_" item.
Created attachment 7859 [details] State after auto-resize This shows the state of the list view *after* clicking on the expand icon of the "worst_it_" item.
Which KDevelop version?
Version 3.0.4 Amilcar do Carmo Lucas wrote: > ------- You are receiving this mail because: ------- > You reported the bug, or are watching the reporter. > > http://bugs.kde.org/show_bug.cgi?id=78113 > amilcar ida ing tu-bs de changed: > > What |Removed |Added > ---------------------------------------------------------------------------- > AssignedTo|kdevelop-devel kdevelop org |kdevelop-bugs kdevelop org > > > > ------- Additional Comments From amilcar ida ing tu-bs de 2004-10-13 14:19 ------- > Which KDevelop version? > >
How about updating to 3.1.1 ?
It is apparently fixed in 3.1.1. Thanks a lot!:-)