search

Falcosc / locus-addon-tasker

Locus Maps API useable as Tasker Plugin
GNU General Public License v3.0
9 stars 2 forks source link

After rec start intent, it takes 4 seconds until %is_track_rec_recording true #31

Open TapioOfTapiola opened 1 year ago

TapioOfTapiola commented 1 year ago

Hi,

not necessarily an issue. I measured it via a loop; here it takes almost 4 seconds after a record start intent - until "get sensors and stats" returns true for %is_track_rec_recording.

I hate static Waits, but my workaround is to wait 5s after intent, then get sensors.

Do you have a better idea?

Thx

TapioOfTapiola commented 1 year ago

OK, I had a better idea. A goto loop - Repeat "get sensors and stats" + Wait 300ms until %is_track_rec_recording == true, for max. 5 seconds.

TapioOfTapiola commented 1 year ago

Hmm, now there was a situation where recording started, but %is_track_rec_recording false for more than 5 seconds.

There's something fishy going on with Locus and rec Start/Stop intents. They work more reliable if I App Start Locus before.

Falcosc commented 1 year ago

If you care about it, I suggest downgrade the version until you find the broken one to help the locus team to identify the issue.