Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[KISEMA-1329] For SCChart simulation with induced data flow, show state of registers #48

Open
fabianheyer opened this issue May 11, 2022 · 0 comments
Assignees
Labels
enhancement New feature or request jira Legacy issues migrated from old KISEMA Jira

Comments

@fabianheyer
Copy link

[Issue KISEMA-1329 migrated from JIRA, first reported on 2017-09-09]

Consider for example the attached simulation screen shot. Wouldn't it be cool if the After1/2/3 registers would indicate their content? This could be done with e.g. "0" or "1". Even better, make these bold and red when they change, analogous to the indication of states that are freshly entered.

DelayFor3-rvh sct

[Andreas Stange (Inactive)] added a comment - [10/Oct/17 1:49 PM]
The value of internal variables (as well as inputs/outputs of the SCChart) can be viewed in the new simulation in the data pool view. The state of Abort1/2/3 would be displayed as true / false in the new data pool view.

Highlighting variables in the diagram when the value changes would also be possible I guess. However, I don't think that this is always desired for all variables. Maybe one could tick the variables in the data pool view that should be watched and highlighted.

ssm[ Steven Smyth] added a comment - [21/Nov/17 3:55 PM]

I think this is more of an pragmatics nice-to-have feature. As Andreas said, the data is available in the simulation data pool. I'm assigning this to Nis.

nbw[ Nis Boerge Wechselberg (Inactive) added a comment - [21/Nov/17 4:02 PM]

I assume this ties into the same visualization part, that is also used for the live values on guards, doesn't it?

@fabianheyer fabianheyer added enhancement New feature or request jira Legacy issues migrated from old KISEMA Jira labels May 11, 2022
@fabianheyer fabianheyer self-assigned this Jun 21, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request jira Legacy issues migrated from old KISEMA Jira
Projects
None yet
Development

No branches or pull requests

1 participant