Hacktoberfest 2026:维护者为十月标记出来的 issue,仍然开放、适合新手。 浏览 Hacktoberfest issue

Bug in macro replacement in display

未关闭
#3,950 2 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 2 天内回复

还没有人认领这个 Issue。

评估

难度
3/5
预计耗时
1-2 天
新手友好度
40/100
Issue 类型
缺陷
描述清晰度
基本清楚
活跃度
活跃
技术栈
java
领域
desktop

调研方向

Start by reproducing the nested-display case: a parent display passes P=QE1:FX4:, R=Current1:, and a child passes RN=$(R)TSTotal in the same macro list as R. Find where the Phoebus display runtime expands macros for child displays and check whether parameters are substituted in order, so later values see earlier replacements. Done when the plot title resolves to QE1:FX4:Current1:TSTotal and the ADL-converted and native .bob cases behave the same.

由索引模型根据 Issue 内容生成。

描述

codathon discussion

I think I have found a bug in macro replacement in display files. In my case these are files that are converted from medm .adl files, but I think the problem is more general.

I originally saw the problem using the adl converter from Phoebus 4.6.10 and Phoebus display 4.7.3. But I have reproduced it using both the converter and display in Phoebus 6.0.0.

This is an example of the problem.

quadEM.bob loads the related display file NDStats, and passes the macro parameters P=QE1:FX4:, R=Current1:

NDStats.bob loads the related display file NDStatsTimeSeriesPlot, and passes the parameters P=$(P), R=$(R)TS:, RN=$(R)TSTotal

The title of this plot is $(P)$(RN)

Image

After substitution the plot title should thus be QE1:FX4:Current1:TSTotal.

However, it is not. As seen below it is QE1:FX4:Current1:TS:TSTotal.

Image

The reason is clear. This is the screen for the Actions of the menu that calls NDStatsTimeSeriesPlot:

Image

What is happening is that it is not using the original value of R when it builds RN, it is using the modified version from the first line.

I can work around the problem by swapping these 2 lines in the .adl file, so that RN is built before R. But it seems that this should be fixed in the translation or runtime engine.

主要语言
Java
星标
130
派生
132
平均合并
2 天 11 小时
30 天内合并 PR
19

环境准备

  • 没有 Dockerfile 或 Docker Compose 文件
  • 有 Pull Request 模板
  • 没有贡献指南

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

ControlSystemStudio/phoebus 的其他 Issue

查看 ControlSystemStudio/phoebus 的全部 Issue

相似的 Issue

更多 Java Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。