Interactive 2D wave optics simulator. Turn any image into a refractive scene, add sources, watch waves refract, diffract and interfere. Probes, intensity maps, video export.
C#
Version 0.1.2: the issue forms set their labels, the problem form's Version is a dropdown of the releases
Alexander Graef469e0fa5229b
diff --git a/.github/ISSUE_TEMPLATE/feature.yml b/.github/ISSUE_TEMPLATE/feature.ymlindex d1cf777..9288ba5 100644--- a/.github/ISSUE_TEMPLATE/feature.yml+++ b/.github/ISSUE_TEMPLATE/feature.yml@@ -18,6 +18,7 @@# The issue form for a feature request: what the user wants to do, the feature as imagined, and how it is done today.name: Feature requestdescription: Something WaveDude Next should be able to do+labels: [enhancement]body:- type: markdownattributes:diff --git a/.github/ISSUE_TEMPLATE/problem.yml b/.github/ISSUE_TEMPLATE/problem.ymlindex dbd02ed..117d38b 100644--- a/.github/ISSUE_TEMPLATE/problem.yml+++ b/.github/ISSUE_TEMPLATE/problem.yml@@ -18,6 +18,7 @@# The issue form for a problem report: what happened, the version, the system information Help > About copies, and the log file.name: Problem reportdescription: Something in WaveDude Next does not work as it should+labels: [bug]body:- type: markdownattributes:@@ -30,12 +31,16 @@ body:description: What you did, what you expected, and what happened instead. A project file or a screenshot helps; drag it into the box.validations:required: true- - type: input+ - type: dropdownid: versionattributes:label: Version- description: In WaveDude Next, open Help > About. The version is the line under the name.- placeholder: 0.1.1 (b904fe4)+ description: In WaveDude Next, open Help > About. The version is the line under the name, the number before the brackets.+ options:+ - 0.1.2+ - 0.1.1+ - 0.1.0+ - Built from source or another versionvalidations:required: true- type: textareadiff --git a/CLAUDE.md b/CLAUDE.mdindex 8369916..ec1a8ab 100644--- a/CLAUDE.md+++ b/CLAUDE.md@@ -118,7 +118,9 @@ harnesses run.`obj\...\win-x64\R2R`, which both profiles share: a publish after a composite one reused the composite's component stubswithout their image, so the EXE died at start with a fail-fast before its first log line (both profiles;`DOTNET_ReadyToRun=0` let it start, which named the cause); that folder would need a clean before every publish. Version in- `Directory.Build.props`; the commit hash lands in About. The license header is the `.editorconfig`+ `Directory.Build.props`; the commit hash lands in About. **A release adds its version to the problem form before its tag**+ (2026-11-05, the user's choice): the Version dropdown in `.github/ISSUE_TEMPLATE/problem.yml` is a fixed list, since GitHub's+ forms cannot read releases, so the new version goes in at the top, in the commit that bumps `Directory.Build.props`. The license header is the `.editorconfig``file_header_template` (its warranty sentence ends in a full stop: Roslyn cuts the value at `;`). LICENSE.md isthe FSF's GPL-3.0 Markdown verbatim, nothing else (GitHub's detector rejects additions); the About dialog showsit as a document built by `Build/Documents.targets`, whose converter `Build/MarkdownToFlowDocument.cs` (an inline@@ -326,8 +328,9 @@ FrameStore: native memory up to the budget, the rest in a temp file (%LOCALAPPDAclick on a window's title bar while a menu or a context menu is open lands** (`MenuClickThrough`, 2026-11-04, theuser's request: the close button had needed a second click): an open menu holds the mouse for Windows too, so thedismissing click arrives as a client click; it is hit-tested with WM_NCHITTEST and, on the caption, the system menu- or a button, posted again as WM_NCLBUTTONDOWN behind the menu's closing; untested by the harnesses, which post no- mouse, the user tries it.+ or a button, posted again as WM_NCLBUTTONDOWN behind the menu's closing; the harnesses post no mouse, so the user+ tested it by hand (2026-11-05: it works, and it is the behaviour he wants, as other applications have it: a click in+ the non-client area while a menu is open closes the menu and still lands, rather than being swallowed).- **Copy, cut, paste, drag and drop** (2026-10-23, the user's choices): `ProjectClipboard` writes sources, parts,probes and schemes (the `INamed` items) and the Scene, Simulation and Display objects as a fragment of their own fileelements, in the app's format and as plain text (read back from text too, so a text editor takes and gives the XML).diff --git a/Directory.Build.props b/Directory.Build.propsindex c9dda02..10f5075 100644--- a/Directory.Build.props+++ b/Directory.Build.props@@ -3,7 +3,7 @@<!-- shared by every project under the repo root: the product version (the SDK appends the commit hash to theinformational version, which Help > About shows shortened) and the names Explorer's file properties show --><PropertyGroup>- <Version>0.1.1</Version>+ <Version>0.1.2</Version><Product>WaveDude Next</Product><Description>A 2D wave simulator</Description></PropertyGroup>diff --git a/README.md b/README.mdindex 76c698b..d9c7de9 100644--- a/README.md+++ b/README.md@@ -70,7 +70,7 @@ dotnet publish WaveDudeNext.WPF\WaveDudeNext.WPF.csproj -p:PublishProfile=Single## Problems-Report problems on the [issue tracker](https://github.com/graealex/WaveDudeNext/issues). The report template asks for the system information, which Help > About copies to the clipboard with one click, and for the log file `WaveDudeNext.WPF.log` from the folder of the program.+Report problems on the [issue tracker](https://github.com/graealex/WaveDudeNext/issues). The report template asks for the version shown in Help > About, for the system information, which the same dialog copies to the clipboard with one click, and for the log file `WaveDudeNext.WPF.log` from the folder of the program. A separate template exists for feature requests there as well.## Credits and license