On Saturday 17 February 2007 12:10 am, Danny Pansters wrote:
> On Saturday 17 February 2007 00:18, Phil Thompson wrote:
> > On Friday 16 February 2007 10:54 pm, Danny Pansters wrote:
> > > A little bit better:
> > >
> > > If I use pyldlib_dir = ducfg["LIBPL"] it seems to get the correct path
> > >
On Saturday 17 February 2007 00:18, Phil Thompson wrote:
> On Friday 16 February 2007 10:54 pm, Danny Pansters wrote:
> > A little bit better:
> >
> > If I use pyldlib_dir = ducfg["LIBPL"] it seems to get the correct path
> > (/usr/local/lib/python2.4/config/python2.4.a).
>
> Try with tonight's sna
On Friday 16 February 2007 10:54 pm, Danny Pansters wrote:
> A little bit better:
>
> If I use pyldlib_dir = ducfg["LIBPL"] it seems to get the correct path
> (/usr/local/lib/python2.4/config/python2.4.a).
Try with tonight's snapshot which has now been fully ported to Mac and
Windows. I don't run
A little bit better:
If I use pyldlib_dir = ducfg["LIBPL"] it seems to get the correct path
(/usr/local/lib/python2.4/config/python2.4.a).
But still, after that:
desktop# make
`QtCore.so' is up to date.
`QtGui.so' is up to date.
`QtNetwork.so' is up to date.
`QtOpenGL.so' is up to date.
`QtSql.
The image is probably being cached.
If you replace
doc = document % os.path.join(os.getcwd(), 'title.png')
with
doc = document % os.path.join(os.getcwd(),
'title.png?test='+str(time.time()))
in the khtml part.
It should work the way you want. Atleast it does for me.
Joseph Rawson wrote:
> sel
On 16.02.07 16:36:34, Giovanni Bajo wrote:
> On 2/16/2007 3:28 PM, Marcos Dione wrote:
>
> >>> QtCore.QObject.connect( QtCore.SIGNAL("whateveritscalled()"),
> >>> self.yourSlot)
> >> Er, I get a lot of stacktraces over that line because I always forget the
> >> first argument to SIGNAL:
> >>
> >>
On 2/16/2007 3:28 PM, Marcos Dione wrote:
>>> QtCore.QObject.connect( QtCore.SIGNAL("whateveritscalled()"),
>>> self.yourSlot)
>> Er, I get a lot of stacktraces over that line because I always
forget the
>> first argument to SIGNAL:
>>
>> QtCore.QObject.connect( theobjectemittingthesignal,
>> Q
On Fri, Feb 16, 2007 at 03:16:38AM -0600, Dave Fancella wrote:
> > QtCore.QObject.connect( QtCore.SIGNAL("whateveritscalled()"),
> > self.yourSlot)
>
> Er, I get a lot of stacktraces over that line because I always forget the
> first argument to SIGNAL:
>
> QtCore.QObject.connect( theobjectemitt
> QtCore.QObject.connect( QtCore.SIGNAL("whateveritscalled()"),
> self.yourSlot)
Er, I get a lot of stacktraces over that line because I always forget the
first argument to SIGNAL:
QtCore.QObject.connect( theobjectemittingthesignal,
QtCore.SIGNAL("whateveritscalled()"), self.yourSlot)
So it's:
On Friday 16 February 2007 1:43 am, Ritesh Raj Sarraf wrote:
> In QT4 designer, I don't see a way to add custom slots of my own. All that
> I see is a set of predefined slots. There isn't any option to add a custom
> slot there.
You can't. And it's probably better that way. Instead, you need to
Hi,
On Feb/16/2007, Ritesh Raj Sarraf wrote:
> In QT4 designer, I don't see a way to add custom slots of my own. All
> that I see is a set of predefined slots. There isn't any option to add
> a custom slot there.
as far as I know: no
But I was explaining how you can do the same easily: using "
Carles Pina i Estany wrote:
>
> Hi,
>
> On Feb/15/2007, Miguel Lobo wrote:
>
>> Have you already looked at the Qt4 Designer documentation at
>> http://doc.trolltech.com/4.2/designer-manual.html ?
>
> And usually, I am using the auto-connect name way. Even less work than
> qt3 :-)
>
Sorry if
12 matches
Mail list logo
