forked from tier4/AWSIM
-
Notifications
You must be signed in to change notification settings - Fork 16
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
Implement traffic control features through UI #11
Labels
type:new-feature
New functionalities or additions, feature requests.
Comments
mozhoku
changed the title
Let user manipulate simulation traffic through UI
Enable user manipulate simulation traffic through UI
Mar 11, 2024
mozhoku
changed the title
Enable user manipulate simulation traffic through UI
Give UI to manipulate simulation traffic through UI
Mar 11, 2024
mozhoku
changed the title
Give UI to manipulate simulation traffic through UI
Give user control over simulation traffic through UI
Mar 11, 2024
Is such traffic control available programmatically? Via ROS topics or using some other way? |
mozhoku
changed the title
Give user control over simulation traffic through UI
Proposal: Enhance Simulation Experience with Traffic Control Options
Mar 11, 2024
Not that I'm aware of. But it should be possible. |
xmfcx
changed the title
Proposal: Enhance Simulation Experience with Traffic Control Options
Implement traffic control features through UI
Mar 11, 2024
Let's skip "Shortcut Key" option for this issue, we can consider hotkeys in an issue dedicated to hotkey management in general. |
xmfcx
added
the
type:new-feature
New functionalities or additions, feature requests.
label
Mar 13, 2024
Changes are merged. Closing this issue. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi!
I'm planning to give users control over traffic via GUI.
Proposed Features
With this, users will have more control over traffic in the runtime.
Please share your thoughts and any suggestions you have. 🤗
The text was updated successfully, but these errors were encountered: