On 08/11/06, Jonathan Gordon <[EMAIL PROTECTED]> wrote:
Are you sure?
The problem is with callback owners who dont have thier own threads
(i.e the delayed settings saving). unless the ata thread calls that
callback it wont happen.
Unless its no big deal if settings are not saved on shutdown/usb?
Are you sure?
The problem is with callback owners who dont have thier own threads
(i.e the delayed settings saving). unless the ata thread calls that
callback it wont happen.
Unless its no big deal if settings are not saved on shutdown/usb?
On 08/11/06, Linus Nielsen Feltzing <[EMAIL PROTECTED]>
Jonathan Gordon wrote:
hey,
I'm pretty sure that the idle notify callbacks should be called for
these 2 events.
I'm not. Let the callback owners deal with that.
Linus
Cheers! And thanks for the virtual gallon of Coke *burp*
- Original Message -
From: "Bluechip" <[EMAIL PROTECTED]>
To: ; <[EMAIL PROTECTED]>
Sent: Tuesday, November 07, 2006 12:11 AM
Subject: Fwd: jethead71: *.c
> Just a big hats-off to "jethead71" for a mighty bunch of hard work :-)
>
hey,
I'm pretty sure that the idle notify callbacks should be called for
these 2 events. the problem is whats the best way to do it?
Because there is no way to know which thread gets the event in what
order (I assume this is the case) there could be callbacks putting
events on another threads que
