-
Notifications
You must be signed in to change notification settings - Fork 373
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
Shared recordings 2: exposing recording_id
in C and C++ SDKs
#4384
Conversation
d1d9f72
to
d21853c
Compare
dc5774d
to
bf3ea21
Compare
d21853c
to
376df07
Compare
bf3ea21
to
157b0ca
Compare
Windows fails with Please bless me with you knowledge @Wumpf 🧘 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
almost :)
d788b73
to
c4688be
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
perfect!
We already exposed a way of configuring the `StoreId`, but this is an internal concept that we have never communicated anywhere and is very likely to be unstable as the way we do blueprint recordings evolve (also it's been known to confuse users). This adds a simple, straightforward way of configuring the `recording_id`, akin to what we have in the Python SDK. --- Part of a PR series to fix #4055 once and for all: - #4383 - #4384 - #4385
What the title says. Rendered: ![image](https://github.com/rerun-io/rerun/assets/2910679/1734fdcf-7bc4-4521-91f8-f906610cf974) --- Part of a PR series to fix #4055 once and for all: - #4383 - #4384 - #4385
What the title says.
Part of a PR series to fix #4055 once and for all:
recording_id
in Rust SDK #4383recording_id
in C and C++ SDKs #4384Checklist