A different way to represent the trace log
Open
simulation
- Dominant language
- Java
- Stars
- 3
- Forks
- 5
- PR merge metrics
- No merged PRs in 30d
Description
A different way to represent the trace log could be more suitable, specifically if the models are bigger than the university example. Bigger models = possibly more locations and clocks which could be overwhelming. It might take a long time to scroll, and if the number of components in the simulation query is big, some text will be missing at the right side of the trace box, resulting in something like L9, ….
A possible fix is when clicking on the trace box a pop-up will be shown with all the information contained in it.
Contributor guide
Assessment
This issue has not been assessed yet.