Allow to incorporate a path in entries

[HHeda]

Allows to enter entries in the form of {path/entry}, to access entries that are deeper in the tree or in an other branch

[MatthieuDartiailh]

I would likely need to think more about this than I have the bandwidth to ATM. I understand that the access editor may not be the nicest thing to use but it allows to provide a nice autocompletion interface. Could you motivate this change ?

[HHeda]

I modified this to access to the values of a loop outside of this loop. For example, I wanted to do something like this:

loop1

loop2

do something

save {loop1/loop2_loop_values}

Simply asking for {loop2_loop_values} does not work since the save task is not at the same node.

This worked as runtime but I needed to force the enqueue because the entry was not found. I didn't find another way but I might have missed something...

I then thought that starting the path from root could be enabled too, which led me to add a few options in the checks.

Unless I did a mistake, I only added new possible entries (even though they are not auto completed).

[MatthieuDartiailh]

This can be achieved using the database access editor (select this tab and right click the entry you want to promote).

Please note that your solution does have value but I would need more time to consider what side consequences it may have.

[HHeda]

Oh I didn't know this possibility, thank you !