gmane.comp.python.pyqt-pykde

Re: Introducing PyDingo

piotr maliński — 2008-12-01T21:59:44

2008/12/1, Michał Andrzej Woźniak yahoo.co.uk>: It has to run on Linux/Win/Mac :) And it has to work nicely with QGtkStyle - looks native on GTK WMs. pykde4 is on my todo list to see what I can use. If KParts, KIOslaves could be reused easily without massive pykde code writting then who knows ;) Probably at v 0.5 all questions will be answered :)

Arbitrary number of copies of groupbox?

Christian Aubert — 2008-12-01T21:51:36

I'm trying to generate a report where I have a groupbox containing a number of fields per record. Is there anyway to have a scroll area and create an arbitrary number of copies of that groupbox on the fly? Christian

Re: Introducing PyDingo

Michał Andrzej Woźniak — 2008-12-01T21:50:50

Dnia poniedziałek 01 grudzień 2008, piotr maliński napisał(a): Ah, sorry, mentioning Konqueror and Dolphin - and the whole app being Qt-based - made me think you were going to write primarily KDE-targeted an app (so the deps wouldn't be a problem). It would be a cool thing to be able to use KParts should one want to/like to. Anyway, just an idea for version 1.x. ;) Great! If there will be a possibility to "package" the widgets as KParts, it would contribute a lot to the overall KDE flexibility (one could use your editor widget as an alternative KPart in Konqueror or KWrite, and the "stats://" widget in Konqueror and Dolphin). Had I only the time, I would brobably dive into KParting those widgets myself... eh. Cheers mike

Re: Introducing PyDingo

piotr maliński — 2008-12-01T21:16:27

In theory there can be more than one widget-handler for the same thing (default QScintilla editor could be overriden with for example Kate KPart if someone uses KDE). So using all those KParts would be cool, but if I would use them as required dependency - I get KDE related app (and I want it to be more flexible). Will PyDingo widgets-handlers be KParts - on this stage no. One thing is how to make a KPart in PyQt4/PyKDE4, second - my "widget-handlers" are ~ nearly independent apps, except for the navigation menu, which is connected with run.py - so exact KPart from this wouldn't work, but the widget backed will be easy to reuse and make KPart if needed :) 2008/12/1, Michał Andrzej Woźniak yahoo.co.uk>:

Re: Intro and question

2008-12-01T19:21:50

The signal that tells you when the button has been clicked doesn't carry this kind of information, unfortunately. However, you can create a subclass that emits a signal with the state of the modifier keys: from PyQt4.QtCore import Qt, SIGNAL from PyQt4.QtGui import * class KeyButton(QPushButton): def __init__(self, *args): QPushButton.__init__(self, *args) self.modifiers = Qt.NoModifier self.connect(self, SIGNAL("clicked()"), self.handleClick) def mousePressEvent(self, event): self.modifiers = event.modifiers() QPushButton.mousePressEvent(self, event) def handleClick(self): self.emit(SIGNAL("clicked(Qt::KeyboardModifiers)"), self.modifiers) Basically, the mousePressEvent() method handles the low-level event for mouse button presses and records the state of the modifier keys, but passes the event on to the base class's implementation so that the button behaves normally. In the __init__() method, we connected the button's standard cl

Re: Introducing PyDingo

Michał Andrzej Woźniak — 2008-12-01T19:04:08

Dnia poniedziałek 01 grudzień 2008, piotr maliński napisał(a): One question comes to mind: will it support KParts? It would make the whole thing easier, more robust and more "pluggable" (you could use Konqueror's or Kate's, or KWord's KParts to show files and edit text or documents, resp.)? Or, maybe, will it export some functionality ("stats://"?) through a KPart, so that it could be used in other KPart-compatible apps (like Konqueror)? If not, please treat the above as feature requests/ideas. ;) Good luck with the project!

Re: Intro and question

Christian Aubert — 2008-12-01T18:24:38

Right, this is a keyboard shortcut. I'm looking for a modifier that applies to the mouse click, so that when your ctrl-click or alt-click or right-click, the button has a different behavior. Christian Iliya Gogolev wrote:

Introducing PyDingo

piotr maliński — 2008-12-01T15:43:01

Re: Problem with UTF-8 files and QScintilla

piotr maliński — 2008-12-01T11:18:46

Re: Problem with UTF-8 files and QScintilla

Phil Thompson — 2008-12-01T11:05:08

On Mon, 1 Dec 2008 11:23:38 +0100, "piotr maliński" gmail.com> wrote: Python for Have you tried it without the Text flag? QsciScintilla.setText() encodings. You could also try QsciScintilla.read(). Note, QScintilla has its own mailing list. Phil

Problem with UTF-8 files and QScintilla

piotr maliński — 2008-12-01T10:23:38

Re: Attribute error message

Filip Gruszczyński — 2008-12-01T09:26:46

I guess this should be my line, as it will make my debugging easier :)

Re: Attribute error message

Phil Thompson — 2008-12-01T09:21:25

On Sun, 30 Nov 2008 23:16:18 +0100, "Filip Gruszczyński" gmail.com> wrote: It will be fixed in SIP v4.8. Thanks, Phil

Re: PyQt4-extrawidgets project

piotr maliński — 2008-12-01T07:59:16

Attribute error message

Filip Gruszczyński — 2008-11-30T22:16:18

Right now, when a Python object subclasses QObject and then casts Attribute error the message holds only the name of the attribute. This is a bit inconvenient, because you have to either check all possible classes from which that object was derived or put a print statement and rerun the program. For pure Python object there is information about the type of the object. Could the same be done for objects subclassing QObject or is it deliberately done this way, because it cannot be done otherwise?

Drag status message

Ron Longo — 2008-11-30T20:12:34

Phonon.AudioOutput is NOT a subclass of Phonon.MediaNode

Jan Holthuis — 2008-11-30T12:58:52

ANN: new eric4 4.3.0 snapshot available

Detlev Offenbach — 2008-11-30T12:52:23

Hi, a new snapshot of the eric 4.3 development is available via http://sourceforge.net/project/showfiles.php?group_id=119070&package_id=300692. Here is the changelog. - bug fixes - added a lexer type that guesses the style based on the current text (default for unknown source types) - added context menu entry to select an alternative (Pygments) lexer - updated pygments to version 1.0 - added capability to auto complete using templates (press Tab after entering a valid template name) Regards, Detlev

Re: connecting signals

David Boddie — 2008-11-29T01:57:43

It's a question of defining what the reusable components are and whether they should rely on other objects being present. In your connect() call, you're assuming that the widget will always have a parent with a usable menuWidget() method, for example. You could equally perform the connection in the main window as long as you're comfortable with exposing the internals of the central widget and making this sort of connection: self.connect(menuWidget(),QtCore.SIGNAL("imageSaveRequest(QString)"), self.centralWidget().Graph.SaveImage) Perhaps the main window will always use this kind of central widget, so assuming that it has this internal structure might be OK. Alternatively, you could add a slot to the central widget if you want to "hide" its internal Graph object, or you could set up a signal-to-signal connection: self.connect(menuWidget(),QtCore.SIGNAL("imageSaveRequest(QString)"), self.centralWidget(), SIGNAL("imageSaveRequest(QString)")) Inside the central widget, y

Detecting if a column has been resized by the user;auto-stretching columns.

Anonymous — 2008-11-28T20:02:14

Concerning QTableWidget, i need to figure out all of the above. I couldn't find anything in the documentation, neither by Googling, that would allow me or provide insight on how to do any of these, so i come here as a last resort. Also, does it require subclassing a delegate or item in order to have rows auto-resize based on their content? Or is it possible to pass the size of the content to the cell without subclassing anything? Any insight is appreciated.

connecting signals

Matt Smith — 2008-11-27T18:35:23

There is a lot of leeway in connecting signals, so I was curious about how other people are doing it. I have a widget layout similar to this. MainWindow Menu CentralWidget TabBar StackedWidget Graph Calculator InputWidget Everything above is a widget, and the menu is going to pretty much be connected to everything in some way. Where should I connect it. As of now in the Central widget __init__ use a line such as, self.Graph.connect(parent.menuWidget(),QtCore.SIGNAL("imageSaveRequest( QString )"),self.Graph.SaveImage) I suppose the meat of the question does it matter where I connect a widget to a signal. I mean if I have to do it through some long ugly expression using function calls that return widgets is it going to make a difference once they are connected? thanks, happy thanksgiving. mbs