You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
First of all, thank you for the work done on cstimer, it's truly a gem.
I use it daily with a Bluetooth cube, and I've noticed something strange.
When I connect my cube with cubeast, the synchronization with the cube is almost instantaneous.
However, with cstimer, the dialog window asking for the MAC address takes several seconds to display.
Additionally, if it were possible to store the MAC address in the browser's local storage, or something similar, so that we don't have to go through the dialog window as often, that would be ideal.
Thank you very much.
The text was updated successfully, but these errors were encountered:
the cube is a Gan 12 UI FreePlay :
BT ID : GAN12uiFp-2EE
I'm using the browser based version on Google Chrome, both on cubeast and cstimer.
Right now, I have just made another test with a Moyu AI v10 (WCU_MY32_A6A7), same issue.
So I don't think it's related to the hardware.
Regards
I'm asking because I'm working on my own timer at CubersDen.com and this is on my list. Currently only supporting gan timer on chrome but I do have setting for user to save in his profile so once the Mac is there you don't have to put it in again, but my project is like a "week old" so long way to go. Gathering all insights I can.
Hello,
First of all, thank you for the work done on cstimer, it's truly a gem.
I use it daily with a Bluetooth cube, and I've noticed something strange.
When I connect my cube with cubeast, the synchronization with the cube is almost instantaneous.
However, with cstimer, the dialog window asking for the MAC address takes several seconds to display.
Additionally, if it were possible to store the MAC address in the browser's local storage, or something similar, so that we don't have to go through the dialog window as often, that would be ideal.
Thank you very much.
The text was updated successfully, but these errors were encountered: