DSP Robotics Support

It continues from here:
viewtopic.php?f=2&t=1741&start=160#p9038

While SM/FS can deal with relative filepaths directly, there is a problem with triggers. Or at least there was, when we worked on it with Trog, long time ago in SM age. Anyway, the solution to avoid "relative vs absolute" issues - was to provide fixed absolute path. Then triggers worked correctly. But how to do this if you prefer to move your file here and there?

Well - there is a primitive called "start folder". While when working with schematics - it shows "pass through" path you provide via input string, in exported files - it shows the path where exported file is physically located. Your input string is blocked. Below are few examples. Export it, move the file around the folders, run it, and see where the path leads.

*

And now the bad news. There is a primitive, that should show paths to your schematics. For some reason - sometimes it works, sometimes - not. When I started to put together things - it showed the path, but few FS restarts later - it no longer works on my machine. Moving the schematic somewhere else is not helping, modifying is not helping, modifying and reloading is not helping, so there seems to be some sort of bug.

If it would work, then you could use it to provide the absolute path to your schematic, and that path would follow your schematic. And it would not interfere with "start folder".

*

In the next post - I will wire for you some trigger work for loading files and acting when file isn't there.

So here it is.

In order to know, whether there is a file or not - you don't need to check the folders. You also don't need to use that trigger "on done". Either you get the output or not.

Before exporting - reload and save it at least once, without external file, or trigger emptying the string, so that you don't have the content inside the schematics buffer.

Tell me how it works on your systems.

p.s.: check it on exported files only.

...and small update to first post.

1) in exported files, "start folder" primitive sends a trigger on load.
2) in exported files, it passes through other incoming triggers, but not strings. It keeps the file path.