Skip to content
This repository has been archived by the owner on Nov 28, 2019. It is now read-only.

Confusing handling of None #50

Open
ceball opened this issue Jun 23, 2017 · 3 comments
Open

Confusing handling of None #50

ceball opened this issue Jun 23, 2017 · 3 comments

Comments

@ceball
Copy link
Member

ceball commented Jun 23, 2017

Here are some examples - there will likely be more problems than just these.

Displays value of 0 when it's actually None:

screen shot 2017-06-23 at 12 13 47 am

Also note that because dragging doesn't change the value if dropped at the original location, it can be even more confusing:

screencast 2017-06-23 00-27-01

We're not looking to support selecting None as a value in the GUI, but probably None values should be removed by interaction.

@jbednar
Copy link
Member

jbednar commented Jun 23, 2017

Fixing both of these would be great, but the first is probably the priority.

@ceball
Copy link
Member Author

ceball commented Jun 27, 2017

Same for boolean/checkbox:

screen shot 2017-06-27 at 12 01 56 pm

After select and deselect:

screen shot 2017-06-27 at 12 04 53 pm

@ceball
Copy link
Member Author

ceball commented Jul 9, 2017

Range:
screencast 2017-07-09 01-42-01
(although I think if you drag min and max a value gets set)

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

No branches or pull requests

2 participants