Potential feature: temporary frames

[balandbal]

If you name a frame to something that start with an underscore, e.g., _my_frame, it will not be exported to the YAML config file, but will still be set in TF and appear in the frame list on the left in the frame editor.

Now,

• this can result in broken config files if I manually set a parent frame to, following the example, _my_frame,
• though I have to type the full frame name in this case as it is not suggested by the editor for auto-completion.
• Also, _my_frame does not appear in the editor on the right, so I can not use the editor for changing parent frames to it, which I suppose is good
• Such "temporary" frames could be useful for, e.g., measuring relative transformations (that's what I used it for)

Should it be made into a feature? That would mean, at the very least either

• preventing the user from setting a "temporary" frame as parent at all, or
• preventing the user from setting a "temporary" frame as parent to a "non-temporary" frame

[lorenz-halt]

The underscore feature is actually intended, however not bug free as you mentioned. At some point in time, pitasc would automatically create temporary (_...) frames in order to work as expected. That was separated from tf a while ago, that actually creating a tf frame is not necessary anymore. Idk, if at least initially defining these frames is needed to make the visualization (option somewhere) work. Nevertheless, being able to see temp-frames in rviz was useful.. About your suggestion, I would prefer the latter. But the first is probably sufficient. Von: Balázs András Bálint ***@***.***> Gesendet: Freitag, 5. Juli 2024 12:16 An: ipa320/rqt_frame_editor_plugin ***@***.***> Cc: Subscribed ***@***.***> Betreff: [ipa320/rqt_frame_editor_plugin] Potential feature: temporary frames (Issue #36) If you name a frame to something that start with an underscore, e.g., _my_frame, it will not be exported to the YAML config file, but will still be set in TF and appear in the frame list on the left in the frame editor. Now, * this can result in broken config files if I manually set a parent frame to, following the example, _my_frame, * though I have to type the full frame name in this case as it is not suggested by the editor for auto-completion. * Also, _my_frame does not appear in the editor on the right, so I can not use the editor for changing parent frames to it, which I suppose is good * Such "temporary" frames could be useful for, e.g., measuring relative transformations (that's what I used it for) Should it be made into a feature? That would mean, at the very least either * preventing the user from setting a "temporary" frame as parent at all, or * preventing the user from setting a "temporary" frame as parent to a "non-temporary" frame — Reply to this email directly, view it on GitHub<#36>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AARDOLMDJQYE6QGIDWDWSJ3ZKZW6RAVCNFSM6AAAAABKM5TOBWVHI2DSMVQWIX3LMV43ASLTON2WKOZSGM4TEMZQGY2TKMQ>. You are receiving this because you are subscribed to this thread.Message ID: ***@***.******@***.***>>