Skip to content
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.

Sign up for GitHub

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

Jump to bottom

MultiRange should provide its own component #73

Open
TimPietrusky opened this issue Sep 22, 2018 · 0 comments
Open

MultiRange should provide its own component #73

TimPietrusky opened this issue Sep 22, 2018 · 0 comments
Labels
enhancement
Projects
Next

Comments

@TimPietrusky
Copy link
Member

The different ranges of a MultiRange dmx property should be handled in its own component so that someone can just select it and then put the values inside.

The solution with the title is confusing and you never know what values are expected!
@TimPietrusky TimPietrusky created this issue from a note in Next (To do) Sep 22, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement
Projects
Next
  
To do
Milestone
No milestone
Development

No branches or pull requests
1 participant
@TimPietrusky