Re: [PyKDE] QString in PyQt4 - Request for Comments

2005-10-19 Thread Simon Edwards
On Thursday 20 October 2005 03:21, Giovanni Bajo wrote: > James Emerton <[EMAIL PROTECTED]> wrote: > > > I'm very in favour of the automatic conversion of QStrings into native > > Python strings. I always thought that multiple string types was an > > annoyance exclusive to C++. I'm also not conv

[PyKDE] rotated CanvasText

2005-10-19 Thread Florian Remek
Helo dear python-hackers, im quite new to python and pyqt and stumbled across a problem which seems unsolvable for me. I wrote a little test application using the canvas painting facility and wanted to rotate a canvasText. But i cant figure how to get it properly repainted after i moved the view o

[PyKDE] eric3 default font can't be changed!

2005-10-19 Thread S Brown
The usual way of changing the default font in eric3 doesn't seem to be working. I select Preferences->Editor->Highlighting Style->Python->Default and then change the font colour or font itself and nothing changes in the editor. Now the weird thing is that I *am* able to change any of the ot

Re: [PyKDE] QString in PyQt4 - Request for Comments

2005-10-19 Thread Giovanni Bajo
James Emerton <[EMAIL PROTECTED]> wrote: > I'm very in favour of the automatic conversion of QStrings into native > Python strings. I always thought that multiple string types was an > annoyance exclusive to C++. I'm also not convinced that performance > is a compelling argument for the preserva

[PyKDE] About problem in open a form into other form

2005-10-19 Thread Jefferson Bosa
I can't open a Form builded in QtDesigner, into other form too builded in qtdesigner. Ex the code: from qt import * from Form_principal import Form_principal from Form_imagem_Impl import Form_imagem_Impl class Form_principal_Impl(Form_principal):     def __init__(self,parent = None,name = None,f

Re: [PyKDE] PyQt C API

2005-10-19 Thread James Emerton
> This is the inner loop of the rendering code for a custom graph widget. The > optimisation target isnt the PyQt code itself, but rather the next layer up, > which calls PyQt. It will be much more convenient for this C (or C++, or > pyrex) code to call the Qt C++ API directly. Now, I've never tou

Re: [PyKDE] QString in PyQt4 - Request for Comments

2005-10-19 Thread James Emerton
I'm very in favour of the automatic conversion of QStrings into native Python strings. I always thought that multiple string types was an annoyance exclusive to C++. I'm also not convinced that performance is a compelling argument for the preservation of QString in Python. See performance data:

Re: [PyKDE] Re: QString in PyQt4 - Request for Comments

2005-10-19 Thread Sundance
I heard Michael Thompson said: > No, the goal should be to work away at making QString interacted with > str/unicode more invisibly/naturally - where possible. Yeah, I'd sort of second that. The 'pythonic' way is pretty much duck typing, I think, in this sort of situation. How difficult would i

Re: [PyKDE] QString in PyQt4 - Request for Comments

2005-10-19 Thread David Boddie
On Wednesday 19 October 2005 09:47, Phil Thompson wrote: > On Wednesday 19 October 2005 1:17 am, David Boddie wrote: > > * Maintenance of QStrings passed to Python implemented methods - > > sometimes it's good to keep things in the same form that they were > > supplied in, although maybe it's not

[PyKDE] sender() and PYSIGNALs

2005-10-19 Thread Giovanni Bajo
Hello, It appears that QObject::sender() returns None when called from a slot invoked through a PYSIGNAL. Is there a way to access the information also for PYSIGNALs? Would it be possible to modify sender() so that it works also for PYSIGNALs? -- Giovanni Bajo ___

Re: [PyKDE] eric3, qscintilla and code folding

2005-10-19 Thread Baz Walter
On Tuesday 18 Oct 2005 14:36, Brad Ralph wrote: > > The problem is I seem to be too fussy. When you fold all of the children > (Ctrl - Click) it becomes a bit annoying to have to unfold the if > statements and triple quoted strings of any method that you are working in. > I know that this can be

Re: [PyKDE] QString in PyQt4 - Request for Comments

2005-10-19 Thread Phil Thompson
On Wednesday 19 October 2005 5:23 pm, Jim Bublitz wrote: > On Wednesday 19 October 2005 00:47, Phil Thompson wrote: > > QString just wouldn't exist in PyQt4. > > Would there still be something to allow me to handle something like: > > QMap > > with sipBuildResult and sipForceConvertTo_QString?

Re: [PyKDE] QString in PyQt4 - Request for Comments

2005-10-19 Thread Jim Bublitz
On Wednesday 19 October 2005 00:47, Phil Thompson wrote: > QString just wouldn't exist in PyQt4. Would there still be something to allow me to handle something like: QMap with sipBuildResult and sipForceConvertTo_QString? Also, KDE still uses QCString in a bunch of places - will that disap

Re: [PyKDE] QString in PyQt4 - Request for Comments

2005-10-19 Thread Nigel Stewart
As I've said, I have made that selling point many times - mainly as a sop to C++ programmers and avoid religious my-language-is-better-than-yours arguments. However, I don't know of anybody who has actually done it. We selectively port from Python to C++, depending on the broader mod

Re: [PyKDE] PyQt C API

2005-10-19 Thread Toby Dickenson
On Tuesday 18 October 2005 18:02, Phil Thompson wrote: > Or you can use the lower level sipConvertToCpp() which skips some error > checking. Thanks. One other problem is how to get the sipWrapperType pointer A sip generated extension module gets these pointers via api_export_module, but th

Re: [PyKDE] QString in PyQt4 - Request for Comments

2005-10-19 Thread Giovanni Bajo
Phil Thompson <[EMAIL PROTECTED]> wrote: >> Being a newb here, I could be way off base, but one of the selling >> points I keep reading for using PyQt and PyKDE are for rapid >> prototyping apps that later get converted to C++. Would getting rid >> of QStrings not impose a greater conversion burd

Re: [PyKDE] QString in PyQt4 - Request for Comments

2005-10-19 Thread Gerard Vermeulen
On Wed, 19 Oct 2005 09:56:27 +0100 Phil Thompson <[EMAIL PROTECTED]> wrote: > > As I've said, I have made that selling point many times - mainly as a sop to > C++ programmers and avoid religious my-language-is-better-than-yours > arguments. However, I don't know of anybody who has actually done

Re: [PyKDE] QString in PyQt4 - Request for Comments

2005-10-19 Thread Phil Thompson
On Wednesday 19 October 2005 8:09 pm, John Layt wrote: > On Wed, 19 Oct 2005 00:17, David Boddie wrote: > > I think that there are two groups of people who expect different things, > > and QString is possibly controversial to many people because it's > > peculiar to see a class that duplicates the

Re: [PyKDE] QString in PyQt4 - Request for Comments

2005-10-19 Thread John Layt
On Wed, 19 Oct 2005 00:17, David Boddie wrote: > I think that there are two groups of people who expect different things, > and QString is possibly controversial to many people because it's peculiar > to see a class that duplicates the functionality of a built-in type. > However, I think that there

[PyKDE] Windows version of eric3 won't start.

2005-10-19 Thread Bjoern Paschen
Hi there. I installed the GPL QT package for windows from the download section of the eric3 homepage and the newest eric3 version 3.7.2 from sf.net. I am running Active Python 2.4.1. Eric throws me an exception when i start eric3.py in the commandline. (eric3.pyw which is started through the icon

Re: [PyKDE] QString in PyQt4 - Request for Comments

2005-10-19 Thread Phil Thompson
On Wednesday 19 October 2005 1:17 am, David Boddie wrote: > On Tue, 18 Oct 2005 18:24:08, Phil Thompson wrote: > > I'm wondering whether QString should be dropped in PyQt4 in order to make > > it more Pythonic. > > On one hand, it sounds like a nice idea. It would mean that you don't > have to thin

Re: [PyKDE] segfault using hasattr on a wrappertype class

2005-10-19 Thread Phil Thompson
On Tuesday 18 October 2005 11:12 pm, Giovanni Bajo wrote: > Phil Thompson <[EMAIL PROTECTED]> wrote: > >> behaviour: > > import sip > > isinstance(sip.wrapper, object) > >> > >> True > >> > > issubclass(sip.wrapper, object) > >> > >> True > >> > >> Dunno if it's related to the fix. > >