- there is problem using the webpage UIFLow 2.0 on IOS: it is not possible to create or modify an UI item (it is working on UIFlow 1)...
- more generally, what is the most efficient way to fill a bug report for UIFlow 2.0
The “disable block” option, which is in UIFlow 1.12 web is very convenient, why it is not in UIFLow 2.0 web
Yes I am using Safari on IOS, but I also tried other web browser and with all, it was not possible to create any objet on the UI view of the CoreS3 through the webpage of uiflow 2.0 alpha 20 with latest IOS and Safari on iPad…
On uiflow 1 everything work well on IOS, so I think that is is some coding problem of the webpage of uiflow 2.0
I cannot use the UI design part of uiflow 2.0 (alpha 20) on IOS, while I can do it without any problem with uiflow 1, or uiflow 2.0 on OSX:
It is impossible to create any design element/field on the screen view for the CoreS3
Does anyone has a hint, or is it a functionnality not yet implemented
Hi dev Team,
I made small test on Alpha17:
now "get UTC time" works correctly :)
There is problem when using "Set timezone GMTx":
using "Set timezone GMT+2" and then "get local time", it should return UTC+2/GMT+2 but it return UTC-2/GMT-2
There is still problem with "get system uptime in seconds" which is not adjusted to epoch 2000 and returns a very big value
Thanks, I'll give it a try to unbind, and then will try a rebind
yes it is solved now that MAC address was correctly registered in your server, and the binding process went through correctly, and therefore the burning or UIFLow...
That takes me to a question:
How could I unbind an S3 M5Stack device registered with an account, if I want another person with another account to take on it?
yes I tried,
it seems that UIFlow (based on 1.19.1) doesn't take epoch into account, which is year 2000 in MP 1.19.1 or 1.20.
Apart that there is confusion created on gmtime() and localtime() in UIFlow apis.
Also to mention that in MP 1.20, the returned values from gmtime() and localtime() are not all time reliable (sometimes the ntpserver requested in MP localtime() return what in fact is gmtime()...)