Bug

[Ken Brakey]

Try making a link from "/usr/lib/QT2" to wherever qt-2.2.x is really.
Ken


Joachim Ansorg wrote:
> 
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> Hi!
> 
> I have the same problem for weeks and I already reported it some weeks ago.
> 
> Joachim
> 
> On Monday, 26. March 2001 04:33, you wrote:
> > Hello
> >
> > I have reported this bug before around Feb 28
> > and I can't for the life of me find it .
> > Maybe if I repost again someone else can assist
> > in tracking this fscking bug down.
> >
> > KDevelop Sources are from cvs -rKDEVELOP_1_4 < 48 hrs old
> > KDE Sources are from CVS compiled locally also < 48 hrs old.
> > Open KDevelop maximized (so you get the 2 little boxes in the
> > maximize/minimize button)
> > Open a project compile it and then hit the debug button
> > Eureka your KDevelop window will resize itself and move.
> > And while the debugger is running clicking on the top
> > left hand corner (the only one I can see) selecting maximize
> > will "almost" maximize the window it's about 50 pixels too large
> > IOW you can't see the close icon on the top right. Then clicking
> > back on the restore button the window returns to the "offset" position.
> >
> > Am I the only one that experiences this?
> > I have recently updated cvs sources as of about 3 hrs ago and made clean
> > and the fscking bug is still there.
> >
> > With all due respect to the developers WTF is going on I gave a "fairly
> > detailed" bug report almost 1 month ago and had some responses that
> > to quote Ralf Nolden
> > "This obviously is another side-effect of the setAutoSaveSettings() in
> > the CKDevelop constructor where that is called. That has been commented
> > out and I tagged that fixed one for the release as everything else until
> > ... "
> >
> > This was almost 30 days ago and I can still reproduce this from cvs sources
> > < 3 hours ago and a make clean.
> >
> > Tracking down something like this I will admit is frustrating and that's
> > why I am sounding so harsh. Is it something that came in w/ the new
> > kdelibs? I would suspect that it's not a KDevelop bug as it has to do with
> > window placement and maximizing.
> > And with the changes i.e can't run apps linked with an older
> > version of kde you will get DCOP errors if you try; it is awfully hard for
> > someone unfamiliar with the code to track down.
> >
> > Now that I've ticked off all the people that are involved I need some
> > suggestions, How do you suggest I track this bugger down? If I don't
> > have something that would help... I have more than enough disk space,
> > reasonable bandwidth, some spare time, and a very strong desire to fix this
> > fscking bug.
> 
> - --
> Joachim Ansorg
> BibleTime - www.bibletime.de - info at bibletime.de
> BibleTime is an easy to use Bible study tool for KDE / Linux.
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.0.1e-SuSE (GNU/Linux)
> Comment: For info see http://www.gnupg.org
> 
> iD8DBQE6vt/cXu8IiUJO3NcRAu3mAJsHkc1CwMVZZsjFVkhG7xc1NXjbcwCfTH6R
> 3nzcGidv77ZFFo7ohZrEru4=
> =yC5D
> -----END PGP SIGNATURE-----
> 
> -
> to unsubscribe from this list send an email to kdevelop-request at kdevelop.org with the following body:
> unsubscribe »your-email-address«

-- 
Common Sense, is Inveresly proportional 
to the World's Population. -- ME!
---=== ICQ#--275 14 825 ===---

-
to unsubscribe from this list send an email to kdevelop-request at kdevelop.org with the following body:
unsubscribe »your-email-address«