beacon output is wrong.

[ntfiv]

初めまして。興味深いソフトですので試用させていただきました。
beacon「type」で出力される情報がおかしくなっているようです。
「optional data」に設定すると「type」が出力されるようです。
ご確認をお願いします。

automatic translation
Nice to meet you. This is an interesting software, so I tried it.
It seems that the information output by beacon "type" is not correct.
If you set it to "optional data", the "type" seems to be output.
Please check it.

[zbx1425]

It seems that I accidentally set the arguments in the wrong order.
The software haven't been completely tested, sorry for the inconvenience!
I'll fix it as soon as possible.

For temporary fix, change Line 119 of www/js/lua_generator_bve.js inside installation directory (

BlocklyAts/www/js/lua_generator_bve.js

Line 119 in 8fa58f8

return "function __atsapi_setbeacondata(__atsarg_type, __atsarg_signal, __atsarg_distance, __atsarg_optional)\n";

)
from

  return "function __atsapi_setbeacondata(__atsarg_type, __atsarg_signal, __atsarg_distance, __atsarg_optional)\n";

to:

  return "function __atsapi_setbeacondata(__atsarg_distance, __atsarg_optional, __atsarg_signal, __atsarg_type)\n";

[ntfiv]

Thank you!　I was able to take first aid.

[zbx1425]

New version 1.0.5.2 should fix #1 and #2.
Please check it out when you have time to spare.
If the issues are fixed, you can then close the issues. Thanks a lot!

[ntfiv]

Looks fine to me!　Thank you so much!