Torsten Maehne

Thanks for reporting this issue! I am not able to reproduce this behaviour on Linux and macOS. So it may be specific to Windows and the used JDK. How did...

I am neither able to reproduce this issue on Debian Trixie in a KDE Plasma 6.3.6 Wayland session using a logisim-evolution DEB package built from HEAD using the `openjdk-21-jdk` package....

Thanks for reporting this issue! Unfortunately, I can confirm that our documentation is outdated (and inconsistent across translations) and doesn't match the current chronogram implementation, which we back-ported from @kevinawalsh...

I can confirm this behaviour, but we unfortunately haven't found yet a way to fix it - see issue #1809.

I cannot reproduce the issue using the native MSI installer, which we [provide](https://github.com/logisim-evolution/logisim-evolution#download) for Windows. Did you maybe try to execute the JAR archive using a too old JRE/JDK? Currently,...

Can you reproduce the issue also with the MSI installer from our [nightly builds](https://github.com/logisim-evolution/logisim-evolution?tab=readme-ov-file#nightly-builds)? Does the error only occur on the command line or also when you launch Logisim-evolution from...

Thanks for this enhancement proposal. PRs in this direction are welcome.

@MinekPo1: The `Probe` component already exists in the `Wiring` library. The goal would be to expose the value displayed in the probe via a dynamic component in the symbol of...

Sorry, but I cannot reproduce your issue with the latest release Logisim-evolution 4.0.0. Your description is too vague. Please, provide step-by-step instructions how to reproduce the issue if possible accompanied...

@peddyjet or @charles-fox: Could you please have a look at this issue, as you contributed this enhancement in PR #2226?