Closed RedCarrottt closed 7 years ago
This bug can be fixed after modularization of app/sys manager and OPEL manager renewal. Since they are the feature of Alpha 3, this issue is better to be handled in Alpha 4(#140).
After internal discussion with @esevan, we recalled that SensorViewer has coupling with every layers in OPEL Manager, App/Sys Framework and Sensor Framework. It is because P2P communication SW stack used in SensorViewer is implemented in old fashion. The SW stack can be replaced with newer sensor API.
Therefore, I will deprecate P2P communication stack coupled with SensorViewer, and replace it with sensor API.
해당 버그는 Alpha 4에서 App/Sys Manager와 OPEL Manager의 구조 개편을 통해 해결할 예정이었습니다만, 당장 Beta 1에서도 SensorViewer가 동작해야 하므로, 임시 방편으로 하드코딩하여 고칠 계획입니다.
Beta 1에서 하드코딩을 통해 버그를 해결하고, Alpha 4에서 OPEL Manager 구조 개편을 하도록 하겠습니다.
일단 Issue #132 가 진행되어야 근본적으로 문제가 해결되지만, 현재 하드코딩으로 일시적으로 해결되었습니다. (PR #161, #162) 따라서 해당 issue를 close합니다.
When opening sensor viewer in OPEL Manager, Bluetooth communication with OPEL device seems to fail.
I guess that the failure occurs in Communication FW NIL, since the failure appeared after all the NILs had been upgraded to Node.js 4.0.0.
After I inspect the code of OPEL Manager, I found that there is a strong coupling between SensorViewer application and OPEL communicator. It can be another reason of the failure.
I think it should be handled in Alpha 2(#99).