AEXÍúA»êà´AEXÍúɽ¿Í¼ÊµÄ¢Ü·
±ÌA'AE®'
(http://www.pwblog.com/user/xru01/syusyoku/)ÍÀåïÌwÍÅÍæèØé±Æª¢ïƾíêĢܷB
ÄAAJÌTuvCðçØèÉø«N±³ê½¡ñÌsµA»ê±»NÔÉí½ÁÄA¢EoÏÉCpNgð^¦±¯éÅ
David Boddie wrote:
> You can either construct some sort of event handling mechanism or use
> signals and slots. Personally, I'd use signals and slots for this, if
> possible.
>
> The idea would be to set up a connection between your callback code and
> the status bar's showMessage() slot. Then y
On Sun Nov 25 15:22:24 CET 2007, Alexander Tuchacek wrote:
> i try to adress an qt object
>
> self.statusbar.showMessage("rtt %s" % (n.rtt))
>
> in an callback function, comming from a shared lib importet by ctypes, on
> osx this works wonderfull
>
> when i run the same code on linux (ubu
Alexander Tuchacek wrote:
> i try to adress an qt object
>
> self.statusbar.showMessage("rtt %s" % (n.rtt))
>
> in an callback function, comming from a shared lib importet by
> ctypes, on osx this works wonderfull
>
> when i run the same code on linux (ubuntu gutsy), i get this core
> dump,
hallo,
i try to adress an qt object
self.statusbar.showMessage("rtt %s" % (n.rtt))
in an callback function, comming from a shared lib importet by ctypes, on
osx this works wonderfull
when i run the same code on linux (ubuntu gutsy), i get this core dump, ok,
i understand that the problem
