-
-
Notifications
You must be signed in to change notification settings - Fork 22
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Feature Request: nextScan for MapJS? #402
Comments
Although I'd rather not work on projects we are deprecating, I might take a stab if I'm bored to add support before MapJS is archived. |
MapJS has technically had a variation of this feature since the beginning, it was just something intended for Chuck that wasn't actually implemented :lappy: |
How so?
…On Thu., Oct. 6, 2022, 11:06 a.m. Derick M., ***@***.***> wrote:
MapJS has technically had a variation of this feature since the beginning,
it was just something intended for Chuck that wasn't actually implemented
:lappy:
—
Reply to this email directly, view it on GitHub
<#402 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AFJBRRXNPYCJJRJBMGVBXBLWB3TFRANCNFSM6AAAAAAQ4WOPXI>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
@TurtIeSocks Is referring to this part of MapJS which would sends a payload to a listener (i.e. GoFestController and others) to rescan the IVs and was a basic example of scan on-demand. |
WatWowMap/ReactMap#383
RealDeviceMap/RealDeviceMap#297
Referencing above.
The text was updated successfully, but these errors were encountered: