KEditListBox and KConfigDialogManager
bastian at kde.org
Tue Sep 14 17:40:42 BST 2004
The silence means I missed your mail :-}
Based on your description it sounds ok but could you send me the patches once
more so that I can have a look?
On Tuesday 14 September 2004 17:31, Richard Lärkäng wrote:
> On Sunday 05 September 2004 19.02, Richard Lärkäng wrote:
> > Hi!
> Does the silence mean it's OK to commit?
> > I added support for KConfigXT in the kcm for libkcddb, and ran into some
> > problems.
> > Now I have a QListBox with items where I need to store all of the items,
> > which isn't possible with the properties there is now, it will only save
> > the one which is selected.
> > But then I realized that KEditListBox would be better suited for what I
> > want to do, but it doesn't work very well with KConfigDialogManager,
> > because it doesn't have any properties (although the default is set to
> > "currentItem" in KApplication).
> > So I'm wondering if I could set the default property to "items" in
> > KApplication for KEditListBox and add that property to KEditListBox and
> > also add a method setItems(). It won't break any applications because it
> > didn't have any properties before, and also when looking through some
> > places where KEditListBox is used, items() seems to be used a lot more
> > than currentItem().
> > The attached patches does that, can I commit?
> > Btw, the example in KConfigDialogManager about adding a new widget to
> > the propertymap crashed on me, and the attached patch seems more correct,
> > can I commit that too?
> > Richard Lärkäng
bastian at kde.org | Novell BrainShare Europe 2004 | bastian at suse.com
bastian at kde.org | 12-18 September, Barcelona, Spain | bastian at suse.com
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 189 bytes
Desc: not available
More information about the kde-core-devel