External Tox: file paths inside are broken

Relative file paths inside an External Tox are relative to the current project instead of the External Tox. I’ve been trying to create more reusable components using External Toxes, however, this doesn’t work as the assets/images/code inside the External Tox are not portable, even on the same computer. I am trying to build a library of reusable toxes that I can easily drop into any other project. I also don’t want to use absolute paths for obvious reasons so that I can share this with multiple computers and teammates. Right now, unless the tox is completely self contained, it doesn’t work.

Any solution to this?

Thanks TD Community! (first post!)

Edit: Also if anyone have tried or have any tips relating to creating a reusable library. Been using Touch for a year or so now, but I’m just at the very beginning of this new journey and looking for any ideas!

Hi @nopjia

Is your external .tox set to Enabled? This will have no impact if not.
Are you using the Relative File Path Behavior menu?

Can you please share a small zip file showcasing your problem ?

Best,
Michel

Hi Michel,

Thank you! Using those two options made it work. Sorry I kinda just expected the drag and drop to just work and didn’t know about this option!

However, this doesn’t work when drag and drop from the palette. Somehow that has a different behavior where the “External .tox Path” is blanked out. Why is that?

Also why would the “Enable External .tox” option be turned off with drag and drop? It is usually on by default when creating a plain Base from the Dialog.

What components are you referring to ? Clones aren’t externals. If you remove the cloning or turn off the Enable toggle, then it enables the external features. A Master can be external though.

It’s turned off to avoid a potential conflict when drag n dropping a .tox that is set to be relative, to another project, where somehow, a matching file name / path (imagine .py file) can be found but where the content of the file is different.

Point taken though, and we are discussing these UX choices internally.