Embedded Displays and Template/Instances handle relative filepaths differently
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 58/100
Research direction
Start by opening the attached minimal example and comparing how an Embedded Display and a Template/Instance resolve file-widget paths. Trace the display path-resolution entry points for both cases; the payload does not name specific files or tests. Done means Template/Instance file paths resolve relative to the sub-display's directory, consistently with Embedded Display behavior.
Written by the indexing model from the issue text.
Description
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.
- Dominant language
- Java
- Stars
- 130
- Forks
- 132
- Avg merge
- 2d 12h
- Merged PRs (30d)
- 22
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- No contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from ControlSystemStudio/phoebus
-
Difficulty 1/5 Under an hour Newbie friendliness 85/100
ControlSystemStudio/phoebus#3998 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
ControlSystemStudio/phoebus#3983 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
ControlSystemStudio/phoebus#3979 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 80/100
ControlSystemStudio/phoebus#3962 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
ControlSystemStudio/phoebus#3865 · 1 comment ·
Maintainers usually reply within 1 day
All issues in ControlSystemStudio/phoebus
Similar issues
-
status: waiting-for-triage
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
spring-projects/spring-framework#37614 ·
Maintainers usually reply within 1 day
-
azure-spring azure-spring-aad Client
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Azure/azure-sdk-for-java#51046 · 1 reaction ·
Maintainers usually reply within 1 day
-
helm-knative-apply.sh fails with Helm 4Possibly taken A pull request linked to this issue is open or already merged. Openarea: triage theme: undefined
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
jhipster/generator-jhipster#35895 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
oracle/graalvm-reachability-metadata#11659 ·
Maintainers usually reply within 1 day