You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I agree to follow the Code of Conduct that this project adheres to.
I have searched the issue tracker for a feature request that matches the one I want to file, without success.
Problem Description
I'm using Electron for the scene below: "cloud rendering"
Run a electron instance for a WebGL page, and inject a WebRTC client into the page, then the WebGL rendering result can be lively encoded to video stream, and streaming to a client chrome page.
However, i need to let client's user input events to be remote sent back to server-side electron window instance, but i found Electron's BrowserWindow doesn't provide such api.
Proposed Solution
Add user input events inject api to Browser, such as BrowserWindow.sendInputEvent( event ); to support pass in raw touch{begin/move/end} or mouse{down/move/up} events...
Alternatives Considered
If no such convenient apis, i had to use OS-specific way to do this, which is under investigation now...
Additional Information
No response
The text was updated successfully, but these errors were encountered:
IPC should be possible, since input events in chromium is sent by IPC, but it's usually sent from browser main window to renderer process, not from external to browser window?
Preflight Checklist
Problem Description
I'm using Electron for the scene below: "cloud rendering"
Run a electron instance for a WebGL page, and inject a WebRTC client into the page, then the WebGL rendering result can be lively encoded to video stream, and streaming to a client chrome page.
However, i need to let client's user input events to be remote sent back to server-side electron window instance, but i found Electron's BrowserWindow doesn't provide such api.
Proposed Solution
Add user input events inject api to Browser, such as BrowserWindow.sendInputEvent( event ); to support pass in raw touch{begin/move/end} or mouse{down/move/up} events...
Alternatives Considered
If no such convenient apis, i had to use OS-specific way to do this, which is under investigation now...
Additional Information
No response
The text was updated successfully, but these errors were encountered: