Ohh sorry That = What ? 
Yes, its very tricky to reproduce which is why I’ve yet to make a ticket about it and attach a project. I’ll get around to it when I get the chance.
since here you are using the API 2.0 (xojo.core causes those bugs as far as i know).
Timer.CancellCallLater is the one you need
Timer.CallLater is the right one
I do not recomment Xojo.Core.Timer.* since it’s deprecated.
1 Like
So it would seem Derk, I’ve managed to reproduce it quite easily now using Xojo.Core.Timer.CancelCall but not with Timer.CancelCallLater so it does look like its been stealth “fixed” as I can’t find a feedback report about it in the transition from Xojo.Core.Timer.CancelCall to Timer.CancelCallLater
This is a bit concerning as Geoff said in a recent hangout “Most of these APIs with the exception of Web Framework 2 … are new APIs on top of an existing implementation … in the future when we fix bugs in these implementations in the overwhelming majority of cases that bug will get fixed in the original implementation … and in the new one”.
I hope this isn’t a sign of things to come for those stuck with API 1
I’m doing a careful migration to API2 because I know that API1 residuals will bring problems soon, with the newer OS changes only being introduced in newer libs and APIs, we will start to get a larger gap between the legacy and the current frameworks. Specially in the Apple side of the things.
Whoa, wait. What’s the difference between
Timer.CancelCallLater
and
Timer.CancelCall
?
Timer.CancelCall doesn’t exist?
CancelCallLater
https://documentation.xojo.com/api/language/timer.html#timer-cancelcalllater
CancelCall is not there… where did you get that?
The pseudo code above. We all make mistakes when writing code in the post editor sometimes 
Oh, this is from Xojo.Core.Timer.CancelCall
