From koffice-devel Sun Aug 22 21:04:13 2004 From: p.stirnweiss_koffice () bluewin ! ch Date: Sun, 22 Aug 2004 21:04:13 +0000 To: koffice-devel Subject: Re: Character style Message-Id: <40F7A9ED000FE3FA () mssbzhb-int ! msg ! bluewin ! ch> X-MARC-Message: https://marc.info/?l=koffice-devel&m=109320868614801 >-- Message original -- >Date: Sun, 22 Aug 2004 22:59:45 +0200 >To: For developer's discussion about KOffice >From: Thomas Zander >Subject: Re: Character style >Reply-To: For developer's discussion about KOffice > > >On Sun, Aug 22, 2004 at 10:49:20PM +0200, p.stirnweiss_koffice@bluewin.ch >wrote: >> Yes, I am thinking about working on dialogs. The style manager interests >> me. The whole thing seems a bit cumbersome. There are a few things I would >> like to know: >> >> - first if Thomas would be so kind as explaining me a bit more what he >had >> in mind for replacing the two lists of styles by a small calss and an enum... > >Sure; I'll try to make a little time for that tomorrow.. > >> - why are we using Qt widgets when KDE widgets are available? (for example >> the style manager lists of style is displayed in a QListBox when a KListBox >> exists. Wouldn't using a KListBox bring more consistency ? > >I honestly don't even know why there is a KListBox; so I can't really answer >this. >Anyone? According to the docs, the KListBox is only overidding the click behaviour to respect the general double-click policy. Extends the functionality of QListBox to honor the system wide settings for Single Click/Double Click mode, Auto Selection and Change Cursor over Link. A variant of QListBox that honors KDE's system-wide settings. >But in basis I think I agree with that.. > >-- >Thomas Zander >_______________________________________________ >koffice-devel mailing list >koffice-devel@mail.kde.org >https://mail.kde.org/mailman/listinfo/koffice-devel _______________________________________________ koffice-devel mailing list koffice-devel@mail.kde.org https://mail.kde.org/mailman/listinfo/koffice-devel