While I was looking for a way to speed up loading data into a listview, I thought about using one-shot timers to load in batches so the user can see the first batch right away instead of waiting for the full load. This is especially useful when dealing with a lot of data.
But I noticed something that seems off, and I'm not sure if it's an Opus bug, intended behavior, or just an error in my script : After a timer is called repeatedly (given the scenario described above), there comes a point where calling it no longer fires its event. And it stays that way until the command finishes.
Things that make me think it's an Opus issue:
-
If you use a timer with a fixed name, this happens after X calls and that control's event never recovers.
-
If you use a timer without a name and let Opus assign one, it also happens after X calls, but because the control gets a new name each time, it only happens ONCE. After that you can't reproduce the problem anymore.
Could it be that a timer has a limited number of calls or something like that?
Note: I don't have a small test script that reproduces the issue. Since I'm aware that Jon and Leo are too busy to be checking users' scripts, anyone with free time who wants to take a look can DM me and I'll send the code.