When a main display embeds a sub-display that contains a file widget (picture, symbol, display etc.) the main display constructs the path to that file differently depending on whether the sub-display is an Embedded Display or a Template/Instance.
If Embedded Display, the main display interprets the filepath as relative to the sub-display's directory, which is what I would expect.
If Template/Instance, the main display interprets the filepath as relative to the main display's directory, which has undesirable consequences.
See attached minimal example. embedded-test.zip
This comes up in real life for example if a user wants to instantiate multiple copies of motor/motorApp/op/bob/autoconvert/motorx.bob with Template/Instance. The buttons to for example motorx_setup.bob won't work.
When a main display embeds a sub-display that contains a file widget (picture, symbol, display etc.) the main display constructs the path to that file differently depending on whether the sub-display is an Embedded Display or a Template/Instance.
If Embedded Display, the main display interprets the filepath as relative to the sub-display's directory, which is what I would expect.
If Template/Instance, the main display interprets the filepath as relative to the main display's directory, which has undesirable consequences.
See attached minimal example. embedded-test.zip
This comes up in real life for example if a user wants to instantiate multiple copies of motor/motorApp/op/bob/autoconvert/motorx.bob with Template/Instance. The buttons to for example motorx_setup.bob won't work.