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

Introduce camera-specific properties and runtime type switching #462

Merged
merged 1 commit into from
Jul 13, 2018

Conversation

tribal-tec
Copy link
Contributor

No description provided.

@tribal-tec tribal-tec force-pushed the camera branch 3 times, most recently from 21a64ff to a129978 Compare July 12, 2018 15:57
, type(_getType<T>())
, _data(value)
, _min(min_)
, _max(max_)
, _min(limits.first)
Copy link
Contributor

Choose a reason for hiding this comment

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

Should it not be just limit and limit.min/limit.max? limits would implies there is a set of limit pairs.

{
auto value = prop.get<T>();
jsonSchema =
staticjson::export_json_schema(&value, &schema.GetAllocator());
Copy link
Contributor

Choose a reason for hiding this comment

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

Could make a const out of schema.GetAllocator()?

Also add enum support (type int with list of strings) to PropertyMap to expose
them property in JSON.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants