-
Notifications
You must be signed in to change notification settings - Fork 3
BREAKING CHANGE upgrade to object link 2.2 #5
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
Conversation
|
|
||
| void OLinkRemote::writeMessage(const std::string msg) | ||
| { | ||
| qDebug() << Q_FUNC_INFO << QString::fromStdString(msg); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
will this slow down the message handling. On every msg we write the whole message out. Should we use maybe later the logging categories? Or remove these logs from code?
|
|
||
| void OLinkRemote::handleMessage(const QString &msg) | ||
| { | ||
| qDebug() << Q_FUNC_INFO << msg; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
samehere. debug on every message
| registry.addSource(testbed1OlinkStructArrayInterfaceService); | ||
|
|
||
| // Use the server. | ||
| registry.removeSource(testbed2OlinkManyParamInterfaceService->olinkObjectName()); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
can the registry remove all sources on destructor?
and make some fixes along the way
use dependecies for libs downloaded from repository instead of copying files
clean up shared folder
add examples - requires adding a namespace modulename::