Aaron/All,
The following is a typical class call I use for a new Widget with a pixmap.
Can you see anything here that would cause the screen blanking out?
Kevin
___
class dvdWidget (QWidget, Ui_dvdWidget):
def __init__(self, parent = None):
QWidg
On 21.02.08 22:58:00, Aaron Digulla wrote:
> Reinaldo de Carvalho schrieb:
>
> > The objective of this thread is only dont freeze window. No concurrent
> > acccess will happen to GUI components. A have a hundred of methods
> > called by pushButtons or SIGNALs from Qlistview like itemChanged, that
Reinaldo de Carvalho schrieb:
> The objective of this thread is only dont freeze window. No concurrent
> acccess will happen to GUI components. A have a hundred of methods
> called by pushButtons or SIGNALs from Qlistview like itemChanged, that
> manipulate the GUI mainly to populate many QListVie
>
> That's pure chance. Eventually, your app will do something it shouldn't
> and it will "suddenly" break. You simply can't rely that it will be
> stable (even if some things will in fact work).
The objective of this thread is only dont freeze window. No concurrent
acccess will happen to GUI
Reinaldo de Carvalho schrieb:
> Why is possible access GUI from any thread? This seems not to be
> allowed (Phil say "design error") but my application is running
> without problems.
That's pure chance. Eventually, your app will do something it shouldn't
and it will "suddenly" break. You simply c
> Mark's book has a chapter dedicated to threading...
>
> http://www.qtrac.eu/pyqtbook.html
>
> ...or there is the Qt docs...
>
>From http://doc.trolltech.com/4.3/threads.html:
"Note that QCoreApplication::exec() must always be called from the
main thread (the thread that executes main()), not f
On Thursday 21 February 2008, Rafał Zawadzki wrote:
> Thursday 21 February 2008 14:35:50 Phil Thompson napisał(a):
> > On Thursday 21 February 2008, Reinaldo de Carvalho wrote:
> > > "threading" dont have postEvent-like then I must use Qthread?
> >
> > You could use the standard Python Queue and in
On Thursday 21 February 2008, Reinaldo de Carvalho wrote:
> > > QThread can be called with threding "target=" like argument? I will
> > > like start methods from PushButtons without freeze mainWidget when
> > > execute.
> >
> > Just reimplement QThread.run() and call your simulate() function.
>
Thursday 21 February 2008 14:35:50 Phil Thompson napisał(a):
> On Thursday 21 February 2008, Reinaldo de Carvalho wrote:
> > "threading" dont have postEvent-like then I must use Qthread?
>
> You could use the standard Python Queue and in the main thread convert them
> to events and post them locall
>
> > QThread can be called with threding "target=" like argument? I will
> > like start methods from PushButtons without freeze mainWidget when
> > execute.
>
>
> Just reimplement QThread.run() and call your simulate() function.
>
I have one hundred methods called by pushButtons, then a need
On Thursday 21 February 2008, Reinaldo de Carvalho wrote:
> "threading" dont have postEvent-like then I must use Qthread?
You could use the standard Python Queue and in the main thread convert them to
events and post them locally - but using QThread is easier.
> QThread can be called with thredi
* Mark Summerfield [Thu, 21 Feb 2008 11:26:15 +]:
> Aside: AFAIK there is no way to intercept a left-click with
> QSystemTrayIcon; it is a QObject subclass (but not a QWidget subclass)
> so you can't reimplement either mouse or keyboard handlers. So if you
> want interaction it can only be by
"threading" dont have postEvent-like then I must use Qthread?
QThread can be called with threding "target=" like argument? I will
like start methods from PushButtons without freeze mainWidget when
execute.
--
Reinaldo Carvalho
On 2/21/08, Phil Thompson <[EMAIL PROTECTED]> wrote:
> On Thursday
On Thursday 21 February 2008, Reinaldo de Carvalho wrote:
> I solved the problem setting null strig to textLabel1 before start thread:
>
> [...]
>
> def thread_start( self ):
>self.gbox.setEnabled(False)
>self.textLabel1.setText("")
>self.thread1 = threading.Thread(target=self.simulate)
Thursday 21 February 2008 12:26:15 napisałeś(-łaś):
> On 2008-02-21, Rafał Zawadzki wrote:
> > Hello. I am using python-qt4 on kubuntu 7.10.
> >
> > I found a very strange behaviour in the below code:
> >
> > * after exit (choose Quit from menu on systray icon application
> > segfaults)
>
> I don't
I solved the problem setting null strig to textLabel1 before start thread:
[...]
def thread_start( self ):
self.gbox.setEnabled(False)
self.textLabel1.setText("")
self.thread1 = threading.Thread(target=self.simulate)
self.thread1.setDaemon(1)
self.thread1.start()
def simulate( sel
On 2008-02-21, Rafał Zawadzki wrote:
> Hello. I am using python-qt4 on kubuntu 7.10.
>
> I found a very strange behaviour in the below code:
>
> * after exit (choose Quit from menu on systray icon application
> segfaults)
I don't get the segfault using Qt 4.3.3; but there was a problem with Qt
4.3
Hello. I am using python-qt4 on kubuntu 7.10.
I found a very strange behaviour in the below code:
* after exit (choose Quit from menu on systray icon application segfaults)
* showMessage is showed centered on the screen - in class reference it is
connected with systracicon.
I suppose that these
18 matches
Mail list logo
