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.

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

Many property setters should use dropdowns for their inputs #155

Closed
halatmit opened this issue Nov 2, 2014 · 3 comments
Closed

Many property setters should use dropdowns for their inputs #155

halatmit opened this issue Nov 2, 2014 · 3 comments

Comments

@halatmit
Copy link
Contributor

halatmit commented Nov 2, 2014

There are many examples of properties that can take on specific values. For example,
screen.AlignVertical can take only the arguments: left, center, or right, and the designer provides a dropdown that has only those options. In the blocks, however, the setter takes a numeric input. The user needs to know which number corresponds to the desired value, and the implementation code must check whether the number is legal.

Instead, we could make the setter block use a dropdown for selecting the input.
Implement this system and change the component property code to make use of this.

@halatmit
Copy link
Contributor Author

This is the same as issue #195

@halatmit
Copy link
Contributor Author

Here's another nice use for dropdown blocks in specifying widths and heights:
see
https://groups.google.com/forum/#!topic/mitappinventortest/h6I7RHVW8GU

screen shot 2015-08-14 at 4 16 01 pm

@ewpatton
Copy link
Member

Dropdowns for known sets of property values has been addressed by the helper blocks.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants