macOS: Fl::add_timeout() must always create a new timer (#248)
The old version would reschedule an existing timer if a matching timer existed already which was unique to macOS. The new behavior is consistent on all platforms and allows to create multiple timer entries with the same callback and userdata.
This commit is contained in:
parent
87475c20d6
commit
135ba3a7e1
@ -465,18 +465,7 @@ static void do_timer(CFRunLoopTimerRef timer, void* data)
|
||||
|
||||
void Fl_Cocoa_Screen_Driver::add_timeout(double time, Fl_Timeout_Handler cb, void* data)
|
||||
{
|
||||
// check, if this timer slot exists already
|
||||
for (int i = 0; i < mac_timer_used; ++i) {
|
||||
MacTimeout& t = mac_timers[i];
|
||||
// if so, simply change the fire interval
|
||||
if (t.callback == cb && t.data == data) {
|
||||
t.next_timeout = CFAbsoluteTimeGetCurrent() + time;
|
||||
CFRunLoopTimerSetNextFireDate(t.timer, t.next_timeout );
|
||||
t.pending = 1;
|
||||
return;
|
||||
}
|
||||
}
|
||||
// no existing timer to use. Create a new one:
|
||||
// always create a new timer entry
|
||||
fl_intptr_t timer_id = -1;
|
||||
// find an empty slot in the timer array
|
||||
for (int i = 0; i < mac_timer_used; ++i) {
|
||||
|
||||
Loading…
Reference in New Issue
Block a user