You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
To work around situations where blueprint APIs don't yet cover features, users can still manually edit blueprint in the viewer and save them. Unfortunately these blueprints still need to be distributed and manually loaded.
We should add a logging API that opens and existing .rbl file, and sends it to the viewer.
@jleibs i was looking for this feature. You first proposed a new logging API which I'd very much like to have.
Then you said this already works using log_file. Can you tell me how?
EDIT: Omg, this is way easier than I thought: docs rr.log_file_from_path(<path_to_rbl>)
To work around situations where blueprint APIs don't yet cover features, users can still manually edit blueprint in the viewer and save them. Unfortunately these blueprints still need to be distributed and manually loaded.
We should add a logging API that opens and existing .rbl file, and sends it to the viewer.
for example:
The text was updated successfully, but these errors were encountered: