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

List:       kde-devel
Subject:    qproperty - bug - problem
From:       Simon Hausmann <tronical () gmx ! net>
Date:       1999-06-05 11:05:11
[Download RAW message or body]

Hello,

I have a problem and I need some advice/help :)

I found two bugs in QProperty, and I reported them twice (once on
snapshot-users and once to the original Author) , without any reaction or
fix (although I provided a patch) .
Well, it doesn't matter why this hasn't been fixed in Qt's CVS by some of
the Trolls, they will probably have their reasons (perhaps being busy with
the beta release; qproperty is not part of the release) , I don't care.

BUT: I have a bunch of code sitting on my hdd (including patches for
KOffice to make filters, tools and plugins working again!) , but I can't
commit this code, because it depends on a working QProperty. If I would
just commit the code then it would break kservicetype and kded would then
crash on startup. A non-working kded prevents KOffice apps from
working, so Reggie for example couldn't continue hacking KWord/KPresenter
if he'd cvs update (just as example) .

My question is simple:
What can be done, so I can commit?

Should I post a patch (conforming to the QPL this way) to
kde-devel@/koffice@ and make everyone require to apply it?

Should I try to work around the bug? (although it would be a very ugly
workaround IMHO)

Or could I even commit the QProperty patch into CVS (now that QProp is
temporarily in kdelibs) ?

(I hope this doesn't sound like ranting. I'm just asking for little help:)

Ciao,
  Simon

--
Simon Hausmann       <hausmann@kde.org>
http://www.kde.org/  <tronical@gmx.net>

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