This one doesn't look fixed yet. I updated kaa.base with the weakref
fix. dischi?
On Wed, 2006-04-19 at 20:02 -0400, Jason Tackaberry wrote:
> Do a keyword query that will yield 0 results:
>
> [EMAIL PROTECTED] ~]$ beacon --monitor --search keywords=asdf
> Query took 0.00084400
Jason Tackaberry wrote:
> Do a monitored artist search (for an artist you have). Say you searched
> for an artist that was in foo.mp3. Now do:
>
>cp foo.mp3 bar.mp3
>
> (Assuming this directory is being monitored.) Notice that bar.mp3
> doesn't get picked up. I think what's happening is tha
On Thu, 2006-04-20 at 09:17 -0400, Jason Tackaberry wrote:
> Python makes this kind of thing really easy too. Just use a generator:
>
> def my_workhorse_func():
>for i in somelist:
> do_complicated_thing(i)
> yield True
>yield False
>
> kaa.signals["idle"].connect(my_workhors
On Thu, 2006-04-20 at 14:24 +0200, Hans Meine wrote:
> It's not an "issue to be solved", it's a features AFAIK. I use that a lot
> (with Qt actually) as a poor man's (and hassle-free!) threading technique, to
> do calculations in the background.
Python makes this kind of thing really easy too.
Hans Meine wrote:
> Hi!
>
> On Wednesday 19 April 2006 17:47, Dirk Meyer wrote:
>> > No need for this. The default largest select sleep time in nf_generic
>> > anyway is 100ms. That's plenty for an idle loop. And that not doing
>> > this would solve the 100% cpu issue.
>>
>> Not for gtk. If you
On Thursday 20 April 2006 14:24, Hans Meine wrote:
> > Not for gtk. If you add something to idle in gtk and don't remove it,
> > you will always use 100% CPU time.
>
> It's not an "issue to be solved", it's a features AFAIK. I use that a lot
> (with Qt actually) as a poor man's (and hassle-free!)
Hi!
On Wednesday 19 April 2006 17:47, Dirk Meyer wrote:
> > No need for this. The default largest select sleep time in nf_generic
> > anyway is 100ms. That's plenty for an idle loop. And that not doing
> > this would solve the 100% cpu issue.
>
> Not for gtk. If you add something to idle in gtk
