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

MCQ/GMCQ - properties.schema _shouldBeSelected: 'false' is a better default? #1383

Closed
brian-learningpool opened this issue Jan 18, 2017 · 4 comments

Comments

@brian-learningpool
Copy link
Member

It's been mentioned that it might make sense for the _shouldBeSelected property should be defaulted to false rather than true. The rationale for this is that there are generally more false choices than true options.

Any thoughts on this?

@moloko
Copy link
Contributor

moloko commented Jan 18, 2017

Yep makes sense to me.

Also, I have to say having (finally!) started to use the authoring tool a bit more, I'm really preferring the use of the Checkbox input type for Boolean properties like this... Why make the user click twice when one click will do the job?

Actually it would be nice to see an option for a switch control like you get on iOS but appreciate I'm going way off topic now ;-)

@moloko
Copy link
Contributor

moloko commented Jan 18, 2017

Also, I have to say having (finally!) started to use the authoring tool a bit more, I'm really preferring the use of the Checkbox input type for Boolean properties like this... Why make the user click twice when one click will do the job?

Actually it would be nice to see an option for a switch control like you get on iOS but appreciate I'm going way off topic now ;-)

Ah, I see this has already been covered in adaptlearning/adapt_authoring#1380

@brian-learningpool
Copy link
Member Author

@brian-learningpool brian-learningpool self-assigned this Jan 19, 2017
@brian-learningpool
Copy link
Member Author

PRs merged.

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