-
Notifications
You must be signed in to change notification settings - Fork 9
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
Omnibus Launcher #141
Omnibus Launcher #141
Conversation
…us into starting_omnibus
now we listen to all can messages (acts as our interrupt function) and then check if the specified peiod has changed, in which case, send the can message.
…us into starting_omnibus
* Deal with 1920x1080 screen resolution on Wayland * Fix dynamic text for Wayland
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.
Seems to work on Linux.
Reviewed 1 of 1 files at r2, all commit messages.
Reviewable status: complete! all files reviewed, all discussions resolved (waiting on @Andre-The-Greek and @KavinSatheeskumar)
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.
Works on windows.
NOTE: This has been tested on macOS, Linux and Windows
Currently, launching Omnibus is a pain. The core library plus any sources and sinks all need to be started from separate terminals.
New launcher process:
sources
andsinks
folders to get the current onesdashboard
close, CTRL+C or a fatal error, kill all started processThis is an initial launcher design, more features coming in future PRs (log files, multiple source/sink selection, etc.)
This change is