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

Store touchscreen config #169

Merged
merged 4 commits into from Nov 21, 2018
Merged

Store touchscreen config #169

merged 4 commits into from Nov 21, 2018

Conversation

Lu-ni
Copy link
Member

@Lu-ni Lu-ni commented Nov 14, 2018

Each touchscreen need to have his own configuration to work well.

  • Store touch screen configuration in each robot config.

Next step will be to implement touch screen calibration.

@antoinealb
Copy link
Member

Could you document somewhere how those values can be obtained?

parameter_scalar_declare_with_default(&screen.ay, &screen.ns, "ay", 0);
parameter_scalar_declare_with_default(&screen.bx, &screen.ns, "bx", 0);
parameter_scalar_declare_with_default(&screen.by, &screen.ns, "by", 0);
parameter_scalar_declare_with_default(&screen.cx, &screen.ns, "cx", 0);
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Might be better not to have any defaults as the default value of 0. will cause the screen to act in weird ways. I would prefer to have an assert fail.

@Lu-ni
Copy link
Member Author

Lu-ni commented Nov 17, 2018

Tested and working now

@Lu-ni
Copy link
Member Author

Lu-ni commented Nov 19, 2018

Could you document somewhere how those values can be obtained?

Where should I put the file ? A README.md in the gui folder (../src/gui/) ?

@antoinealb
Copy link
Member

Yes I think this would work.

1 similar comment
@antoinealb
Copy link
Member

Yes I think this would work.

@Lu-ni Lu-ni merged commit 9c28bf1 into master Nov 21, 2018
@SyrianSpock SyrianSpock deleted the store-touchscreen-config branch November 21, 2018 20:44
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants