-
Notifications
You must be signed in to change notification settings - Fork 72
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
Electron Renderer Process #924
Comments
Based on my limited knowledge about Electron, this is how Electron supports nodejs modules. Please see https://www.electronjs.org/docs/latest/tutorial/process-model#the-main-process |
@KhalilSelyan Hello, may I ask how you dealt with this problem? I encountered the same problem as you |
I moved away from rclnodejs and used ros-foxglove-bridge with ws-protocol both from foxglove |
Hi @KhalilSelyan, how about the performance using ros-bridge? As I understand, the current |
i remember the issues i had with the ros-bridge was that it was slow and couldn't handle big pointcloud messages + other stuff -- i'm working with the autoware software -- although after finding the foxglove rosbridge it was much better at handling all those with barely any lag , still not as perfect as a native connection i would assume but definitely good enough if configured correctly in my opinion, but for your other question i'm not entirely sure how to answer them sorry |
@KhalilSelyan please check with rclnodejs Electron demo just added https://github.com/RobotWebTools/rclnodejs/tree/develop/electron_demo |
Description
It seems as though you can only access rclnodejs on the electron main process (node backend) and not on the frontend the renderer process. Is there any way to get it running directly from the frontend ?
Steps To Reproduce
create a electron project and add rclnodejs and try to access it in the front end
because of electron updates since i believe electron 11 "non context-aware native modules are not allowed"
i need to be able to run the native connection directly from the frontend because of buffering issues when trying to send from main process to renderer process because pointclouds and image messages are too big
Expected Behavior
Actual Behavior
The text was updated successfully, but these errors were encountered: