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

add khronos object bindings #15

Merged
merged 2 commits into from
Aug 14, 2024
Merged

Conversation

Schmluk
Copy link
Contributor

@Schmluk Schmluk commented Aug 14, 2024

  • Adds python bindings for Khronos attributes.

@Schmluk Schmluk requested a review from nathanhhughes August 14, 2024 22:12
Copy link
Collaborator

@nathanhhughes nathanhhughes left a comment

Choose a reason for hiding this comment

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

LGTM!

Comment on lines 162 to 167
.def_readwrite("trajectory_timestamps",
&KhronosObjectAttributes::trajectory_timestamps)
.def_readwrite("trajectory_positions",
&KhronosObjectAttributes::trajectory_positions)
.def_readwrite("dynamic_object_points",
&KhronosObjectAttributes::dynamic_object_points)
Copy link
Collaborator

Choose a reason for hiding this comment

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

For future reference: these might be better as read-only (or opaque bindings). Otherwise there can be some weirdness with setting them on the python side and not seeing them on the c++ side (see here)

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Thanks for the pointer! Making these readonly for now, can reconsider in the future if we needed write access for some reason.

@Schmluk Schmluk merged commit e03d875 into develop Aug 14, 2024
4 checks passed
@Schmluk Schmluk deleted the feature/khronos_attrs_bindings branch August 14, 2024 22:59
nathanhhughes pushed a commit that referenced this pull request Dec 12, 2024
* add khronos object bindings

* make complex types readonly for safety for now
nathanhhughes pushed a commit that referenced this pull request Dec 12, 2024
* add khronos object bindings

* make complex types readonly for safety for now
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.

2 participants