[PyQt] QPrinter.setOutputToFile is missing
Hi, I think, QPrinter's setOutputToFile function is not wrapped. It is in the documentation of the Qt4. from PyQt4.QtCore import * from PyQt4.QtGui import * a = QApplication([]) p = QPrinter() p.setOutputToFile(True) Traceback (most recent call last): File "", line 1, in AttributeError: setOutputToFile I am using kubuntu gutsy with following packages sip 4.7.1 pyqt 4.3 Mike ___ PyQt mailing listPyQt@riverbankcomputing.com http://www.riverbankcomputing.com/mailman/listinfo/pyqt
Re: [PyQt] Next SIP and PyQt4 Releases
I think QColorDialog cannot be instantiated or subclassed from PyQt. I
don't really know if the same behaviour exists in C++. I looked at the
source code of the QColorDialog::getColor function and it is
QColor QColorDialog::getColor(const QColor& initial, QWidget *parent)
{
QColorDialog *dlg = new QColorDialog(parent, true); //modal
dlg->setWindowTitle(QColorDialog::tr("Select color"));
dlg->setColor(initial);
dlg->selectColor(initial);
int resultCode = dlg->exec();
QColor result;
if (resultCode == QDialog::Accepted)
result = dlg->color();
delete dlg;
return result;
}
Looking at the code, I can see that, it can be instantiated from C++.
Mike
On 9/26/07, Phil Thompson <[EMAIL PROTECTED]> wrote:
> The next releases of SIP and PyQt4 will be made in the next few days. Both are
> maintenance releases (ie. mostly bug fixes). If anybody thinks there is
> something that still needs fixing then now is the time to shout.
>
> Phil
> ___
> PyQt mailing listPyQt@riverbankcomputing.com
> http://www.riverbankcomputing.com/mailman/listinfo/pyqt
>
___
PyQt mailing listPyQt@riverbankcomputing.com
http://www.riverbankcomputing.com/mailman/listinfo/pyqt
[PyQt] setTextFormat missing in QTextEdit
Hi, setTextFormat and textFormat are missing QTextEdit. They are also not existant in the PyQt4 class reference. I am using Qt 4.2.3 and PyQt 4.2 Mike ___ PyQt mailing listPyQt@riverbankcomputing.com http://www.riverbankcomputing.com/mailman/listinfo/pyqt
[PyKDE] Re: [PyQt3] Saving QPixmap onto a str
Hi, I got it. Someone may also need this. I am trying to serialize QPixmap to send it over network. Here's the solution. Qt classes cannot be pickled. pixmap = This is a pixmap already in memory'''' buffer = QBuffer() pixmap.save(buffer, 'XPM') data = buffer.getData() --- from qt import * from cStringIO import StringIO class QBuffer(QIODevice): def __init__(self): QIODevice.__init__(self) self.open( IO_ReadOnly) def open(self, mode): self.__io = StringIO() return True def close(self): self.__io.close() def flush(self): self.__io.flush() def readAll(self): return self.__io.read() def getch(self): return self.__io.read(1) def readBlock(self, size): result = self.__io.read(size) if result: return (result,) return None def writeBlock(self, data, length=None): if type(data) == QByteArray: data = data.data() self.__io.write(data) return len(data) def getData(self): return self.__io.getvalue() On 9/4/06, Mike Tammerman <[EMAIL PROTECTED]> wrote: Hi, I am trying to save a QPixmap onto a str object. I tried using QBuffer. But QBuffer does not exist in pyqt3. I am using the kubuntu's default pyqt3 package which is 3.5.1. Sip version is 4.3.2. I don't want to use temporary files. Can you help me. Mike ___ PyKDE mailing listPyKDE@mats.imk.fraunhofer.de http://mats.imk.fraunhofer.de/mailman/listinfo/pykde
[PyKDE] [PyQt3] Saving QPixmap onto a str
Hi, I am trying to save a QPixmap onto a str object. I tried using QBuffer. But QBuffer does not exist in pyqt3. I am using the kubuntu's default pyqt3 package which is 3.5.1. Sip version is 4.3.2. I don't want to use temporary files. Can you help me. Mike ___ PyKDE mailing listPyKDE@mats.imk.fraunhofer.de http://mats.imk.fraunhofer.de/mailman/listinfo/pykde
[PyKDE] How to avoid line wrapping in eric 3.9
Hi, I have installed eric 3.9, but the lines are automatically wrapped like in xemacs or like below something on the ->| ->line I tried to disable it, but I couldn't find the settings. I am using eric 3.9 qscintilla 1.6 pyqt 3.15.1 pykde 3.15.0 on kubuntu dapper How can I disable it. Thanks Mike ___ PyKDE mailing listPyKDE@mats.imk.fraunhofer.de http://mats.imk.fraunhofer.de/mailman/listinfo/pykde
Re: [PyKDE] Debugging a segfault in Linux
I checked all the __init__ functions, but I hadn't missed anything as you mentioned. However, I catched another traceback which is smaller and complete. I searched the previous mails in the archieve and found these http://mats.imk.fraunhofer.de/pipermail/pykde/2003-November/006529.html http://mats.imk.fraunhofer.de/pipermail/pykde/2003-November/006508.html They had also faced the same problem like mine, but there seems to be no solution. Mike #0 0xb767e318 in QObject::parent (this=0x139) at qobject.h:154 #1 0xb767ebd5 in QWidget::parentWidget (this=0x139, sameWindow=false) at qwidget.h:856 #2 0xb778fbb5 in ~QWidget (this=0x85fd868) at kernel/qwidget.cpp:946 #3 0xb6de0c48 in sipQWidget::~sipQWidget () from /usr/lib/python2.4/site-packages/qt.so #4 0xb7753b8e in QObject::event (this=0x85fd868, e=0x85f9f78) at kernel/qobject.cpp:750 #5 0xb7791268 in QWidget::event (this=0x85fd868, e=0x85f9f78) at kernel/qwidget.cpp:4658 #6 0xb6de3ec9 in sipQWidget::event () from /usr/lib/python2.4/site-packages/qt.so #7 0xb76edf80 in QApplication::internalNotify (this=0x82b6ba8, receiver=0x85fd868, e=0x85f9f78) at kernel/qapplication.cpp:2635 #8 0xb76eecf6 in QApplication::notify (this=0x82b6ba8, receiver=0x85fd868, e=0x85f9f78) at kernel/qapplication.cpp:2523 #9 0xb6dff877 in sipQApplication::notify () from /usr/lib/python2.4/site-packages/qt.so #10 0xb767edb7 in QApplication::sendEvent (receiver=0x85fd868, event=0x85f9f78) at qapplication.h:491 #11 0xb76ef4a3 in QApplication::sendPostedEvents (receiver=0x0, event_type=0) at kernel/qapplication.cpp:3261 #12 0xb76ef5aa in QApplication::sendPostedEvents () at kernel/qapplication.cpp:3172 #13 0xb769206c in QEventLoop::processEvents (this=0x83bd4c0, flags=4) at kernel/qeventloop_x11.cpp:202 #14 0xb7705cfb in QEventLoop::enterLoop (this=0x83bd4c0) at kernel/qeventloop.cpp:198 #15 0xb76ecc3f in QApplication::enter_loop (this=0x82b6ba8) at kernel/qapplication.cpp:2790 #16 0xb6e026b3 in sipQApplication::sipEmit_guiThreadAwake () from /usr/lib/python2.4/site-packages/qt.so #17 0x080b6a11 in PyEval_EvalFrame () #18 0x080b726d in PyEval_EvalCodeEx () #19 0x080b5719 in PyEval_EvalFrame () #20 0x080b726d in PyEval_EvalCodeEx () #21 0x080b73ae in PyEval_EvalCode () #22 0x080d8ffc in PyRun_FileExFlags () #23 0x080d929c in PyRun_SimpleFileExFlags () #24 0x08055a06 in Py_Main () #25 0xb7e5fea2 in __libc_start_main () from /lib/tls/i686/cmov/libc.so.6 #26 0x08054f21 in _start () On 3/17/06, Andreas Pakulat <[EMAIL PROTECTED]> wrote: > On 17.03.06 17:14:54, Diez B. Roggisch wrote: > This often happens when deriving from a Qt class and not doing > > Q.__init__(self) > > within the new class' __init__ method. However IIRC Python or sip tells > you then that the underlying C++ Object "vanished". > > Andreas > > -- > You'll never see all the places, or read all the books, but fortunately, > they're not all recommended. > > ___ > PyKDE mailing listPyKDE@mats.imk.fraunhofer.de > http://mats.imk.fraunhofer.de/mailman/listinfo/pykde > ___ PyKDE mailing listPyKDE@mats.imk.fraunhofer.de http://mats.imk.fraunhofer.de/mailman/listinfo/pykde
Re: [PyKDE] Debugging a segfault in Linux
This question may be very silly, but is there a way to associate the backtrace with my python script. Here is the backtrace of the core file, that may be useful. #0 0xb7656318 in QObject::parent (this=0x) at qobject.h:154 #1 0xb7656bd5 in QWidget::parentWidget (this=0x, sameWindow=false) at qwidget.h:856 #2 0xb7767bb5 in ~QWidget (this=0x85e3ce0) at kernel/qwidget.cpp:946 #3 0xb77ed2ef in ~QFrame (this=0x85e3ce0) at qframe.h:48 #4 0xb780b5d5 in ~QLineEdit (this=0x85e3ce0) at widgets/qlineedit.cpp:442 #5 0xb77d5110 in QComboBox::setLineEdit (this=0x85ff618, edit=0x8609050) at widgets/qcombobox.cpp:2258 #6 0xb6d88802 in sipQComboBox::sipEmit_textChanged () from /usr/lib/python2.4/site-packages/qt.so #7 0x080b6a11 in PyEval_EvalFrame () Mike On 3/17/06, Diez B. Roggisch <[EMAIL PROTECTED]> wrote: > > Program received signal SIGSEGV, Segmentation fault. > > [Switching to Thread -1209734944 (LWP 16726)] > > 0xb7682318 in QObject::parent (this=0x) at qobject.h:154 > > This looks fishy - a "this" with value -1 ist most probably an uninitialized > pointer. Try investigating that. > > Diez > > ___ > PyKDE mailing listPyKDE@mats.imk.fraunhofer.de > http://mats.imk.fraunhofer.de/mailman/listinfo/pykde > ___ PyKDE mailing listPyKDE@mats.imk.fraunhofer.de http://mats.imk.fraunhofer.de/mailman/listinfo/pykde
Re: [PyKDE] Debugging a segfault in Linux
Now, I recompiled python2.4-qt3 with -g parameters and discarded the
-OO and -O2 parameters. After I had run my program in gdb, I got the
following error
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread -1209734944 (LWP 16726)]
0xb7682318 in QObject::parent (this=0x) at qobject.h:154
154 qobject.h: No such file or directory.
in qobject.h
I downloaded the source of libqt3-mt package and checked the line at
qobject.h:154, it is
public:
QObject *parent() const { return parentObj; }
But, I still didn't understand why my app crashes. I tried to make a
small demo of the problem, it doesn't crash when I make it smaller.
Mike
On 3/17/06, Diez B. Roggisch <[EMAIL PROTECTED]> wrote:
> On Friday 17 March 2006 15:27, Mike Tammerman wrote:
> > Hi,
> >
> > I'm trying to implement a distributed media player using twisted and
> > pyqt. Sometimes, I am getting segfaults for the gui part. I am using
> > custom widgets and I don't know if the reason of the problem is myself
> > or pyqt or something else.
> >
> > I want to learn how to debug pyqt apps. Is there a practical way
> > you're using? I am using ubuntu(breezy) and its pre-compiled packages.
>
> You'll need debug-builds of whatever you can get one for - so most probably
> you should build every piece of the toolchain with debug information enabled.
>
> Luckily you're on a debian-based system. That means that you can get the
> source-packages easily (apt-source or apt-get source). Fetch them with all
> dependencies. Then you can build the packages yourself - check out the
> /debian/rules, ususally there are the configure-statements. Build
> with e.g.
>
> fakeroot debian/rules binary
>
> Then install the packages.
> When everything is set up, you can debug things using the gdb - just pass e.g.
> python as execuatbe like this
>
> gdb python
>
> gdb> set args gdb> run
>
>
> That all ist just a rough sketch, atop of my head. But it should give you some
> pointesr I hope.
>
> Diez
>
> ___
> PyKDE mailing listPyKDE@mats.imk.fraunhofer.de
> http://mats.imk.fraunhofer.de/mailman/listinfo/pykde
>
___
PyKDE mailing listPyKDE@mats.imk.fraunhofer.de
http://mats.imk.fraunhofer.de/mailman/listinfo/pykde
[PyKDE] Debugging a segfault in Linux
Hi, I'm trying to implement a distributed media player using twisted and pyqt. Sometimes, I am getting segfaults for the gui part. I am using custom widgets and I don't know if the reason of the problem is myself or pyqt or something else. I want to learn how to debug pyqt apps. Is there a practical way you're using? I am using ubuntu(breezy) and its pre-compiled packages. Thanks, Mike ___ PyKDE mailing listPyKDE@mats.imk.fraunhofer.de http://mats.imk.fraunhofer.de/mailman/listinfo/pykde
Re: [PyKDE] QString in PyQt4 - Request for Comments
I don't know how difficult or feasible it is, but I would suggest
using macros, so people can choose whether to use QString or python
str while compiling pyqt.
Just an idea.
Mike
On 10/18/05, Phil Thompson <[EMAIL PROTECTED]> wrote:
> I'm wondering whether QString should be dropped in PyQt4 in order to make it
> more Pythonic.
>
> At the moment Python strings and unicode strings are automatically converted
> to QStrings when passed as arguments - so there would be no change there. If
> a QString was returned by a method or an operator then a unicode string would
> be returned instead.
>
> Obviously you would lose all of QString's methods and would have to rely on
> what Python gives you for manipulating strings.
>
> One of the limitations of QString has been that you couldn't do...
>
> q = "Py" + QString("Qt")
>
> ...but with current snapshots you can - so this is an argument for keeping
> QString as it has become easier to use.
>
> BTW, the following is a consequence of the additional support...
>
> s = "Py"
> # s is of type str
> s += QString("Qt")
> # s is now of type QString
>
> Comments, opinions welcome.
>
> Phil
>
> ___
> PyKDE mailing listPyKDE@mats.imk.fraunhofer.de
> http://mats.imk.fraunhofer.de/mailman/listinfo/pykde
>
___
PyKDE mailing listPyKDE@mats.imk.fraunhofer.de
http://mats.imk.fraunhofer.de/mailman/listinfo/pykde
Re: [PyKDE] eric3 crash upon deleting selected line
Hi, Although, I tested with the GPL'ed version of Qt, I think the problem is not related with neither Qt nor Eric. When I try to run eric from console, I get the following assertion; Assertion [line < pdoc->LinesTotal()] failed at ..\src\Editor.cpp Therefore, it seems to be a scintilla bug. Here's the my scenario of this behaviour with eric3.8-snapshot20050724. * open eric3 * open preferences dialog and from the project section, check the options - Load session upon opening - Save session upon closing * create a project * add some files to the project * save the project * close eric leaving some files open in the tabs * reopen eric3 * open the saved project (the files will be opened momentarily) * do nothing but go to the last line of the opened file in the tabs * select a whole line * press the delete key, it crashes On the other way, this crash is very strange. For example; After the project is loaded and session restored, I jumped to another file in the tabs. I chose a comment line standing at the very beginings of the file and it didn't crash. In any way, I couldn't make eric3 crash on Linux. It works perfectly :) Mike P.S.: Detlev, sorry for direct mail. On 9/21/05, Detlev Offenbach <[EMAIL PROTECTED]> wrote: > Am Dienstag, 20. September 2005 15:16 schrieb Burkhard Doliwa: > > Hi, > > > > I have made the experience that eric3 tends to crash when I try to > > delete a selected line in the text editor using the delete-key. > > > > Furthermore, the problem of having a permanent foreground eric3 window > > (see my email from 13.9.2005) only arises after having used the debugger > > once. Before that, the eric3 windows behaves completely normal. > > > > [This is for a Windows 2000 box, eric3-snapshot 20050410 > > python 2.4.1, PyQt(>>> qt.qVersion()=='3.3.4'),...] > > > > Under linux: no strange behavior, no crashes. > > > > Have these bugs (despite the problems related to free Win-Qt) been > > removed in the youngest version of eric3? > > > > > > These problems are all related to the usage of Qt free on Windows. Therefore I > cannot do anything about them in eric3, which means "No, the have not been > removed". Please ask the project producing Qt-Free for Win to fix their > stuff. Using the commercial version of Qt eric3 behaves exactly the same way > under Linux and Win32. > > Detlev > -- > Detlev Offenbach > [EMAIL PROTECTED] > > ___ > PyKDE mailing listPyKDE@mats.imk.fraunhofer.de > http://mats.imk.fraunhofer.de/mailman/listinfo/pykde > ___ PyKDE mailing listPyKDE@mats.imk.fraunhofer.de http://mats.imk.fraunhofer.de/mailman/listinfo/pykde
[PyKDE] PyKDE on Debian
Hi, I am using Debian, but I am not able to install pykde for the following reason. I also tried the latest snapshot on the web, but gives the same error. Any suggestions would be very helpful. Thanks Mike PyKDE version 3.11.3 --- Python include directory is /usr/include/python2.4 Python version is 2.4.1 sip version is 4.2.1 (4.2.1) Qt directory is /usr/share/qt3 Qt version is 3.3.3 PyQt directory is /usr/share/sip/qt PyQt version is 3.14.1 (3.14.1) KDE base directory is /usr KDE include directory is /usr/include/kde KDE lib directory is /usr/lib KDE version is 3.3.2 (0x30302) PyKDE modules will be installed in /usr/lib/python2.4/site-packages PyKDE .sip files will be installed in /usr/share/sip PyKDE modules to be built: dcop kdecore kdesu kdefx kdeui kio kutils kfile kparts khtml kspell kdeprint kmdi Generating the C++ source for the dcop module... sip: /usr/share/sip/qt/qt/qtmod.sip:49: syntax error Error: Unable to create the C++ code. ___ PyKDE mailing listPyKDE@mats.imk.fraunhofer.de http://mats.imk.fraunhofer.de/mailman/listinfo/pykde
Re: [PyKDE] PyKDE without KApplication
Mostly it creates a segfault, the basic one is --- from qt import * from kdeprint import * import sys a = QApplication(sys.argv) KPrinter() --- Mike On 6/30/05, Andreas Pakulat <[EMAIL PROTECTED]> wrote: > On 30.Jun 2005 - 17:33:34, Mike Tammerman wrote: > > Is there a way to instantiate pykde classes using QApplication instead > > KApplication. > > I think so, at least most. For instance KMainWindow is derived from > QMainWindow and thus it should be possible to use > > QApplication.setMainWidget > > Instead of KApplication. And also you should be able to use a KDE widget > wherever a QWidget can be used. Note: I did not test this myself, these > are only assumptions based on the information about the classes from the > kde docs. > > Andreas > > -- > Your business will go through a period of considerable expansion. > > ___ > PyKDE mailing listPyKDE@mats.imk.fraunhofer.de > http://mats.imk.fraunhofer.de/mailman/listinfo/pykde > ___ PyKDE mailing listPyKDE@mats.imk.fraunhofer.de http://mats.imk.fraunhofer.de/mailman/listinfo/pykde
[PyKDE] PyKDE without KApplication
Is there a way to instantiate pykde classes using QApplication instead KApplication. Thanks. Mike ___ PyKDE mailing listPyKDE@mats.imk.fraunhofer.de http://mats.imk.fraunhofer.de/mailman/listinfo/pykde
Re: [PyKDE] how to identify empty space on a qcanvas
1. Retrieve all items from the canvas with QCanvas.allItems() method, then make a set with the points of the item. Call it A. 2. Make a full set with all the points in the canvas. Call it B. 3. Get the difference. (B - A) If your items are as simple as rectangels, it would be trivial. Mike On 5/27/05, Solly Brown <[EMAIL PROTECTED]> wrote: > I've got a qcanvas with a number of canvasitems moving about on it. I need > to efficiently identify which areas of the canvas are empty (ie. don't > have any objects on them). > > The simplest implementation is to lay down a grid of qpoints on the > canvas, and then just check whether there are collisions with each point > -- if there are no collisions then that particular point area is empty. > > The problem with this is that it's really slow... a 40x40 grid has 1600 > points and looping through all of them and calling 'collisions' on each > one makes my display slow to a crawl. > > Can anyone suggest an efficient way of identifying which points on a grid > are clear (don't have collisions above them)? > > Thanks for your help! > > Solly > > ___ > PyKDE mailing listPyKDE@mats.imk.fraunhofer.de > http://mats.imk.fraunhofer.de/mailman/listinfo/pykde > ___ PyKDE mailing listPyKDE@mats.imk.fraunhofer.de http://mats.imk.fraunhofer.de/mailman/listinfo/pykde
Re: [PyKDE] ANN: eric3 3.7.0-rc1 released
I changed the keywords, added my own keywords which is lowercase todo: If the keyword is below the cursor, the page scrolls down. Otherwise, the page scrolls up. But try this behaviour in a long enough file. My files are approximately 500 lines long. An example situation: 1. I put an TODO: keyword at line 30, changed and saved at line 370. The page scrolled up until the the cursor had reached the bottom. 2. I put the same keyword at line 400, changed and saved at line 33. The page scrolled down until the cursor had reached the top. Adding or deleting new keywords doesn't affect this behaviour. Mike On 5/26/05, Detlev Offenbach <[EMAIL PROTECTED]> wrote: > Anything more, that might be specific. Have you changed the Task Marker > keywords? It is working fine over here. Anybody else out there having seen > this? > > Detlev > > Am Donnerstag, 26. Mai 2005 13:31 schrieb Mike Tammerman: > > Recently I recognized, this only happens when there is a Task Marker > > keyword in the file. Sorry for the wrong information in the previous mail. > > > > Mike > > > > On 5/26/05, Mike Tammerman <[EMAIL PROTECTED]> wrote: > > > As Richards claims, it occurs when I save a file. The page scrolls until > > > the cursor stands at the bottom of the page. It doesn't depend any > > > specific file, happens all the time. It seems like the editor scans the > > > file and recoordinates the scroll bar. > > > > > > I am using Debian Testing with > > > > > > Python 2.4.1 > > > Qt 3.3.3 > > > PyQt 3.14.1 > > > sip 4.2.1 > > > QScintilla 1.5.1 > > > and eric 3.7.0-rc1 > > > > > > Mike > > > > > > On 5/26/05, Detlev Offenbach <[EMAIL PROTECTED]> wrote: > > > > Am Mittwoch, 25. Mai 2005 17:37 schrieb Richard Smith: > > > > > On 5/25/05, Mike Tammerman <[EMAIL PROTECTED]> wrote: > > > > > > I don't know if it is a bug or feature. > > > > > > > > > > > > Whenever I save a file, the cursor stands at the bottom of the page > > > > > > > > and > > > > > > > > > > page scrolls. > > > > > > > > > > I've noticed something like that as well but I haven't spent any time > > > > > to see what it was actually doing. > > > > > > > > Haven't seen anything like this over here. Could you give more specific > > > > instructions on how to reproduce it. Maybe you send me a file, that > > > > shows > > > > this behavior. > > > > > > > > Detlev > > > > -- > > > > Detlev Offenbach > > > > [EMAIL PROTECTED] > > -- > Detlev Offenbach > [EMAIL PROTECTED] > ___ PyKDE mailing listPyKDE@mats.imk.fraunhofer.de http://mats.imk.fraunhofer.de/mailman/listinfo/pykde
Re: [PyKDE] ANN: eric3 3.7.0-rc1 released
Recently I recognized, this only happens when there is a Task Marker keyword in the file. Sorry for the wrong information in the previous mail. MikeOn 5/26/05, Mike Tammerman <[EMAIL PROTECTED]> wrote: As Richards claims, it occurs when I save a file. The page scrolls until the cursor stands at the bottom of the page. It doesn't depend any specific file, happens all the time. It seems like the editor scans the file and recoordinates the scroll bar. I am using Debian Testing with Python 2.4.1 Qt 3.3.3 PyQt 3.14.1 sip 4.2.1 QScintilla 1.5.1 and eric 3.7.0-rc1 MikeOn 5/26/05, Detlev Offenbach < [EMAIL PROTECTED]> wrote: Am Mittwoch, 25. Mai 2005 17:37 schrieb Richard Smith:> On 5/25/05, Mike Tammerman <[EMAIL PROTECTED] > wrote:> > I don't know if it is a bug or feature. > >> > Whenever I save a file, the cursor stands at the bottom of the page and> > page scrolls.>> I've noticed something like that as well but I haven't spent any time> to see what it was actually doing. Haven't seen anything like this over here. Could you give more specificinstructions on how to reproduce it. Maybe you send me a file, that showsthis behavior.Detlev--Detlev Offenbach [EMAIL PROTECTED] ___ PyKDE mailing listPyKDE@mats.imk.fraunhofer.de http://mats.imk.fraunhofer.de/mailman/listinfo/pykde
Re: [PyKDE] ANN: eric3 3.7.0-rc1 released
As Richards claims, it occurs when I save a file. The page scrolls until the cursor stands at the bottom of the page. It doesn't depend any specific file, happens all the time. It seems like the editor scans the file and recoordinates the scroll bar. I am using Debian Testing with Python 2.4.1 Qt 3.3.3 PyQt 3.14.1 sip 4.2.1 QScintilla 1.5.1 and eric 3.7.0-rc1 MikeOn 5/26/05, Detlev Offenbach <[EMAIL PROTECTED]> wrote: Am Mittwoch, 25. Mai 2005 17:37 schrieb Richard Smith:> On 5/25/05, Mike Tammerman <[EMAIL PROTECTED]> wrote:> > I don't know if it is a bug or feature. > >> > Whenever I save a file, the cursor stands at the bottom of the page and> > page scrolls.>> I've noticed something like that as well but I haven't spent any time> to see what it was actually doing. Haven't seen anything like this over here. Could you give more specificinstructions on how to reproduce it. Maybe you send me a file, that showsthis behavior.Detlev--Detlev Offenbach [EMAIL PROTECTED] ___ PyKDE mailing listPyKDE@mats.imk.fraunhofer.de http://mats.imk.fraunhofer.de/mailman/listinfo/pykde
Re: [PyKDE] ANN: eric3 3.7.0-rc1 released
I don't know if it is a bug or feature. Whenever I save a file, the cursor stands at the bottom of the page and page scrolls. Mike ___ PyKDE mailing listPyKDE@mats.imk.fraunhofer.de http://mats.imk.fraunhofer.de/mailman/listinfo/pykde
