[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-devel
Subject:    Re: kcontrol and KTreeList
From:       Reginald Stadlbauer <reggie () troll ! no>
Date:       1999-06-23 17:56:15
[Download RAW message or body]

On Wed, 23 Jun 1999, Mario Weilguni wrote:
>At Wed, 23 Jun 1999 Reginald Stadlbauer wrote:
>> On Wed, 23 Jun 1999, Carlo Robazza wrote:
>> >Hello again,
>> >
>> >I am doing some work on kcontrol and have a few questions about
>> >KTreeList. A little background may help. I have modified kcontrol so
>> >that if the user closes a module and there are still others in memory,
>> >then another is brought to the forefront; sort of a stacking effect.
>> >
>> >The problem is that the highlighted element in the tree list does not
>> >change. I want to be able to, through software, highlight a specific
>> >element in the tree list. One of the problems, as I see it, is that this
>> >element may not be visible (i.e. tree closed down). The only way that I
>> >can see to do it right now is to use the function "void forEveryItem
>> >(KForEvery func, void *user)" to itereate through the list. Then when
>> >the one I want is found I would have to make sure that I make it
>> >visible, if it isn't already, then use the function "void setCurrentItem
>> >(int index)" to highlight it.
>> >
>> >I am not even certain that this is possible so I thought I would check
>> >with the list to see if there is an easier way that I am missing.
>> 
>> I really think we should drop KTreeList in the KControlCenter and use
>> QListView. QListView is so much easier to use. I also think that KTreeList
>> should be removed from kdelibs in some time.
>
>No, we should move it to a new library libkdecompat. This KTreeList stuff is
>too complicated to be replaced by QListView, and cannot be easily removed.
>Better move it to a library.

And this library will disappear then one day hopefully :-)

--
Reggie

[prev in list] [next in list] [prev in thread] [next in thread]