Public report of Taiizor/ReaLTaiizor, published 17 November 2026. It has the same score, grades and number of
findings as the full report. The details of security findings (where they are in the code, which known
vulnerabilities and which passwords or keys were found) are left out, so nobody can use them against the project.
Public
Executive reportMeasured under the Code Assurance Index, an open standard for code quality, using its published scoring rules (rubric version 2026.11.4). Assert signed this survey and filed it in the standard's public register, where anyone can look it up by its survey ID. Check this survey →
Signed and filed in the standard's public register, 17 November 2026, 06:41 UTC · Survey ID cd_1f13914bd10f4006ba9ee33ca5c9e4be
Taiizor/ReaLTaiizor
Measured 17 November 2026, 06:39 UTC, at code version 2b72501
Boundary Type-Coupling is not measured: Bounded contexts not declared.
Supply-chain provenance & signing is not measured: Supply-chain provenance is not scored (this pipeline releases no artifact), but its build steps or GitHub Actions workflows have integrity defects, or nothing watches its dependency set for published advisories.
CAI scoreWeak
CriticalWeakAdequateStrongExemplary
The score is built from these lenses. Each lens grades one area of the code, such as how easy it is to change or how well it is protected. The weakest lens counts most, so one weak area pulls the score down instead of being averaged away.
A large codebase: 123,511 lines of product code in 202 projects, tests not counted · Estimated rebuild effort: about 1.7 person-years · Weakest lens: Security and Compliance, 36.4
Findings by how serious they are
104 critical1034 serious148 minor
7 dimensions are left out of the score. For each one, we either couldn't measure it in this code, or found no evidence of the safeguard we look for, such as a tested backup restore. They count neither for nor against the score, and Limitations lists each one with its reason.
This survey was produced by
Canine Code Analyzer
Producer
Canine Development
Analyzer
Canine Code Analyzer engine 1.0.0
Measured
17 November 2026, 06:39 UTC
A measurement, not a certificate. The Code Assurance Index records a number
together with the evidence it was worked out from, so anyone can recalculate it, but it doesn't certify or guarantee
the code. The standard was written by Canine Development, which also builds the Canine Code Analyzer. It is open to any tool that
implements it, and today the Canine Code Analyzer is the only one that does.
The score is deterministic, which means the same code always gets the same score. We work it out with tools that follow published rules, and an AI model never decides it, so anyone who applies the same rules to the same code gets the same number. How it is done is explained under Methodology ▸
52of 52 dimensions measured by tools.
1281of 1286 findings point to an exact file and line, so you can open each one in the code. The other 5 concern the repository as a whole, such as missing documentation.
52dimensions across 6 lenses, read from 123,511 lines of product code in 202 projects.
Taiizor/ReaLTaiizor falls short of our standard for production because we found no encryption of stored data, no key vault and no enforced HTTPS. It scores 44.5 out of 100 and is rated Weak, and 12 of its 104 critical findings are security problems.
Security and Compliance, at 36.4, is the weakest lens and counts most in the score. The best first step is encrypting the sensitive stored data and keeping its keys in a vault, worth about 7.8 points. Fixing the silenced warnings comes next, worth about 3.2 points. Raising Security and Compliance to 70 would lift the score to about 51.4.
Ten pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. One automatic update takes new releases before a bad one can be spotted, and fifty errors are caught and ignored, so failures can go unnoticed. Pinning each tool to an exact version, setting a waiting period for automatic updates and handling or logging the ignored errors would close these risks. Fixing the weaknesses the scanner points to would fix the security weakness in the code. The 36 data fields that are written but never read need removing.
The product code is 123,511 lines, about €250,000 to rebuild. The check for known security holes in its packages couldn't finish, so that result is missing, not a clean pass.
A lens is capped at Adequate while one of its dimensions scores below 4 out of 10, however well the rest of the lens does. That way a serious problem in one place always shows in the lens's rating.
How the score is built: what each lens counts forThe lenses don't count equally. The weakest lens counts most, the next weakest a little less, and so on, so a weak area pulls the score down instead of being averaged away. In the bar below, each part's width shows how much that lens counts and its colour shows its rating. Improving the widest part moves the score most, and as that lens improves, it counts for less, because another lens becomes the weakest.
If Security and Compliance rose from 36.4 to 70, the lowest score rated Strong, the score would rise from 44.5 to about 51.4.
Code composition: what the lines of code are
Business logic 28%Supporting code 47%Generated by tools 26%
Rebuild cost: about €250,000 · Estimate
Cost to rebuild
€83,000 to €430,000, for 1,384 to 4,483 hours of work, about 1.7 person-years for 1 to 4 engineers
Difficulty of the problem
Standard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write.
Quality factor
×0.7 at a score of 45. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it.
Size
Large: 123,511 lines of product code
Comment lines
The estimate prices 119,401 lines. Comment lines count towards the size of 123,511 lines but aren't priced as work.
What it is not
Not a quotation: nobody has offered to build it for that. Not a valuation: it says nothing about what the business is worth. Not a certified figure: no professional has signed it as one.
How the estimate is made: We price the hours a team would need to write this code again, at €60 to €95 an hour. Declarations and boilerplate are priced at a fast rate and logic at a slower one, and the logic is then multiplied by the difficulty of the problem and by the quality factor. The estimate can be about 30% off either way, and it moves most with the hourly rate and the difficulty.
Top priorities
The three actions that raise the score most for the work they take. The full ranked list is in the Roadmap.
1
Encrypt sensitive data at rest (ASP.NET Core Data Protection / column encryption) and manage keys in a vault.
Skip if delegated to infra (Postgres TDE, KMS, etc.).
Raises the score by about 7.8 points · Medium effort · Data Protection
2
Resolve the 2 NoWarnInCsproj finding(s) in Explicit Debt — start with ReaLTaiizor.csproj (2).
Raises the score by about 3.2 points · Low effort · Explicit Debt
3
Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED.
Each conclusion below combines several dimensions into one point that no single dimension shows, and lists the measurements it rests on.
Where the investment is most exposed · Value at risk
This code would cost about €250,000 to build again, about 1.7 person-years of work. Its weakest lens is Security and Compliance, at 36.4 (Weak). Security and Compliance is about how well the product is protected, and how it handles personal data. Because the weakest lens counts most in the score, work on Security and Compliance also moves the score most.
Based on: the rebuild estimate · the Security and Compliance grade · how much each lens counts
What to do: Start with the Security and Compliance actions in Top priorities.
If you do one thing first · First action
Encrypt sensitive data at rest (ASP.NET Core Data Protection / column encryption) and manage keys in a vault. Of all the actions in this report, it raises the score most for the work it takes: about 7.8 points for medium effort. The next survey will show the change in the score.
Based on: the ranked actions in Top priorities, by score gain and effort
What hard-to-read code costs each year · Cost
Four dimensions measure how easy the code is to work in: two measure how tangled its logic is, one how much of it is copied, and one how well each part sticks to a single job. In this codebase they average 6.5 out of 10. Code at that level is slower to change than clean code, and we estimate the extra work at 4% to 8% on every change. The history of the code shows how much it changes: about 416 lines over the last 90 days, which is about 1,687 lines a year. At that pace, the extra work comes to an estimated 0.2 to 0.9 engineer-days a year, and it grows as more code changes.
How this is estimated: The number of changed lines is measured from the history of the code. The rest rests on two assumptions of our own: code scoring 8 out of 10 or more adds no extra work, and each point below 8 adds 2.5% to 5.6% to every change, never less than 2% to 5% and never more than 40% to 60% in all; and an engineer changes 150 to 400 lines in a day. The result is a range for planning, not a measurement.
Based on: Cyclomatic Complexity · Cognitive Complexity · Code Duplication · Cohesion (LCOM4) · the code's change history
What to do: Start with the files listed under Churn × Complexity Hotspots, which change often and are hard to read, because that is where the extra work is paid most often.
Architecture — bounded-context dependency graph
Each box is a bounded context (its layer projects grouped, or a project count when large); arrows show dependencies between contexts. A shared kernel is where many arrows converge.
Architecture: which parts of the code depend on which
The code is divided into modules, groups of code that each handle one part of the product, and a module depends on another when it uses code from it. The table lists the modules both down the side and across the top, in an order where each module should only use modules listed above it. A number in a cell means the module on that row uses the module in that column, and it counts the pairs of building blocks (types) that connect them. The one thing to look for is a mark above the diagonal line. It means two or more modules use each other in a loop (a dependency cycle), so none of them can be changed, tested or released on its own.
57 modules, with 114 dependencies between them. 2 loops run through 15 of the modules, marked above the diagonal.
The table shows the 40 modules with the most connections; 17 more are left out to keep it readable.
Which modules use which. The module on each row uses the module in each column, and the number counts the pairs of types that connect them. A cell above the diagonal is part of a loop.
ReaLTaiizor.Animate.Metro uses ReaLTaiizor.Enum.Metro, so a change to ReaLTaiizor.Enum.Metro can break ReaLTaiizor.Animate.Metro, while a change to ReaLTaiizor.Animate.Metro can't break ReaLTaiizor.Enum.Metro.
Position
Below the diagonal: ReaLTaiizor.Animate.Metro uses a module listed above it, which is the healthy direction.
ReaLTaiizor.Animate.Poison uses ReaLTaiizor.Enum.Poison, so a change to ReaLTaiizor.Enum.Poison can break ReaLTaiizor.Animate.Poison, while a change to ReaLTaiizor.Animate.Poison can't break ReaLTaiizor.Enum.Poison.
Position
Below the diagonal: ReaLTaiizor.Animate.Poison uses a module listed above it, which is the healthy direction.
ReaLTaiizor.Child.Crown uses ReaLTaiizor.Enum.Crown, so a change to ReaLTaiizor.Enum.Crown can break ReaLTaiizor.Child.Crown, while a change to ReaLTaiizor.Child.Crown can't break ReaLTaiizor.Enum.Crown.
Position
Below the diagonal: ReaLTaiizor.Child.Crown uses a module listed above it, which is the healthy direction.
12→25 ReaLTaiizor.Child.Crown uses ReaLTaiizor.Controlspart of a loop✕
Connections
2 pairs of types, where a type in ReaLTaiizor.Child.Crown uses a type in ReaLTaiizor.Controls.
ReaLTaiizor.Child.Crown uses ReaLTaiizor.Controls, so a change to ReaLTaiizor.Controls can break ReaLTaiizor.Child.Crown, while a change to ReaLTaiizor.Child.Crown can't break ReaLTaiizor.Controls.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
12→28 ReaLTaiizor.Child.Crown uses ReaLTaiizor.Formspart of a loop✕
Connections
1 pair of types, where a type in ReaLTaiizor.Child.Crown uses a type in ReaLTaiizor.Forms.
ReaLTaiizor.Child.Crown uses ReaLTaiizor.Forms, so a change to ReaLTaiizor.Forms can break ReaLTaiizor.Child.Crown, while a change to ReaLTaiizor.Child.Crown can't break ReaLTaiizor.Forms.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
ReaLTaiizor.Docking.Crown uses ReaLTaiizor.Enum.Crown, so a change to ReaLTaiizor.Enum.Crown can break ReaLTaiizor.Docking.Crown, while a change to ReaLTaiizor.Docking.Crown can't break ReaLTaiizor.Enum.Crown.
Position
Below the diagonal: ReaLTaiizor.Docking.Crown uses a module listed above it, which is the healthy direction.
13→21 ReaLTaiizor.Docking.Crown uses ReaLTaiizor.Nativepart of a loop✕
Connections
2 pairs of types, where a type in ReaLTaiizor.Docking.Crown uses a type in ReaLTaiizor.Native.
ReaLTaiizor.Docking.Crown uses ReaLTaiizor.Native, so a change to ReaLTaiizor.Native can break ReaLTaiizor.Docking.Crown, while a change to ReaLTaiizor.Docking.Crown can't break ReaLTaiizor.Native.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
13→25 ReaLTaiizor.Docking.Crown uses ReaLTaiizor.Controlspart of a loop✕
Connections
1 pair of types, where a type in ReaLTaiizor.Docking.Crown uses a type in ReaLTaiizor.Controls.
ReaLTaiizor.Docking.Crown uses ReaLTaiizor.Controls, so a change to ReaLTaiizor.Controls can break ReaLTaiizor.Docking.Crown, while a change to ReaLTaiizor.Docking.Crown can't break ReaLTaiizor.Controls.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
13→28 ReaLTaiizor.Docking.Crown uses ReaLTaiizor.Formspart of a loop✕
Connections
1 pair of types, where a type in ReaLTaiizor.Docking.Crown uses a type in ReaLTaiizor.Forms.
ReaLTaiizor.Docking.Crown uses ReaLTaiizor.Forms, so a change to ReaLTaiizor.Forms can break ReaLTaiizor.Docking.Crown, while a change to ReaLTaiizor.Docking.Crown can't break ReaLTaiizor.Forms.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
ReaLTaiizor.Drawing.Poison uses ReaLTaiizor.Enum.Poison, so a change to ReaLTaiizor.Enum.Poison can break ReaLTaiizor.Drawing.Poison, while a change to ReaLTaiizor.Drawing.Poison can't break ReaLTaiizor.Enum.Poison.
Position
Below the diagonal: ReaLTaiizor.Drawing.Poison uses a module listed above it, which is the healthy direction.
ReaLTaiizor.Nerator.CS uses ReaLTaiizor.Enum.Poison, so a change to ReaLTaiizor.Enum.Poison can break ReaLTaiizor.Nerator.CS, while a change to ReaLTaiizor.Nerator.CS can't break ReaLTaiizor.Enum.Poison.
Position
Below the diagonal: ReaLTaiizor.Nerator.CS uses a module listed above it, which is the healthy direction.
16→18 ReaLTaiizor.Properties uses ReaLTaiizor.Child.Poisonpart of a loop✕
Connections
1 pair of types, where a type in ReaLTaiizor.Properties uses a type in ReaLTaiizor.Child.Poison.
ReaLTaiizor.Properties uses ReaLTaiizor.Child.Poison, so a change to ReaLTaiizor.Child.Poison can break ReaLTaiizor.Properties, while a change to ReaLTaiizor.Properties can't break ReaLTaiizor.Child.Poison.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
ReaLTaiizor.Util uses ReaLTaiizor.Enum.Poison, so a change to ReaLTaiizor.Enum.Poison can break ReaLTaiizor.Util, while a change to ReaLTaiizor.Util can't break ReaLTaiizor.Enum.Poison.
Position
Below the diagonal: ReaLTaiizor.Util uses a module listed above it, which is the healthy direction.
17→19 ReaLTaiizor.Util uses ReaLTaiizor.Colorspart of a loop✕
Connections
1 pair of types, where a type in ReaLTaiizor.Util uses a type in ReaLTaiizor.Colors.
ReaLTaiizor.Util uses ReaLTaiizor.Colors, so a change to ReaLTaiizor.Colors can break ReaLTaiizor.Util, while a change to ReaLTaiizor.Util can't break ReaLTaiizor.Colors.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
ReaLTaiizor.Child.Poison uses ReaLTaiizor.Localization.Poison, so a change to ReaLTaiizor.Localization.Poison can break ReaLTaiizor.Child.Poison, while a change to ReaLTaiizor.Child.Poison can't break ReaLTaiizor.Localization.Poison.
Position
Below the diagonal: ReaLTaiizor.Child.Poison uses a module listed above it, which is the healthy direction.
ReaLTaiizor.Child.Poison uses ReaLTaiizor.Properties, so a change to ReaLTaiizor.Properties can break ReaLTaiizor.Child.Poison, while a change to ReaLTaiizor.Child.Poison can't break ReaLTaiizor.Properties.
Position
Below the diagonal: ReaLTaiizor.Child.Poison uses a module listed above it, which is the healthy direction.
18→25 ReaLTaiizor.Child.Poison uses ReaLTaiizor.Controlspart of a loop✕
Connections
2 pairs of types, where a type in ReaLTaiizor.Child.Poison uses a type in ReaLTaiizor.Controls.
ReaLTaiizor.Child.Poison uses ReaLTaiizor.Controls, so a change to ReaLTaiizor.Controls can break ReaLTaiizor.Child.Poison, while a change to ReaLTaiizor.Child.Poison can't break ReaLTaiizor.Controls.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
ReaLTaiizor.Colors uses ReaLTaiizor.Util, so a change to ReaLTaiizor.Util can break ReaLTaiizor.Colors, while a change to ReaLTaiizor.Colors can't break ReaLTaiizor.Util.
Position
Below the diagonal: ReaLTaiizor.Colors uses a module listed above it, which is the healthy direction.
ReaLTaiizor.Interface.Poison uses ReaLTaiizor.Enum.Poison, so a change to ReaLTaiizor.Enum.Poison can break ReaLTaiizor.Interface.Poison, while a change to ReaLTaiizor.Interface.Poison can't break ReaLTaiizor.Enum.Poison.
Position
Below the diagonal: ReaLTaiizor.Interface.Poison uses a module listed above it, which is the healthy direction.
ReaLTaiizor.Interface.Poison uses ReaLTaiizor.Drawing.Poison, so a change to ReaLTaiizor.Drawing.Poison can break ReaLTaiizor.Interface.Poison, while a change to ReaLTaiizor.Interface.Poison can't break ReaLTaiizor.Drawing.Poison.
Position
Below the diagonal: ReaLTaiizor.Interface.Poison uses a module listed above it, which is the healthy direction.
20→32 ReaLTaiizor.Interface.Poison uses ReaLTaiizor.Managerpart of a loop✕
Connections
3 pairs of types, where a type in ReaLTaiizor.Interface.Poison uses a type in ReaLTaiizor.Manager.
ReaLTaiizor.Interface.Poison uses ReaLTaiizor.Manager, so a change to ReaLTaiizor.Manager can break ReaLTaiizor.Interface.Poison, while a change to ReaLTaiizor.Interface.Poison can't break ReaLTaiizor.Manager.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
ReaLTaiizor.Native uses ReaLTaiizor.Enum.Crown, so a change to ReaLTaiizor.Enum.Crown can break ReaLTaiizor.Native, while a change to ReaLTaiizor.Native can't break ReaLTaiizor.Enum.Crown.
Position
Below the diagonal: ReaLTaiizor.Native uses a module listed above it, which is the healthy direction.
ReaLTaiizor.Native uses ReaLTaiizor.Docking.Crown, so a change to ReaLTaiizor.Docking.Crown can break ReaLTaiizor.Native, while a change to ReaLTaiizor.Native can't break ReaLTaiizor.Docking.Crown.
Position
Below the diagonal: ReaLTaiizor.Native uses a module listed above it, which is the healthy direction.
21→28 ReaLTaiizor.Native uses ReaLTaiizor.Formspart of a loop✕
Connections
1 pair of types, where a type in ReaLTaiizor.Native uses a type in ReaLTaiizor.Forms.
ReaLTaiizor.Native uses ReaLTaiizor.Forms, so a change to ReaLTaiizor.Forms can break ReaLTaiizor.Native, while a change to ReaLTaiizor.Native can't break ReaLTaiizor.Forms.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
ReaLTaiizor.Util.FoxBase uses ReaLTaiizor.Util, so a change to ReaLTaiizor.Util can break ReaLTaiizor.Util.FoxBase, while a change to ReaLTaiizor.Util.FoxBase can't break ReaLTaiizor.Util.
Position
Below the diagonal: ReaLTaiizor.Util.FoxBase uses a module listed above it, which is the healthy direction.
ReaLTaiizor.Interface.Crown uses ReaLTaiizor.Util, so a change to ReaLTaiizor.Util can break ReaLTaiizor.Interface.Crown, while a change to ReaLTaiizor.Interface.Crown can't break ReaLTaiizor.Util.
Position
Below the diagonal: ReaLTaiizor.Interface.Crown uses a module listed above it, which is the healthy direction.
ReaLTaiizor.Interface.Crown uses ReaLTaiizor.Colors, so a change to ReaLTaiizor.Colors can break ReaLTaiizor.Interface.Crown, while a change to ReaLTaiizor.Interface.Crown can't break ReaLTaiizor.Colors.
Position
Below the diagonal: ReaLTaiizor.Interface.Crown uses a module listed above it, which is the healthy direction.
ReaLTaiizor.Helper uses ReaLTaiizor.Util, so a change to ReaLTaiizor.Util can break ReaLTaiizor.Helper, while a change to ReaLTaiizor.Helper can't break ReaLTaiizor.Util.
Position
Below the diagonal: ReaLTaiizor.Helper uses a module listed above it, which is the healthy direction.
ReaLTaiizor.Helper uses ReaLTaiizor.Colors, so a change to ReaLTaiizor.Colors can break ReaLTaiizor.Helper, while a change to ReaLTaiizor.Helper can't break ReaLTaiizor.Colors.
Position
Below the diagonal: ReaLTaiizor.Helper uses a module listed above it, which is the healthy direction.
ReaLTaiizor.Helper uses ReaLTaiizor.Interface.Crown, so a change to ReaLTaiizor.Interface.Crown can break ReaLTaiizor.Helper, while a change to ReaLTaiizor.Helper can't break ReaLTaiizor.Interface.Crown.
Position
Below the diagonal: ReaLTaiizor.Helper uses a module listed above it, which is the healthy direction.
24→25 ReaLTaiizor.Helper uses ReaLTaiizor.Controlspart of a loop✕
Connections
1 pair of types, where a type in ReaLTaiizor.Helper uses a type in ReaLTaiizor.Controls.
ReaLTaiizor.Helper uses ReaLTaiizor.Controls, so a change to ReaLTaiizor.Controls can break ReaLTaiizor.Helper, while a change to ReaLTaiizor.Helper can't break ReaLTaiizor.Controls.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
24→32 ReaLTaiizor.Helper uses ReaLTaiizor.Managerpart of a loop✕
Connections
1 pair of types, where a type in ReaLTaiizor.Helper uses a type in ReaLTaiizor.Manager.
ReaLTaiizor.Helper uses ReaLTaiizor.Manager, so a change to ReaLTaiizor.Manager can break ReaLTaiizor.Helper, while a change to ReaLTaiizor.Helper can't break ReaLTaiizor.Manager.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
ReaLTaiizor.Controls uses ReaLTaiizor, so a change to ReaLTaiizor can break ReaLTaiizor.Controls, while a change to ReaLTaiizor.Controls can't break ReaLTaiizor.
Position
Below the diagonal: ReaLTaiizor.Controls uses a module listed above it, which is the healthy direction.
ReaLTaiizor.Controls uses ReaLTaiizor.Enum.Crown, so a change to ReaLTaiizor.Enum.Crown can break ReaLTaiizor.Controls, while a change to ReaLTaiizor.Controls can't break ReaLTaiizor.Enum.Crown.
Position
Below the diagonal: ReaLTaiizor.Controls uses a module listed above it, which is the healthy direction.
ReaLTaiizor.Controls uses ReaLTaiizor.Enum.Material, so a change to ReaLTaiizor.Enum.Material can break ReaLTaiizor.Controls, while a change to ReaLTaiizor.Controls can't break ReaLTaiizor.Enum.Material.
Position
Below the diagonal: ReaLTaiizor.Controls uses a module listed above it, which is the healthy direction.
44 pairs of types, where a type in ReaLTaiizor.Controls uses a type in ReaLTaiizor.Enum.Metro. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
ReaLTaiizor.Controls uses ReaLTaiizor.Enum.Metro, so a change to ReaLTaiizor.Enum.Metro can break ReaLTaiizor.Controls, while a change to ReaLTaiizor.Controls can't break ReaLTaiizor.Enum.Metro.
Position
Below the diagonal: ReaLTaiizor.Controls uses a module listed above it, which is the healthy direction.
54 pairs of types, where a type in ReaLTaiizor.Controls uses a type in ReaLTaiizor.Enum.Poison. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
ReaLTaiizor.Controls uses ReaLTaiizor.Enum.Poison, so a change to ReaLTaiizor.Enum.Poison can break ReaLTaiizor.Controls, while a change to ReaLTaiizor.Controls can't break ReaLTaiizor.Enum.Poison.
Position
Below the diagonal: ReaLTaiizor.Controls uses a module listed above it, which is the healthy direction.
33 pairs of types, where a type in ReaLTaiizor.Controls uses a type in ReaLTaiizor.Extension.Metro. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
ReaLTaiizor.Controls uses ReaLTaiizor.Extension.Metro, so a change to ReaLTaiizor.Extension.Metro can break ReaLTaiizor.Controls, while a change to ReaLTaiizor.Controls can't break ReaLTaiizor.Extension.Metro.
Position
Below the diagonal: ReaLTaiizor.Controls uses a module listed above it, which is the healthy direction.
ReaLTaiizor.Controls uses ReaLTaiizor.Extension.Poison, so a change to ReaLTaiizor.Extension.Poison can break ReaLTaiizor.Controls, while a change to ReaLTaiizor.Controls can't break ReaLTaiizor.Extension.Poison.
Position
Below the diagonal: ReaLTaiizor.Controls uses a module listed above it, which is the healthy direction.
ReaLTaiizor.Controls uses ReaLTaiizor.Localization.Poison, so a change to ReaLTaiizor.Localization.Poison can break ReaLTaiizor.Controls, while a change to ReaLTaiizor.Controls can't break ReaLTaiizor.Localization.Poison.
Position
Below the diagonal: ReaLTaiizor.Controls uses a module listed above it, which is the healthy direction.
ReaLTaiizor.Controls uses ReaLTaiizor.Animate.Metro, so a change to ReaLTaiizor.Animate.Metro can break ReaLTaiizor.Controls, while a change to ReaLTaiizor.Controls can't break ReaLTaiizor.Animate.Metro.
Position
Below the diagonal: ReaLTaiizor.Controls uses a module listed above it, which is the healthy direction.
ReaLTaiizor.Controls uses ReaLTaiizor.Animate.Poison, so a change to ReaLTaiizor.Animate.Poison can break ReaLTaiizor.Controls, while a change to ReaLTaiizor.Controls can't break ReaLTaiizor.Animate.Poison.
Position
Below the diagonal: ReaLTaiizor.Controls uses a module listed above it, which is the healthy direction.
ReaLTaiizor.Controls uses ReaLTaiizor.Child.Crown, so a change to ReaLTaiizor.Child.Crown can break ReaLTaiizor.Controls, while a change to ReaLTaiizor.Controls can't break ReaLTaiizor.Child.Crown.
Position
Below the diagonal: ReaLTaiizor.Controls uses a module listed above it, which is the healthy direction.
ReaLTaiizor.Controls uses ReaLTaiizor.Drawing.Poison, so a change to ReaLTaiizor.Drawing.Poison can break ReaLTaiizor.Controls, while a change to ReaLTaiizor.Controls can't break ReaLTaiizor.Drawing.Poison.
Position
Below the diagonal: ReaLTaiizor.Controls uses a module listed above it, which is the healthy direction.
80 pairs of types, where a type in ReaLTaiizor.Controls uses a type in ReaLTaiizor.Util. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
ReaLTaiizor.Controls uses ReaLTaiizor.Util, so a change to ReaLTaiizor.Util can break ReaLTaiizor.Controls, while a change to ReaLTaiizor.Controls can't break ReaLTaiizor.Util.
Position
Below the diagonal: ReaLTaiizor.Controls uses a module listed above it, which is the healthy direction.
ReaLTaiizor.Controls uses ReaLTaiizor.Child.Poison, so a change to ReaLTaiizor.Child.Poison can break ReaLTaiizor.Controls, while a change to ReaLTaiizor.Controls can't break ReaLTaiizor.Child.Poison.
Position
Below the diagonal: ReaLTaiizor.Controls uses a module listed above it, which is the healthy direction.
ReaLTaiizor.Controls uses ReaLTaiizor.Interface.Poison, so a change to ReaLTaiizor.Interface.Poison can break ReaLTaiizor.Controls, while a change to ReaLTaiizor.Controls can't break ReaLTaiizor.Interface.Poison.
Position
Below the diagonal: ReaLTaiizor.Controls uses a module listed above it, which is the healthy direction.
ReaLTaiizor.Controls uses ReaLTaiizor.Native, so a change to ReaLTaiizor.Native can break ReaLTaiizor.Controls, while a change to ReaLTaiizor.Controls can't break ReaLTaiizor.Native.
Position
Below the diagonal: ReaLTaiizor.Controls uses a module listed above it, which is the healthy direction.
ReaLTaiizor.Controls uses ReaLTaiizor.Util.FoxBase, so a change to ReaLTaiizor.Util.FoxBase can break ReaLTaiizor.Controls, while a change to ReaLTaiizor.Controls can't break ReaLTaiizor.Util.FoxBase.
Position
Below the diagonal: ReaLTaiizor.Controls uses a module listed above it, which is the healthy direction.
61 pairs of types, where a type in ReaLTaiizor.Controls uses a type in ReaLTaiizor.Helper. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
ReaLTaiizor.Controls uses ReaLTaiizor.Helper, so a change to ReaLTaiizor.Helper can break ReaLTaiizor.Controls, while a change to ReaLTaiizor.Controls can't break ReaLTaiizor.Helper.
Position
Below the diagonal: ReaLTaiizor.Controls uses a module listed above it, which is the healthy direction.
25→26 ReaLTaiizor.Controls uses ReaLTaiizor.Child.Materialpart of a loop✕
Connections
5 pairs of types, where a type in ReaLTaiizor.Controls uses a type in ReaLTaiizor.Child.Material.
ReaLTaiizor.Controls uses ReaLTaiizor.Child.Material, so a change to ReaLTaiizor.Child.Material can break ReaLTaiizor.Controls, while a change to ReaLTaiizor.Controls can't break ReaLTaiizor.Child.Material.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
25→28 ReaLTaiizor.Controls uses ReaLTaiizor.Formspart of a loop✕
Connections
6 pairs of types, where a type in ReaLTaiizor.Controls uses a type in ReaLTaiizor.Forms.
ReaLTaiizor.Controls uses ReaLTaiizor.Forms, so a change to ReaLTaiizor.Forms can break ReaLTaiizor.Controls, while a change to ReaLTaiizor.Controls can't break ReaLTaiizor.Forms.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
25→32 ReaLTaiizor.Controls uses ReaLTaiizor.Managerpart of a loop✕
Connections
80 pairs of types, where a type in ReaLTaiizor.Controls uses a type in ReaLTaiizor.Manager. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
ReaLTaiizor.Controls uses ReaLTaiizor.Manager, so a change to ReaLTaiizor.Manager can break ReaLTaiizor.Controls, while a change to ReaLTaiizor.Controls can't break ReaLTaiizor.Manager.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
25→37 ReaLTaiizor.Controls uses ReaLTaiizor.Interface.Metropart of a loop✕
Connections
24 pairs of types, where a type in ReaLTaiizor.Controls uses a type in ReaLTaiizor.Interface.Metro.
ReaLTaiizor.Controls uses ReaLTaiizor.Interface.Metro, so a change to ReaLTaiizor.Interface.Metro can break ReaLTaiizor.Controls, while a change to ReaLTaiizor.Controls can't break ReaLTaiizor.Interface.Metro.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
25→39 ReaLTaiizor.Controls uses ReaLTaiizor.Child.Metropart of a loop✕
Connections
1 pair of types, where a type in ReaLTaiizor.Controls uses a type in ReaLTaiizor.Child.Metro.
ReaLTaiizor.Controls uses ReaLTaiizor.Child.Metro, so a change to ReaLTaiizor.Child.Metro can break ReaLTaiizor.Controls, while a change to ReaLTaiizor.Controls can't break ReaLTaiizor.Child.Metro.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
ReaLTaiizor.Child.Material uses ReaLTaiizor.Util, so a change to ReaLTaiizor.Util can break ReaLTaiizor.Child.Material, while a change to ReaLTaiizor.Child.Material can't break ReaLTaiizor.Util.
Position
Below the diagonal: ReaLTaiizor.Child.Material uses a module listed above it, which is the healthy direction.
ReaLTaiizor.Child.Material uses ReaLTaiizor.Helper, so a change to ReaLTaiizor.Helper can break ReaLTaiizor.Child.Material, while a change to ReaLTaiizor.Child.Material can't break ReaLTaiizor.Helper.
Position
Below the diagonal: ReaLTaiizor.Child.Material uses a module listed above it, which is the healthy direction.
ReaLTaiizor.Child.Material uses ReaLTaiizor.Controls, so a change to ReaLTaiizor.Controls can break ReaLTaiizor.Child.Material, while a change to ReaLTaiizor.Child.Material can't break ReaLTaiizor.Controls.
Position
Below the diagonal: ReaLTaiizor.Child.Material uses a module listed above it, which is the healthy direction.
26→32 ReaLTaiizor.Child.Material uses ReaLTaiizor.Managerpart of a loop✕
Connections
2 pairs of types, where a type in ReaLTaiizor.Child.Material uses a type in ReaLTaiizor.Manager.
ReaLTaiizor.Child.Material uses ReaLTaiizor.Manager, so a change to ReaLTaiizor.Manager can break ReaLTaiizor.Child.Material, while a change to ReaLTaiizor.Child.Material can't break ReaLTaiizor.Manager.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
ReaLTaiizor.Nerator.UC.THEME uses ReaLTaiizor.Controls, so a change to ReaLTaiizor.Controls can break ReaLTaiizor.Nerator.UC.THEME, while a change to ReaLTaiizor.Nerator.UC.THEME can't break ReaLTaiizor.Controls.
Position
Below the diagonal: ReaLTaiizor.Nerator.UC.THEME uses a module listed above it, which is the healthy direction.
ReaLTaiizor.Forms uses ReaLTaiizor.Enum.Material, so a change to ReaLTaiizor.Enum.Material can break ReaLTaiizor.Forms, while a change to ReaLTaiizor.Forms can't break ReaLTaiizor.Enum.Material.
Position
Below the diagonal: ReaLTaiizor.Forms uses a module listed above it, which is the healthy direction.
ReaLTaiizor.Forms uses ReaLTaiizor.Enum.Metro, so a change to ReaLTaiizor.Enum.Metro can break ReaLTaiizor.Forms, while a change to ReaLTaiizor.Forms can't break ReaLTaiizor.Enum.Metro.
Position
Below the diagonal: ReaLTaiizor.Forms uses a module listed above it, which is the healthy direction.
ReaLTaiizor.Forms uses ReaLTaiizor.Enum.Poison, so a change to ReaLTaiizor.Enum.Poison can break ReaLTaiizor.Forms, while a change to ReaLTaiizor.Forms can't break ReaLTaiizor.Enum.Poison.
Position
Below the diagonal: ReaLTaiizor.Forms uses a module listed above it, which is the healthy direction.
ReaLTaiizor.Forms uses ReaLTaiizor.Extension.Metro, so a change to ReaLTaiizor.Extension.Metro can break ReaLTaiizor.Forms, while a change to ReaLTaiizor.Forms can't break ReaLTaiizor.Extension.Metro.
Position
Below the diagonal: ReaLTaiizor.Forms uses a module listed above it, which is the healthy direction.
ReaLTaiizor.Forms uses ReaLTaiizor.Drawing.Poison, so a change to ReaLTaiizor.Drawing.Poison can break ReaLTaiizor.Forms, while a change to ReaLTaiizor.Forms can't break ReaLTaiizor.Drawing.Poison.
Position
Below the diagonal: ReaLTaiizor.Forms uses a module listed above it, which is the healthy direction.
ReaLTaiizor.Forms uses ReaLTaiizor.Util, so a change to ReaLTaiizor.Util can break ReaLTaiizor.Forms, while a change to ReaLTaiizor.Forms can't break ReaLTaiizor.Util.
Position
Below the diagonal: ReaLTaiizor.Forms uses a module listed above it, which is the healthy direction.
ReaLTaiizor.Forms uses ReaLTaiizor.Interface.Poison, so a change to ReaLTaiizor.Interface.Poison can break ReaLTaiizor.Forms, while a change to ReaLTaiizor.Forms can't break ReaLTaiizor.Interface.Poison.
Position
Below the diagonal: ReaLTaiizor.Forms uses a module listed above it, which is the healthy direction.
ReaLTaiizor.Forms uses ReaLTaiizor.Native, so a change to ReaLTaiizor.Native can break ReaLTaiizor.Forms, while a change to ReaLTaiizor.Forms can't break ReaLTaiizor.Native.
Position
Below the diagonal: ReaLTaiizor.Forms uses a module listed above it, which is the healthy direction.
ReaLTaiizor.Forms uses ReaLTaiizor.Helper, so a change to ReaLTaiizor.Helper can break ReaLTaiizor.Forms, while a change to ReaLTaiizor.Forms can't break ReaLTaiizor.Helper.
Position
Below the diagonal: ReaLTaiizor.Forms uses a module listed above it, which is the healthy direction.
ReaLTaiizor.Forms uses ReaLTaiizor.Controls, so a change to ReaLTaiizor.Controls can break ReaLTaiizor.Forms, while a change to ReaLTaiizor.Forms can't break ReaLTaiizor.Controls.
Position
Below the diagonal: ReaLTaiizor.Forms uses a module listed above it, which is the healthy direction.
ReaLTaiizor.Forms uses ReaLTaiizor.Child.Material, so a change to ReaLTaiizor.Child.Material can break ReaLTaiizor.Forms, while a change to ReaLTaiizor.Forms can't break ReaLTaiizor.Child.Material.
Position
Below the diagonal: ReaLTaiizor.Forms uses a module listed above it, which is the healthy direction.
28→32 ReaLTaiizor.Forms uses ReaLTaiizor.Managerpart of a loop✕
Connections
5 pairs of types, where a type in ReaLTaiizor.Forms uses a type in ReaLTaiizor.Manager.
ReaLTaiizor.Forms uses ReaLTaiizor.Manager, so a change to ReaLTaiizor.Manager can break ReaLTaiizor.Forms, while a change to ReaLTaiizor.Forms can't break ReaLTaiizor.Manager.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
28→37 ReaLTaiizor.Forms uses ReaLTaiizor.Interface.Metropart of a loop✕
Connections
1 pair of types, where a type in ReaLTaiizor.Forms uses a type in ReaLTaiizor.Interface.Metro.
ReaLTaiizor.Forms uses ReaLTaiizor.Interface.Metro, so a change to ReaLTaiizor.Interface.Metro can break ReaLTaiizor.Forms, while a change to ReaLTaiizor.Forms can't break ReaLTaiizor.Interface.Metro.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
ReaLTaiizor.AppLocker uses ReaLTaiizor.Controls, so a change to ReaLTaiizor.Controls can break ReaLTaiizor.AppLocker, while a change to ReaLTaiizor.AppLocker can't break ReaLTaiizor.Controls.
Position
Below the diagonal: ReaLTaiizor.AppLocker uses a module listed above it, which is the healthy direction.
ReaLTaiizor.AppLocker uses ReaLTaiizor.Forms, so a change to ReaLTaiizor.Forms can break ReaLTaiizor.AppLocker, while a change to ReaLTaiizor.AppLocker can't break ReaLTaiizor.Forms.
Position
Below the diagonal: ReaLTaiizor.AppLocker uses a module listed above it, which is the healthy direction.
ReaLTaiizor.Hashing uses ReaLTaiizor.Controls, so a change to ReaLTaiizor.Controls can break ReaLTaiizor.Hashing, while a change to ReaLTaiizor.Hashing can't break ReaLTaiizor.Controls.
Position
Below the diagonal: ReaLTaiizor.Hashing uses a module listed above it, which is the healthy direction.
ReaLTaiizor.Hashing uses ReaLTaiizor.Forms, so a change to ReaLTaiizor.Forms can break ReaLTaiizor.Hashing, while a change to ReaLTaiizor.Hashing can't break ReaLTaiizor.Forms.
Position
Below the diagonal: ReaLTaiizor.Hashing uses a module listed above it, which is the healthy direction.
ReaLTaiizor.MAChanger uses ReaLTaiizor.Controls, so a change to ReaLTaiizor.Controls can break ReaLTaiizor.MAChanger, while a change to ReaLTaiizor.MAChanger can't break ReaLTaiizor.Controls.
Position
Below the diagonal: ReaLTaiizor.MAChanger uses a module listed above it, which is the healthy direction.
ReaLTaiizor.MAChanger uses ReaLTaiizor.Forms, so a change to ReaLTaiizor.Forms can break ReaLTaiizor.MAChanger, while a change to ReaLTaiizor.MAChanger can't break ReaLTaiizor.Forms.
Position
Below the diagonal: ReaLTaiizor.MAChanger uses a module listed above it, which is the healthy direction.
ReaLTaiizor.Manager uses ReaLTaiizor.Enum.Metro, so a change to ReaLTaiizor.Enum.Metro can break ReaLTaiizor.Manager, while a change to ReaLTaiizor.Manager can't break ReaLTaiizor.Enum.Metro.
Position
Below the diagonal: ReaLTaiizor.Manager uses a module listed above it, which is the healthy direction.
ReaLTaiizor.Manager uses ReaLTaiizor.Enum.Poison, so a change to ReaLTaiizor.Enum.Poison can break ReaLTaiizor.Manager, while a change to ReaLTaiizor.Manager can't break ReaLTaiizor.Enum.Poison.
Position
Below the diagonal: ReaLTaiizor.Manager uses a module listed above it, which is the healthy direction.
ReaLTaiizor.Manager uses ReaLTaiizor.Util, so a change to ReaLTaiizor.Util can break ReaLTaiizor.Manager, while a change to ReaLTaiizor.Manager can't break ReaLTaiizor.Util.
Position
Below the diagonal: ReaLTaiizor.Manager uses a module listed above it, which is the healthy direction.
ReaLTaiizor.Manager uses ReaLTaiizor.Colors, so a change to ReaLTaiizor.Colors can break ReaLTaiizor.Manager, while a change to ReaLTaiizor.Manager can't break ReaLTaiizor.Colors.
Position
Below the diagonal: ReaLTaiizor.Manager uses a module listed above it, which is the healthy direction.
ReaLTaiizor.Manager uses ReaLTaiizor.Interface.Poison, so a change to ReaLTaiizor.Interface.Poison can break ReaLTaiizor.Manager, while a change to ReaLTaiizor.Manager can't break ReaLTaiizor.Interface.Poison.
Position
Below the diagonal: ReaLTaiizor.Manager uses a module listed above it, which is the healthy direction.
ReaLTaiizor.Manager uses ReaLTaiizor.Forms, so a change to ReaLTaiizor.Forms can break ReaLTaiizor.Manager, while a change to ReaLTaiizor.Manager can't break ReaLTaiizor.Forms.
Position
Below the diagonal: ReaLTaiizor.Manager uses a module listed above it, which is the healthy direction.
ReaLTaiizor.Nerator.UI uses ReaLTaiizor.Nerator.CS, so a change to ReaLTaiizor.Nerator.CS can break ReaLTaiizor.Nerator.UI, while a change to ReaLTaiizor.Nerator.UI can't break ReaLTaiizor.Nerator.CS.
Position
Below the diagonal: ReaLTaiizor.Nerator.UI uses a module listed above it, which is the healthy direction.
ReaLTaiizor.Nerator.UI uses ReaLTaiizor.Controls, so a change to ReaLTaiizor.Controls can break ReaLTaiizor.Nerator.UI, while a change to ReaLTaiizor.Nerator.UI can't break ReaLTaiizor.Controls.
Position
Below the diagonal: ReaLTaiizor.Nerator.UI uses a module listed above it, which is the healthy direction.
ReaLTaiizor.Nerator.UI uses ReaLTaiizor.Nerator.UC.THEME, so a change to ReaLTaiizor.Nerator.UC.THEME can break ReaLTaiizor.Nerator.UI, while a change to ReaLTaiizor.Nerator.UI can't break ReaLTaiizor.Nerator.UC.THEME.
Position
Below the diagonal: ReaLTaiizor.Nerator.UI uses a module listed above it, which is the healthy direction.
ReaLTaiizor.Nerator.UI uses ReaLTaiizor.Forms, so a change to ReaLTaiizor.Forms can break ReaLTaiizor.Nerator.UI, while a change to ReaLTaiizor.Nerator.UI can't break ReaLTaiizor.Forms.
Position
Below the diagonal: ReaLTaiizor.Nerator.UI uses a module listed above it, which is the healthy direction.
ReaLTaiizor.Portscan uses ReaLTaiizor.Controls, so a change to ReaLTaiizor.Controls can break ReaLTaiizor.Portscan, while a change to ReaLTaiizor.Portscan can't break ReaLTaiizor.Controls.
Position
Below the diagonal: ReaLTaiizor.Portscan uses a module listed above it, which is the healthy direction.
ReaLTaiizor.Portscan uses ReaLTaiizor.Forms, so a change to ReaLTaiizor.Forms can break ReaLTaiizor.Portscan, while a change to ReaLTaiizor.Portscan can't break ReaLTaiizor.Forms.
Position
Below the diagonal: ReaLTaiizor.Portscan uses a module listed above it, which is the healthy direction.
ReaLTaiizor.Stopwatch uses ReaLTaiizor.Controls, so a change to ReaLTaiizor.Controls can break ReaLTaiizor.Stopwatch, while a change to ReaLTaiizor.Stopwatch can't break ReaLTaiizor.Controls.
Position
Below the diagonal: ReaLTaiizor.Stopwatch uses a module listed above it, which is the healthy direction.
ReaLTaiizor.Stopwatch uses ReaLTaiizor.Forms, so a change to ReaLTaiizor.Forms can break ReaLTaiizor.Stopwatch, while a change to ReaLTaiizor.Stopwatch can't break ReaLTaiizor.Forms.
Position
Below the diagonal: ReaLTaiizor.Stopwatch uses a module listed above it, which is the healthy direction.
ReaLTaiizor.Translate uses ReaLTaiizor.Controls, so a change to ReaLTaiizor.Controls can break ReaLTaiizor.Translate, while a change to ReaLTaiizor.Translate can't break ReaLTaiizor.Controls.
Position
Below the diagonal: ReaLTaiizor.Translate uses a module listed above it, which is the healthy direction.
ReaLTaiizor.Translate uses ReaLTaiizor.Forms, so a change to ReaLTaiizor.Forms can break ReaLTaiizor.Translate, while a change to ReaLTaiizor.Translate can't break ReaLTaiizor.Forms.
Position
Below the diagonal: ReaLTaiizor.Translate uses a module listed above it, which is the healthy direction.
ReaLTaiizor.Interface.Metro uses ReaLTaiizor.Enum.Metro, so a change to ReaLTaiizor.Enum.Metro can break ReaLTaiizor.Interface.Metro, while a change to ReaLTaiizor.Interface.Metro can't break ReaLTaiizor.Enum.Metro.
Position
Below the diagonal: ReaLTaiizor.Interface.Metro uses a module listed above it, which is the healthy direction.
ReaLTaiizor.Interface.Metro uses ReaLTaiizor.Manager, so a change to ReaLTaiizor.Manager can break ReaLTaiizor.Interface.Metro, while a change to ReaLTaiizor.Interface.Metro can't break ReaLTaiizor.Manager.
Position
Below the diagonal: ReaLTaiizor.Interface.Metro uses a module listed above it, which is the healthy direction.
44 pairs of types, where a type in ReaLTaiizor_CR uses a type in ReaLTaiizor.Controls. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
ReaLTaiizor_CR uses ReaLTaiizor.Controls, so a change to ReaLTaiizor.Controls can break ReaLTaiizor_CR, while a change to ReaLTaiizor_CR can't break ReaLTaiizor.Controls.
Position
Below the diagonal: ReaLTaiizor_CR uses a module listed above it, which is the healthy direction.
ReaLTaiizor_CR uses ReaLTaiizor.Forms, so a change to ReaLTaiizor.Forms can break ReaLTaiizor_CR, while a change to ReaLTaiizor_CR can't break ReaLTaiizor.Forms.
Position
Below the diagonal: ReaLTaiizor_CR uses a module listed above it, which is the healthy direction.
ReaLTaiizor_CR uses ReaLTaiizor.Manager, so a change to ReaLTaiizor.Manager can break ReaLTaiizor_CR, while a change to ReaLTaiizor_CR can't break ReaLTaiizor.Manager.
Position
Below the diagonal: ReaLTaiizor_CR uses a module listed above it, which is the healthy direction.
ReaLTaiizor.Child.Metro uses ReaLTaiizor.Enum.Metro, so a change to ReaLTaiizor.Enum.Metro can break ReaLTaiizor.Child.Metro, while a change to ReaLTaiizor.Child.Metro can't break ReaLTaiizor.Enum.Metro.
Position
Below the diagonal: ReaLTaiizor.Child.Metro uses a module listed above it, which is the healthy direction.
ReaLTaiizor.Child.Metro uses ReaLTaiizor.Manager, so a change to ReaLTaiizor.Manager can break ReaLTaiizor.Child.Metro, while a change to ReaLTaiizor.Child.Metro can't break ReaLTaiizor.Manager.
Position
Below the diagonal: ReaLTaiizor.Child.Metro uses a module listed above it, which is the healthy direction.
ReaLTaiizor.Child.Metro uses ReaLTaiizor.Interface.Metro, so a change to ReaLTaiizor.Interface.Metro can break ReaLTaiizor.Child.Metro, while a change to ReaLTaiizor.Child.Metro can't break ReaLTaiizor.Interface.Metro.
Position
Below the diagonal: ReaLTaiizor.Child.Metro uses a module listed above it, which is the healthy direction.
ReaLTaiizor.Action.Metro uses ReaLTaiizor.Enum.Metro, so a change to ReaLTaiizor.Enum.Metro can break ReaLTaiizor.Action.Metro, while a change to ReaLTaiizor.Action.Metro can't break ReaLTaiizor.Enum.Metro.
Position
Below the diagonal: ReaLTaiizor.Action.Metro uses a module listed above it, which is the healthy direction.
ReaLTaiizor.Action.Metro uses ReaLTaiizor.Controls, so a change to ReaLTaiizor.Controls can break ReaLTaiizor.Action.Metro, while a change to ReaLTaiizor.Action.Metro can't break ReaLTaiizor.Controls.
Position
Below the diagonal: ReaLTaiizor.Action.Metro uses a module listed above it, which is the healthy direction.
ReaLTaiizor.Action.Metro uses ReaLTaiizor.Manager, so a change to ReaLTaiizor.Manager can break ReaLTaiizor.Action.Metro, while a change to ReaLTaiizor.Action.Metro can't break ReaLTaiizor.Manager.
Position
Below the diagonal: ReaLTaiizor.Action.Metro uses a module listed above it, which is the healthy direction.
ReaLTaiizor.Action.Metro uses ReaLTaiizor.Child.Metro, so a change to ReaLTaiizor.Child.Metro can break ReaLTaiizor.Action.Metro, while a change to ReaLTaiizor.Action.Metro can't break ReaLTaiizor.Child.Metro.
Position
Below the diagonal: ReaLTaiizor.Action.Metro uses a module listed above it, which is the healthy direction.
At a glance — Code Health · 43.2 · Weak · gated by X1 ·
Findings mapped to OWASP categories; the specific CVEs/secrets are in the Security dimension cards below and findings.md (redacted only on the public version of this report).
OWASP category
Findings
Severity
A05:2025 — Injection
17
High / Critical
Roadmap
Top priorities: Encrypt sensitive data at rest (ASP.NET Core Data Protection / column encryption) and manage keys in a vault. Skip if delegated to infra (Postgres TDE, KMS, etc.); Resolve the 2 NoWarnInCsproj finding(s) in Explicit Debt — start with ReaLTaiizor.csproj (2); Resolve the 36 WriteOnlyPrivateField finding(s) in Explicit Debt — start with ForeverForm.cs (3), DungeonCheckBox.cs (2), ForeverComboBox.cs (2).
Ranked by impact ÷ effort. "Helps" is the estimated gain on the 0–100 health score.
Do this
Helps
Effort
Dimension
Encrypt sensitive data at rest (ASP.NET Core Data Protection / column encryption) and manage keys in a vault. Skip if delegated to infra (Postgres TDE, KMS, etc.).
Every finding carries one of four grades. Three say how serious it is. The fourth says this
survey could not settle it — and it is a grade, not a gap.
Critical — 104
A definite problem that already costs you something and drags the score down: a
missing authorisation check, a dependency with a known exploit, a build that does not reproduce. Failure here
tends to cause failures elsewhere.
Serious — 1034
Likely wrong, but not failing yet. It degrades
the codebase over a longer horizon and can cause failures elsewhere — not urgent this week, not something to
carry for two years either.
Minor — 148
Recorded, with no effect on how the codebase functions.
Present so the survey is complete, not because it needs doing.
Could not be resolved — 7
Something this survey could not settle
from the outside, and which could be critical or serious. Either a control was required and no
positive evidence of it exists in the repository — a backup job that nothing shows was ever restored from proves
nothing about restores — or our own analysis could not run over that part of the tree. This is not a clean
result. These are excluded from the score rather than awarded a pass, so the number on the cover neither
rewards nor penalises them: if you act on this survey without resolving them, you carry that risk yourself. Each
one is named under Limitations.
Methodology & how to trust this report
This survey is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. All 52 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.9, the weighted average across measured dimensions.
Every figure here is one of two kinds, and we label which: ✓ Measured — a deterministic fact (LoC, complexity, coverage); ~ Modeled — an estimate from a stated model (cost, effort, value-at-risk), always a range with its assumptions, never a precise fact. We never present a modelled estimate as if it were measured. Perfect or absent scores carry their provenance too (ADR-0011): ✓ Tool-verified means the property itself was measured across the surface; ○ Nothing flagged means the probes came back clean — a claim bounded by what a repository can show; ⊘ Not evidenced means a working control (a tested restore, an automated rollback) showed no positive evidence — absence of evidence is not evidence of a control, so it's excluded from the score rather than awarded a spurious 10.
What we checked — 52 dimensions across the health lenses
Each chip is a dimension scored from real signals across architecture, testing, dependencies, security & compliance, documentation, git-history and code quality — in one coherent pass. A surface report typically covers a handful.
How to trust any code-health report — three questions
Can you open the finding? Real findings cite a repo-relative file and line you can open at the cited line — never an absolute scratch path. Here, 1281 of 1286 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line. (Every path in this report is repo-relative by construction: paths are normalized at the producer and the report is rejected if any rooted path leaks through.)
Is there a tool behind the number? Every score below names the method that produced it: Roslyn, git or a scanner, not a narrative.
Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
This report answers yes to all three. That's the bar to hold any assessment to.
Tools & methods
The actual versions used this run (captured at analysis time) — re-run on the same commit for the identical score.
Method
Backs
Version
Evaluator
Roslyn static analysis
Complexity, cohesion, coupling, dead code, API surface, layering
What ran differently this time — a tool absent, degraded, or that fell back to an estimate. Named openly, not folded silently into the scores. A degraded run also records its exact cause in diagnostics.md.
D12 Dependency Hygiene — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `dotnet list package` did not return usable output (restore or query failed); no outdated/vulnerable/deprecated data to assess. The tool said: `dotnet list package` exited 1 with no output.
D16 Bus Factor — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. Single-maintainer repository — bus factor is not applicable (12 contributor(s) across 1222 commit(s) sampled, automation and bot accounts excluded). One of them holds 96% of the history; the other 11 hold 0.4% each on average, below the 5% at which there is somebody to hand the work to. That is a single maintainer with drive-by contributors, not a team whose knowledge has concentrated — so the bus factor is not applicable and there is nothing here for the owner to act on.
D17 Explicit Debt — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. The C# workspace loaded this repository's projects but reported a load failure, and the dead-code reference search is unreliable over a graph that did not load cleanly, so it was skipped. The other debt markers on this row were read; dead symbols were not, and their absence from the score is not a finding that the code has none. First load diagnostic: Failure: Msbuild failed when processing the file 'src/ReaLTaiizor/ReaLTaiizor.csproj' with message: Unable to load the service index for source https://pkgs.dev.azure.com/dnceng/public/_packaging/dotnet6/nuget/v3/index.json.
The proxy tunnel request to proxy 'http://egress:3128/' failed with status code '403'.".
D18 Solution Shape — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. The build did not finish within its budget on this run; structural metrics are reported, build/warning status is unknown.
D19 Documentation Quality — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This kind did not reach the 95 % precision gate in three adjudicated runs (docs/plans/deterministic-engine/adjudication/D19-sample3-v3.md), so by the pre-registered fallback it publishes no row until a re-measurement shows it does. The candidates are counted here, not reported as findings, and the score does not include them.
D21 Naming Consistency — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. D21's naming rules read C# through Roslyn and every other language through its sidecar model; these languages are left out (PHP's reading is its own change, a Roslyn-loaded VB or F# project has no population builder yet). Their declarations carry no naming verdict this run — this says nothing about whether their names are consistent.
D21 Naming Consistency — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. PREREGISTRATION version 20's fallback (adjudication D21-sample3-v3): this rule kind was adjudicated below the 95 % precision gate, so its candidates are counted here and not published, and the score covers only the acronym-spelling and awaitable-suffix rules. The kind returns as rows only after it shows a measured precision; this says nothing about whether these names are consistent.
D21 Naming Consistency — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. PREREGISTRATION version 20's fallback (adjudication D21-sample3-v3): this rule kind was adjudicated below the 95 % precision gate, so its candidates are counted here and not published, and the score covers only the acronym-spelling and awaitable-suffix rules. The kind returns as rows only after it shows a measured precision; this says nothing about whether these names are consistent.
D22 Internal API Consistency — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. The loaded project set declares no packable project and no `.Contracts` project, so there is no intentionally-exposed surface for API consistency to be judged over.
D23 Boundary Type-Coupling — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Large codebase (123,511 production LoC in the .NET projects) with no declared bounded contexts — cross-boundary type coupling is unassessed Bounded contexts cannot be inferred from a codebase that is not physically organised by them (D-321), so with none declared there are no boundaries for the coupling pass to measure across. You can widen what we reach: name this codebase's bounded contexts (≥2 module groups, e.g. per subsystem) so cross-boundary type coupling can be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
D30 Dependency Vulnerabilities — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Nuget: pkgs.dev.azure.com could not be reached (NU1301: Unable to load the service index for source https://pkgs.dev.azure.com/dnceng/public/_packaging/dotnet6/nuget/v3/index.json. The proxy tunnel request to proxy 'http://egress:3128/' failed with status code '403'.). The scanner exists and ran; what failed is the scan's network path to the registry, so nothing was read and nothing here is a statement about the repository. A re-run with the registry reachable measures it.
D32 Data Compliance (PII/GDPR) — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `src/ReaLTaiizor/Animate/Poison/DelayedCall.cs` produced a parse error, so every rule in this engine's `gdpr.yml` was absent there. That absence is NOT a clean result: these rules detect personal data crossing a boundary into a log sink, a URL or browser storage, and a file that was never parsed cannot report any of the three. The rest of the tree analysed normally and its rows above stand; only these files are unaccounted for. You can widen what we reach: fix the syntax error (or exclude the file deliberately) and re-scan to cover it.
IC1 Incompleteness & stubs — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 269 further occurrence(s) are not listed individually; the score already reflects all 309.
P10 Library API & versioning — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 826 further occurrence(s) are not listed individually; the score already reflects all 866.
P5 DR & Backup — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. No backup/snapshot/replication config, RTO/RPO or restore-procedure documentation was found — and no production persistence was detected either (no data-access packages, no data-store services, no database resources), so there is nothing in this repository whose loss a DR control would recover. If this system's data lives in a platform or ops repo we can't see, that's where the DR evidence belongs.
X10 Duplicated predicate — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. 25 further occurrence(s) are not listed individually; the score already reflects all 65.
X18 Disposal-pattern correctness — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 48 further occurrence(s) are not listed individually; the score already reflects all 88.
X3 Exception handling — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 23 further occurrence(s) are not listed individually; the score already reflects all 63.
Package restore incomplete — third-party types were unresolved in part of the solution — NuGet restore did not complete for src/ReaLTaiizor/ReaLTaiizor.csproj, src/ReaLTaiizor_CR/ReaLTaiizor_CR.csproj, so those projects were analysed with framework references only: every check keyed on a third-party type saw an error type there and reported nothing. Findings on those projects are a lower bound; run `dotnet restore` on them and rescan.
Repo exclusion declarations (.gitattributes linguist-generated/vendored, .editorconfig generated_code): none declared — every source file was scored.
Limitations & what we did not check
We assess the repository exactly as committed, and only the repository. By design we do not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
For each dimension that was measured, what a static, repo-only scan structurally cannot see — the honest edge of the measurement, not a failure of it.
D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
D8 Code Coverage: Coverage is measured by building and running the test suite inside our isolated image — the target repo is never modified, and nothing on your systems runs. So coverage exists only when the suite builds and runs within the inline time budget; one that needs external services, can't build, or exceeds the budget yields no coverage (D8 then degrades to not-measured, not a low score). Line coverage also says nothing about assertion quality.
D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
D18 Solution Shape: Build integrity reflects whether the solution compiled in this environment — a build that needs a private feed, a specific SDK, or a generated file absent from the repo can read as broken when it is merely unreproducible here.
D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
D20 ADR Quality: ADR quality checks the structure of the decision records present: it cannot know about decisions made and never recorded, and it does not judge how well a record argues its case. Records in a language the section lexicon does not cover are not evaluated.
D21 Naming Consistency: Naming consistency compares each name with the convention its structural peers follow in this repository: it cannot tell whether a consistently used name is a good one, and languages other than C# and TypeScript are not measured.
D24 Comment Value: Comment value is measured as redundancy only: a comment that repeats its code's words is found, but a paraphrase in other words, a vague comment, or one the code contradicts is not, and whether a comment is valuable is not claimed. Comments in other scripts or languages, and outside C#, are not judged.
D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
D27 Navigability: Indirection/navigability is structural — it measures hops to follow a call, not whether that indirection buys real flexibility or just ceremony.
D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a Dockerfile (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.
What it measures: How tangled the control flow is — methods with many branches are hard to test and change.
Method: Cyclomatic complexity per method (1 + decision points), computed exhaustively across production source; test projects separated by convention. Deterministic.
80 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was MaterialMaskedTextBox.OnPaint at 77. A further 5 method(s) were over the threshold but excluded as flat dispatchers (a long switch/match over independent cases: many branches, almost no nesting), the largest being FormHelper.Open at 25 — they are counted neither in the figure above nor in this dimension's score. 3 files carry no cyclomatic complexity row at all for this reason — every one of their over-threshold methods was excluded, so the exclusion is disclosed nowhere in the file itself: demo/ReaLTaiizor.UI/ReaLTaiizor.UI/Helpers/FormHelper.cs (FormHelper.Open at 25), src/ReaLTaiizor/Drawing/Poison/PoisonPaint.cs (PoisonPaint.GetStyleColor at 17), src/ReaLTaiizor/Manager/MaterialSkinManager.cs (MaterialSkinManager.GetFontByType at 16). They are named here because the per-file figures other dimensions report are taken BEFORE this exclusion, so such a file can show a high maximum complexity elsewhere in this report and nothing here, with nothing to reconcile the two.
+ 75 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Bring the 2 bodies over 60 down to 60 or less in Cyclomatic Complexity — start with MaterialMaskedTextBox.OnPaint (cyclomatic 77), MaterialTextBoxEdit.OnPaint (cyclomatic 77). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 2 together lifts Cyclomatic Complexity from 6.3 to about 6.5/10, projected with the scoring formula itself and assuming each lands exactly at 60; a cleaner split scores higher.
Detailed fixes: d1_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: How hard the code is for a person to follow, beyond raw branching.
Method: Cognitive complexity per method (Sonar-style nesting-penalized score), computed exhaustively over production code, excluding test projects. Deterministic.
+ 140 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Bring the 10 bodies over 60 down to 60 or less in Cognitive Complexity — start with ParrotBarGraph.OnPaint (cognitive 139), MaterialMaskedTextBox.OnPaint (cognitive 126), MaterialTextBoxEdit.OnPaint (cognitive 126). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 10 together lifts Cognitive Complexity from 5.7 to about 6.5/10, projected with the scoring formula itself and assuming each lands exactly at 60; a cleaner split scores higher.
Detailed fixes: d2_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D3 · God Classes8.8 / 10Strong✓ Tool-verified
What it measures: Over-large classes that try to do too much ("god classes").
Method: God-class detection by line and method-count thresholds per logical type (partial classes unified), filtered for generated code and registration/contract false positives. Deterministic.
Resolve the 17 FileTooLong finding(s) in God Classes — start with Air.cs, Moon.cs, Space.cs. — One of this dimension's main actionable groups (17 warning-level).
Resolve the 16 ClassTooLong finding(s) in God Classes — start with MaterialMaskedTextBox.cs, MaterialTextBoxEdit.cs, MaterialForm.cs. — One of this dimension's main actionable groups (16 warning-level).
Resolve the 15 TooManyMethods finding(s) in God Classes — start with Moon.cs (2), Air.cs (2), Space.cs (2). — One of this dimension's main actionable groups (15 warning-level).
Detailed fixes: d3_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D4 · Code Duplication4.6 / 10Weak✓ Tool-verified
What it measures: How much of the production code is copy-pasted: the share of production lines inside a reported copy (every copy of a duplicated block or of an edited member, each line once), 10 at none and 0 at a quarter of the lines.
Method: Code duplication via token-stream sliding windows with type-aware normalization (locals masked, type names preserved), scored on the share of production lines inside a reported copy (each line once; 10 at none, 0 at a quarter). Deterministic.
470 duplicated block group(s) detected. 13.5 % of the production lines (16,690 of 123,511) are in a reported copy. A further 42 rows report members as variants of one another; the share counts each copied line once, however many rows cite it. 1 of the 512 are in trees this repository does not ship — vendored, example/demo, project-template, fixture and benchmark code — and are ranked below the shipped groups rather than excluded from them: the duplication there is real and is still counted in this dimension's score. The dimensions that publish a production-file census leave those trees out of theirs, so this count is deliberately drawn over the wider population.
+ 170 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 25 Duplicated block (6 lines × 2) finding(s) in Code Duplication — start with SpaceSeparatorHorizontal.cs (3), HopeRoundButton.cs (2), MetroEllipse.cs. — One of this dimension's main actionable groups (25 warning-level).
Resolve the 25 Duplicated block (7 lines × 2) finding(s) in Code Duplication — start with ParrotBarGraph.cs (2), AloneCheckBox.cs, MetroButton.cs. — One of this dimension's main actionable groups (25 warning-level).
Resolve the 23 Duplicated block (10 lines × 2) finding(s) in Code Duplication — start with ParrotButton.cs (2), Air.cs (2), Moon.cs (2). — One of this dimension's main actionable groups (23 warning-level).
Detailed fixes: d4_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D5 · Coupling10.0 / 10Exemplary✓ Tool-verified
What it measures: Whether volatile projects sit underneath others that depend on them (so their churn ripples upward), and whether project dependencies form cycles. A widely-depended-on but stable shared/kernel project is healthy, not penalised.
Method: Dependency cycles via elementary-DFS over real .csproj references, plus Martin instability (afferent/efferent) per project. Exhaustive over the reference graph, deterministic.
Coverage: Exhaustive · type-level: afferent/efferent coupling + cycles computed over every production type — the population is all types, not a name convention.
What it measures: Whether a class's methods are focused on a single responsibility.
Method: LCOM4 cohesion per production class with at least two methods: connected components of methods sharing state or calls, computed syntactically. Deterministic, not a proxy.
Coverage: Exhaustive · type-level: LCOM4 cohesion computed over every production class — the population is all types, not a name convention.
Resolve the 5 Low cohesion finding(s) in Cohesion (LCOM4) — start with Form17.cs, PoisonDataGridView.cs, PoisonListView.cs. — One of this dimension's main actionable groups (5 warning-level).
Detailed fixes: d6_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D8 · Code Coverage0.0 / 10Critical✓ Tool-verified
What it measures: How much of the code is actually exercised by tests.
Method: Coverage from the analyzer's own run of the suite, computed per-file with structured exclusions for generated, trivial, and glue code. A coverage report found in the repository is never read. When the suite can't be built/run in-image, coverage is reported NOT-MEASURED (excluded from the score) with the precondition to make it measurable — never a LoC-ratio proxy folded in as if measured. Deterministic.
What it measures: Whether any secrets (keys, tokens, passwords) have leaked into the code.
Method: In-process native secret scanner (entropy plus signature patterns) across all tracked files; no external tool. A clean result is a measured 10, not no-data zero. Deterministic.
What it measures: Whether the licenses of third-party packages are compatible with your policy.
Method: Third-party package licenses resolved from declared package metadata and checked against the configured policy (allow/deny/copyleft). Deterministic; clean = no incompatible license found at metadata depth.
0 of 87 packages use a banned license. ★ DEPTH: this repository's MSBuild projects declare 9 direct `PackageReference`(s), and 79 further package(s) were reached beyond them by closing the graph over nuget.org's own nuspec dependency graph — so a banned licence pulled in only by a dependency's OWN dependencies is inside this verdict. A package whose licence nuget.org could not be asked for is not graded, and version ranges are taken at their lower bound, so this is the closure as that graph states it rather than a restored consumer's exact resolution.
What it measures: Files that change often and are also complex — the riskiest hotspots.
Method: Per production file churn times cyclomatic complexity over a rolling window, computed from git and Roslyn/JS/Razor analysis. Exhaustive, deterministic per commit date.
What it measures: Acknowledged debt left in the code — TODOs, dead code, suppressed warnings.
Method: Roslyn syntactic debt markers (suppressions/TODO/FIXME/HACK/empty-catch/commented-code/Obsolete) plus SymbolFinder dead-code analysis; weighted-debt-per-KLoC density deducted 2.0x per unit. Deterministic, exhaustive.
169 deducted debt markers + unmeasured dead symbols across 123511 LoC in the .NET projects (1.0/KLoC) → score 8.0. Dead code not measured: the solution did not load cleanly, so the reference search was skipped.
+ 3 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 50 EmptyCatchBlock finding(s) in Explicit Debt — start with SkyComboBox.cs (3), HopeForm.cs (3), Material.cs (3). — One of this dimension's main actionable groups (50 issue-level).
Resolve the 36 WriteOnlyPrivateField finding(s) in Explicit Debt — start with ForeverForm.cs (3), DungeonCheckBox.cs (2), ForeverComboBox.cs (2). — One of this dimension's main actionable groups (36 issue-level).
Resolve the 2 NoWarnInCsproj finding(s) in Explicit Debt — start with ReaLTaiizor.csproj (2). — One of this dimension's main actionable groups (2 issue-level).
Detailed fixes: d17_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether the solution is laid out in a sensible, conventional structure.
Method: Solution structure: project count, decomposition, shell-project detection, build success (confirmed failures cap the score); traced to actual .sln files and binaries. Deterministic.
202 projects, 6311 source files, 123511 hand-written lines of code (123511 production / 0 test — the split is derived per file: test is what its project, its own path, or a compile-guarded region marks as test, and a file carrying no test signal counts as production), plus 40843 generated (machine-written code — designer, scaffolded and tool-emitted files — excluded from quality), 9 inter-project edges (build status unknown — did not finish).
What it measures: Whether the project's documentation is clear, complete, and useful.
Method: Every README, docs/ document and root guide parsed by its markup and measured in Unicode letters. Published: a runnable or packaged .NET project whose README (or a document it links, or a root guide) shows no example, and a root README naming none of three or more projects. Overview, licence, boilerplate, wall-of-text, empty-section and XML-doc rows are measured and withheld (counted in gaps) after adjudication. Deterministic, exhaustive, advisory.
2 of 2 documentation facets pass in full. 9 document(s) read across 14 unit(s).
✓ On the Gold path — maintain.
Detailed fixes: d19_recommendation.md.
Do you agree with this assessment?
D20 · ADR Quality0.0 / 10Critical✓ Tool-verified
What it measures: Whether architecture decisions are recorded well (context, decision, consequences).
Method: Every ADR read by its section structure: nine located rules (a missing Decision, Context or Consequences section, a stale status, two records deciding the same question, a dangling supersede link, a number-only title, a single option, no named cost, no status where the log uses one, no enforcement field where the log adopted one), each a fixed deduction from 10; the score is the mean over evaluated records. Deterministic, no model. Advisory.
No ADRs foundsrc/ReaLTaiizor/ReaLTaiizor.csproj:17
What to do
Resolve the 1 No ADRs found finding(s) in ADR Quality — start with ReaLTaiizor.csproj. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d20_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether names — types, methods, variables — are clear and consistent.
Method: Seven vocabulary-free rules (N1-N7) mine each naming convention from the repository and flag a name that breaks a convention its structural peers in the same unit follow; production C# and TypeScript, each its own population. Deterministic, no model, no sample. Advisory.
What it measures: Whether comments are worth it — explaining WHY (valuable) rather than WHAT (redundant).
Method: Every inline C# comment compared word by word with the identifiers, literals and constructs of the code it annotates (taken from the syntax); a comment whose words that code already contains is redundant, as are closing-brace labels and generator template text. Comments giving a reason or a reference are kept; other scripts and languages are not judged. Deterministic, exhaustive, advisory.
doc comments repeat the namessrc/ReaLTaiizor/Controls/Button/MaterialButton.cs:65
What to do
Resolve the 22 redundant comment finding(s) in Comment Value — start with SpaceLabel.cs (3), PoisonDropDownButton.cs (2), SpaceForm.cs (2). — One of this dimension's main actionable groups (22 recommendation-level).
Detailed fixes: d24_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: How far you must trace to follow a call — low indirection and co-located slices read easier.
Method: Call indirection (interface hops, cross-namespace calls, slice-locality scaled) over a sampled set of method invocations, size-aware baseline. Sampled; confidence discounted by symbol-resolution gaps. C# also names each pass-through layer (a class whose every public method only forwards its own parameters to one collaborator) as a located finding; the score is not affected.
Coverage: Slice locality from the first namespace segments, SAMPLED (≤400 methods) — not exhaustive.
99 % of calls cross a namespace and 1 % go through an interface, but 100 % of collaborators are co-located — so a call's collaborators sit together and tracing stays easy. Baseline: large — vertical-slice locality expected.
What it measures: Whether any secrets were ever committed — scanned across the full git history, not just now.
Method: Secret scan via TWO gitleaks detect passes in an isolated checkout — the full git history, then a second --no-git pass over the working tree as it stands — merged and de-duplicated by (rule, file, line); each match flagged High. Both invocations are recorded in the audit trail. Exhaustive; when the tool is absent, or when its output cannot be parsed into the expected shape, the dimension is WITHHELD as an explicit measurement gap on our side — unscored and excluded from the lens, never a hedged middling score.
What it measures: Real static-analysis (SAST) findings — likely security bugs in the code, any language.
Method: Polyglot static analysis via semgrep across the repo using the pinned, image-baked p/security-audit + p/owasp-top-ten rulesets (no scan-time registry fetch); severity rules (ERROR/WARNING/INFO) map to a full-band severity-weighted score. Exhaustive, deterministic; degrades on parse failure.
Coverage: semgrep pattern rules over all files — exhaustive for the rule set, blind to classes of bug without a rule (clean = no rule matched).
17 finding(s): 0 critical, 12 high, 5 medium, 0 low. 10 unpinned-GitHub-Actions row(s) are reported here but scored by D36 (supply-chain provenance), which measures that posture as `pinned_actions` — one pinning decision is charged once, not once per lens. semgrep hit a parse error in 1 file(s) — `src/ReaLTaiizor/Animate/Poison/DelayedCall.cs` — so no absence of findings in them is evidence of anything, and nothing in them was analysed. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them. In 1 of those file(s) — `src/ReaLTaiizor/Animate/Poison/DelayedCall.cs` — the break is at a TYPE DECLARATION (a C# primary constructor semgrep's grammar cannot parse), so the loss is wider than the named lines: rules scoped to that type see no type to scope to and are blind over its whole body, while rules matching statements keep working there. Absence of a type-scoped finding in those types is not evidence of anything. Separately, one or more rules could not re-parse an embedded snippet in 3 file(s) (e.g. a workflow `run:` block read as shell). Those files WERE scanned and their other rows are unaffected; only those rules' view of those snippets is missing.
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
What to do
Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
No action in Static Analysis (SAST) — all 10 REDACTED finding(s) are reported here at file:line but scored by D36 (supply-chain provenance), so none is charged to this dimension. — One of this dimension's main actionable groups (10 issue-level, 0 of them charged here).
Detailed fixes: d29_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether anyone still has living knowledge of each file, or it has been orphaned — last understood long ago by someone now gone quiet. The sibling of the bus factor: D16 asks who owns it, D34 asks whether anyone still knows it.
Method: File orphaning as total living-knowledge decay below one focused-commit's worth within a year, computed per-file from the D16 decay model. Exhaustive, deterministic over fixed history.
Every significant source file has living knowledge — recently and meaningfully worked. Counted over 384 of the 634 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
What it measures: Whether files that change together actually belong together — pairs that repeatedly co-change in git history despite having no explicit code dependency, surfacing the hidden/logical coupling (and boundaries in the wrong place) a static scan can't see.
Method: Pairwise co-occurrence over the per-commit file sets in git history (production source only — tests and generated dropped): Degree-of-Coupling = shared ÷ min individual revisions, reported above noise floors (each file ≥10 revisions, ≥5 shared commits, ≥50% strength); sweeping commits excluded. Deterministic over fixed history.
Coverage: Population: PRODUCTION source files only — test and generated files are dropped before pairing, so a class co-changing with its own test (trivially ~100%) can't drown the real production↔production coupling. Pairs ranked by Degree-of-Coupling. A non-source file is never a coupling PARTICIPANT either: documentation, schemas, config and data files are dropped with the rest, so a code↔docs pair — a command and the reference page that restates it — is not reported however strongly the two co-change; nor is coupling that runs THROUGH a build step or config file.
Resolve the 4 Change-coupling hub finding(s) in Change Coupling — start with MaterialRadioButton.cs, MaterialButton.cs, MaterialFloatingActionButton.cs. — One of this dimension's main actionable groups (4 warning-level).
Resolve the 3 Change coupling finding(s) in Change Coupling — start with HopeTextBox.cs, MaterialCheckBox.cs, MaterialContextMenuStrip.cs. — One of this dimension's main actionable groups (3 warning-level).
Detailed fixes: d35_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether any dependency the repository declares is published as MALICIOUS rather than merely vulnerable — a package that is an attacker's work, in any ecosystem osv-scanner reads. Reported apart from D30 because the answer is binary: there is no safe version to upgrade to, and the fix is to remove the package and rotate every credential it could have read.
Method: The same dependency scan D30 reads, partitioned on the scanner's own classification rather than rescanned: a row is MALICIOUS when its id is in the `MAL-` space (the ossf/malicious-packages feed) OR its `database_specific.cwe_ids` carries `CWE-506` ("Embedded Malicious Code"). Both channels are structural; the summary text is deliberately NOT read, because a malicious-package record whose summary says only "Critical severity vulnerability" is a real shape ([GHSA redacted]) and a text matcher misses it. Scored BINARY: any surviving row is 0, whatever its severity and however many CVEs sit beside it — a hostile dependency is not a quantity. Applicability and degradation are D30's: NotApplicable only when no ecosystem is readable, and an unscannable ecosystem degrades rather than reading clean. Advisory since rubric-2026.11.2 (CAI decision 0006): the malicious-package feed is a database that changes daily, so the reading is shown and never moves a scored dimension, lens or the headline.
What it measures: Whether anyone still ships security patches for the platform this repository RUNS ON — the runtime it pins and the framework majors its own constraints hold it to. Separate from D12 because the question differs: a current Django on an end-of-life Python is perfectly up to date and completely unsupported, and the fix is a migration rather than a version bump. What the repository says it merely SUPPORTS is never charged.
Method: End-of-life PLATFORM read from the repository's own declarations and graded against a FROZEN, dated table of vendor support dates — no network, no feed, no API, so this dimension answers identically inside a closed scan fence. Two subjects: a RUNTIME the project pins (a single or all-end-of-life TargetFramework, a .nvmrc or .python-version, a requires-python CAP) and a FRAMEWORK major a dependency constraint cannot move off (a caret, tilde or exact version; `vue@^2.7.16` pins Vue 2). A FLOOR is deliberately never charged — `requires-python = ">=3.8"` states what a package SUPPORTS, not what it runs on — and a multi-target project is charged only when EVERY target is out of support. Runtime 4.0/product capped 8.0, framework 1.5 capped 4.5. The table is safe to freeze because a statement about support that ended in the past cannot become false: it loses recall as it ages, never precision, and a test asserts every entry predates the freeze date. Disjoint from D31 (a container image's OS layer) and D29 (the toolchain a CI workflow installs). Abstains when the repository declares no platform this pass reads — never scores it clean.
0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 26 platform declaration(s) and 0 dependency declaration(s). This dimension reads what the repository says about ITSELF — a pinned target framework, a version file, a capped requires-python, a Rust toolchain pin, a framework major a constraint cannot move off. A FLOOR is deliberately never charged: `requires-python = ">=3.8"` states what the package SUPPORTS, not what it runs on, and a well-maintained library declares exactly that while running its own CI on a current release. The end-of-life facts are FROZEN and dated, so this dimension needs no network and answers identically inside a closed scan fence; as the table ages it loses recall and never precision, because a statement about support that ended in the past cannot become false. The OS layer of a container image is D31's question and the toolchain a CI workflow installs is D29's; this row is neither.
Other · Architecture — How the codebase splits by code ROLE — domain, application, infrastructure, test, generated. The significance map behind the knowledge/coupling weighting, and a DDD signal in its own right: a thin domain core under fat infrastructure is the anemic-domain smell, quantified. How each file's role is decided, because the split is only as good as that: a generated name or a build-output tree makes it Generated, a test project makes it Test, and otherwise the file's NAMESPACE and PATH words are matched against fixed vocabularies in a fixed ORDER — domain, then infrastructure, then application — so a file whose words hit two layers is counted under the earlier one. A production file matching none of them counts as application, so that share reads 'application or unclassified' rather than a measured application layer. Roles come from naming convention, never from what the code does.
Method: Roslyn line-count by code ROLE: every source file classified Domain/Application/Infrastructure/Test/Generated by namespace + path convention (the shared CodeRoleClassifier), then significant lines summed per role. Deterministic; the advisory score is the business-logic (domain+application) share of production code.
Coverage: Population: ALL source files, each bucketed into ONE of five roles (Domain/Application/Infrastructure/Test/Generated) by namespace + path convention — a file whose layer isn't named in the convention falls to Application (the neutral default), and the split is line-count, not semantic depth or business value.
Other · Architecture — Whether singleton services avoid mutable shared instance state that concurrent callers would race on.
Method: Roslyn scan: singleton field mutations unguarded by lock or Interlocked, per type; syntax-based guard detection. Deterministic, traceable per field.
`DelayedCall` keeps one instance of itself in the static `dcList`, so that one instance serves the whole process and is shared by every thread that reaches it — and it mutates instance state outside any lock (oldData; e.g. `oldData` at line 82). — src/ReaLTaiizor/Animate/Poison/DelayedCall.cs:13
`PoisonTaskWindow` keeps one instance of itself in the static `singletonWindow`, so that one instance serves the whole process and is shared by every thread that reaches it — and it mutates instance state outside any lock (isInitialized, timer, elapsedTime, progressWidth; e.g. `isInitialized` at line 169). — src/ReaLTaiizor/Controls/Window/PoisonTaskWindow.cs:20
`MaterialSkinManager` keeps one instance of itself in the static `<Instance>k__BackingField`, so that one instance serves the whole process and is shared by every thread that reaches it — and it mutates instance state outside any lock (_formsToManage; e.g. `_formsToManage` at line 546). — src/ReaLTaiizor/Manager/MaterialSkinManager.cs:24
`PrecisionTimerAir` is not registered, but `ThemeShareAir` creates it and keeps it in the static `ThemeTimer`, so that one instance serves the whole process and is shared by every thread that reaches it — and it mutates instance state outside any lock (TimerCallback, Handle, Enabled; e.g. `TimerCallback` at line 2558). — src/ReaLTaiizor/Util/Air.cs:2536
`MaterialMouseWheelRedirector` keeps one instance of itself in the static `instance`, so that one instance serves the whole process and is shared by every thread that reaches it — and it mutates instance state outside any lock (currentControl; e.g. `currentControl` at line 1393). — src/ReaLTaiizor/Util/Material.cs:1325
`PrecisionTimerMoon` is not registered, but `ThemeShareMoon` creates it and keeps it in the static `ThemeTimer`, so that one instance serves the whole process and is shared by every thread that reaches it — and it mutates instance state outside any lock (TimerCallback, Handle, Enabled; e.g. `TimerCallback` at line 2563). — src/ReaLTaiizor/Util/Moon.cs:2541
`PrecisionTimerSpace` is not registered, but `ThemeShareSpace` creates it and keeps it in the static `ThemeTimer`, so that one instance serves the whole process and is shared by every thread that reaches it — and it mutates instance state outside any lock (TimerCallback, Handle, Enabled; e.g. `TimerCallback` at line 2562). — src/ReaLTaiizor/Util/Space.cs:2540
`PoisonPanel` is not registered, but the singleton `PoisonTaskWindow` creates it and keeps it in `controlContainer`, so one instance outlives every request and is shared by every caller that reaches it — and it mutates instance state outside any lock (HorizontalScrollbar, VerticalScrollbar; e.g. `HorizontalScrollbar` at line 198). — src/ReaLTaiizor/Controls/Panel/PoisonPanel.cs:21
`PoisonScrollBar` is not registered, but the singleton `PoisonPanel` creates it and keeps it in `VerticalPoisonScrollbar`, so one instance outlives every request and is shared by every caller that reaches it — and it mutates instance state outside any lock (isFirstScrollEventHorizontal, isFirstScrollEventVertical, scrollOrientation, curValue, largeChange, dontUpdateColor; e.g. `isFirstScrollEventHorizontal` at line 163). — src/ReaLTaiizor/Controls/ScrollBar/PoisonScrollBar.cs:22
`AppLocker` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (PProcs; e.g. `PProcs` at line 38). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt. — ready/ReaLTaiizor.AppLocker/ReaLTaiizor.AppLocker/AppLocker.cs:10
`Translate` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (Lang; e.g. `Lang` at line 28). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt. — ready/ReaLTaiizor.Translate/ReaLTaiizor.Translate/Translate.cs:12
`CyberButton` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (tmp_color_background_pen; e.g. `tmp_color_background_pen` at line 234). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt. — src/ReaLTaiizor/Controls/Button/CyberButton.cs:19
`CyberCheckBox` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (tmp_color_background_pen; e.g. `tmp_color_background_pen` at line 193). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt. — src/ReaLTaiizor/Controls/CheckBox/CyberCheckBox.cs:19
`MaterialCheckBox` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (CheckmarkLine; e.g. `CheckmarkLine` at line 445). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt. — src/ReaLTaiizor/Controls/CheckBox/MaterialCheckBox.cs:20
`MetroMessageBox` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (BackgroundColor, BorderColor, ForegroundColor; e.g. `BackgroundColor` at line 241). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt. — src/ReaLTaiizor/Controls/MessageBox/MetroMessageBox.cs:17
`RoyalMessageBox` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (mode; e.g. `mode` at line 32). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt. — src/ReaLTaiizor/Controls/MessageBox/RoyalMessageBox.cs:14
`CyberRadioButton` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (tmp_color_background_pen; e.g. `tmp_color_background_pen` at line 209). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt. — src/ReaLTaiizor/Controls/RadioButton/CyberRadioButton.cs:19
`HopeRichTextBox` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (_currentControlStartSize; e.g. `_currentControlStartSize` at line 103). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt. — src/ReaLTaiizor/Controls/RichTextBox/HopeRichTextBox.cs:18
`MetroContextMenuStrip` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (ForegroundColor, BackgroundColor, ArrowColor, SelectedItemBackColor, SelectedItemColor, SeparatorColor; e.g. `ForegroundColor` at line 104). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt. — src/ReaLTaiizor/Controls/Strip/MetroContextMenuStrip.cs:20
`ThemeShareAir` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (Invalidate, Frames; e.g. `Invalidate` at line 2437). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt. — src/ReaLTaiizor/Util/Air.cs:2419
`DrawEngine` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (Temp; e.g. `Temp` at line 129). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt. — src/ReaLTaiizor/Util/Cyber.cs:19
`ThemeLost` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (TitleFont, HeaderFont, BodyFont, FontColor, FontBrush, FontPen; e.g. `TitleFont` at line 42). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt. — src/ReaLTaiizor/Util/Lost.cs:15
`MaterialNativeTextRenderer` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (_fontsCache; e.g. `_fontsCache` at line 401). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt. — src/ReaLTaiizor/Util/Material.cs:162
`ThemeShareMoon` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (Invalidate, Frames; e.g. `Invalidate` at line 2441). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt. — src/ReaLTaiizor/Util/Moon.cs:2423
`ThemeShareSpace` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (Invalidate, Frames; e.g. `Invalidate` at line 2439). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt. — src/ReaLTaiizor/Util/Space.cs:2420
`Status` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (ChangedStatus; e.g. `ChangedStatus` at line 16). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt. — ready/ReaLTaiizor.Nerator/ReaLTaiizor.Nerator/CS/Status.cs:5
What to do
Keep singletons stateless or back their state with thread-safe types (Concurrent*/Immutable*); otherwise concurrent callers race.
A `static` field is one slot for the whole process, however its type is created: back it with a thread-safe type (ConcurrentDictionary, Interlocked), take a lock around every write, or move it into a registered singleton that does.
Other · Architecture — Whether the project-reference graph is acyclic (cycles block independent build/deploy and signal eroding boundaries).
Method: Project reference cycles via elementary-DFS over real .csproj references, using the engine shared with D5/D7; cyclic versus acyclic. Exhaustive, deterministic.
The namespaces ReaLTaiizor.Colors ↔ ReaLTaiizor.Util depend on each other. The lightest dependency in the cycle is ReaLTaiizor.Colors → ReaLTaiizor.Util (ReaLTaiizor.Colors.MaterialColorScheme → ReaLTaiizor.Util.MaterialTextShade, 1 type pair(s)); cut that one first, e.g. by moving the shared type to a namespace both can use or inverting it behind an interface. — src/ReaLTaiizor/Colors/Material.cs:4
The namespaces ReaLTaiizor.Child.Crown ↔ ReaLTaiizor.Child.Material ↔ ReaLTaiizor.Child.Metro ↔ ReaLTaiizor.Child.Poison ↔ ReaLTaiizor.Controls ↔ ReaLTaiizor.Docking.Crown ↔ ReaLTaiizor.Forms ↔ ReaLTaiizor.Helper ↔ ReaLTaiizor.Interface.Metro ↔ ReaLTaiizor.Interface.Poison ↔ ReaLTaiizor.Manager ↔ ReaLTaiizor.Native ↔ ReaLTaiizor.Properties depend on each other. The lightest dependency in the cycle is ReaLTaiizor.Child.Crown → ReaLTaiizor.Forms (ReaLTaiizor.Child.Crown.CrownDialog → ReaLTaiizor.Forms.CrownForm, 1 type pair(s)); cut that one first, e.g. by moving the shared type to a namespace both can use or inverting it behind an interface. — src/ReaLTaiizor/Child/Crown/CrownDialog.cs:5
What to do
Break namespace cycles inside a project by moving the shared type to a namespace both sides can use, or by inverting the back edge behind an interface.
Other · Architecture — Whether dependencies point inward (Domain ← Application ← Infrastructure/Web) — the clean-architecture dependency rule, checked across the project graph.
Method: Layer violations by name-segment inference (Domain/Core to Application to Infrastructure/Web) over the project-reference graph. Exhaustive over all projects, deterministic.
Other · Architecture — Whether the codebase has a recognisable, scale-appropriate structure (a named architectural style, or modular enough for its size) rather than being an ad-hoc ball of mud.
Method: Roslyn plus csproj analysis: architecture style detection (DDD, clean, vertical-slice, CQRS) and structure fitness for repo size. Deterministic.
Other · Architecture — Whether interfaces stay focused rather than fat — the Interface-Segregation principle (SOLID 'I').
Method: Roslyn scan: public interface declared-member counts (accessors fold into their property/event); fat-interface threshold (over 15 declared members) flagged per type. Each finding also reports the distinct-OPERATION count — members counted by name, so an overload group counts once — which decides whether it states the caller-side ISP harm or the implementer-side burden of an overload set. TypeScript: exported interfaces that declare behaviour, counted over their REQUIRED operations (method signatures and function-typed properties with no `?`, once per signature) — data-shape interfaces and ambient .d.ts declarations are outside the population; JavaScript declares no interfaces and is not applicable. Deterministic, type-level.
Do you agree with this assessment?
C1 · Data Protection0.0 / 10Critical✓ Tool-verified
Other · Security — Whether sensitive data is encrypted at rest and in transit and keys are vaulted.
Method: Roslyn plus filesystem scan: encryption presence (EF ColumnEncryption, key-vault references, HTTPS enforcement) and key-derivation KDF detection. Deterministic.
No data-protection or encryption usage (ASP.NET Data Protection, AES, column encryption, PBKDF2) was found — sensitive data at rest may be unprotected. If TDE/KMS/vault is delegated to infrastructure, ignore.
What to do
Encrypt sensitive data at rest (ASP.NET Core Data Protection / column encryption) and manage keys in a vault. Skip if delegated to infra (Postgres TDE, KMS, etc.).
Enforce HTTPS (UseHttpsRedirection / RequireHttpsMetadata) so data in transit is always encrypted.
Other · Code Health — Unreviewed-generation residue: shipped members still throwing NotImplementedException, and placeholder string literals left in non-test, non-generated code. Scored as a quality signature, never as a claim about authorship.
Method: Roslyn syntax scan: NotImplementedException throws and placeholder string literals in non-test, non-generated shipped code. Deterministic, code-shape signature.
A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface. — src/ReaLTaiizor/Native/User32.cs:97
What to do
Finish or delete NotImplementedException stubs and replace placeholder literals before shipping.
Other · Code Health — Unfinished work detected by code SHAPE, not keywords: members that only throw a "not implemented" exception, methods that take inputs and return a constant, async methods that never await, dead `if (false)` / `#if false` branches, and skeleton types most of whose members are holes. A real, objective slice of technical debt.
Method: Roslyn syntax scan: incompleteness by code shape (constant-returning methods, async-never-await, #if false branches, guards that return what the code already falls through to, tests an earlier guard already decided, comparisons against NaN, skeleton types), not keyword-gated. Deterministic, code-shape heuristic.
The first 2 statements of the `if` and of the `else` are identical, so they run on both paths regardless of the condition. Lift them above the `if` — leaving them duplicated inside makes the branches read as though they handled this differently. (×4) — src/ReaLTaiizor/Controls/Bar/ParrotNavigationBar.cs:43, src/ReaLTaiizor/Controls/ControlBox/MetroControlBox.cs:447, src/ReaLTaiizor/Controls/ControlBox/NightControlBox.cs:269, …
Both arms of `_isDefault ? … : …` are `ThemeProvider.Theme.Colors.DarkBackground`, so no input can make the condition matter. Implement the distinction that was intended, or drop the condition. — src/ReaLTaiizor/Controls/Button/CrownButton.cs:342
The `if` and its `else` contain the same 1 statement, so no input can make the condition matter. Implement the distinction that was intended, or drop the branch and keep the body. (×4) — src/ReaLTaiizor/Controls/Button/ParrotButton.cs:333, src/ReaLTaiizor/Controls/Button/ParrotButton.cs:395, src/ReaLTaiizor/Controls/Button/ParrotButton.cs:403, …
The `if` and its `else` contain the same 2 statements, so no input can make the condition matter. Implement the distinction that was intended, or drop the branch and keep the body. — src/ReaLTaiizor/Controls/CheckBox/CheckBox.cs:120
The first 3 statements of the `if` and of the `else` are identical, so they run on both paths regardless of the condition. Lift them above the `if` — leaving them duplicated inside makes the branches read as though they handled this differently. (×6) — src/ReaLTaiizor/Controls/ControlBox/ThunderControlBox.cs:208, src/ReaLTaiizor/Controls/ControlBox/ThunderControlBox.cs:237, src/ReaLTaiizor/Controls/ControlBox/ThunderControlBox.cs:270, …
The first 4 statements of the `if` and of the `else` are identical, so they run on both paths regardless of the condition. Lift them above the `if` — leaving them duplicated inside makes the branches read as though they handled this differently. — src/ReaLTaiizor/Controls/ControlBox/ThunderControlBox.cs:263
Both arms of `TabIndex == 0 ? … : …` are `1`, so no input can make the condition matter. Implement the distinction that was intended, or drop the condition. (×2) — src/ReaLTaiizor/Controls/TabPage/TabPage.cs:265, src/ReaLTaiizor/Controls/TabPage/TabPage.cs:287
Both arms of `Theme == Themes.LIGHT ? … : …` are `BACKGROUND_HOVER_RED`, so no input can make the condition matter. Implement the distinction that was intended, or drop the condition. — src/ReaLTaiizor/Manager/MaterialSkinManager.cs:351
Both arms of `Theme == Themes.LIGHT ? … : …` are `BACKGROUND_HOVER_RED_BRUSH`, so no input can make the condition matter. Implement the distinction that was intended, or drop the condition. — src/ReaLTaiizor/Manager/MaterialSkinManager.cs:352
Both arms of `Theme == Themes.LIGHT ? … : …` are `BACKGROUND_DOWN_RED_BRUSH`, so no input can make the condition matter. Implement the distinction that was intended, or drop the condition. — src/ReaLTaiizor/Manager/MaterialSkinManager.cs:353
`AnimateWindow` is a shipped member whose whole body throws NotImplementedException — scaffolding that was never completed. Implement it or remove the dead surface. — src/ReaLTaiizor/Native/User32.cs:97
`ThrowNewException` takes parameters but its body is empty — it accepts inputs and does nothing. Either implement it or remove it. — src/ReaLTaiizor/Util/Moon.cs:2592
A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers). (×12) — ready/ReaLTaiizor.MAChanger/ReaLTaiizor.MAChanger/MAChanger.cs:67, ready/ReaLTaiizor.Nerator/ReaLTaiizor.Nerator/CS/Generator.cs:47, ready/ReaLTaiizor.Nerator/ReaLTaiizor.Nerator/CS/Strength.cs:245, …
14 consecutive lines of code sit inside a `/* … */` block — a block of code switched off rather than removed, which rots and confuses. Delete it (version control remembers). — ready/ReaLTaiizor.Nerator/ReaLTaiizor.Nerator/CS/Generator.cs:52
4 consecutive lines of code sit inside a `/* … */` block — a block of code switched off rather than removed, which rots and confuses. Delete it (version control remembers). (×2) — ready/ReaLTaiizor.Nerator/ReaLTaiizor.Nerator/CS/Generator.cs:73, ready/ReaLTaiizor.Nerator/ReaLTaiizor.Nerator/CS/Generator.cs:80
15 consecutive lines of code sit inside a `/* … */` block — a block of code switched off rather than removed, which rots and confuses. Delete it (version control remembers). — ready/ReaLTaiizor.Portscan/ReaLTaiizor.Portscan/Portscan.cs:375
What to do
Finish or delete the unfinished stubs (NotImplementedException / empty / constant-returning bodies) — they are dead surface that looks live.
Clear the softer debt: remove commented-out code and dead branches, re-enable or delete skipped tests, and replace blanket warning suppressions with targeted ones.
Maturity · Maturity — Whether the repository and its projects have a README, and whether it is substantive.
Method: Filesystem scan: README presence, word count, and headings for depth; git history for staleness. Exhaustive across root and project dirs, deterministic.
Maturity · Maturity — Whether key decisions (ADRs) and the high-level shape (C4/diagrams) are written down.
Method: Filesystem scan: ADR folder/naming conventions or content, plus Mermaid/PlantUML/C4/architecture.md discovery. Exhaustive, deterministic.
No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
No C4/Structurizr/PlantUML/Mermaid/Graphviz/D2 diagram, no drawn diagram named for the architecture, no file named `architecture` or `design` in any markup this check reads, and nothing in the README, docs or contributor guides that announces the shape — no `## Architecture` heading, no "architecture overview"/"high-level design" phrasing, no "the architecture is …" introduction, no guided code tour. A shape laid out in prose that never names itself as the architecture is not visible to this check, and neither is one kept outside the repository, so this row reports the absence of a re-findable shape document — not evidence that nobody wrote the shape down.
What to do
Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
Add a C4 context/container diagram (Structurizr, PlantUML or Mermaid) or an architecture.md overview.
Maturity · Maturity — Whether the repository is organised deliberately: production code and tests are set apart in a way its ecosystem or the repository itself declares.
Method: Filesystem scan: src/test folder separation and namespace-prefix consistency (majority RootNamespace agreement). Exhaustive across projects, deterministic.
Readiness · Readiness — Whether an automated pipeline builds and tests every change.
Method: Filesystem scan: CI workflow files (.github/workflows, .gitlab-ci.yml, etc.) for build and test stages. Exhaustive, deterministic.
Do you agree with this assessment?
P10 · Library API & versioning9.1 / 10Exemplary✓ Tool-verified
Readiness · Readiness — For a library: a deliberate (small) public API surface and explicit semantic versioning so consumers can depend on it safely.
Method: Roslyn scan: public API surface area and semantic-versioning markers (SemVer attributes, changelog entries) for libraries; off .NET, a library is the ecosystem's publication act (an npm package that is not private and names an entry point, a PyPI distribution with a build system, a Rust library crate, a Maven/Gradle module that publishes, a Go module with no package main, a gemspec, a Composer library, a SwiftPM library product, a pub.dev or Hex package), its surface is the share of types the language's code model records as public (Rust, Swift, Java, Kotlin, Go, Dart; not measured where the model records no type visibility or, as in TypeScript, only module-level export), and its version is read from the manifest, a semver CHANGELOG, release tooling or semver git tags. Exhaustive, deterministic.
`ReaLTaiizor.Action.Metro.MetroBadgeActionList` (src/ReaLTaiizor/Action/Metro/MetroBadgeActionList.cs:16) is public, and the library's own code uses it, but no other project in this repository uses it (read: `ReaLTaiizor_CR(net48)`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such. — src/ReaLTaiizor/Action/Metro/MetroBadgeActionList.cs:16
`ReaLTaiizor.Action.Metro.MetroBadgeActionList` (src/ReaLTaiizor/Action/Metro/MetroBadgeActionList.cs:16) is public, and the library's own code uses it, but no other project in this repository uses it (read: `ReaLTaiizor_CR(net481)`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such. — src/ReaLTaiizor/Action/Metro/MetroBadgeActionList.cs:16
`ReaLTaiizor.Action.Metro.MetroBadgeActionList` (src/ReaLTaiizor/Action/Metro/MetroBadgeActionList.cs:16) is public, and the library's own code uses it, but no other project in this repository uses it (read: `ReaLTaiizor_CR(netcoreapp3.1-windows)`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such. — src/ReaLTaiizor/Action/Metro/MetroBadgeActionList.cs:16
`ReaLTaiizor.Action.Metro.MetroBadgeActionList` (src/ReaLTaiizor/Action/Metro/MetroBadgeActionList.cs:16) is public, and the library's own code uses it, but no other project in this repository uses it (read: `ReaLTaiizor_CR(net6.0-windows)`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such. — src/ReaLTaiizor/Action/Metro/MetroBadgeActionList.cs:16
`ReaLTaiizor.Action.Metro.MetroBadgeActionList` (src/ReaLTaiizor/Action/Metro/MetroBadgeActionList.cs:16) is public, and the library's own code uses it, but no other project in this repository uses it (read: `ReaLTaiizor_CR(net7.0-windows)`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such. — src/ReaLTaiizor/Action/Metro/MetroBadgeActionList.cs:16
`ReaLTaiizor.Action.Metro.MetroBadgeActionList` (src/ReaLTaiizor/Action/Metro/MetroBadgeActionList.cs:16) is public, and the library's own code uses it, but no other project in this repository uses it (read: `ReaLTaiizor_CR(net8.0-windows)`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such. — src/ReaLTaiizor/Action/Metro/MetroBadgeActionList.cs:16
`ReaLTaiizor.Action.Metro.MetroBadgeActionList` (src/ReaLTaiizor/Action/Metro/MetroBadgeActionList.cs:16) is public, and the library's own code uses it, but no other project in this repository uses it (read: `ReaLTaiizor_CR(net9.0-windows)`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such. — src/ReaLTaiizor/Action/Metro/MetroBadgeActionList.cs:16
`ReaLTaiizor.Action.Metro.MetroBadgeActionList` (src/ReaLTaiizor/Action/Metro/MetroBadgeActionList.cs:16) is public, and the library's own code uses it, but no other project in this repository uses it (read: `ReaLTaiizor_CR(net10.0-windows)`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such. — src/ReaLTaiizor/Action/Metro/MetroBadgeActionList.cs:16
`ReaLTaiizor.Action.Metro.MetroBadgeActionList` (src/ReaLTaiizor/Action/Metro/MetroBadgeActionList.cs:16) is public, and the library's own code uses it, but no other project in this repository uses it (read: `ReaLTaiizor_CR(net11.0-windows)`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such. — src/ReaLTaiizor/Action/Metro/MetroBadgeActionList.cs:16
`ReaLTaiizor.Action.Metro.MetroButtonActionList` (src/ReaLTaiizor/Action/Metro/MetroButtonActionList.cs:16) is public, and the library's own code uses it, but no other project in this repository uses it (read: `ReaLTaiizor_CR(net48)`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such. — src/ReaLTaiizor/Action/Metro/MetroButtonActionList.cs:16
`ReaLTaiizor.Action.Metro.MetroButtonActionList` (src/ReaLTaiizor/Action/Metro/MetroButtonActionList.cs:16) is public, and the library's own code uses it, but no other project in this repository uses it (read: `ReaLTaiizor_CR(net481)`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such. — src/ReaLTaiizor/Action/Metro/MetroButtonActionList.cs:16
`ReaLTaiizor.Action.Metro.MetroButtonActionList` (src/ReaLTaiizor/Action/Metro/MetroButtonActionList.cs:16) is public, and the library's own code uses it, but no other project in this repository uses it (read: `ReaLTaiizor_CR(netcoreapp3.1-windows)`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such. — src/ReaLTaiizor/Action/Metro/MetroButtonActionList.cs:16
`ReaLTaiizor.Action.Metro.MetroButtonActionList` (src/ReaLTaiizor/Action/Metro/MetroButtonActionList.cs:16) is public, and the library's own code uses it, but no other project in this repository uses it (read: `ReaLTaiizor_CR(net6.0-windows)`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such. — src/ReaLTaiizor/Action/Metro/MetroButtonActionList.cs:16
`ReaLTaiizor.Action.Metro.MetroButtonActionList` (src/ReaLTaiizor/Action/Metro/MetroButtonActionList.cs:16) is public, and the library's own code uses it, but no other project in this repository uses it (read: `ReaLTaiizor_CR(net7.0-windows)`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such. — src/ReaLTaiizor/Action/Metro/MetroButtonActionList.cs:16
`ReaLTaiizor.Action.Metro.MetroButtonActionList` (src/ReaLTaiizor/Action/Metro/MetroButtonActionList.cs:16) is public, and the library's own code uses it, but no other project in this repository uses it (read: `ReaLTaiizor_CR(net8.0-windows)`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such. — src/ReaLTaiizor/Action/Metro/MetroButtonActionList.cs:16
`ReaLTaiizor.Action.Metro.MetroButtonActionList` (src/ReaLTaiizor/Action/Metro/MetroButtonActionList.cs:16) is public, and the library's own code uses it, but no other project in this repository uses it (read: `ReaLTaiizor_CR(net9.0-windows)`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such. — src/ReaLTaiizor/Action/Metro/MetroButtonActionList.cs:16
`ReaLTaiizor.Action.Metro.MetroButtonActionList` (src/ReaLTaiizor/Action/Metro/MetroButtonActionList.cs:16) is public, and the library's own code uses it, but no other project in this repository uses it (read: `ReaLTaiizor_CR(net10.0-windows)`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such. — src/ReaLTaiizor/Action/Metro/MetroButtonActionList.cs:16
`ReaLTaiizor.Action.Metro.MetroButtonActionList` (src/ReaLTaiizor/Action/Metro/MetroButtonActionList.cs:16) is public, and the library's own code uses it, but no other project in this repository uses it (read: `ReaLTaiizor_CR(net11.0-windows)`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such. — src/ReaLTaiizor/Action/Metro/MetroButtonActionList.cs:16
`ReaLTaiizor.Action.Metro.MetroDefaultButtonActionList` (src/ReaLTaiizor/Action/Metro/MetroDefaultButtonActionList.cs:16) is public, and the library's own code uses it, but no other project in this repository uses it (read: `ReaLTaiizor_CR(net48)`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such. — src/ReaLTaiizor/Action/Metro/MetroDefaultButtonActionList.cs:16
`ReaLTaiizor.Action.Metro.MetroDefaultButtonActionList` (src/ReaLTaiizor/Action/Metro/MetroDefaultButtonActionList.cs:16) is public, and the library's own code uses it, but no other project in this repository uses it (read: `ReaLTaiizor_CR(net481)`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such. — src/ReaLTaiizor/Action/Metro/MetroDefaultButtonActionList.cs:16
`ReaLTaiizor.Action.Metro.MetroDefaultButtonActionList` (src/ReaLTaiizor/Action/Metro/MetroDefaultButtonActionList.cs:16) is public, and the library's own code uses it, but no other project in this repository uses it (read: `ReaLTaiizor_CR(netcoreapp3.1-windows)`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such. — src/ReaLTaiizor/Action/Metro/MetroDefaultButtonActionList.cs:16
`ReaLTaiizor.Action.Metro.MetroDefaultButtonActionList` (src/ReaLTaiizor/Action/Metro/MetroDefaultButtonActionList.cs:16) is public, and the library's own code uses it, but no other project in this repository uses it (read: `ReaLTaiizor_CR(net6.0-windows)`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such. — src/ReaLTaiizor/Action/Metro/MetroDefaultButtonActionList.cs:16
`ReaLTaiizor.Action.Metro.MetroDefaultButtonActionList` (src/ReaLTaiizor/Action/Metro/MetroDefaultButtonActionList.cs:16) is public, and the library's own code uses it, but no other project in this repository uses it (read: `ReaLTaiizor_CR(net7.0-windows)`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such. — src/ReaLTaiizor/Action/Metro/MetroDefaultButtonActionList.cs:16
`ReaLTaiizor.Action.Metro.MetroDefaultButtonActionList` (src/ReaLTaiizor/Action/Metro/MetroDefaultButtonActionList.cs:16) is public, and the library's own code uses it, but no other project in this repository uses it (read: `ReaLTaiizor_CR(net8.0-windows)`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such. — src/ReaLTaiizor/Action/Metro/MetroDefaultButtonActionList.cs:16
`ReaLTaiizor.Action.Metro.MetroDefaultButtonActionList` (src/ReaLTaiizor/Action/Metro/MetroDefaultButtonActionList.cs:16) is public, and the library's own code uses it, but no other project in this repository uses it (read: `ReaLTaiizor_CR(net9.0-windows)`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such. — src/ReaLTaiizor/Action/Metro/MetroDefaultButtonActionList.cs:16
`ReaLTaiizor.Action.Metro.MetroDefaultButtonActionList` (src/ReaLTaiizor/Action/Metro/MetroDefaultButtonActionList.cs:16) is public, and the library's own code uses it, but no other project in this repository uses it (read: `ReaLTaiizor_CR(net10.0-windows)`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such. — src/ReaLTaiizor/Action/Metro/MetroDefaultButtonActionList.cs:16
`ReaLTaiizor.Action.Metro.MetroDefaultButtonActionList` (src/ReaLTaiizor/Action/Metro/MetroDefaultButtonActionList.cs:16) is public, and the library's own code uses it, but no other project in this repository uses it (read: `ReaLTaiizor_CR(net11.0-windows)`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such. — src/ReaLTaiizor/Action/Metro/MetroDefaultButtonActionList.cs:16
`ReaLTaiizor.Action.Metro.MetroEllipseActionList` (src/ReaLTaiizor/Action/Metro/MetroEllipseActionList.cs:16) is public, and the library's own code uses it, but no other project in this repository uses it (read: `ReaLTaiizor_CR(net48)`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such. — src/ReaLTaiizor/Action/Metro/MetroEllipseActionList.cs:16
`ReaLTaiizor.Action.Metro.MetroEllipseActionList` (src/ReaLTaiizor/Action/Metro/MetroEllipseActionList.cs:16) is public, and the library's own code uses it, but no other project in this repository uses it (read: `ReaLTaiizor_CR(net481)`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such. — src/ReaLTaiizor/Action/Metro/MetroEllipseActionList.cs:16
`ReaLTaiizor.Action.Metro.MetroEllipseActionList` (src/ReaLTaiizor/Action/Metro/MetroEllipseActionList.cs:16) is public, and the library's own code uses it, but no other project in this repository uses it (read: `ReaLTaiizor_CR(netcoreapp3.1-windows)`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such. — src/ReaLTaiizor/Action/Metro/MetroEllipseActionList.cs:16
`ReaLTaiizor.Action.Metro.MetroEllipseActionList` (src/ReaLTaiizor/Action/Metro/MetroEllipseActionList.cs:16) is public, and the library's own code uses it, but no other project in this repository uses it (read: `ReaLTaiizor_CR(net6.0-windows)`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such. — src/ReaLTaiizor/Action/Metro/MetroEllipseActionList.cs:16
`ReaLTaiizor.Action.Metro.MetroEllipseActionList` (src/ReaLTaiizor/Action/Metro/MetroEllipseActionList.cs:16) is public, and the library's own code uses it, but no other project in this repository uses it (read: `ReaLTaiizor_CR(net7.0-windows)`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such. — src/ReaLTaiizor/Action/Metro/MetroEllipseActionList.cs:16
`ReaLTaiizor.Action.Metro.MetroEllipseActionList` (src/ReaLTaiizor/Action/Metro/MetroEllipseActionList.cs:16) is public, and the library's own code uses it, but no other project in this repository uses it (read: `ReaLTaiizor_CR(net8.0-windows)`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such. — src/ReaLTaiizor/Action/Metro/MetroEllipseActionList.cs:16
`ReaLTaiizor.Action.Metro.MetroEllipseActionList` (src/ReaLTaiizor/Action/Metro/MetroEllipseActionList.cs:16) is public, and the library's own code uses it, but no other project in this repository uses it (read: `ReaLTaiizor_CR(net9.0-windows)`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such. — src/ReaLTaiizor/Action/Metro/MetroEllipseActionList.cs:16
`ReaLTaiizor.Action.Metro.MetroEllipseActionList` (src/ReaLTaiizor/Action/Metro/MetroEllipseActionList.cs:16) is public, and the library's own code uses it, but no other project in this repository uses it (read: `ReaLTaiizor_CR(net10.0-windows)`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such. — src/ReaLTaiizor/Action/Metro/MetroEllipseActionList.cs:16
`ReaLTaiizor.Action.Metro.MetroEllipseActionList` (src/ReaLTaiizor/Action/Metro/MetroEllipseActionList.cs:16) is public, and the library's own code uses it, but no other project in this repository uses it (read: `ReaLTaiizor_CR(net11.0-windows)`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such. — src/ReaLTaiizor/Action/Metro/MetroEllipseActionList.cs:16
`ReaLTaiizor.Action.Metro.MetroTileActionList` (src/ReaLTaiizor/Action/Metro/MetroTileActionList.cs:16) is public, and the library's own code uses it, but no other project in this repository uses it (read: `ReaLTaiizor_CR(net48)`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such. — src/ReaLTaiizor/Action/Metro/MetroTileActionList.cs:16
`ReaLTaiizor.Action.Metro.MetroTileActionList` (src/ReaLTaiizor/Action/Metro/MetroTileActionList.cs:16) is public, and the library's own code uses it, but no other project in this repository uses it (read: `ReaLTaiizor_CR(net481)`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such. — src/ReaLTaiizor/Action/Metro/MetroTileActionList.cs:16
`ReaLTaiizor.Action.Metro.MetroTileActionList` (src/ReaLTaiizor/Action/Metro/MetroTileActionList.cs:16) is public, and the library's own code uses it, but no other project in this repository uses it (read: `ReaLTaiizor_CR(netcoreapp3.1-windows)`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such. — src/ReaLTaiizor/Action/Metro/MetroTileActionList.cs:16
`ReaLTaiizor.Action.Metro.MetroTileActionList` (src/ReaLTaiizor/Action/Metro/MetroTileActionList.cs:16) is public, and the library's own code uses it, but no other project in this repository uses it (read: `ReaLTaiizor_CR(net6.0-windows)`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such. — src/ReaLTaiizor/Action/Metro/MetroTileActionList.cs:16
What to do
Make `ReaLTaiizor.Action.Metro.MetroBadgeActionList` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Action.Metro.MetroBadgeActionList` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Action.Metro.MetroBadgeActionList` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Action.Metro.MetroBadgeActionList` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Action.Metro.MetroBadgeActionList` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Action.Metro.MetroBadgeActionList` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Action.Metro.MetroBadgeActionList` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Action.Metro.MetroBadgeActionList` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Action.Metro.MetroBadgeActionList` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Action.Metro.MetroButtonActionList` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Action.Metro.MetroButtonActionList` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Action.Metro.MetroButtonActionList` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Action.Metro.MetroButtonActionList` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Action.Metro.MetroButtonActionList` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Action.Metro.MetroButtonActionList` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Action.Metro.MetroButtonActionList` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Action.Metro.MetroButtonActionList` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Action.Metro.MetroButtonActionList` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Action.Metro.MetroDefaultButtonActionList` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Action.Metro.MetroDefaultButtonActionList` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Action.Metro.MetroDefaultButtonActionList` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Action.Metro.MetroDefaultButtonActionList` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Action.Metro.MetroDefaultButtonActionList` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Action.Metro.MetroDefaultButtonActionList` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Action.Metro.MetroDefaultButtonActionList` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Action.Metro.MetroDefaultButtonActionList` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Action.Metro.MetroDefaultButtonActionList` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Action.Metro.MetroEllipseActionList` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Action.Metro.MetroEllipseActionList` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Action.Metro.MetroEllipseActionList` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Action.Metro.MetroEllipseActionList` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Action.Metro.MetroEllipseActionList` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Action.Metro.MetroEllipseActionList` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Action.Metro.MetroEllipseActionList` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Action.Metro.MetroEllipseActionList` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Action.Metro.MetroEllipseActionList` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Action.Metro.MetroTileActionList` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Action.Metro.MetroTileActionList` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Action.Metro.MetroTileActionList` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Action.Metro.MetroTileActionList` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Action.Metro.MetroTileActionList` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Action.Metro.MetroTileActionList` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Action.Metro.MetroTileActionList` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Action.Metro.MetroTileActionList` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Action.Metro.MetroTileActionList` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Action.Metro.MetroTrackBarActionList` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Action.Metro.MetroTrackBarActionList` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Action.Metro.MetroTrackBarActionList` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Action.Metro.MetroTrackBarActionList` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Action.Metro.MetroTrackBarActionList` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Action.Metro.MetroTrackBarActionList` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Action.Metro.MetroTrackBarActionList` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Action.Metro.MetroTrackBarActionList` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Action.Metro.MetroTrackBarActionList` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Animate.Metro.IntAnimate` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Animate.Metro.IntAnimate` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Animate.Metro.IntAnimate` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Animate.Metro.IntAnimate` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Animate.Metro.IntAnimate` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Animate.Metro.IntAnimate` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Animate.Metro.IntAnimate` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Animate.Metro.IntAnimate` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Animate.Metro.IntAnimate` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Animate.Metro.Interpolation` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Animate.Metro.Interpolation` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Animate.Metro.Interpolation` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Animate.Metro.Interpolation` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Animate.Metro.Interpolation` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Animate.Metro.Interpolation` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Animate.Metro.Interpolation` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Animate.Metro.Interpolation` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Animate.Metro.Interpolation` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Animate.Metro.PointFAnimate` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Animate.Metro.PointFAnimate` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Animate.Metro.PointFAnimate` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Animate.Metro.PointFAnimate` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Animate.Metro.PointFAnimate` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Animate.Metro.PointFAnimate` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Animate.Metro.PointFAnimate` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Animate.Metro.PointFAnimate` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Animate.Metro.PointFAnimate` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Animate.Poison.MoveAnimation` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Animate.Poison.MoveAnimation` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Animate.Poison.MoveAnimation` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Animate.Poison.MoveAnimation` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Animate.Poison.MoveAnimation` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Animate.Poison.MoveAnimation` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Animate.Poison.MoveAnimation` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Animate.Poison.MoveAnimation` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Animate.Poison.MoveAnimation` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Child.Material.MaterialBaseTextBoxContextMenuStrip` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Child.Material.MaterialBaseTextBoxContextMenuStrip` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Child.Material.MaterialBaseTextBoxContextMenuStrip` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Child.Material.MaterialBaseTextBoxContextMenuStrip` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Child.Material.MaterialBaseTextBoxContextMenuStrip` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Child.Material.MaterialBaseTextBoxContextMenuStrip` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Child.Material.MaterialBaseTextBoxContextMenuStrip` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Child.Material.MaterialBaseTextBoxContextMenuStrip` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Child.Material.MaterialBaseTextBoxContextMenuStrip` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Child.Material.MaterialDrawerForm` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Child.Material.MaterialDrawerForm` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Child.Material.MaterialDrawerForm` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Child.Material.MaterialDrawerForm` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Child.Material.MaterialDrawerForm` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Child.Material.MaterialDrawerForm` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Child.Material.MaterialDrawerForm` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Child.Material.MaterialDrawerForm` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Child.Material.MaterialDrawerForm` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Child.Material.MaterialItemCollection` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Child.Material.MaterialItemCollection` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Child.Material.MaterialItemCollection` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Child.Material.MaterialItemCollection` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Child.Material.MaterialItemCollection` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Child.Material.MaterialItemCollection` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Child.Material.MaterialItemCollection` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Child.Material.MaterialItemCollection` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Child.Material.MaterialItemCollection` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Child.Material.MaterialItemCollectionEditor` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Child.Material.MaterialItemCollectionEditor` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Child.Material.MaterialItemCollectionEditor` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Child.Material.MaterialItemCollectionEditor` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Child.Material.MaterialItemCollectionEditor` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Child.Material.MaterialItemCollectionEditor` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Child.Material.MaterialItemCollectionEditor` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Child.Material.MaterialItemCollectionEditor` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Child.Material.MaterialItemCollectionEditor` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Child.Metro.MetroTabPage` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Child.Metro.MetroTabPage` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Child.Metro.MetroTabPage` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Child.Metro.MetroTabPage` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Child.Metro.MetroTabPage` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Child.Metro.MetroTabPage` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Child.Metro.MetroTabPage` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Child.Metro.MetroTabPage` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Child.Metro.MetroTabPage` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Colors.HopeColors` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Colors.HopeColors` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Colors.HopeColors` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Colors.HopeColors` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Colors.HopeColors` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Colors.HopeColors` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Colors.HopeColors` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Colors.HopeColors` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Colors.HopeColors` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Colors.PoisonColors` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Colors.PoisonColors` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Colors.PoisonColors` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Colors.PoisonColors` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Colors.PoisonColors` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Colors.PoisonColors` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Colors.PoisonColors` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Colors.PoisonColors` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Colors.PoisonColors` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Colors.RoyalColors` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Colors.RoyalColors` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Colors.RoyalColors` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Colors.RoyalColors` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Colors.RoyalColors` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Colors.RoyalColors` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Colors.RoyalColors` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Colors.RoyalColors` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Colors.RoyalColors` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.MetroBadge` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.MetroBadge` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.MetroBadge` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.MetroBadge` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.MetroBadge` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.MetroBadge` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.MetroBadge` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.MetroBadge` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.MetroBadge` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.MetroButton` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.MetroButton` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.MetroButton` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.MetroButton` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.MetroButton` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.MetroButton` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.MetroButton` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.MetroButton` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.MetroButton` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.MetroDefaultButton` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.MetroDefaultButton` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.MetroDefaultButton` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.MetroDefaultButton` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.MetroDefaultButton` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.MetroDefaultButton` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.MetroDefaultButton` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.MetroDefaultButton` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.MetroDefaultButton` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.MetroCheckBox` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.MetroCheckBox` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.MetroCheckBox` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.MetroCheckBox` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.MetroCheckBox` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.MetroCheckBox` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.MetroCheckBox` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.MetroCheckBox` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.MetroCheckBox` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.MaterialDivider` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.MaterialDivider` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.MaterialDivider` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.MaterialDivider` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.MaterialDivider` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.MaterialDivider` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.MaterialDivider` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.MaterialDivider` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.MaterialDivider` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.MetroDivider` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.MetroDivider` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.MetroDivider` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.MetroDivider` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.MetroDivider` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.MetroDivider` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.MetroDivider` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.MetroDivider` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.MetroDivider` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.MaterialDrawer` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.MaterialDrawer` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.MaterialDrawer` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.MaterialDrawer` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.MaterialDrawer` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.MaterialDrawer` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.MaterialDrawer` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.MaterialDrawer` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.MaterialDrawer` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.MetroEllipse` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.MetroEllipse` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.MetroEllipse` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.MetroEllipse` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.MetroEllipse` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.MetroEllipse` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.MetroEllipse` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.MetroEllipse` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.MetroEllipse` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.ParrotObjectEllipse` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.ParrotObjectEllipse` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.ParrotObjectEllipse` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.ParrotObjectEllipse` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.ParrotObjectEllipse` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.ParrotObjectEllipse` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.ParrotObjectEllipse` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.ParrotObjectEllipse` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.ParrotObjectEllipse` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.ParrotFormHandle` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.ParrotFormHandle` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.ParrotFormHandle` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.ParrotFormHandle` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.ParrotFormHandle` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.ParrotFormHandle` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.ParrotFormHandle` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.ParrotFormHandle` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.ParrotFormHandle` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.CrownLabel` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.CrownLabel` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.CrownLabel` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.CrownLabel` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.CrownLabel` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.CrownLabel` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.CrownLabel` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.CrownLabel` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.CrownLabel` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.MaterialLabel` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.MaterialLabel` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.MaterialLabel` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.MaterialLabel` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.MaterialLabel` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.MaterialLabel` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.MaterialLabel` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.MaterialLabel` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.MaterialLabel` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.MetroLabel` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.MetroLabel` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.MetroLabel` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.MetroLabel` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.MetroLabel` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.MetroLabel` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.MetroLabel` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.MetroLabel` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.MetroLabel` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.PoisonLabel` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.PoisonLabel` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.PoisonLabel` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.PoisonLabel` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.PoisonLabel` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.PoisonLabel` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.PoisonLabel` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.PoisonLabel` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.PoisonLabel` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.MetroLinkLabel` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.MetroLinkLabel` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.MetroLinkLabel` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.MetroLinkLabel` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.MetroLinkLabel` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.MetroLinkLabel` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.MetroLinkLabel` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.MetroLinkLabel` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.MetroLinkLabel` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.PoisonLinkLabel` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.PoisonLinkLabel` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.PoisonLinkLabel` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.PoisonLinkLabel` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.PoisonLinkLabel` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.PoisonLinkLabel` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.PoisonLinkLabel` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.PoisonLinkLabel` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.PoisonLinkLabel` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.MetroListBox` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.MetroListBox` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.MetroListBox` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.MetroListBox` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.MetroListBox` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.MetroListBox` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.MetroListBox` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.MetroListBox` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.MetroListBox` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.CrownMessageBox` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.CrownMessageBox` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.CrownMessageBox` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.CrownMessageBox` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.CrownMessageBox` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.CrownMessageBox` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.CrownMessageBox` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.CrownMessageBox` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.CrownMessageBox` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.MetroNumeric` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.MetroNumeric` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.MetroNumeric` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.MetroNumeric` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.MetroNumeric` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.MetroNumeric` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.MetroNumeric` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.MetroNumeric` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.MetroNumeric` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.Panel` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.Panel` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.Panel` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.Panel` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.Panel` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.Panel` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.Panel` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.Panel` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.Panel` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.PoisonPanel` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.PoisonPanel` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.PoisonPanel` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.PoisonPanel` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.PoisonPanel` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.PoisonPanel` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.PoisonPanel` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.PoisonPanel` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.PoisonPanel` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.MetroProgressBar` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.MetroProgressBar` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.MetroProgressBar` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.MetroProgressBar` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.MetroProgressBar` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.MetroProgressBar` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.MetroProgressBar` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.MetroProgressBar` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.MetroProgressBar` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.PoisonProgressSpinner` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.PoisonProgressSpinner` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.PoisonProgressSpinner` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.PoisonProgressSpinner` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.PoisonProgressSpinner` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.PoisonProgressSpinner` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.PoisonProgressSpinner` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.PoisonProgressSpinner` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.PoisonProgressSpinner` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.MetroRadioButton` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.MetroRadioButton` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.MetroRadioButton` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.MetroRadioButton` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.MetroRadioButton` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.MetroRadioButton` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.MetroRadioButton` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.MetroRadioButton` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.MetroRadioButton` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.RadioButton` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.RadioButton` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.RadioButton` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.RadioButton` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.RadioButton` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.RadioButton` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.RadioButton` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.RadioButton` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.RadioButton` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.MetroRichTextBox` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.MetroRichTextBox` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.MetroRichTextBox` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.MetroRichTextBox` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.MetroRichTextBox` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.MetroRichTextBox` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.MetroRichTextBox` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.MetroRichTextBox` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.MetroRichTextBox` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.MaterialScrollBar` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.MaterialScrollBar` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.MaterialScrollBar` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.MaterialScrollBar` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.MaterialScrollBar` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.MaterialScrollBar` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.MaterialScrollBar` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.MaterialScrollBar` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.MaterialScrollBar` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.MetroScrollBar` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.MetroScrollBar` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.MetroScrollBar` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.MetroScrollBar` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.MetroScrollBar` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.MetroScrollBar` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.MetroScrollBar` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.MetroScrollBar` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.MetroScrollBar` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.ParrotSleeper` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.ParrotSleeper` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.ParrotSleeper` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.ParrotSleeper` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.ParrotSleeper` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.ParrotSleeper` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.ParrotSleeper` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.ParrotSleeper` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.ParrotSleeper` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.CrownContextMenuStrip` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.CrownContextMenuStrip` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.CrownContextMenuStrip` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.CrownContextMenuStrip` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.CrownContextMenuStrip` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.CrownContextMenuStrip` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.CrownContextMenuStrip` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.CrownContextMenuStrip` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.CrownContextMenuStrip` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.MaterialToolStripMenuItem` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.MaterialToolStripMenuItem` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.MaterialToolStripMenuItem` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.MaterialToolStripMenuItem` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.MaterialToolStripMenuItem` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.MaterialToolStripMenuItem` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.MaterialToolStripMenuItem` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.MaterialToolStripMenuItem` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.MaterialToolStripMenuItem` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.MetroContextMenuStrip` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.MetroContextMenuStrip` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.MetroContextMenuStrip` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.MetroContextMenuStrip` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.MetroContextMenuStrip` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.MetroContextMenuStrip` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.MetroContextMenuStrip` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.MetroContextMenuStrip` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.MetroContextMenuStrip` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.PoisonContextMenuStrip` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.PoisonContextMenuStrip` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.PoisonContextMenuStrip` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.PoisonContextMenuStrip` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.PoisonContextMenuStrip` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.PoisonContextMenuStrip` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.PoisonContextMenuStrip` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.PoisonContextMenuStrip` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.PoisonContextMenuStrip` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.MetroSwitch` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.MetroSwitch` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.MetroSwitch` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.MetroSwitch` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.MetroSwitch` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.MetroSwitch` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.MetroSwitch` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.MetroSwitch` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.MetroSwitch` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.MetroTabControl` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.MetroTabControl` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.MetroTabControl` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.MetroTabControl` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.MetroTabControl` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.MetroTabControl` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.MetroTabControl` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.MetroTabControl` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.MetroTabControl` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.MaterialTextBoxContextMenuStrip` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.MaterialTextBoxContextMenuStrip` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.MaterialTextBoxContextMenuStrip` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.MaterialTextBoxContextMenuStrip` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.MaterialTextBoxContextMenuStrip` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.MaterialTextBoxContextMenuStrip` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.MaterialTextBoxContextMenuStrip` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.MaterialTextBoxContextMenuStrip` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.MaterialTextBoxContextMenuStrip` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.MetroTextBox` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.MetroTextBox` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.MetroTextBox` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.MetroTextBox` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.MetroTextBox` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.MetroTextBox` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.MetroTextBox` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.MetroTextBox` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.MetroTextBox` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.PoisonTextBox` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.PoisonTextBox` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.PoisonTextBox` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.PoisonTextBox` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.PoisonTextBox` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.PoisonTextBox` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.PoisonTextBox` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.PoisonTextBox` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.PoisonTextBox` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.MaterialMultiLineTextBoxEdit` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.MaterialMultiLineTextBoxEdit` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.MaterialMultiLineTextBoxEdit` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.MaterialMultiLineTextBoxEdit` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.MaterialMultiLineTextBoxEdit` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.MaterialMultiLineTextBoxEdit` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.MaterialMultiLineTextBoxEdit` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.MaterialMultiLineTextBoxEdit` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.MaterialMultiLineTextBoxEdit` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.MetroTile` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.MetroTile` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.MetroTile` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.MetroTile` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.MetroTile` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.MetroTile` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.MetroTile` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.MetroTile` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.MetroTile` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.PoisonTile` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.PoisonTile` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.PoisonTile` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.PoisonTile` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.PoisonTile` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.PoisonTile` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.PoisonTile` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.PoisonTile` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.PoisonTile` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.MetroToolTip` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.MetroToolTip` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.MetroToolTip` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.MetroToolTip` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.MetroToolTip` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.MetroToolTip` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.MetroToolTip` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.MetroToolTip` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.MetroToolTip` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.MetroTrackBar` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.MetroTrackBar` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.MetroTrackBar` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.MetroTrackBar` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.MetroTrackBar` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.MetroTrackBar` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.MetroTrackBar` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.MetroTrackBar` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Controls.MetroTrackBar` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Design.Metro.MetroStyleManagerDesigner` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Design.Metro.MetroStyleManagerDesigner` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Design.Metro.MetroStyleManagerDesigner` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Design.Metro.MetroStyleManagerDesigner` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Design.Metro.MetroStyleManagerDesigner` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Design.Metro.MetroStyleManagerDesigner` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Design.Metro.MetroStyleManagerDesigner` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Design.Metro.MetroStyleManagerDesigner` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Design.Metro.MetroStyleManagerDesigner` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Design.Metro.MetroTabControlDesigner` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Design.Metro.MetroTabControlDesigner` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Design.Parrot.ParrotFormDesigner` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Design.Parrot.ParrotFormDesigner` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Design.Parrot.ParrotFormDesigner` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Design.Parrot.ParrotFormDesigner` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Design.Parrot.ParrotFormDesigner` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Design.Parrot.ParrotFormDesigner` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Design.Parrot.ParrotFormDesigner` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Design.Parrot.ParrotFormDesigner` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Design.Parrot.ParrotFormDesigner` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Drawing.Poison.PoisonPaint` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Drawing.Poison.PoisonPaint` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Drawing.Poison.PoisonPaint` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Drawing.Poison.PoisonPaint` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Drawing.Poison.PoisonPaint` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Drawing.Poison.PoisonPaint` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Drawing.Poison.PoisonPaint` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Drawing.Poison.PoisonPaint` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Drawing.Poison.PoisonPaint` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Extension.Metro.MetroFonts` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Extension.Metro.MetroFonts` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Extension.Metro.MetroFonts` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Extension.Metro.MetroFonts` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Extension.Metro.MetroFonts` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Extension.Metro.MetroFonts` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Extension.Metro.MetroFonts` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Extension.Metro.MetroFonts` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Extension.Metro.MetroFonts` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Extension.Poison.PoisonBrushes` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Extension.Poison.PoisonBrushes` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Extension.Poison.PoisonBrushes` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Extension.Poison.PoisonBrushes` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Extension.Poison.PoisonBrushes` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Extension.Poison.PoisonBrushes` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Extension.Poison.PoisonBrushes` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Extension.Poison.PoisonBrushes` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Extension.Poison.PoisonBrushes` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Extension.Poison.PoisonFonts` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Extension.Poison.PoisonFonts` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Extension.Poison.PoisonFonts` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Extension.Poison.PoisonFonts` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Extension.Poison.PoisonFonts` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Extension.Poison.PoisonFonts` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Extension.Poison.PoisonFonts` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Extension.Poison.PoisonFonts` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Extension.Poison.PoisonFonts` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Extension.Poison.PoisonPens` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Extension.Poison.PoisonPens` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Extension.Poison.PoisonPens` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Extension.Poison.PoisonPens` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Extension.Poison.PoisonPens` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Extension.Poison.PoisonPens` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Extension.Poison.PoisonPens` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Extension.Poison.PoisonPens` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Extension.Poison.PoisonPens` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Forms.MaterialFlexibleForm` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Forms.MaterialFlexibleForm` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Forms.MaterialFlexibleForm` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Forms.MaterialFlexibleForm` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Forms.MaterialFlexibleForm` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Forms.MaterialFlexibleForm` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Forms.MaterialFlexibleForm` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Forms.MaterialFlexibleForm` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Forms.MaterialFlexibleForm` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Helper.CrownHelper` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Helper.CrownHelper` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Helper.CrownHelper` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Helper.CrownHelper` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Helper.CrownHelper` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Helper.CrownHelper` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Helper.CrownHelper` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Helper.CrownHelper` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Helper.CrownHelper` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Helper.PoisonDataGridHelper` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Helper.PoisonDataGridHelper` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Helper.PoisonDataGridHelper` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Helper.PoisonDataGridHelper` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Helper.PoisonDataGridHelper` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Helper.PoisonDataGridHelper` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Helper.PoisonDataGridHelper` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Helper.PoisonDataGridHelper` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Helper.PoisonDataGridHelper` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.RoundRectangle` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.MSColorTable` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.DefaultCColorTable` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.RectDrawing` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.RoundRectangle` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.MSColorTable` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.DefaultCColorTable` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.RectDrawing` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.RoundRectangle` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.MSColorTable` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.DefaultCColorTable` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.RectDrawing` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.RoundRectangle` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.MSColorTable` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.DefaultCColorTable` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.RectDrawing` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.RoundRectangle` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.MSColorTable` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.DefaultCColorTable` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.RectDrawing` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.RoundRectangle` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.MSColorTable` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.DefaultCColorTable` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.RectDrawing` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.RoundRectangle` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.MSColorTable` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.DefaultCColorTable` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.RectDrawing` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.RoundRectangle` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.MSColorTable` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.DefaultCColorTable` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.RectDrawing` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.RoundRectangle` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.MSColorTable` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.DefaultCColorTable` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.RectDrawing` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Util.ThemeShareAir` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Util.ThemeShareAir` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Util.ThemeShareAir` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Util.ThemeShareAir` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Util.ThemeShareAir` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Util.ThemeShareAir` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Util.ThemeShareAir` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Util.ThemeShareAir` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Util.ThemeShareAir` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Util.AloneLibrary` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Util.AloneLibrary` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Util.AloneLibrary` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Util.AloneLibrary` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Util.AloneLibrary` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Util.AloneLibrary` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Util.AloneLibrary` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Util.AloneLibrary` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Util.AloneLibrary` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Util.CyberLibrary` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Util.CyberLibrary` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Util.CyberLibrary` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Util.CyberLibrary` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Util.CyberLibrary` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Util.CyberLibrary` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Util.CyberLibrary` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Util.CyberLibrary` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Util.CyberLibrary` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Util.ForeverLibrary` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Util.ForeverLibrary` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Util.ForeverLibrary` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Util.ForeverLibrary` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Util.ForeverLibrary` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Util.ForeverLibrary` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Util.ForeverLibrary` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Util.ForeverLibrary` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Util.ForeverLibrary` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Util.FoxLibrary` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Util.FoxLibrary` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Util.FoxLibrary` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Util.FoxLibrary` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Util.FoxLibrary` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Util.FoxLibrary` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Util.FoxLibrary` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Util.FoxLibrary` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Util.FoxLibrary` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Util.HopeStringAlign` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Util.HopeBase.ToolStripRender` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Util.HopeBase.DateRectHopeBase` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Util.HopeStringAlign` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Util.HopeBase.ToolStripRender` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Util.HopeBase.DateRectHopeBase` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Util.HopeStringAlign` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Util.HopeBase.ToolStripRender` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Util.HopeBase.DateRectHopeBase` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Util.HopeStringAlign` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Util.HopeBase.ToolStripRender` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Util.HopeBase.DateRectHopeBase` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Util.HopeStringAlign` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Util.HopeBase.ToolStripRender` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Util.HopeBase.DateRectHopeBase` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Util.HopeStringAlign` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Util.HopeBase.ToolStripRender` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Util.HopeBase.DateRectHopeBase` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Util.HopeStringAlign` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Util.HopeBase.ToolStripRender` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Util.HopeBase.DateRectHopeBase` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Util.HopeStringAlign` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Util.HopeBase.ToolStripRender` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Util.HopeBase.DateRectHopeBase` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Util.HopeStringAlign` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Util.HopeBase.ToolStripRender` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Util.HopeBase.DateRectHopeBase` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Util.ThemeLost` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Util.ThemeLost` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Util.ThemeLost` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Util.ThemeLost` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Util.ThemeLost` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Util.ThemeLost` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Util.ThemeLost` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Util.ThemeLost` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Util.ThemeLost` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Util.MaterialNativeTextRenderer` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Util.MaterialNativeTextRenderer` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Util.MaterialNativeTextRenderer` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Util.MaterialNativeTextRenderer` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Util.MaterialNativeTextRenderer` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Util.MaterialNativeTextRenderer` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Util.MaterialNativeTextRenderer` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Util.MaterialNativeTextRenderer` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Util.MaterialNativeTextRenderer` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Util.ThemeShareMoon` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Util.ThemeShareMoon` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Util.ThemeShareMoon` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Util.ThemeShareMoon` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Util.ThemeShareMoon` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Util.ThemeShareMoon` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Util.ThemeShareMoon` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Util.ThemeShareMoon` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Util.ThemeShareMoon` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Util.Percentage` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Util.StripeRemoval` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Util.KitMenuStripRenderer` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Util.Percentage` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Util.StripeRemoval` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Util.KitMenuStripRenderer` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Util.Percentage` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Util.StripeRemoval` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Util.KitMenuStripRenderer` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Util.Percentage` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Util.StripeRemoval` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Util.KitMenuStripRenderer` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Util.Percentage` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Util.StripeRemoval` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Util.KitMenuStripRenderer` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Util.Percentage` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Util.StripeRemoval` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Util.KitMenuStripRenderer` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Util.Percentage` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Util.StripeRemoval` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Util.KitMenuStripRenderer` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Util.Percentage` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Util.StripeRemoval` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Util.KitMenuStripRenderer` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Util.Percentage` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Util.StripeRemoval` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Util.KitMenuStripRenderer` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Util.HiddenTabs` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Util.ListViewColumnSorter` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Util.HiddenTabs` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Util.ListViewColumnSorter` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Util.HiddenTabs` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Util.ListViewColumnSorter` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Util.HiddenTabs` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Util.ListViewColumnSorter` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Util.HiddenTabs` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Util.ListViewColumnSorter` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Util.HiddenTabs` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Util.ListViewColumnSorter` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Util.HiddenTabs` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Util.ListViewColumnSorter` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Util.HiddenTabs` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Util.ListViewColumnSorter` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Util.HiddenTabs` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Util.ListViewColumnSorter` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Util.DrawRibbon` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Util.ImageToCodeClassRibbon` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Util.DrawRibbon` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Util.ImageToCodeClassRibbon` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Util.DrawRibbon` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Util.ImageToCodeClassRibbon` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Util.DrawRibbon` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Util.ImageToCodeClassRibbon` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Util.DrawRibbon` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Util.ImageToCodeClassRibbon` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Util.DrawRibbon` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Util.ImageToCodeClassRibbon` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Util.DrawRibbon` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Util.ImageToCodeClassRibbon` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Util.DrawRibbon` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Util.ImageToCodeClassRibbon` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Util.DrawRibbon` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Util.ImageToCodeClassRibbon` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Util.RoyalToolStripRenderer` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Util.RoyalToolStripRenderer` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Util.RoyalToolStripRenderer` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Util.RoyalToolStripRenderer` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Util.RoyalToolStripRenderer` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Util.RoyalToolStripRenderer` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Util.RoyalToolStripRenderer` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Util.RoyalToolStripRenderer` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Util.RoyalToolStripRenderer` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Util.ThemeShareSpace` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Util.ThemeShareSpace` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Util.ThemeShareSpace` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Util.ThemeShareSpace` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Util.ThemeShareSpace` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Util.ThemeShareSpace` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Util.ThemeShareSpace` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Util.ThemeShareSpace` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Util.ThemeShareSpace` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Util.DrawThunder` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Util.DrawThunder` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Util.DrawThunder` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Util.DrawThunder` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Util.DrawThunder` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Util.DrawThunder` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Util.DrawThunder` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Util.DrawThunder` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ReaLTaiizor.Util.DrawThunder` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Readiness · Readiness — Whether SAST, secret/dependency scanning and performance benchmarking are wired in (presence, not runtime).
Method: Filesystem scan: SAST configuration, dependency-update automation, secret scanning, and a benchmark harness or benchmark step — in this repository's own ecosystem. Exhaustive, deterministic.
`REDACTED` schedules updates, but no `package-ecosystem` entry covers `github-actions`, which this tree depends on — so those dependencies get no update pull requests and no advisory pressure, however complete the dep-scan credit looks. Add the missing entry to the `updates:` list. — REDACTED:2
What to do
Dependabot is configured but does not watch `github-actions` — add that `package-ecosystem` entry to REDACTED so those dependencies get the same automatic update and advisory pressure as the ones it already covers.
Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
Readiness · Readiness — Whether releases are traceable — a maintained changelog and explicit version stamping.
Method: Filesystem scan: changelog file presence and version tags in csproj or git tags. Exhaustive, deterministic.
No CHANGELOG/HISTORY/RELEASES file — what shipped when isn't easy to reconstruct for support or audit. (Versioning/tagging makes releases traceable, but a changelog records the what.)
What to do
Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release.
Readiness · Performance — Whether asynchronous code stays responsive — it avoids sync-over-async blocking (a .NET .Wait()/.GetAwaiter().GetResult(), a time.sleep or blocking HTTP call inside a Python coroutine, a *Sync call inside an async JavaScript function, block_on inside a Rust async fn, runBlocking inside a Kotlin suspend function, block() inside a Reactor publisher) that stalls a thread or event loop and risks deadlock, and, where the code is a reusable library on .NET, awaits with ConfigureAwait(false) so it never captures and stalls its caller's context.
Method: Production-source scan: sync-over-async blocking counted everywhere — .Wait()/.GetAwaiter().GetResult() in .NET; off .NET, read from each language's code model, a blocking call inside an async function (Python, TS/JS, Rust, Kotlin, Swift, Dart) or inside a Java method returning a Reactor Mono/Flux or a Scala method returning a Future or effect — and, for a .NET library with ≥5 awaits, the share of awaits using ConfigureAwait(false). Deterministic, syntax/text detection.
Other · Code Health — Whether the code avoids sync-over-async (deadlock-prone blocking on tasks) and async void.
Method: Roslyn syntax scan: async methods scanned for .Wait()/.GetAwaiter().GetResult() and async-void outside event handlers. Deterministic, hard fact per invocation.
`async void` can't be awaited and its exceptions crash the process instead of propagating. Return `Task` — or, where the delegate contract requires void (timer/event/callback registrations), make this a thin void shim that awaits a Task-returning inner method inside try/catch so exceptions are contained. (×5) — ready/ReaLTaiizor.Translate/ReaLTaiizor.Translate/Translate.cs:23, ready/ReaLTaiizor.Translate/ReaLTaiizor.Translate/Translate.cs:33, ready/ReaLTaiizor.Translate/ReaLTaiizor.Translate/Translate.cs:42, …
`Task.WaitAll` blocks this thread until the tasks complete — sync-over-async: it can deadlock under a synchronization context and it parks a thread for as long as the work runs. `await Task.WhenAll(…)` instead. — ready/ReaLTaiizor.Portscan/ReaLTaiizor.Portscan/Portscan.cs:391
Other · Code Health — Whether any branch is dead by construction — a switch arm whose label can never equal a case-normalised subject, or an `else if` whose predicate the arm above has already swallowed.
Method: Roslyn syntax + semantics: switch labels compared against the subject's own case normaliser, and if/else-if chains checked for a literal an earlier arm's containment test already swallows. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X13 · Undrained process stream10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a child process that has BOTH standard streams redirected drains both — reading one to the end while the other is never read deadlocks once the child fills the unread pipe.
Method: Roslyn syntax + semantics: ProcessStartInfo launches with both streams redirected, checked for a drain of each stream across the enclosing type. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same rule: a `spawn` imported from `child_process` whose stdout and stderr are both pipes (no options, no `stdio`, or `stdio` of `'pipe'`), bound to a local that never leaves its scope, where exactly one of the two streams is read, the other never, and the child’s `close`/`exit` (or the read stream’s end) is awaited; a shell redirect in the call’s arguments or a `kill` of the child suppresses it. The same rule reads Python’s `subprocess.Popen`, Dart’s `Process.start`, Ruby’s `Open3.popen3`, and Scala’s JDK process starts (`new ProcessBuilder(…).start()` with no `redirectErrorStream`/`redirectError`/`redirectOutput`/`inheritIO`, `Runtime.getRuntime.exec`) where one of `getInputStream`/`getErrorStream` is read and the other never while `waitFor()` is called or the read stream is read to its end. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether a loop that shortens a string until it fits a length budget has a floor — one with none grinds the value down to the empty string, or past it into a negative-length `Substring`.
Method: Roslyn syntax + semantics: while/do loops whose body's only effect on a string is to drop its last character, checked for whether anything — a direct comparison on the length, a body guard, a break — bounds that length below. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same rule: a `while`/`do` loop whose body’s one assignment to a value is `x = x.slice(0, -1)` or `x = x.slice|substring|substr(0, x.length - 1)`, driven by a condition that reads `x.length` only as a term of a larger expression — never compared directly, never tested for truthiness, and with no other read of `x` — and whose body has no `break`, `return`, `throw` or `if` naming `x`. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether a type's disposal matches what it OWNS — releasing what it created, leaving alone what it was handed, and not declaring a finalizer for state that has nothing unmanaged to finalize.
Method: Roslyn syntax + semantics: every assignment to a disposable field is read to decide whether the type CREATED the value or was handed it, and the type's disposal is checked against that answer — an injected interface it disposes, a value it constructed and never releases, a finalizer on a type holding nothing unmanaged, and a disposable local whose every reference is a plain member read. A value handed to a container that disposes its contents (a parent control's `Controls` collection, a component `IContainer`) is released by that container and is not reported; generated code is out of population. On a repository with no .NET source the same ownership questions are read in JavaScript/TypeScript off the engine’s own token stream (test, vendored, generated and minified paths not): a class declaring `dispose()`, `[Symbol.dispose]()` or `[Symbol.asyncDispose]()` that disposes a field it was handed through a constructor parameter typed as a repository interface or resolved by a dependency-injection container; that assigns a field only ever from `new X(…)` of a disposable class and neither releases it anywhere in the class nor names it in its disposal member or a method that member calls, nor hands it to anything else; and a `const`/`let` local built from literals only whose every reference opens a statement operating on a non-release member of it. A class is disposable when every repository declaration of its name declares or inherits a disposal member, or when it is a documented library disposable (`vscode` EventEmitter, CancellationTokenSource and Disposable; three.js geometries, materials, textures, render targets, renderers, controls and composers). The finalizer arm has no JavaScript counterpart: a class cannot declare one. Dart is read for the owned-and-never-released arm: a Flutter `State` (or a class declaring `dispose()`/`close()`) whose library-private field is written only with direct creations of a framework controller, `FocusNode`, `StreamController` or periodic `Timer` (or a `.listen(…)` into a field declared `StreamSubscription`), which nothing in the class or its library releases (`dispose`/`close`/`cancel`) and which is never handed on except as a named argument. Ruby is read for the owned-and-never-released arm and the abandoned-local arm: a class declaring an instance `close`, `dispose`, `shutdown`, `stop`, `disconnect` or `terminate` whose instance variable is written only with a blockless core descriptor creation (`File.open`/`new`, `Tempfile`, `Dir.open`, `IO.popen`, the `socket` and `openssl` socket classes) that no method of the class closes and that is never handed on (passed, returned, stored, exposed by `attr_reader`, delegated) — a class whose superclass or mixin lies outside the repository is not judged — and a blockless creation read through and dropped (`File.open(path).read`) or held in a local that is never closed, returned, passed or stored (a `&:read` block-pass, an `autoclose: false` borrow and a `fileno` hand-over are not abandonment). PHP is read for the same two arms: a class (not a trait, and not one using a trait) declaring an instance `close`, `dispose`, `shutdown`, `stop`, `disconnect` or `terminate` whose `private` property (or a `final` class's `protected` one) is written only with a direct core `fopen`, `tmpfile`, `popen`, `proc_open`, `fsockopen`, `stream_socket_client`/`server` or `opendir` that nothing in the class closes (`fclose`, `pclose`, `closedir`, `unset`, a reset to `null`) and that is never handed on, and a handle held in a function's local, or read through as the argument of a reader, that is never closed, returned, passed, captured or stored; a `php://` stream, `curl_init`, `SplFileObject`, `PDO` and a function the repository declares under the core name are not read. Deterministic, provable per finding. Advisory.
`hopeContextMenuStrip1` (line 609) is a component the designer creates for `Form14` with no container: it is not built with `new T(components)`, not added to `components`, and not added to a parent control's `Controls` or to a component's own child collection — the only routes by which the framework would release it for you. And the type's disposal never names it: searched `Dispose` (Form14.designer.cs line 14), plus every method those call by name. So `Form14` owns it and never releases it; whatever it holds (a dialog's window handle, a file-system watch, a process handle) stays until finalization, once per instance. Release it in `Dispose(bool)` (`hopeContextMenuStrip1?.Dispose();` under `disposing`) — that method may be edited, or moved to the hand-written partial; only `InitializeComponent` belongs to the designer — or register it with the container so `components.Dispose()` releases it. — demo/ReaLTaiizor.UI/ReaLTaiizor.UI/Form14.designer.cs:609
`FL` is a `FrameLost`, which implements `IDisposable`, and it is created here (line 17). Every use of it in `LostAcceptButton1_Click` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var FL = …;`), which releases it at the end of the scope on every path including a throw. — demo/ReaLTaiizor.UI/ReaLTaiizor.UI/Form15.cs:17
`TFL` is a `ToolFrameLost`, which implements `IDisposable`, and it is created here (line 26). Every use of it in `LostCancelButton1_Click` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var TFL = …;`), which releases it at the end of the scope on every path including a throw. — demo/ReaLTaiizor.UI/ReaLTaiizor.UI/Form15.cs:26
`SnackBarMessage` is a `MaterialSnackBar`, which implements `IDisposable`, and it is created here (line 245). Every use of it in `MaterialTextBox2_LeadingIconClick` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var SnackBarMessage = …;`), which releases it at the end of the scope on every path including a throw. — demo/ReaLTaiizor.UI/ReaLTaiizor.UI/Form17.cs:245
`SnackBarMessage` is a `MaterialSnackBar`, which implements `IDisposable`, and it is created here (line 252). Every use of it in `MaterialButton6_Click` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var SnackBarMessage = …;`), which releases it at the end of the scope on every path including a throw. — demo/ReaLTaiizor.UI/ReaLTaiizor.UI/Form17.cs:252
`SnackBarMessage` is a `MaterialSnackBar`, which implements `IDisposable`, and it is created here (line 326). Every use of it in `MaterialTextBox21_LeadingIconClick` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var SnackBarMessage = …;`), which releases it at the end of the scope on every path including a throw. — demo/ReaLTaiizor.UI/ReaLTaiizor.UI/Form17.cs:326
`SnackBarMessage` is a `MaterialSnackBar`, which implements `IDisposable`, and it is created here (line 332). Every use of it in `MaterialTextBox21_TrailingIconClick` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var SnackBarMessage = …;`), which releases it at the end of the scope on every path including a throw. — demo/ReaLTaiizor.UI/ReaLTaiizor.UI/Form17.cs:332
`materialDialog` is a `MaterialDialog`, which implements `IDisposable`, and it is created here (line 343). Every use of it in `MaterialButton25_Click` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var materialDialog = …;`), which releases it at the end of the scope on every path including a throw. — demo/ReaLTaiizor.UI/ReaLTaiizor.UI/Form17.cs:343
`SnackBarMessage` is a `MaterialSnackBar`, which implements `IDisposable`, and it is created here (line 346). Every use of it in `MaterialButton25_Click` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var SnackBarMessage = …;`), which releases it at the end of the scope on every path including a throw. — demo/ReaLTaiizor.UI/ReaLTaiizor.UI/Form17.cs:346
`materialContextMenuStrip1` (line 3480) is a component the designer creates for `Form17` with no container: it is not built with `new T(components)`, not added to `components`, and not added to a parent control's `Controls` or to a component's own child collection — the only routes by which the framework would release it for you. And the type's disposal never names it: searched `Dispose` (Form17.Designer.cs line 17), plus every method those call by name. So `Form17` owns it and never releases it; whatever it holds (a dialog's window handle, a file-system watch, a process handle) stays until finalization, once per instance. Release it in `Dispose(bool)` (`materialContextMenuStrip1?.Dispose();` under `disposing`) — that method may be edited, or moved to the hand-written partial; only `InitializeComponent` belongs to the designer — or register it with the container so `components.Dispose()` releases it. — demo/ReaLTaiizor.UI/ReaLTaiizor.UI/Form17.Designer.cs:3480
`MetroToolTip1` (line 2433) is a component the designer creates for `Form19` with no container: it is not built with `new T(components)`, not added to `components`, and not added to a parent control's `Controls` or to a component's own child collection — the only routes by which the framework would release it for you. And the type's disposal never names it: searched `Dispose` (Form19.Designer.cs line 14), plus every method those call by name. So `Form19` owns it and never releases it; whatever it holds (a dialog's window handle, a file-system watch, a process handle) stays until finalization, once per instance. Release it in `Dispose(bool)` (`MetroToolTip1?.Dispose();` under `disposing`) — that method may be edited, or moved to the hand-written partial; only `InitializeComponent` belongs to the designer — or register it with the container so `components.Dispose()` releases it. — demo/ReaLTaiizor.UI/ReaLTaiizor.UI/Form19.Designer.cs:2433
`MetroContextMenuStrip1` (line 2434) is a component the designer creates for `Form19` with no container: it is not built with `new T(components)`, not added to `components`, and not added to a parent control's `Controls` or to a component's own child collection — the only routes by which the framework would release it for you. And the type's disposal never names it: searched `Dispose` (Form19.Designer.cs line 14), plus every method those call by name. So `Form19` owns it and never releases it; whatever it holds (a dialog's window handle, a file-system watch, a process handle) stays until finalization, once per instance. Release it in `Dispose(bool)` (`MetroContextMenuStrip1?.Dispose();` under `disposing`) — that method may be edited, or moved to the hand-written partial; only `InitializeComponent` belongs to the designer — or register it with the container so `components.Dispose()` releases it. — demo/ReaLTaiizor.UI/ReaLTaiizor.UI/Form19.Designer.cs:2434
`metroStyleManager1` (line 2436) is a component the designer creates for `Form19` with no container: it is not built with `new T(components)`, not added to `components`, and not added to a parent control's `Controls` or to a component's own child collection — the only routes by which the framework would release it for you. And the type's disposal never names it: searched `Dispose` (Form19.Designer.cs line 14), plus every method those call by name. So `Form19` owns it and never releases it; whatever it holds (a dialog's window handle, a file-system watch, a process handle) stays until finalization, once per instance. Release it in `Dispose(bool)` (`metroStyleManager1?.Dispose();` under `disposing`) — that method may be edited, or moved to the hand-written partial; only `InitializeComponent` belongs to the designer — or register it with the container so `components.Dispose()` releases it. — demo/ReaLTaiizor.UI/ReaLTaiizor.UI/Form19.Designer.cs:2436
`poisonToolTip` (line 1449) is a component the designer creates for `Form20` with no container: it is not built with `new T(components)`, not added to `components`, and not added to a parent control's `Controls` or to a component's own child collection — the only routes by which the framework would release it for you. And the type's disposal never names it: searched `Dispose` (Form20.Designer.cs line 16), plus every method those call by name. So `Form20` owns it and never releases it; whatever it holds (a dialog's window handle, a file-system watch, a process handle) stays until finalization, once per instance. Release it in `Dispose(bool)` (`poisonToolTip?.Dispose();` under `disposing`) — that method may be edited, or moved to the hand-written partial; only `InitializeComponent` belongs to the designer — or register it with the container so `components.Dispose()` releases it. — demo/ReaLTaiizor.UI/ReaLTaiizor.UI/Form20.Designer.cs:1449
`test` is a `DialogControls`, which implements `IDisposable`, and it is created here (line 176). Every use of it in `Dialog_Click` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var test = …;`), which releases it at the end of the scope on every path including a throw. — demo/ReaLTaiizor.UI/ReaLTaiizor.UI/Form21.cs:176
`parrotObjectEllipse1` (line 1152) is a component the designer creates for `Form22` with no container: it is not built with `new T(components)`, not added to `components`, and not added to a parent control's `Controls` or to a component's own child collection — the only routes by which the framework would release it for you. And the type's disposal never names it: searched `Dispose` (Form22.designer.cs line 14), plus every method those call by name. So `Form22` owns it and never releases it; whatever it holds (a dialog's window handle, a file-system watch, a process handle) stays until finalization, once per instance. Release it in `Dispose(bool)` (`parrotObjectEllipse1?.Dispose();` under `disposing`) — that method may be edited, or moved to the hand-written partial; only `InitializeComponent` belongs to the designer — or register it with the container so `components.Dispose()` releases it. — demo/ReaLTaiizor.UI/ReaLTaiizor.UI/Form22.designer.cs:1152
`parrotSplashScreen1` (line 1153) is a component the designer creates for `Form22` with no container: it is not built with `new T(components)`, not added to `components`, and not added to a parent control's `Controls` or to a component's own child collection — the only routes by which the framework would release it for you. And the type's disposal never names it: searched `Dispose` (Form22.designer.cs line 14), plus every method those call by name. So `Form22` owns it and never releases it; whatever it holds (a dialog's window handle, a file-system watch, a process handle) stays until finalization, once per instance. Release it in `Dispose(bool)` (`parrotSplashScreen1?.Dispose();` under `disposing`) — that method may be edited, or moved to the hand-written partial; only `InitializeComponent` belongs to the designer — or register it with the container so `components.Dispose()` releases it. — demo/ReaLTaiizor.UI/ReaLTaiizor.UI/Form22.designer.cs:1153
`newForm` is a `Form`, which implements `IDisposable`, and it is created here (line 71). Every use of it in `Button_Click` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var newForm = …;`), which releases it at the end of the scope on every path including a throw. — demo/ReaLTaiizor.UI/ReaLTaiizor.UI/Forms/FormManager.cs:71
`AP` is a `AppPassword`, which implements `IDisposable`, and it is created here (line 40). Every use of it in `RAL_Tick` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var AP = …;`), which releases it at the end of the scope on every path including a throw. — ready/ReaLTaiizor.AppLocker/ReaLTaiizor.AppLocker/AppLocker.cs:40
`backgroundWorker1` (line 162) is a component the designer creates for `AppPassword` with no container: it is not built with `new T(components)`, not added to `components`, and not added to a parent control's `Controls` or to a component's own child collection — the only routes by which the framework would release it for you. And the type's disposal never names it: searched `Dispose` (AppPassword.Designer.cs line 15), plus every method those call by name. So `AppPassword` owns it and never releases it; whatever it holds (a dialog's window handle, a file-system watch, a process handle) stays until finalization, once per instance. Release it in `Dispose(bool)` (`backgroundWorker1?.Dispose();` under `disposing`) — that method may be edited, or moved to the hand-written partial; only `InitializeComponent` belongs to the designer — or register it with the container so `components.Dispose()` releases it. — ready/ReaLTaiizor.AppLocker/ReaLTaiizor.AppLocker/AppPassword.Designer.cs:162
`AP` is a `AppPassword`, which implements `IDisposable`, and it is created here (line 26). Every use of it in `LOCK_Click` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var AP = …;`), which releases it at the end of the scope on every path including a throw. — ready/ReaLTaiizor.AppLocker/ReaLTaiizor.AppLocker/RunApp.cs:26
`PTT` (line 136) is a component the designer creates for `RunApp` with no container: it is not built with `new T(components)`, not added to `components`, and not added to a parent control's `Controls` or to a component's own child collection — the only routes by which the framework would release it for you. And the type's disposal never names it: searched `Dispose` (RunApp.Designer.cs line 15), plus every method those call by name. So `RunApp` owns it and never releases it; whatever it holds (a dialog's window handle, a file-system watch, a process handle) stays until finalization, once per instance. Release it in `Dispose(bool)` (`PTT?.Dispose();` under `disposing`) — that method may be edited, or moved to the hand-written partial; only `InitializeComponent` belongs to the designer — or register it with the container so `components.Dispose()` releases it. — ready/ReaLTaiizor.AppLocker/ReaLTaiizor.AppLocker/RunApp.Designer.cs:136
`metroToolTip1` (line 312) is a component the designer creates for `Area` with no container: it is not built with `new T(components)`, not added to `components`, and not added to a parent control's `Controls` or to a component's own child collection — the only routes by which the framework would release it for you. And the type's disposal never names it: searched `Dispose` (Area.Designer.cs line 15), plus every method those call by name. So `Area` owns it and never releases it; whatever it holds (a dialog's window handle, a file-system watch, a process handle) stays until finalization, once per instance. Release it in `Dispose(bool)` (`metroToolTip1?.Dispose();` under `disposing`) — that method may be edited, or moved to the hand-written partial; only `InitializeComponent` belongs to the designer — or register it with the container so `components.Dispose()` releases it. — ready/ReaLTaiizor.Stopwatch/ReaLTaiizor.Stopwatch/Area.Designer.cs:312
`parrotObjectEllipse1` (line 182) is a component the designer creates for `Stopwatch` with no container: it is not built with `new T(components)`, not added to `components`, and not added to a parent control's `Controls` or to a component's own child collection — the only routes by which the framework would release it for you. And the type's disposal never names it: searched `Dispose` (Stopwatch.Designer.cs line 15), plus every method those call by name. So `Stopwatch` owns it and never releases it; whatever it holds (a dialog's window handle, a file-system watch, a process handle) stays until finalization, once per instance. Release it in `Dispose(bool)` (`parrotObjectEllipse1?.Dispose();` under `disposing`) — that method may be edited, or moved to the hand-written partial; only `InitializeComponent` belongs to the designer — or register it with the container so `components.Dispose()` releases it. — ready/ReaLTaiizor.Stopwatch/ReaLTaiizor.Stopwatch/Stopwatch.Designer.cs:182
`parrotSplashScreen1` (line 184) is a component the designer creates for `Stopwatch` with no container: it is not built with `new T(components)`, not added to `components`, and not added to a parent control's `Controls` or to a component's own child collection — the only routes by which the framework would release it for you. And the type's disposal never names it: searched `Dispose` (Stopwatch.Designer.cs line 15), plus every method those call by name. So `Stopwatch` owns it and never releases it; whatever it holds (a dialog's window handle, a file-system watch, a process handle) stays until finalization, once per instance. Release it in `Dispose(bool)` (`parrotSplashScreen1?.Dispose();` under `disposing`) — that method may be edited, or moved to the hand-written partial; only `InitializeComponent` belongs to the designer — or register it with the container so `components.Dispose()` releases it. — ready/ReaLTaiizor.Stopwatch/ReaLTaiizor.Stopwatch/Stopwatch.Designer.cs:184
`parrotFormEllipse1` (line 308) is a component the designer creates for `Login1` with no container: it is not built with `new T(components)`, not added to `components`, and not added to a parent control's `Controls` or to a component's own child collection — the only routes by which the framework would release it for you. And the type's disposal never names it: searched `Dispose` (Login1.Designer.cs line 14), plus every method those call by name. So `Login1` owns it and never releases it; whatever it holds (a dialog's window handle, a file-system watch, a process handle) stays until finalization, once per instance. Release it in `Dispose(bool)` (`parrotFormEllipse1?.Dispose();` under `disposing`) — that method may be edited, or moved to the hand-written partial; only `InitializeComponent` belongs to the designer — or register it with the container so `components.Dispose()` releases it. — sample/ReaLTaiizor.Login/ReaLTaiizor.Login/Login1.Designer.cs:308
`parrotFormHandle1` (line 309) is a component the designer creates for `Login1` with no container: it is not built with `new T(components)`, not added to `components`, and not added to a parent control's `Controls` or to a component's own child collection — the only routes by which the framework would release it for you. And the type's disposal never names it: searched `Dispose` (Login1.Designer.cs line 14), plus every method those call by name. So `Login1` owns it and never releases it; whatever it holds (a dialog's window handle, a file-system watch, a process handle) stays until finalization, once per instance. Release it in `Dispose(bool)` (`parrotFormHandle1?.Dispose();` under `disposing`) — that method may be edited, or moved to the hand-written partial; only `InitializeComponent` belongs to the designer — or register it with the container so `components.Dispose()` releases it. — sample/ReaLTaiizor.Login/ReaLTaiizor.Login/Login1.Designer.cs:309
`parrotFormHandle2` (line 312) is a component the designer creates for `Login1` with no container: it is not built with `new T(components)`, not added to `components`, and not added to a parent control's `Controls` or to a component's own child collection — the only routes by which the framework would release it for you. And the type's disposal never names it: searched `Dispose` (Login1.Designer.cs line 14), plus every method those call by name. So `Login1` owns it and never releases it; whatever it holds (a dialog's window handle, a file-system watch, a process handle) stays until finalization, once per instance. Release it in `Dispose(bool)` (`parrotFormHandle2?.Dispose();` under `disposing`) — that method may be edited, or moved to the hand-written partial; only `InitializeComponent` belongs to the designer — or register it with the container so `components.Dispose()` releases it. — sample/ReaLTaiizor.Login/ReaLTaiizor.Login/Login1.Designer.cs:312
`parrotControlEllipse1` (line 491) is a component the designer creates for `Player` with no container: it is not built with `new T(components)`, not added to `components`, and not added to a parent control's `Controls` or to a component's own child collection — the only routes by which the framework would release it for you. And the type's disposal never names it: searched `Dispose` (Player.designer.cs line 16), plus every method those call by name. So `Player` owns it and never releases it; whatever it holds (a dialog's window handle, a file-system watch, a process handle) stays until finalization, once per instance. Release it in `Dispose(bool)` (`parrotControlEllipse1?.Dispose();` under `disposing`) — that method may be edited, or moved to the hand-written partial; only `InitializeComponent` belongs to the designer — or register it with the container so `components.Dispose()` releases it. — sample/ReaLTaiizor.Player/ReaLTaiizor.Player/Player.designer.cs:491
`parrotControlEllipse2` (line 492) is a component the designer creates for `Player` with no container: it is not built with `new T(components)`, not added to `components`, and not added to a parent control's `Controls` or to a component's own child collection — the only routes by which the framework would release it for you. And the type's disposal never names it: searched `Dispose` (Player.designer.cs line 16), plus every method those call by name. So `Player` owns it and never releases it; whatever it holds (a dialog's window handle, a file-system watch, a process handle) stays until finalization, once per instance. Release it in `Dispose(bool)` (`parrotControlEllipse2?.Dispose();` under `disposing`) — that method may be edited, or moved to the hand-written partial; only `InitializeComponent` belongs to the designer — or register it with the container so `components.Dispose()` releases it. — sample/ReaLTaiizor.Player/ReaLTaiizor.Player/Player.designer.cs:492
`parrotControlEllipse3` (line 493) is a component the designer creates for `Player` with no container: it is not built with `new T(components)`, not added to `components`, and not added to a parent control's `Controls` or to a component's own child collection — the only routes by which the framework would release it for you. And the type's disposal never names it: searched `Dispose` (Player.designer.cs line 16), plus every method those call by name. So `Player` owns it and never releases it; whatever it holds (a dialog's window handle, a file-system watch, a process handle) stays until finalization, once per instance. Release it in `Dispose(bool)` (`parrotControlEllipse3?.Dispose();` under `disposing`) — that method may be edited, or moved to the hand-written partial; only `InitializeComponent` belongs to the designer — or register it with the container so `components.Dispose()` releases it. — sample/ReaLTaiizor.Player/ReaLTaiizor.Player/Player.designer.cs:493
`metroStyleManager1` (line 766) is a component the designer creates for `Rufus` with no container: it is not built with `new T(components)`, not added to `components`, and not added to a parent control's `Controls` or to a component's own child collection — the only routes by which the framework would release it for you. And the type's disposal never names it: searched `Dispose` (Rufus.Designer.cs line 15), plus every method those call by name. So `Rufus` owns it and never releases it; whatever it holds (a dialog's window handle, a file-system watch, a process handle) stays until finalization, once per instance. Release it in `Dispose(bool)` (`metroStyleManager1?.Dispose();` under `disposing`) — that method may be edited, or moved to the hand-written partial; only `InitializeComponent` belongs to the designer — or register it with the container so `components.Dispose()` releases it. — sample/ReaLTaiizor.Rufus/ReaLTaiizor.Rufus/Rufus.Designer.cs:766
`parrotObjectEllipse1` (line 247) is a component the designer creates for `Splash` with no container: it is not built with `new T(components)`, not added to `components`, and not added to a parent control's `Controls` or to a component's own child collection — the only routes by which the framework would release it for you. And the type's disposal never names it: searched `Dispose` (Splash.Designer.cs line 14), plus every method those call by name. So `Splash` owns it and never releases it; whatever it holds (a dialog's window handle, a file-system watch, a process handle) stays until finalization, once per instance. Release it in `Dispose(bool)` (`parrotObjectEllipse1?.Dispose();` under `disposing`) — that method may be edited, or moved to the hand-written partial; only `InitializeComponent` belongs to the designer — or register it with the container so `components.Dispose()` releases it. — sample/ReaLTaiizor.Splash/ReaLTaiizor.Splash/Splash.Designer.cs:247
`parrotFormHandle1` (line 259) is a component the designer creates for `Splash` with no container: it is not built with `new T(components)`, not added to `components`, and not added to a parent control's `Controls` or to a component's own child collection — the only routes by which the framework would release it for you. And the type's disposal never names it: searched `Dispose` (Splash.Designer.cs line 14), plus every method those call by name. So `Splash` owns it and never releases it; whatever it holds (a dialog's window handle, a file-system watch, a process handle) stays until finalization, once per instance. Release it in `Dispose(bool)` (`parrotFormHandle1?.Dispose();` under `disposing`) — that method may be edited, or moved to the hand-written partial; only `InitializeComponent` belongs to the designer — or register it with the container so `components.Dispose()` releases it. — sample/ReaLTaiizor.Splash/ReaLTaiizor.Splash/Splash.Designer.cs:259
`parrotControlEllipse1` (line 2586) is a component the designer creates for `Store` with no container: it is not built with `new T(components)`, not added to `components`, and not added to a parent control's `Controls` or to a component's own child collection — the only routes by which the framework would release it for you. And the type's disposal never names it: searched `Dispose` (Store.Designer.cs line 14), plus every method those call by name. So `Store` owns it and never releases it; whatever it holds (a dialog's window handle, a file-system watch, a process handle) stays until finalization, once per instance. Release it in `Dispose(bool)` (`parrotControlEllipse1?.Dispose();` under `disposing`) — that method may be edited, or moved to the hand-written partial; only `InitializeComponent` belongs to the designer — or register it with the container so `components.Dispose()` releases it. — sample/ReaLTaiizor.Store/ReaLTaiizor.Store/Store.Designer.cs:2586
`parrotControlEllipse2` (line 2590) is a component the designer creates for `Store` with no container: it is not built with `new T(components)`, not added to `components`, and not added to a parent control's `Controls` or to a component's own child collection — the only routes by which the framework would release it for you. And the type's disposal never names it: searched `Dispose` (Store.Designer.cs line 14), plus every method those call by name. So `Store` owns it and never releases it; whatever it holds (a dialog's window handle, a file-system watch, a process handle) stays until finalization, once per instance. Release it in `Dispose(bool)` (`parrotControlEllipse2?.Dispose();` under `disposing`) — that method may be edited, or moved to the hand-written partial; only `InitializeComponent` belongs to the designer — or register it with the container so `components.Dispose()` releases it. — sample/ReaLTaiizor.Store/ReaLTaiizor.Store/Store.Designer.cs:2590
`parrotControlEllipse3` (line 2602) is a component the designer creates for `Store` with no container: it is not built with `new T(components)`, not added to `components`, and not added to a parent control's `Controls` or to a component's own child collection — the only routes by which the framework would release it for you. And the type's disposal never names it: searched `Dispose` (Store.Designer.cs line 14), plus every method those call by name. So `Store` owns it and never releases it; whatever it holds (a dialog's window handle, a file-system watch, a process handle) stays until finalization, once per instance. Release it in `Dispose(bool)` (`parrotControlEllipse3?.Dispose();` under `disposing`) — that method may be edited, or moved to the hand-written partial; only `InitializeComponent` belongs to the designer — or register it with the container so `components.Dispose()` releases it. — sample/ReaLTaiizor.Store/ReaLTaiizor.Store/Store.Designer.cs:2602
`parrotControlEllipse4` (line 2603) is a component the designer creates for `Store` with no container: it is not built with `new T(components)`, not added to `components`, and not added to a parent control's `Controls` or to a component's own child collection — the only routes by which the framework would release it for you. And the type's disposal never names it: searched `Dispose` (Store.Designer.cs line 14), plus every method those call by name. So `Store` owns it and never releases it; whatever it holds (a dialog's window handle, a file-system watch, a process handle) stays until finalization, once per instance. Release it in `Dispose(bool)` (`parrotControlEllipse4?.Dispose();` under `disposing`) — that method may be edited, or moved to the hand-written partial; only `InitializeComponent` belongs to the designer — or register it with the container so `components.Dispose()` releases it. — sample/ReaLTaiizor.Store/ReaLTaiizor.Store/Store.Designer.cs:2603
`parrotControlEllipse5` (line 2604) is a component the designer creates for `Store` with no container: it is not built with `new T(components)`, not added to `components`, and not added to a parent control's `Controls` or to a component's own child collection — the only routes by which the framework would release it for you. And the type's disposal never names it: searched `Dispose` (Store.Designer.cs line 14), plus every method those call by name. So `Store` owns it and never releases it; whatever it holds (a dialog's window handle, a file-system watch, a process handle) stays until finalization, once per instance. Release it in `Dispose(bool)` (`parrotControlEllipse5?.Dispose();` under `disposing`) — that method may be edited, or moved to the hand-written partial; only `InitializeComponent` belongs to the designer — or register it with the container so `components.Dispose()` releases it. — sample/ReaLTaiizor.Store/ReaLTaiizor.Store/Store.Designer.cs:2604
`MetroCheckBox` implements `IDisposable` — so it has told every caller it holds something worth releasing — and it constructs `_animator` itself (line 81), which makes that instance its own. But `_animator` is named in none of the methods the disposal search covered: `Dispose` (line 381), `Dispose` (line 381) — that is `Dispose` plus every method `Dispose` calls BY NAME, so a release reached through an interface, a delegate or a base class is not followed and is worth checking before acting. On what was read, the type's disposal releases everything except the one thing it owns. A disposable the owner never disposes is held until finalization if its type has a finalizer, and forever if it does not — which for a synchronisation primitive, a timer, a stream or a handle means the resource accumulates once per instance for the life of the process. Release it in `Dispose` (`_animator?.Dispose();`), or, if it truly does not need releasing, drop `IDisposable` from the type so the claim and the behaviour agree. — src/ReaLTaiizor/Controls/CheckBox/MetroCheckBox.cs:81
What to do
Each finding names the value and the span that decides who owns it — the `new` that created it, or the constructor parameter that handed it over. Confirm ownership from that span, then make the disposal match it: release what this type created, leave what it was injected with to whoever created THAT, and drop a finalizer whose type holds nothing unmanaged to release.
Other · Code Health — Whether an argument guard throws the exception its own condition describes — a guard that rejects a value for being EMPTY and reports it as `ArgumentNullException` tells the caller a parameter was null when it provably was not.
Method: Roslyn syntax: `throw new ArgumentNullException(nameof(p))` statements (or a repository exception type deriving from it) controlled by an `if` — directly or through the `using`, `lock` or `try` that wraps the throw — whose condition is read for a test that is true of a NON-null `p` — an emptiness test that dereferences it (`p.Count == 0`, `!p.Any()`) or a BCL predicate documented true of the empty value (`string.IsNullOrEmpty(p)`); in the `else` branch, for a conjunct of the admitting condition that is FALSE of a non-null `p`. Range guards are read for bounds that leave nothing and for a `p > C.Count` bound whose index then reaches `C[p]`, `C.RemoveAt(p)` or a method of the same type that indexes with it. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether a `when` guard is free of side effects — a guard that increments a counter or assigns while deciding whether its arm matches applies that change during PATTERN MATCHING, on an arm that may not be selected, and skips it entirely when a short-circuit to its left answers first.
Method: Roslyn syntax: `when` guards on case labels and switch-expression arms, read for a mutation (`++`/`--`/assignment) sitting in a position the guard's own `&&`/`||`/`??`/`?:`/`?.` can skip. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X27 · Collection changed while being enumerated7.8 / 10Strong✓ Tool-verified
Other · Code Health — Whether a `foreach` leaves the collection it is walking alone — a body that adds to or removes from the very collection the loop is enumerating invalidates the enumerator it is holding, so the next `MoveNext` throws `InvalidOperationException` and the remaining items are never seen.
Method: Roslyn syntax + semantics: `foreach` statements whose body calls a structural mutator (`Add`/`Remove`/`Clear`/`Insert`/…) on the very expression the loop is enumerating. Two arms. ARM A — the source is a concrete fragile BCL collection, or a live `Keys`/`Values` view over one, and the mutator resolves to that same collection's own member; concurrent and immutable collections and arrays are outside the population by construction, since their enumerators survive a structural change. ARM B — the source is an argument-less accessor CALL on a receiver whose body is in source: the accessor must return a stored field VERBATIM and a sibling member must structurally change that same field, both read off the implementations rather than from the members' names. A mutation the loop provably exits immediately after (`break`/`return`/`throw`/`goto`), or one written inside a nested loop or a lambda, is counted and never reported. Deterministic, provable per finding. Advisory.
The loop walks `dcList`, and line 234 calls `dc.Cancel(…)`, which reaches `Unregister(this)` in `DelayedCall.Cancel` — a structural change to that same `List` while the loop's enumerator is live. The next `MoveNext` throws `InvalidOperationException: Collection was modified; enumeration operation may not execute`, so every pass that reaches this call ends the loop by exception instead of by running out of items, and the remaining items are never seen. — src/ReaLTaiizor/Animate/Poison/DelayedCall.cs:232
The loop walks `dcList`, and line 245 calls `dc.Fire(…)`, which reaches `FireNow()` in `DelayedCall.Fire` — a structural change to that same `List` while the loop's enumerator is live. The next `MoveNext` throws `InvalidOperationException: Collection was modified; enumeration operation may not execute`, so every pass that reaches this call ends the loop by exception instead of by running out of items, and the remaining items are never seen. — src/ReaLTaiizor/Animate/Poison/DelayedCall.cs:243
What to do
Each finding names the two spans that cannot both stand — the `foreach` source, and the call inside the body that structurally changes that same collection. Confirm from those two, then pick one: enumerate a snapshot (`foreach (var x in c.ToList())`), collect what needs changing and apply it after the loop, or — where the loop was only ever meant to act on the first match — `break` immediately after the mutation, which is the one shape that is already safe.
Do you agree with this assessment?
X29 · Per-element action decided by a fixed element10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a decision taken once per element is taken ABOUT that element — a test inside a counted loop that reads a fixed subscript of the very collection its guarded statement indexes by the loop variable applies element zero's answer to all of them, so the elements that differ from it are all handled wrongly, and in the same direction.
Method: Roslyn syntax only, no semantic model: every `for` statement declaring exactly ONE loop variable, and every `if` inside its body that is not under a nested loop or a lambda. A site enters the population when the `if`’s condition never mentions the loop variable while the statement it guards indexes some collection by that variable ALONE (`c[i]`; `c[i + 1]` and `c[i, j]` are outside it). A finding additionally needs the AGREEING TWIN at the same-collection grain: the condition must read THAT SAME collection at a subscript that does not move — written into the condition, or reached through a local declared BEFORE the loop, so an alias bound inside the body is not followed. Both collection expressions must be simple identifiers. On a repository with no .NET source the same rule reads JavaScript/TypeScript off the engine’s own token stream (tests included, bundles and vendored paths not): a `for (let|var|const x = …; …; …)` with one declarator and a braced body, an alias followed only when it is declared before the loop in a block that encloses it and never assigned inside the loop. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether exceptions are handled rather than silently swallowed or rethrown with lost stack traces.
Method: Roslyn syntax scan: every catch clause counted; empty catches and bare rethrows flagged. Population is all catch clauses, not estimated. Deterministic, hard fact.
An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it. (×39) — sample/ReaLTaiizor.Splash/ReaLTaiizor.Splash/Splash.cs:58, src/ReaLTaiizor/Controls/Close/ForeverClose.cs:46, src/ReaLTaiizor/Controls/ComboBox/DungeonComboBox.cs:28, …
`catch` does nothing with the exception it caught — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch. Log it through whatever this codebase already uses to report problems, or let it propagate; if one specific failure genuinely cannot matter, catch exactly that exception type and say why in a comment on the catch. — src/ReaLTaiizor/Controls/DatePicker/HopeDatePicker.cs:71
What to do
Swallowed exception (empty catch)
Do you agree with this assessment?
X30 · Support guard that admits what it rejects10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a guard written as a NEGATED `||` says what its author meant — `!(a || b || x != k)` is `!a && !b && x == k` by De Morgan, so a bail-out that mixes capabilities the code needs with a fault it refuses turns inside out: it fires only where the capabilities are ABSENT, and lets every value the fault term names walk straight into the body that cannot handle it.
Method: Roslyn syntax only, no semantic model: every logical-not whose operand is a parenthesised `||` chain of two or more disjuncts, flattened (a left-nested `a || b || c` read once would see `(a || b)` as one disjunct). A site enters the population on that shape alone. A finding additionally needs the disjuncts to DISAGREE in polarity: at least one bare boolean read — an identifier or member access, never an invocation, which is a predicate rather than a capability flag — and at least one `x != <constant>`, the only form that negates into an exact-value pin (`== null` negates into a looser requirement and is outside the fault set). Consistently-polarised disjunctions, all-fault or all-capability, are counted and never reported; a negated `&&` is outside the population entirely. No same-receiver gate: it was measured to cost a real defect and remove no false positive. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
Reference — by lens
The score is the rank-weighted fold of these lenses (worst-heaviest), each including its meta-dimensions; a lens with a Critical contributor is capped at Fair (its band reads "gated by …") and is never the strongest area however high its average.
Unscored — 4 check(s) recorded observations but carry no score
These checks ran and found something, but they do not carry a score — either by design (an advisory check reports evidence rather than grading it) or because they could not be scored here. They are excluded from the score for that reason, not because there was nothing to see.
D36 Supply-chain Provenance & Signing — 2 observation(s) recorded · The CI pipeline publishes no artifact — no package publish, container push or release with files to download. Supply-chain provenance, signing and an SBOM describe a PUBLISHED artifact for the people who obtain it, so there is nothing to attest here; a deployment of the service itself publishes nothing for anyone else to verify. Add them to the release pipeline when this repo starts publishing artifacts (a package, a container image, or a release with downloadable files). Build integrity and workflow-token hygiene are reported below: they describe what the CI runs and the token it runs with, neither of which is affected by whether the pipeline ships an artifact.
SC1 Supply-chain hygiene — 26 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
X10 Duplicated predicate — 40 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
X7 Silent fallback defaults — 12 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 5 control(s) we could not find positive evidence for
These checks grade a working control, and the repository shows no evidence of one. That is deliberately not scored as a zero: a repository cannot show an ops runbook, a database TTL or an infrastructure-side audit log, so absence of evidence here is not evidence the control is missing. It is also not a statement that the check is irrelevant to this codebase — the thing it grades applies; we just could not see it. Excluded from the score either way.
C3 Audit Trail — Repo shows no audit-logging mechanism (IAuditable, an immutable audit log, an EF SaveChanges interceptor) for sensitive changes — absence of evidence is not evidence of a working control. Record an audit trail in code (or document where it lives) so this dimension can be scored.
C4 Data Retention — Repo shows no data-retention / TTL / cleanup mechanism for personal data — absence of evidence is not evidence of a working control. Define retention periods and a purge/cleanup job (or TTL) in code, or document where retention is enforced, so this dimension can be scored.
C5 Data-Subject Rights — Repo shows no corroborated data-subject-rights mechanism (erasure / export-portability / consent) tied to a subject id or GDPR vocabulary — absence of evidence is not evidence of a working control. Implement erasure, data export/portability and consent tracking over the subject's records.
P4 Deployment & Rollback — not evidenced — no deploy/rollback/approval signal in the repo; absence of evidence is not evidence of a manual release
P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 56 check(s) not relevant to this codebase
These checks had nothing to measure here (no tests, no git history, the codebase is small, or the architecture style doesn't apply), so they're omitted above rather than scored low.
AC1 Text alternatives — No web markup found — accessibility is not applicable to this repository.
AC2 Forms & labels — No web markup found — accessibility is not applicable to this repository.
AC3 Page structure — No web markup found — accessibility is not applicable to this repository.
AC4 Keyboard semantics — No web markup found — accessibility is not applicable to this repository.
AC5 ARIA correctness — No web markup found — accessibility is not applicable to this repository.
AC6 Visual & motion safety — No web markup found — accessibility is not applicable to this repository.
AX1 Captive dependencies — no DI registrations detected
AX7 Slice cohesion — not applicable — not a vertical-slice architecture
AX8 Test isolation — no test/production split to check
AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
AXB1 Runtime evidence locked — no reproducible boot — This repository has nothing the runtime tiers could boot or serve — no markup, no UI framework or web-server dependency, no UI component source, no native UI project and no API definition — nothing here is a surface to boot — so runtime a11y/egress/header evidence has no subject here. Not applicable: this is neither a gap in the scan nor a finding about your code.
C2 Access Controls — No access-control surface detected in the analyzed source — no web/app surface to authorize (no HTTP API or web-UI project) and no authorization code at all (no [Authorize]/policies, no imperative guard methods). Access control is therefore N/A here — this is a library/CLI, which is authorized by its CALLER, not by itself. If this codebase grows request handlers, the dimension reactivates and a default-deny posture is expected then.
D10 Test Quality — No tests were found in the analyzed repository to assess for quality.
D11 Test Reliability — No test suite was found to re-run, so reliability couldn't be assessed. Two searches produced that zero and both came back empty: the classifier that reads the loaded workspace recognised no suite it could run, and a walk of the source on disk — which covers the JS/TS `*.test.*` and `*.spec.*` conventions and probes for a Pester suite — found no test source in any other ecosystem either. Neither search reaches a suite that is missing from the loaded workspace and carries no name either walk recognises, so this is 'no suite found by those two searches', not a verdict that the repository has none.
D12 Dependency Hygiene — Dependency hygiene not measured
D16 Bus Factor — single-maintainer repository — bus factor is not applicable
D22 Internal API Consistency — No intentionally-exposed public API to evaluate for consistency.
D23 Boundary Type-Coupling — Cross-context type coupling could not be assessed — this codebase's bounded contexts are neither declared nor inferable.
D25 ADR Conformance — no ADRs to check
D30 Dependency Vulnerabilities — Not measured — a package registry could not be reached
D31 IaC & Container Security — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.
D32 Data Compliance (PII/GDPR) — 1 file(s) were not parsed by semgrep — the PII/GDPR ruleset never ran over them
D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
D7 Architectural Integrity — no checkable ADRs and no dependency cycles — architectural integrity not assessed
DM1 Domain Modelling — not scored — this repository shows none of the 3 signals this lens looks for
ED1 Event-Driven — not scored — this repository shows none of the 3 signals this lens looks for
ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
M4 Documentation accuracy — Not applicable: the 9 current-state document(s) make no claim of a kind M4 checks.
P12 CI test-gate honesty — Reported, not scored — and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
P2 Observability — This repo is a library, not a deployed service — it has no process to operate, so production observability (structured logging, tracing/metrics, health checks) is N/A. A library may log via an injected ILogger, but the absence of operational telemetry is not a defect here. If it grows a host (web API, worker), the dimension reactivates.
P7 Outbound HTTP resilience — not applicable — this isn't a service/API/worker
P8 Schema migrations — no EF Core usage detected
P9 Domain vs controller coverage — coverage not measured: this check compares the coverage of the analyzer's own test run across the domain and web layers, and that run measured none here — Test coverage (D8) says why
PF1 Benchmark discipline — Not applicable: no benchmark suite was found by the two searches this check runs — a BenchmarkDotNet package reference in any project file (loaded, or on disk), and a script whose name contains `benchmark` that this repository's CI runs. Neither can see a suite in another ecosystem's idiom, so this is not a verdict that the repository has none. Benchmarks are credited as a bonus, so their absence is neither scored nor deducted, and nothing is asked of a repository that has none.
PF2 Allocation hygiene — Not scored: this check counted allocation-aware idioms (Span, pools, stackalloc) per line, which describes what kind of code a repository is rather than whether it has an allocation problem, so it was withdrawn. Nothing here is a finding about your code.
S1 Web-Security Posture — No web surface detected in the analyzed source — no HTTP API or web-UI project (no controllers/minimal-API endpoints, no Razor/Blazor views) and no web middleware (HTTPS redirection, HSTS, security headers, cookies). Transport security, security headers, secure cookies, CSRF/input-validation and middleware-order controls are therefore N/A here — this is a library/CLI/worker, not a web app. Crypto hygiene was still checked and found nothing to flag. If this codebase becomes web-facing, the dimension reactivates automatically.
X14 Bypassable address classification — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X15 Unvalidated length from an untrusted reader — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X17 Uncapped recursion over a caller-supplied document — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X19 Unrestored process-global state — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X2 Cancellation propagation — no async method does work a token could cancel
X22 Contradicted release guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X23 Unguarded diagnostic materialisation — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X24 Document value interpolated into markup unescaped — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X25 Inert configuration knob — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X26 Unsynchronised callback handoff — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X28 Index access outside its own emptiness guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X32 Type resolved by simple name across every loaded assembly — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X4 Structured logging — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X5 Nullable reference types — no NRT-eligible projects
X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Appendix A — Findings (grouped)
The findings behind the scores, grouped by severity, then by dimension and kind. The high-severity issues are enumerated in full below; items per group are capped at 25 with any overflow stated explicitly per group, never silently truncated. The complete machine-readable list of every finding (all severities) is the companion findings.md in this report's bundle.
EmptyCatchBlock sample/ReaLTaiizor.Splash/ReaLTaiizor.Splash/Splash.cs:58— empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
EmptyCatchBlock src/ReaLTaiizor/Controls/Close/ForeverClose.cs:46— empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
EmptyCatchBlock src/ReaLTaiizor/Controls/ComboBox/DungeonComboBox.cs:28— empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
EmptyCatchBlock src/ReaLTaiizor/Controls/ComboBox/ForeverComboBox.cs:108— empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
EmptyCatchBlock src/ReaLTaiizor/Controls/ComboBox/MaterialComboBox.cs:85— empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
EmptyCatchBlock src/ReaLTaiizor/Controls/ComboBox/MetroComboBox.cs:127— empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
EmptyCatchBlock src/ReaLTaiizor/Controls/ComboBox/SkyComboBox.cs:28— empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
EmptyCatchBlock src/ReaLTaiizor/Controls/ComboBox/SkyComboBox.cs:55— empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
EmptyCatchBlock src/ReaLTaiizor/Controls/ComboBox/SkyComboBox.cs:176— empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
EmptyCatchBlock src/ReaLTaiizor/Controls/ComboBoxEdit/ComboBoxEdit.cs:28— empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
EmptyCatchBlock src/ReaLTaiizor/Controls/ControlBox/ControlBox.cs:206— empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
EmptyCatchBlock src/ReaLTaiizor/Controls/ControlBox/MetroControlBox.cs:418— empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
EmptyCatchBlock src/ReaLTaiizor/Controls/ControlBox/NightControlBox.cs:360— empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
EmptyCatchBlock src/ReaLTaiizor/Controls/ControlBox/ThunderControlBox.cs:77— empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
EmptyCatchBlock src/ReaLTaiizor/Controls/Extender/PoisonStyleExtender.cs:115— empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
EmptyCatchBlock src/ReaLTaiizor/Controls/Extender/PoisonStyleExtender.cs:121— empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
EmptyCatchBlock src/ReaLTaiizor/Controls/Handle/ParrotFormHandle.cs:64— empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
EmptyCatchBlock src/ReaLTaiizor/Controls/ListBox/MaterialListBox.cs:966— empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
EmptyCatchBlock src/ReaLTaiizor/Controls/ListBox/MaterialListBox.cs:979— empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
EmptyCatchBlock src/ReaLTaiizor/Controls/ListBox/MetroListBox.cs:669— empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
EmptyCatchBlock src/ReaLTaiizor/Controls/ListBox/MetroListBox.cs:682— empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
EmptyCatchBlock src/ReaLTaiizor/Controls/Maximize/ForeverMaximize.cs:46— empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
EmptyCatchBlock src/ReaLTaiizor/Controls/MessageBox/PoisonMessageBox.cs:147— empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
EmptyCatchBlock src/ReaLTaiizor/Controls/MessageBox/PoisonMessageBox.cs:168— empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
EmptyCatchBlock src/ReaLTaiizor/Controls/Minimize/ForeverMinimize.cs:46— empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
WriteOnlyPrivateField src/ReaLTaiizor/Animate/Poison/Animate.cs:25— private Control targetControl — assigned 1 time(s), read never — this field is written and never read anywhere its type can be reached from, so the state it keeps answers no question: every assignment to it computes a value that nothing observes, on every instance, for the lifetime of each one. It reads as a flag the code branches on, and nothing branches on it. Delete the field and its assignments — or, if the value was MEANT to be consulted, the missing read is the defect this row is pointing at, and the branch that should have depended on it is not there.
WriteOnlyPrivateField src/ReaLTaiizor/Controls/Button/MaterialFloatingActionButton.cs:360— private Point origin — assigned 1 time(s), read never — this field is written and never read anywhere its type can be reached from, so the state it keeps answers no question: every assignment to it computes a value that nothing observes, on every instance, for the lifetime of each one. It reads as a flag the code branches on, and nothing branches on it. Delete the field and its assignments — or, if the value was MEANT to be consulted, the missing read is the defect this row is pointing at, and the branch that should have depended on it is not there.
WriteOnlyPrivateField src/ReaLTaiizor/Controls/Button/ParrotSuperButton.cs:378— private Color CurrentForeColor — assigned 8 time(s), read never — this field is written and never read anywhere its type can be reached from, so the state it keeps answers no question: every assignment to it computes a value that nothing observes, on every instance, for the lifetime of each one. It reads as a flag the code branches on, and nothing branches on it. Delete the field and its assignments — or, if the value was MEANT to be consulted, the missing read is the defect this row is pointing at, and the branch that should have depended on it is not there.
WriteOnlyPrivateField src/ReaLTaiizor/Controls/CheckBox/DungeonCheckBox.cs:22— private Rectangle R1 — assigned 1 time(s), read never — this field is written and never read anywhere its type can be reached from, so the state it keeps answers no question: every assignment to it computes a value that nothing observes, on every instance, for the lifetime of each one. It reads as a flag the code branches on, and nothing branches on it. Delete the field and its assignments — or, if the value was MEANT to be consulted, the missing read is the defect this row is pointing at, and the branch that should have depended on it is not there.
WriteOnlyPrivateField src/ReaLTaiizor/Controls/CheckBox/DungeonCheckBox.cs:23— private Rectangle R2 — assigned 1 time(s), read never — this field is written and never read anywhere its type can be reached from, so the state it keeps answers no question: every assignment to it computes a value that nothing observes, on every instance, for the lifetime of each one. It reads as a flag the code branches on, and nothing branches on it. Delete the field and its assignments — or, if the value was MEANT to be consulted, the missing read is the defect this row is pointing at, and the branch that should have depended on it is not there.
WriteOnlyPrivateField src/ReaLTaiizor/Controls/CheckBox/ThunderCheckBox.cs:19— private MouseStateThunder State — assigned 5 time(s), read never — this field is written and never read anywhere its type can be reached from, so the state it keeps answers no question: every assignment to it computes a value that nothing observes, on every instance, for the lifetime of each one. It reads as a flag the code branches on, and nothing branches on it. Delete the field and its assignments — or, if the value was MEANT to be consulted, the missing read is the defect this row is pointing at, and the branch that should have depended on it is not there.
WriteOnlyPrivateField src/ReaLTaiizor/Controls/RadioButton/ThunderRadioButton.cs:19— private MouseStateThunder State — assigned 5 time(s), read never — this field is written and never read anywhere its type can be reached from, so the state it keeps answers no question: every assignment to it computes a value that nothing observes, on every instance, for the lifetime of each one. It reads as a flag the code branches on, and nothing branches on it. Delete the field and its assignments — or, if the value was MEANT to be consulted, the missing read is the defect this row is pointing at, and the branch that should have depended on it is not there.
WriteOnlyPrivateField src/ReaLTaiizor/Controls/ComboBox/ForeverComboBox.cs:22— private int y — assigned 1 time(s), read never — this field is written and never read anywhere its type can be reached from, so the state it keeps answers no question: every assignment to it computes a value that nothing observes, on every instance, for the lifetime of each one. It reads as a flag the code branches on, and nothing branches on it. Delete the field and its assignments — or, if the value was MEANT to be consulted, the missing read is the defect this row is pointing at, and the branch that should have depended on it is not there.
WriteOnlyPrivateField src/ReaLTaiizor/Controls/ComboBox/ForeverComboBox.cs:24— private MouseStateForever State — assigned 5 time(s), read never — this field is written and never read anywhere its type can be reached from, so the state it keeps answers no question: every assignment to it computes a value that nothing observes, on every instance, for the lifetime of each one. It reads as a flag the code branches on, and nothing branches on it. Delete the field and its assignments — or, if the value was MEANT to be consulted, the missing read is the defect this row is pointing at, and the branch that should have depended on it is not there.
WriteOnlyPrivateField src/ReaLTaiizor/Controls/TextBox/ForeverTextBox.cs:23— private MouseStateForever State — assigned 5 time(s), read never — this field is written and never read anywhere its type can be reached from, so the state it keeps answers no question: every assignment to it computes a value that nothing observes, on every instance, for the lifetime of each one. It reads as a flag the code branches on, and nothing branches on it. Delete the field and its assignments — or, if the value was MEANT to be consulted, the missing read is the defect this row is pointing at, and the branch that should have depended on it is not there.
WriteOnlyPrivateField src/ReaLTaiizor/Controls/Toggle/ForeverToggle.cs:23— private MouseStateForever State — assigned 5 time(s), read never — this field is written and never read anywhere its type can be reached from, so the state it keeps answers no question: every assignment to it computes a value that nothing observes, on every instance, for the lifetime of each one. It reads as a flag the code branches on, and nothing branches on it. Delete the field and its assignments — or, if the value was MEANT to be consulted, the missing read is the defect this row is pointing at, and the branch that should have depended on it is not there.
WriteOnlyPrivateField src/ReaLTaiizor/Controls/Label/MetroLabel.cs:72— private Methods mth — assigned 1 time(s), read never — this field is written and never read anywhere its type can be reached from, so the state it keeps answers no question: every assignment to it computes a value that nothing observes, on every instance, for the lifetime of each one. It reads as a flag the code branches on, and nothing branches on it. Delete the field and its assignments — or, if the value was MEANT to be consulted, the missing read is the defect this row is pointing at, and the branch that should have depended on it is not there.
WriteOnlyPrivateField src/ReaLTaiizor/Controls/Numeric/ForeverNumeric.cs:22— private MouseStateForever State — assigned 1 time(s), read never — this field is written and never read anywhere its type can be reached from, so the state it keeps answers no question: every assignment to it computes a value that nothing observes, on every instance, for the lifetime of each one. It reads as a flag the code branches on, and nothing branches on it. Delete the field and its assignments — or, if the value was MEANT to be consulted, the missing read is the defect this row is pointing at, and the branch that should have depended on it is not there.
WriteOnlyPrivateField src/ReaLTaiizor/Controls/Numeric/HopeNumeric.cs:26— private string textValue — assigned 1 time(s), read never — this field is written and never read anywhere its type can be reached from, so the state it keeps answers no question: every assignment to it computes a value that nothing observes, on every instance, for the lifetime of each one. It reads as a flag the code branches on, and nothing branches on it. Delete the field and its assignments — or, if the value was MEANT to be consulted, the missing read is the defect this row is pointing at, and the branch that should have depended on it is not there.
WriteOnlyPrivateField src/ReaLTaiizor/Controls/Progress/HopeRoundPrgoressBar.cs:20— private int tempValue — assigned 1 time(s), read never — this field is written and never read anywhere its type can be reached from, so the state it keeps answers no question: every assignment to it computes a value that nothing observes, on every instance, for the lifetime of each one. It reads as a flag the code branches on, and nothing branches on it. Delete the field and its assignments — or, if the value was MEANT to be consulted, the missing read is the defect this row is pointing at, and the branch that should have depended on it is not there.
WriteOnlyPrivateField src/ReaLTaiizor/Controls/RadioButton/MaterialRadioButton.cs:70— private Rectangle _radioButtonBounds — assigned 1 time(s), read never — this field is written and never read anywhere its type can be reached from, so the state it keeps answers no question: every assignment to it computes a value that nothing observes, on every instance, for the lifetime of each one. It reads as a flag the code branches on, and nothing branches on it. Delete the field and its assignments — or, if the value was MEANT to be consulted, the missing read is the defect this row is pointing at, and the branch that should have depended on it is not there.
WriteOnlyPrivateField src/ReaLTaiizor/Controls/ScrollBar/CrownScrollBar.cs:37— private bool _thumbClicked — assigned 1 time(s), read never — this field is written and never read anywhere its type can be reached from, so the state it keeps answers no question: every assignment to it computes a value that nothing observes, on every instance, for the lifetime of each one. It reads as a flag the code branches on, and nothing branches on it. Delete the field and its assignments — or, if the value was MEANT to be consulted, the missing read is the defect this row is pointing at, and the branch that should have depended on it is not there.
WriteOnlyPrivateField src/ReaLTaiizor/Controls/Switch/MaterialSwitch.cs:88— private int _trackOffsetY — assigned 1 time(s), read never — this field is written and never read anywhere its type can be reached from, so the state it keeps answers no question: every assignment to it computes a value that nothing observes, on every instance, for the lifetime of each one. It reads as a flag the code branches on, and nothing branches on it. Delete the field and its assignments — or, if the value was MEANT to be consulted, the missing read is the defect this row is pointing at, and the branch that should have depended on it is not there.
WriteOnlyPrivateField src/ReaLTaiizor/Controls/TabControl/PoisonTabControl.cs:145— private List<string> tabOrder — assigned 1 time(s), read never — this field is written and never read anywhere its type can be reached from, so the state it keeps answers no question: every assignment to it computes a value that nothing observes, on every instance, for the lifetime of each one. It reads as a flag the code branches on, and nothing branches on it. Delete the field and its assignments — or, if the value was MEANT to be consulted, the missing read is the defect this row is pointing at, and the branch that should have depended on it is not there.
WriteOnlyPrivateField src/ReaLTaiizor/Controls/TabPage/ForeverTabPage.cs:20— private int W — assigned 1 time(s), read never — this field is written and never read anywhere its type can be reached from, so the state it keeps answers no question: every assignment to it computes a value that nothing observes, on every instance, for the lifetime of each one. It reads as a flag the code branches on, and nothing branches on it. Delete the field and its assignments — or, if the value was MEANT to be consulted, the missing read is the defect this row is pointing at, and the branch that should have depended on it is not there.
WriteOnlyPrivateField src/ReaLTaiizor/Controls/TextBoxEdit/MaterialMultiLineTextBoxEdit.cs:688— private bool hasHint — assigned 1 time(s), read never — this field is written and never read anywhere its type can be reached from, so the state it keeps answers no question: every assignment to it computes a value that nothing observes, on every instance, for the lifetime of each one. It reads as a flag the code branches on, and nothing branches on it. Delete the field and its assignments — or, if the value was MEANT to be consulted, the missing read is the defect this row is pointing at, and the branch that should have depended on it is not there.
WriteOnlyPrivateField src/ReaLTaiizor/Controls/TrackBar/HopeTrackBar.cs:20— private RectangleF valueBar — assigned 1 time(s), read never — this field is written and never read anywhere its type can be reached from, so the state it keeps answers no question: every assignment to it computes a value that nothing observes, on every instance, for the lifetime of each one. It reads as a flag the code branches on, and nothing branches on it. Delete the field and its assignments — or, if the value was MEANT to be consulted, the missing read is the defect this row is pointing at, and the branch that should have depended on it is not there.
WriteOnlyPrivateField src/ReaLTaiizor/Controls/TrackBar/HopeTrackBar.cs:21— private RectangleF valueRect — assigned 1 time(s), read never — this field is written and never read anywhere its type can be reached from, so the state it keeps answers no question: every assignment to it computes a value that nothing observes, on every instance, for the lifetime of each one. It reads as a flag the code branches on, and nothing branches on it. Delete the field and its assignments — or, if the value was MEANT to be consulted, the missing read is the defect this row is pointing at, and the branch that should have depended on it is not there.
WriteOnlyPrivateField src/ReaLTaiizor/Docking/Crown/CrownDockTabArea.cs:19— private Dictionary<CrownDockContent, CrownDockTab> _tabs — assigned 1 time(s), read never — this field is written and never read anywhere its type can be reached from, so the state it keeps answers no question: every assignment to it computes a value that nothing observes, on every instance, for the lifetime of each one. It reads as a flag the code branches on, and nothing branches on it. Delete the field and its assignments — or, if the value was MEANT to be consulted, the missing read is the defect this row is pointing at, and the branch that should have depended on it is not there.
WriteOnlyPrivateField src/ReaLTaiizor/Forms/Container/ForeverForm.cs:25— private Size _ImageSize — assigned 2 time(s), read never — this field is written and never read anywhere its type can be reached from, so the state it keeps answers no question: every assignment to it computes a value that nothing observes, on every instance, for the lifetime of each one. It reads as a flag the code branches on, and nothing branches on it. Delete the field and its assignments — or, if the value was MEANT to be consulted, the missing read is the defect this row is pointing at, and the branch that should have depended on it is not there.
Namespace dependency cycle src/ReaLTaiizor/Colors/Material.cs:4— The namespaces ReaLTaiizor.Colors ↔ ReaLTaiizor.Util depend on each other. The lightest dependency in the cycle is ReaLTaiizor.Colors → ReaLTaiizor.Util (ReaLTaiizor.Colors.MaterialColorScheme → ReaLTaiizor.Util.MaterialTextShade, 1 type pair(s)); cut that one first, e.g. by moving the shared type to a namespace both can use or inverting it behind an interface.
Namespace dependency cycle src/ReaLTaiizor/Child/Crown/CrownDialog.cs:5— The namespaces ReaLTaiizor.Child.Crown ↔ ReaLTaiizor.Child.Material ↔ ReaLTaiizor.Child.Metro ↔ ReaLTaiizor.Child.Poison ↔ ReaLTaiizor.Controls ↔ ReaLTaiizor.Docking.Crown ↔ ReaLTaiizor.Forms ↔ ReaLTaiizor.Helper ↔ ReaLTaiizor.Interface.Metro ↔ ReaLTaiizor.Interface.Poison ↔ ReaLTaiizor.Manager ↔ ReaLTaiizor.Native ↔ ReaLTaiizor.Properties depend on each other. The lightest dependency in the cycle is ReaLTaiizor.Child.Crown → ReaLTaiizor.Forms (ReaLTaiizor.Child.Crown.CrownDialog → ReaLTaiizor.Forms.CrownForm, 1 type pair(s)); cut that one first, e.g. by moving the shared type to a namespace both can use or inverting it behind an interface.
NoWarnInCsproj src/ReaLTaiizor/ReaLTaiizor.csproj:54— 1587 — this warning is switched off for the WHOLE project, in every file it builds, including code written years from now: nothing at the call site records that the rule was ever silenced, so the next reader has no reason to look here. Fix what the rule is reporting and drop the code from the list, or — if some occurrences really are legitimate — narrow the suppression to those sites and give each one its reason, so the rule keeps protecting the rest of the project.
NoWarnInCsproj src/ReaLTaiizor/ReaLTaiizor.csproj:54— 1591 — this project generates an XML documentation file as a build output, so its documentation is something it PUBLISHES to whoever consumes the assembly, and this entry switches off a rule whose only job is to report that documentation missing or malformed. The two decisions sit in the same file and the quiet one wins: the documentation this project ships has holes exactly where the rule would have pointed, no build says so, and the people who meet the gap are downstream — in their editor, at the moment they are trying to use the member. Write the documentation the rule is asking for and drop the code from the list; where only some elements genuinely cannot carry it, narrow the suppression to those sites and give each one its reason, so the rest of the API stays covered. If the documentation was never meant to be consumed, the honest fix is the other line — stop generating the file, so the project no longer publishes something it is choosing not to check.
NoWarnInCsproj repeated across 20 files src/ReaLTaiizor_CR/ReaLTaiizor_CR.csproj:26— The identical NoWarnInCsproj (`CA1416`) appears in 20 files (20 occurrences) — a single repo-wide policy (e.g. a Directory.Build.props decision or an idiomatic suppression), not 20 independent debts. Decide it once centrally rather than file-by-file. (Every occurrence still counts toward the score and metrics.)
No automated tests — No automated tests — no test code was found in this repository. Untested code is the largest single risk to changing it safely. Start with the code you change most often: add a suite in a framework a runner can collect (xUnit, NUnit or MSTest), and run it in CI so the gap cannot reopen.
Swallowed exception (empty catch) sample/ReaLTaiizor.Splash/ReaLTaiizor.Splash/Splash.cs:58— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) src/ReaLTaiizor/Controls/Close/ForeverClose.cs:46— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) src/ReaLTaiizor/Controls/ComboBox/DungeonComboBox.cs:28— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) src/ReaLTaiizor/Controls/ComboBox/ForeverComboBox.cs:108— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) src/ReaLTaiizor/Controls/ComboBox/MaterialComboBox.cs:85— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) src/ReaLTaiizor/Controls/ComboBox/MetroComboBox.cs:127— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) src/ReaLTaiizor/Controls/ComboBox/SkyComboBox.cs:28— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) src/ReaLTaiizor/Controls/ComboBox/SkyComboBox.cs:55— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) src/ReaLTaiizor/Controls/ComboBox/SkyComboBox.cs:176— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) src/ReaLTaiizor/Controls/ComboBoxEdit/ComboBoxEdit.cs:28— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) src/ReaLTaiizor/Controls/ControlBox/ControlBox.cs:206— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) src/ReaLTaiizor/Controls/ControlBox/MetroControlBox.cs:418— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) src/ReaLTaiizor/Controls/ControlBox/NightControlBox.cs:360— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) src/ReaLTaiizor/Controls/ControlBox/ThunderControlBox.cs:77— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) src/ReaLTaiizor/Controls/Extender/PoisonStyleExtender.cs:115— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) src/ReaLTaiizor/Controls/Extender/PoisonStyleExtender.cs:121— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) src/ReaLTaiizor/Controls/Handle/ParrotFormHandle.cs:64— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) src/ReaLTaiizor/Controls/ListBox/MaterialListBox.cs:966— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) src/ReaLTaiizor/Controls/ListBox/MaterialListBox.cs:979— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) src/ReaLTaiizor/Controls/ListBox/MetroListBox.cs:669— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) src/ReaLTaiizor/Controls/ListBox/MetroListBox.cs:682— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) src/ReaLTaiizor/Controls/Maximize/ForeverMaximize.cs:46— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) src/ReaLTaiizor/Controls/MessageBox/PoisonMessageBox.cs:147— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) src/ReaLTaiizor/Controls/MessageBox/PoisonMessageBox.cs:168— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) src/ReaLTaiizor/Controls/Minimize/ForeverMinimize.cs:46— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
+ 14 more in this group — see findings.md.
X18 · Disposal-pattern correctness· Owned disposable field is never released · ×28
Owned disposable field is never released demo/ReaLTaiizor.UI/ReaLTaiizor.UI/Form14.designer.cs:609— `hopeContextMenuStrip1` (line 609) is a component the designer creates for `Form14` with no container: it is not built with `new T(components)`, not added to `components`, and not added to a parent control's `Controls` or to a component's own child collection — the only routes by which the framework would release it for you. And the type's disposal never names it: searched `Dispose` (Form14.designer.cs line 14), plus every method those call by name. So `Form14` owns it and never releases it; whatever it holds (a dialog's window handle, a file-system watch, a process handle) stays until finalization, once per instance. Release it in `Dispose(bool)` (`hopeContextMenuStrip1?.Dispose();` under `disposing`) — that method may be edited, or moved to the hand-written partial; only `InitializeComponent` belongs to the designer — or register it with the container so `components.Dispose()` releases it.
Owned disposable field is never released demo/ReaLTaiizor.UI/ReaLTaiizor.UI/Form17.Designer.cs:3480— `materialContextMenuStrip1` (line 3480) is a component the designer creates for `Form17` with no container: it is not built with `new T(components)`, not added to `components`, and not added to a parent control's `Controls` or to a component's own child collection — the only routes by which the framework would release it for you. And the type's disposal never names it: searched `Dispose` (Form17.Designer.cs line 17), plus every method those call by name. So `Form17` owns it and never releases it; whatever it holds (a dialog's window handle, a file-system watch, a process handle) stays until finalization, once per instance. Release it in `Dispose(bool)` (`materialContextMenuStrip1?.Dispose();` under `disposing`) — that method may be edited, or moved to the hand-written partial; only `InitializeComponent` belongs to the designer — or register it with the container so `components.Dispose()` releases it.
Owned disposable field is never released demo/ReaLTaiizor.UI/ReaLTaiizor.UI/Form19.Designer.cs:2433— `MetroToolTip1` (line 2433) is a component the designer creates for `Form19` with no container: it is not built with `new T(components)`, not added to `components`, and not added to a parent control's `Controls` or to a component's own child collection — the only routes by which the framework would release it for you. And the type's disposal never names it: searched `Dispose` (Form19.Designer.cs line 14), plus every method those call by name. So `Form19` owns it and never releases it; whatever it holds (a dialog's window handle, a file-system watch, a process handle) stays until finalization, once per instance. Release it in `Dispose(bool)` (`MetroToolTip1?.Dispose();` under `disposing`) — that method may be edited, or moved to the hand-written partial; only `InitializeComponent` belongs to the designer — or register it with the container so `components.Dispose()` releases it.
Owned disposable field is never released demo/ReaLTaiizor.UI/ReaLTaiizor.UI/Form19.Designer.cs:2434— `MetroContextMenuStrip1` (line 2434) is a component the designer creates for `Form19` with no container: it is not built with `new T(components)`, not added to `components`, and not added to a parent control's `Controls` or to a component's own child collection — the only routes by which the framework would release it for you. And the type's disposal never names it: searched `Dispose` (Form19.Designer.cs line 14), plus every method those call by name. So `Form19` owns it and never releases it; whatever it holds (a dialog's window handle, a file-system watch, a process handle) stays until finalization, once per instance. Release it in `Dispose(bool)` (`MetroContextMenuStrip1?.Dispose();` under `disposing`) — that method may be edited, or moved to the hand-written partial; only `InitializeComponent` belongs to the designer — or register it with the container so `components.Dispose()` releases it.
Owned disposable field is never released demo/ReaLTaiizor.UI/ReaLTaiizor.UI/Form19.Designer.cs:2436— `metroStyleManager1` (line 2436) is a component the designer creates for `Form19` with no container: it is not built with `new T(components)`, not added to `components`, and not added to a parent control's `Controls` or to a component's own child collection — the only routes by which the framework would release it for you. And the type's disposal never names it: searched `Dispose` (Form19.Designer.cs line 14), plus every method those call by name. So `Form19` owns it and never releases it; whatever it holds (a dialog's window handle, a file-system watch, a process handle) stays until finalization, once per instance. Release it in `Dispose(bool)` (`metroStyleManager1?.Dispose();` under `disposing`) — that method may be edited, or moved to the hand-written partial; only `InitializeComponent` belongs to the designer — or register it with the container so `components.Dispose()` releases it.
Owned disposable field is never released demo/ReaLTaiizor.UI/ReaLTaiizor.UI/Form20.Designer.cs:1449— `poisonToolTip` (line 1449) is a component the designer creates for `Form20` with no container: it is not built with `new T(components)`, not added to `components`, and not added to a parent control's `Controls` or to a component's own child collection — the only routes by which the framework would release it for you. And the type's disposal never names it: searched `Dispose` (Form20.Designer.cs line 16), plus every method those call by name. So `Form20` owns it and never releases it; whatever it holds (a dialog's window handle, a file-system watch, a process handle) stays until finalization, once per instance. Release it in `Dispose(bool)` (`poisonToolTip?.Dispose();` under `disposing`) — that method may be edited, or moved to the hand-written partial; only `InitializeComponent` belongs to the designer — or register it with the container so `components.Dispose()` releases it.
Owned disposable field is never released demo/ReaLTaiizor.UI/ReaLTaiizor.UI/Form22.designer.cs:1152— `parrotObjectEllipse1` (line 1152) is a component the designer creates for `Form22` with no container: it is not built with `new T(components)`, not added to `components`, and not added to a parent control's `Controls` or to a component's own child collection — the only routes by which the framework would release it for you. And the type's disposal never names it: searched `Dispose` (Form22.designer.cs line 14), plus every method those call by name. So `Form22` owns it and never releases it; whatever it holds (a dialog's window handle, a file-system watch, a process handle) stays until finalization, once per instance. Release it in `Dispose(bool)` (`parrotObjectEllipse1?.Dispose();` under `disposing`) — that method may be edited, or moved to the hand-written partial; only `InitializeComponent` belongs to the designer — or register it with the container so `components.Dispose()` releases it.
Owned disposable field is never released demo/ReaLTaiizor.UI/ReaLTaiizor.UI/Form22.designer.cs:1153— `parrotSplashScreen1` (line 1153) is a component the designer creates for `Form22` with no container: it is not built with `new T(components)`, not added to `components`, and not added to a parent control's `Controls` or to a component's own child collection — the only routes by which the framework would release it for you. And the type's disposal never names it: searched `Dispose` (Form22.designer.cs line 14), plus every method those call by name. So `Form22` owns it and never releases it; whatever it holds (a dialog's window handle, a file-system watch, a process handle) stays until finalization, once per instance. Release it in `Dispose(bool)` (`parrotSplashScreen1?.Dispose();` under `disposing`) — that method may be edited, or moved to the hand-written partial; only `InitializeComponent` belongs to the designer — or register it with the container so `components.Dispose()` releases it.
Owned disposable field is never released ready/ReaLTaiizor.AppLocker/ReaLTaiizor.AppLocker/AppPassword.Designer.cs:162— `backgroundWorker1` (line 162) is a component the designer creates for `AppPassword` with no container: it is not built with `new T(components)`, not added to `components`, and not added to a parent control's `Controls` or to a component's own child collection — the only routes by which the framework would release it for you. And the type's disposal never names it: searched `Dispose` (AppPassword.Designer.cs line 15), plus every method those call by name. So `AppPassword` owns it and never releases it; whatever it holds (a dialog's window handle, a file-system watch, a process handle) stays until finalization, once per instance. Release it in `Dispose(bool)` (`backgroundWorker1?.Dispose();` under `disposing`) — that method may be edited, or moved to the hand-written partial; only `InitializeComponent` belongs to the designer — or register it with the container so `components.Dispose()` releases it.
Owned disposable field is never released ready/ReaLTaiizor.AppLocker/ReaLTaiizor.AppLocker/RunApp.Designer.cs:136— `PTT` (line 136) is a component the designer creates for `RunApp` with no container: it is not built with `new T(components)`, not added to `components`, and not added to a parent control's `Controls` or to a component's own child collection — the only routes by which the framework would release it for you. And the type's disposal never names it: searched `Dispose` (RunApp.Designer.cs line 15), plus every method those call by name. So `RunApp` owns it and never releases it; whatever it holds (a dialog's window handle, a file-system watch, a process handle) stays until finalization, once per instance. Release it in `Dispose(bool)` (`PTT?.Dispose();` under `disposing`) — that method may be edited, or moved to the hand-written partial; only `InitializeComponent` belongs to the designer — or register it with the container so `components.Dispose()` releases it.
Owned disposable field is never released ready/ReaLTaiizor.Stopwatch/ReaLTaiizor.Stopwatch/Area.Designer.cs:312— `metroToolTip1` (line 312) is a component the designer creates for `Area` with no container: it is not built with `new T(components)`, not added to `components`, and not added to a parent control's `Controls` or to a component's own child collection — the only routes by which the framework would release it for you. And the type's disposal never names it: searched `Dispose` (Area.Designer.cs line 15), plus every method those call by name. So `Area` owns it and never releases it; whatever it holds (a dialog's window handle, a file-system watch, a process handle) stays until finalization, once per instance. Release it in `Dispose(bool)` (`metroToolTip1?.Dispose();` under `disposing`) — that method may be edited, or moved to the hand-written partial; only `InitializeComponent` belongs to the designer — or register it with the container so `components.Dispose()` releases it.
Owned disposable field is never released ready/ReaLTaiizor.Stopwatch/ReaLTaiizor.Stopwatch/Stopwatch.Designer.cs:182— `parrotObjectEllipse1` (line 182) is a component the designer creates for `Stopwatch` with no container: it is not built with `new T(components)`, not added to `components`, and not added to a parent control's `Controls` or to a component's own child collection — the only routes by which the framework would release it for you. And the type's disposal never names it: searched `Dispose` (Stopwatch.Designer.cs line 15), plus every method those call by name. So `Stopwatch` owns it and never releases it; whatever it holds (a dialog's window handle, a file-system watch, a process handle) stays until finalization, once per instance. Release it in `Dispose(bool)` (`parrotObjectEllipse1?.Dispose();` under `disposing`) — that method may be edited, or moved to the hand-written partial; only `InitializeComponent` belongs to the designer — or register it with the container so `components.Dispose()` releases it.
Owned disposable field is never released ready/ReaLTaiizor.Stopwatch/ReaLTaiizor.Stopwatch/Stopwatch.Designer.cs:184— `parrotSplashScreen1` (line 184) is a component the designer creates for `Stopwatch` with no container: it is not built with `new T(components)`, not added to `components`, and not added to a parent control's `Controls` or to a component's own child collection — the only routes by which the framework would release it for you. And the type's disposal never names it: searched `Dispose` (Stopwatch.Designer.cs line 15), plus every method those call by name. So `Stopwatch` owns it and never releases it; whatever it holds (a dialog's window handle, a file-system watch, a process handle) stays until finalization, once per instance. Release it in `Dispose(bool)` (`parrotSplashScreen1?.Dispose();` under `disposing`) — that method may be edited, or moved to the hand-written partial; only `InitializeComponent` belongs to the designer — or register it with the container so `components.Dispose()` releases it.
Owned disposable field is never released sample/ReaLTaiizor.Login/ReaLTaiizor.Login/Login1.Designer.cs:308— `parrotFormEllipse1` (line 308) is a component the designer creates for `Login1` with no container: it is not built with `new T(components)`, not added to `components`, and not added to a parent control's `Controls` or to a component's own child collection — the only routes by which the framework would release it for you. And the type's disposal never names it: searched `Dispose` (Login1.Designer.cs line 14), plus every method those call by name. So `Login1` owns it and never releases it; whatever it holds (a dialog's window handle, a file-system watch, a process handle) stays until finalization, once per instance. Release it in `Dispose(bool)` (`parrotFormEllipse1?.Dispose();` under `disposing`) — that method may be edited, or moved to the hand-written partial; only `InitializeComponent` belongs to the designer — or register it with the container so `components.Dispose()` releases it.
Owned disposable field is never released sample/ReaLTaiizor.Login/ReaLTaiizor.Login/Login1.Designer.cs:309— `parrotFormHandle1` (line 309) is a component the designer creates for `Login1` with no container: it is not built with `new T(components)`, not added to `components`, and not added to a parent control's `Controls` or to a component's own child collection — the only routes by which the framework would release it for you. And the type's disposal never names it: searched `Dispose` (Login1.Designer.cs line 14), plus every method those call by name. So `Login1` owns it and never releases it; whatever it holds (a dialog's window handle, a file-system watch, a process handle) stays until finalization, once per instance. Release it in `Dispose(bool)` (`parrotFormHandle1?.Dispose();` under `disposing`) — that method may be edited, or moved to the hand-written partial; only `InitializeComponent` belongs to the designer — or register it with the container so `components.Dispose()` releases it.
Owned disposable field is never released sample/ReaLTaiizor.Login/ReaLTaiizor.Login/Login1.Designer.cs:312— `parrotFormHandle2` (line 312) is a component the designer creates for `Login1` with no container: it is not built with `new T(components)`, not added to `components`, and not added to a parent control's `Controls` or to a component's own child collection — the only routes by which the framework would release it for you. And the type's disposal never names it: searched `Dispose` (Login1.Designer.cs line 14), plus every method those call by name. So `Login1` owns it and never releases it; whatever it holds (a dialog's window handle, a file-system watch, a process handle) stays until finalization, once per instance. Release it in `Dispose(bool)` (`parrotFormHandle2?.Dispose();` under `disposing`) — that method may be edited, or moved to the hand-written partial; only `InitializeComponent` belongs to the designer — or register it with the container so `components.Dispose()` releases it.
Owned disposable field is never released sample/ReaLTaiizor.Player/ReaLTaiizor.Player/Player.designer.cs:491— `parrotControlEllipse1` (line 491) is a component the designer creates for `Player` with no container: it is not built with `new T(components)`, not added to `components`, and not added to a parent control's `Controls` or to a component's own child collection — the only routes by which the framework would release it for you. And the type's disposal never names it: searched `Dispose` (Player.designer.cs line 16), plus every method those call by name. So `Player` owns it and never releases it; whatever it holds (a dialog's window handle, a file-system watch, a process handle) stays until finalization, once per instance. Release it in `Dispose(bool)` (`parrotControlEllipse1?.Dispose();` under `disposing`) — that method may be edited, or moved to the hand-written partial; only `InitializeComponent` belongs to the designer — or register it with the container so `components.Dispose()` releases it.
Owned disposable field is never released sample/ReaLTaiizor.Player/ReaLTaiizor.Player/Player.designer.cs:492— `parrotControlEllipse2` (line 492) is a component the designer creates for `Player` with no container: it is not built with `new T(components)`, not added to `components`, and not added to a parent control's `Controls` or to a component's own child collection — the only routes by which the framework would release it for you. And the type's disposal never names it: searched `Dispose` (Player.designer.cs line 16), plus every method those call by name. So `Player` owns it and never releases it; whatever it holds (a dialog's window handle, a file-system watch, a process handle) stays until finalization, once per instance. Release it in `Dispose(bool)` (`parrotControlEllipse2?.Dispose();` under `disposing`) — that method may be edited, or moved to the hand-written partial; only `InitializeComponent` belongs to the designer — or register it with the container so `components.Dispose()` releases it.
Owned disposable field is never released sample/ReaLTaiizor.Player/ReaLTaiizor.Player/Player.designer.cs:493— `parrotControlEllipse3` (line 493) is a component the designer creates for `Player` with no container: it is not built with `new T(components)`, not added to `components`, and not added to a parent control's `Controls` or to a component's own child collection — the only routes by which the framework would release it for you. And the type's disposal never names it: searched `Dispose` (Player.designer.cs line 16), plus every method those call by name. So `Player` owns it and never releases it; whatever it holds (a dialog's window handle, a file-system watch, a process handle) stays until finalization, once per instance. Release it in `Dispose(bool)` (`parrotControlEllipse3?.Dispose();` under `disposing`) — that method may be edited, or moved to the hand-written partial; only `InitializeComponent` belongs to the designer — or register it with the container so `components.Dispose()` releases it.
Owned disposable field is never released sample/ReaLTaiizor.Rufus/ReaLTaiizor.Rufus/Rufus.Designer.cs:766— `metroStyleManager1` (line 766) is a component the designer creates for `Rufus` with no container: it is not built with `new T(components)`, not added to `components`, and not added to a parent control's `Controls` or to a component's own child collection — the only routes by which the framework would release it for you. And the type's disposal never names it: searched `Dispose` (Rufus.Designer.cs line 15), plus every method those call by name. So `Rufus` owns it and never releases it; whatever it holds (a dialog's window handle, a file-system watch, a process handle) stays until finalization, once per instance. Release it in `Dispose(bool)` (`metroStyleManager1?.Dispose();` under `disposing`) — that method may be edited, or moved to the hand-written partial; only `InitializeComponent` belongs to the designer — or register it with the container so `components.Dispose()` releases it.
Owned disposable field is never released sample/ReaLTaiizor.Splash/ReaLTaiizor.Splash/Splash.Designer.cs:247— `parrotObjectEllipse1` (line 247) is a component the designer creates for `Splash` with no container: it is not built with `new T(components)`, not added to `components`, and not added to a parent control's `Controls` or to a component's own child collection — the only routes by which the framework would release it for you. And the type's disposal never names it: searched `Dispose` (Splash.Designer.cs line 14), plus every method those call by name. So `Splash` owns it and never releases it; whatever it holds (a dialog's window handle, a file-system watch, a process handle) stays until finalization, once per instance. Release it in `Dispose(bool)` (`parrotObjectEllipse1?.Dispose();` under `disposing`) — that method may be edited, or moved to the hand-written partial; only `InitializeComponent` belongs to the designer — or register it with the container so `components.Dispose()` releases it.
Owned disposable field is never released sample/ReaLTaiizor.Splash/ReaLTaiizor.Splash/Splash.Designer.cs:259— `parrotFormHandle1` (line 259) is a component the designer creates for `Splash` with no container: it is not built with `new T(components)`, not added to `components`, and not added to a parent control's `Controls` or to a component's own child collection — the only routes by which the framework would release it for you. And the type's disposal never names it: searched `Dispose` (Splash.Designer.cs line 14), plus every method those call by name. So `Splash` owns it and never releases it; whatever it holds (a dialog's window handle, a file-system watch, a process handle) stays until finalization, once per instance. Release it in `Dispose(bool)` (`parrotFormHandle1?.Dispose();` under `disposing`) — that method may be edited, or moved to the hand-written partial; only `InitializeComponent` belongs to the designer — or register it with the container so `components.Dispose()` releases it.
Owned disposable field is never released sample/ReaLTaiizor.Store/ReaLTaiizor.Store/Store.Designer.cs:2586— `parrotControlEllipse1` (line 2586) is a component the designer creates for `Store` with no container: it is not built with `new T(components)`, not added to `components`, and not added to a parent control's `Controls` or to a component's own child collection — the only routes by which the framework would release it for you. And the type's disposal never names it: searched `Dispose` (Store.Designer.cs line 14), plus every method those call by name. So `Store` owns it and never releases it; whatever it holds (a dialog's window handle, a file-system watch, a process handle) stays until finalization, once per instance. Release it in `Dispose(bool)` (`parrotControlEllipse1?.Dispose();` under `disposing`) — that method may be edited, or moved to the hand-written partial; only `InitializeComponent` belongs to the designer — or register it with the container so `components.Dispose()` releases it.
Owned disposable field is never released sample/ReaLTaiizor.Store/ReaLTaiizor.Store/Store.Designer.cs:2590— `parrotControlEllipse2` (line 2590) is a component the designer creates for `Store` with no container: it is not built with `new T(components)`, not added to `components`, and not added to a parent control's `Controls` or to a component's own child collection — the only routes by which the framework would release it for you. And the type's disposal never names it: searched `Dispose` (Store.Designer.cs line 14), plus every method those call by name. So `Store` owns it and never releases it; whatever it holds (a dialog's window handle, a file-system watch, a process handle) stays until finalization, once per instance. Release it in `Dispose(bool)` (`parrotControlEllipse2?.Dispose();` under `disposing`) — that method may be edited, or moved to the hand-written partial; only `InitializeComponent` belongs to the designer — or register it with the container so `components.Dispose()` releases it.
Owned disposable field is never released sample/ReaLTaiizor.Store/ReaLTaiizor.Store/Store.Designer.cs:2602— `parrotControlEllipse3` (line 2602) is a component the designer creates for `Store` with no container: it is not built with `new T(components)`, not added to `components`, and not added to a parent control's `Controls` or to a component's own child collection — the only routes by which the framework would release it for you. And the type's disposal never names it: searched `Dispose` (Store.Designer.cs line 14), plus every method those call by name. So `Store` owns it and never releases it; whatever it holds (a dialog's window handle, a file-system watch, a process handle) stays until finalization, once per instance. Release it in `Dispose(bool)` (`parrotControlEllipse3?.Dispose();` under `disposing`) — that method may be edited, or moved to the hand-written partial; only `InitializeComponent` belongs to the designer — or register it with the container so `components.Dispose()` releases it.
+ 3 more in this group — see findings.md.
SC1 · Supply-chain hygiene· NuGet dependencies are not locked · ×26
NuGet dependencies are not locked demo/ReaLTaiizor.UI/ReaLTaiizor.UI/ReaLTaiizor.UI.csproj:87— demo/ReaLTaiizor.UI/ReaLTaiizor.UI/ReaLTaiizor.UI.csproj declares NuGet packages that no committed packages.lock.json resolves and no central package management pins — restores aren't reproducible or pinned (SSDF PW.4.4). Enable <RestorePackagesWithLockFile>true</RestorePackagesWithLockFile> (commit the lockfile) or adopt Directory.Packages.props. Advisory — never scored.
NuGet dependencies are not locked demo/ReaLTaiizor.UX/ReaLTaiizor.UX/ReaLTaiizor.UX.csproj:20— demo/ReaLTaiizor.UX/ReaLTaiizor.UX/ReaLTaiizor.UX.csproj declares NuGet packages that no committed packages.lock.json resolves and no central package management pins — restores aren't reproducible or pinned (SSDF PW.4.4). Enable <RestorePackagesWithLockFile>true</RestorePackagesWithLockFile> (commit the lockfile) or adopt Directory.Packages.props. Advisory — never scored.
NuGet dependencies are not locked ready/ReaLTaiizor.AppLocker/ReaLTaiizor.AppLocker/ReaLTaiizor.AppLocker.csproj:20— ready/ReaLTaiizor.AppLocker/ReaLTaiizor.AppLocker/ReaLTaiizor.AppLocker.csproj declares NuGet packages that no committed packages.lock.json resolves and no central package management pins — restores aren't reproducible or pinned (SSDF PW.4.4). Enable <RestorePackagesWithLockFile>true</RestorePackagesWithLockFile> (commit the lockfile) or adopt Directory.Packages.props. Advisory — never scored.
NuGet dependencies are not locked ready/ReaLTaiizor.Hashing/ReaLTaiizor.Hashing/ReaLTaiizor.Hashing.csproj:20— ready/ReaLTaiizor.Hashing/ReaLTaiizor.Hashing/ReaLTaiizor.Hashing.csproj declares NuGet packages that no committed packages.lock.json resolves and no central package management pins — restores aren't reproducible or pinned (SSDF PW.4.4). Enable <RestorePackagesWithLockFile>true</RestorePackagesWithLockFile> (commit the lockfile) or adopt Directory.Packages.props. Advisory — never scored.
NuGet dependencies are not locked ready/ReaLTaiizor.MAChanger/ReaLTaiizor.MAChanger/ReaLTaiizor.MAChanger.csproj:20— ready/ReaLTaiizor.MAChanger/ReaLTaiizor.MAChanger/ReaLTaiizor.MAChanger.csproj declares NuGet packages that no committed packages.lock.json resolves and no central package management pins — restores aren't reproducible or pinned (SSDF PW.4.4). Enable <RestorePackagesWithLockFile>true</RestorePackagesWithLockFile> (commit the lockfile) or adopt Directory.Packages.props. Advisory — never scored.
NuGet dependencies are not locked ready/ReaLTaiizor.Nerator/ReaLTaiizor.Nerator/ReaLTaiizor.Nerator.csproj:47— ready/ReaLTaiizor.Nerator/ReaLTaiizor.Nerator/ReaLTaiizor.Nerator.csproj declares NuGet packages that no committed packages.lock.json resolves and no central package management pins — restores aren't reproducible or pinned (SSDF PW.4.4). Enable <RestorePackagesWithLockFile>true</RestorePackagesWithLockFile> (commit the lockfile) or adopt Directory.Packages.props. Advisory — never scored.
NuGet dependencies are not locked ready/ReaLTaiizor.Portscan/ReaLTaiizor.Portscan/ReaLTaiizor.Portscan.csproj:20— ready/ReaLTaiizor.Portscan/ReaLTaiizor.Portscan/ReaLTaiizor.Portscan.csproj declares NuGet packages that no committed packages.lock.json resolves and no central package management pins — restores aren't reproducible or pinned (SSDF PW.4.4). Enable <RestorePackagesWithLockFile>true</RestorePackagesWithLockFile> (commit the lockfile) or adopt Directory.Packages.props. Advisory — never scored.
NuGet dependencies are not locked ready/ReaLTaiizor.Stopwatch/ReaLTaiizor.Stopwatch/ReaLTaiizor.Stopwatch.csproj:20— ready/ReaLTaiizor.Stopwatch/ReaLTaiizor.Stopwatch/ReaLTaiizor.Stopwatch.csproj declares NuGet packages that no committed packages.lock.json resolves and no central package management pins — restores aren't reproducible or pinned (SSDF PW.4.4). Enable <RestorePackagesWithLockFile>true</RestorePackagesWithLockFile> (commit the lockfile) or adopt Directory.Packages.props. Advisory — never scored.
NuGet dependencies are not locked ready/ReaLTaiizor.Translate/ReaLTaiizor.Translate/ReaLTaiizor.Translate.csproj:20— ready/ReaLTaiizor.Translate/ReaLTaiizor.Translate/ReaLTaiizor.Translate.csproj declares NuGet packages that no committed packages.lock.json resolves and no central package management pins — restores aren't reproducible or pinned (SSDF PW.4.4). Enable <RestorePackagesWithLockFile>true</RestorePackagesWithLockFile> (commit the lockfile) or adopt Directory.Packages.props. Advisory — never scored.
NuGet dependencies are not locked sample/ReaLTaiizor.Defender/ReaLTaiizor.Defender/ReaLTaiizor.Defender.csproj:20— sample/ReaLTaiizor.Defender/ReaLTaiizor.Defender/ReaLTaiizor.Defender.csproj declares NuGet packages that no committed packages.lock.json resolves and no central package management pins — restores aren't reproducible or pinned (SSDF PW.4.4). Enable <RestorePackagesWithLockFile>true</RestorePackagesWithLockFile> (commit the lockfile) or adopt Directory.Packages.props. Advisory — never scored.
NuGet dependencies are not locked sample/ReaLTaiizor.GenshinImpact/ReaLTaiizor.GenshinImpact/ReaLTaiizor.GenshinImpact.csproj:20— sample/ReaLTaiizor.GenshinImpact/ReaLTaiizor.GenshinImpact/ReaLTaiizor.GenshinImpact.csproj declares NuGet packages that no committed packages.lock.json resolves and no central package management pins — restores aren't reproducible or pinned (SSDF PW.4.4). Enable <RestorePackagesWithLockFile>true</RestorePackagesWithLockFile> (commit the lockfile) or adopt Directory.Packages.props. Advisory — never scored.
NuGet dependencies are not locked sample/ReaLTaiizor.Instagram/ReaLTaiizor.Instagram/ReaLTaiizor.Instagram.csproj:20— sample/ReaLTaiizor.Instagram/ReaLTaiizor.Instagram/ReaLTaiizor.Instagram.csproj declares NuGet packages that no committed packages.lock.json resolves and no central package management pins — restores aren't reproducible or pinned (SSDF PW.4.4). Enable <RestorePackagesWithLockFile>true</RestorePackagesWithLockFile> (commit the lockfile) or adopt Directory.Packages.props. Advisory — never scored.
NuGet dependencies are not locked sample/ReaLTaiizor.Kaspersky/ReaLTaiizor.Kaspersky/ReaLTaiizor.Kaspersky.csproj:20— sample/ReaLTaiizor.Kaspersky/ReaLTaiizor.Kaspersky/ReaLTaiizor.Kaspersky.csproj declares NuGet packages that no committed packages.lock.json resolves and no central package management pins — restores aren't reproducible or pinned (SSDF PW.4.4). Enable <RestorePackagesWithLockFile>true</RestorePackagesWithLockFile> (commit the lockfile) or adopt Directory.Packages.props. Advisory — never scored.
NuGet dependencies are not locked sample/ReaLTaiizor.Login/ReaLTaiizor.Login/ReaLTaiizor.Login.csproj:20— sample/ReaLTaiizor.Login/ReaLTaiizor.Login/ReaLTaiizor.Login.csproj declares NuGet packages that no committed packages.lock.json resolves and no central package management pins — restores aren't reproducible or pinned (SSDF PW.4.4). Enable <RestorePackagesWithLockFile>true</RestorePackagesWithLockFile> (commit the lockfile) or adopt Directory.Packages.props. Advisory — never scored.
NuGet dependencies are not locked sample/ReaLTaiizor.Payment/ReaLTaiizor.Payment/ReaLTaiizor.Payment.csproj:20— sample/ReaLTaiizor.Payment/ReaLTaiizor.Payment/ReaLTaiizor.Payment.csproj declares NuGet packages that no committed packages.lock.json resolves and no central package management pins — restores aren't reproducible or pinned (SSDF PW.4.4). Enable <RestorePackagesWithLockFile>true</RestorePackagesWithLockFile> (commit the lockfile) or adopt Directory.Packages.props. Advisory — never scored.
NuGet dependencies are not locked sample/ReaLTaiizor.Player/ReaLTaiizor.Player/ReaLTaiizor.Player.csproj:20— sample/ReaLTaiizor.Player/ReaLTaiizor.Player/ReaLTaiizor.Player.csproj declares NuGet packages that no committed packages.lock.json resolves and no central package management pins — restores aren't reproducible or pinned (SSDF PW.4.4). Enable <RestorePackagesWithLockFile>true</RestorePackagesWithLockFile> (commit the lockfile) or adopt Directory.Packages.props. Advisory — never scored.
NuGet dependencies are not locked sample/ReaLTaiizor.Rufus/ReaLTaiizor.Rufus/ReaLTaiizor.Rufus.csproj:20— sample/ReaLTaiizor.Rufus/ReaLTaiizor.Rufus/ReaLTaiizor.Rufus.csproj declares NuGet packages that no committed packages.lock.json resolves and no central package management pins — restores aren't reproducible or pinned (SSDF PW.4.4). Enable <RestorePackagesWithLockFile>true</RestorePackagesWithLockFile> (commit the lockfile) or adopt Directory.Packages.props. Advisory — never scored.
NuGet dependencies are not locked sample/ReaLTaiizor.Splash/ReaLTaiizor.Splash/ReaLTaiizor.Splash.csproj:26— sample/ReaLTaiizor.Splash/ReaLTaiizor.Splash/ReaLTaiizor.Splash.csproj declares NuGet packages that no committed packages.lock.json resolves and no central package management pins — restores aren't reproducible or pinned (SSDF PW.4.4). Enable <RestorePackagesWithLockFile>true</RestorePackagesWithLockFile> (commit the lockfile) or adopt Directory.Packages.props. Advisory — never scored.
NuGet dependencies are not locked sample/ReaLTaiizor.Store/ReaLTaiizor.Store/ReaLTaiizor.Store.csproj:26— sample/ReaLTaiizor.Store/ReaLTaiizor.Store/ReaLTaiizor.Store.csproj declares NuGet packages that no committed packages.lock.json resolves and no central package management pins — restores aren't reproducible or pinned (SSDF PW.4.4). Enable <RestorePackagesWithLockFile>true</RestorePackagesWithLockFile> (commit the lockfile) or adopt Directory.Packages.props. Advisory — never scored.
NuGet dependencies are not locked sample/ReaLTaiizor.XAMPP/ReaLTaiizor.XAMPP/ReaLTaiizor.XAMPP.csproj:20— sample/ReaLTaiizor.XAMPP/ReaLTaiizor.XAMPP/ReaLTaiizor.XAMPP.csproj declares NuGet packages that no committed packages.lock.json resolves and no central package management pins — restores aren't reproducible or pinned (SSDF PW.4.4). Enable <RestorePackagesWithLockFile>true</RestorePackagesWithLockFile> (commit the lockfile) or adopt Directory.Packages.props. Advisory — never scored.
NuGet dependencies are not locked src/ReaLTaiizor/ReaLTaiizor.csproj:66— src/ReaLTaiizor/ReaLTaiizor.csproj declares NuGet packages that no committed packages.lock.json resolves and no central package management pins — restores aren't reproducible or pinned (SSDF PW.4.4). Enable <RestorePackagesWithLockFile>true</RestorePackagesWithLockFile> (commit the lockfile) or adopt Directory.Packages.props. Advisory — never scored.
NuGet dependencies are not locked src/ReaLTaiizor_CR/ReaLTaiizor_CR.csproj:34— src/ReaLTaiizor_CR/ReaLTaiizor_CR.csproj declares NuGet packages that no committed packages.lock.json resolves and no central package management pins — restores aren't reproducible or pinned (SSDF PW.4.4). Enable <RestorePackagesWithLockFile>true</RestorePackagesWithLockFile> (commit the lockfile) or adopt Directory.Packages.props. Advisory — never scored.
NuGet dependencies are not locked tutorial/C#/#001 install-from-nuget/install-from-nuget/install-from-nuget.csproj:11— tutorial/C#/#001 install-from-nuget/install-from-nuget/install-from-nuget.csproj declares NuGet packages that no committed packages.lock.json resolves and no central package management pins — restores aren't reproducible or pinned (SSDF PW.4.4). Enable <RestorePackagesWithLockFile>true</RestorePackagesWithLockFile> (commit the lockfile) or adopt Directory.Packages.props. Advisory — never scored.
NuGet dependencies are not locked tutorial/C#/#002 form-summon/form-summon/form-summon.csproj:11— tutorial/C#/#002 form-summon/form-summon/form-summon.csproj declares NuGet packages that no committed packages.lock.json resolves and no central package management pins — restores aren't reproducible or pinned (SSDF PW.4.4). Enable <RestorePackagesWithLockFile>true</RestorePackagesWithLockFile> (commit the lockfile) or adopt Directory.Packages.props. Advisory — never scored.
NuGet dependencies are not locked tutorial/VB/#001 install-from-nuget/install-from-nuget/install-from-nuget.vbproj:19— tutorial/VB/#001 install-from-nuget/install-from-nuget/install-from-nuget.vbproj declares NuGet packages that no committed packages.lock.json resolves and no central package management pins — restores aren't reproducible or pinned (SSDF PW.4.4). Enable <RestorePackagesWithLockFile>true</RestorePackagesWithLockFile> (commit the lockfile) or adopt Directory.Packages.props. Advisory — never scored.
Duplicated block (6 lines × 2) src/ReaLTaiizor/Controls/Ellipse/MetroEllipse.cs:283— src/ReaLTaiizor/Controls/Ellipse/MetroEllipse.cs:283-288 | src/ReaLTaiizor/Controls/Tile/MetroTile.cs:302-307 — before extracting anything, compare `src/ReaLTaiizor/Controls/Ellipse/MetroEllipse.cs` and `src/ReaLTaiizor/Controls/Tile/MetroTile.cs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 66 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/ReaLTaiizor/Controls/Ellipse/MetroEllipse.cs:283` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (6 lines × 2) src/ReaLTaiizor/Controls/ComboBox/MetroComboBox.cs:303— src/ReaLTaiizor/Controls/ComboBox/MetroComboBox.cs:303-308 | src/ReaLTaiizor/Controls/ComboBox/MetroComboBox.cs:317-322 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (6 lines × 2) src/ReaLTaiizor/Controls/ControlBox/ThunderControlBox.cs:232— src/ReaLTaiizor/Controls/ControlBox/ThunderControlBox.cs:232-237 | src/ReaLTaiizor/Controls/ControlBox/ThunderControlBox.cs:265-270 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (6 lines × 2) src/ReaLTaiizor/Controls/Switch/MetroSwitch.cs:133— src/ReaLTaiizor/Controls/Switch/MetroSwitch.cs:133-138 | src/ReaLTaiizor/Controls/Switch/MetroSwitch.cs:147-152 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (6 lines × 2) src/ReaLTaiizor/Controls/Button/MetroDefaultButton.cs:127— src/ReaLTaiizor/Controls/Button/MetroDefaultButton.cs:127-132 | src/ReaLTaiizor/Controls/Ellipse/MetroEllipse.cs:130-135 — before extracting anything, compare `src/ReaLTaiizor/Controls/Button/MetroDefaultButton.cs` and `src/ReaLTaiizor/Controls/Ellipse/MetroEllipse.cs` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 122 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/ReaLTaiizor/Controls/Button/MetroDefaultButton.cs:127` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (6 lines × 2) src/ReaLTaiizor/Controls/Numeric/SkyNumeric.cs:246— src/ReaLTaiizor/Controls/Numeric/SkyNumeric.cs:246-251 | src/ReaLTaiizor/Controls/TextBox/SkyTextBox.cs:187-192 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (6 lines × 2) src/ReaLTaiizor/ReaLTaiizor.cs:31— src/ReaLTaiizor/ReaLTaiizor.cs:31-36 | src/ReaLTaiizor/ReaLTaiizor.cs:63-68 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (6 lines × 2) ready/ReaLTaiizor.Nerator/ReaLTaiizor.Nerator/CS/History.cs:33— ready/ReaLTaiizor.Nerator/ReaLTaiizor.Nerator/CS/History.cs:33-38 | ready/ReaLTaiizor.Nerator/ReaLTaiizor.Nerator/CS/History.cs:51-56 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `ready/ReaLTaiizor.Nerator/ReaLTaiizor.Nerator/CS/History.cs:33` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (6 lines × 2) REDACTED:127— REDACTED:127-132 | REDACTED:143-148 — before extracting anything, compare `REDACTED` and `REDACTED` as WHOLE FILES: 86% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 4 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (6 lines × 2) src/ReaLTaiizor/Controls/ListView/PoisonListView.cs:594— src/ReaLTaiizor/Controls/ListView/PoisonListView.cs:594-599 | src/ReaLTaiizor/Controls/ListView/PoisonListView.cs:687-692 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/ReaLTaiizor/Controls/ListView/PoisonListView.cs:594` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note first that the copies are not typed on the same thing: the declarations holding them bind `e` to `DrawListViewSubItemEventArgs` in one and `DrawListViewItemEventArgs` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
Duplicated block (6 lines × 2) src/ReaLTaiizor/Controls/Button/Button.cs:305— src/ReaLTaiizor/Controls/Button/Button.cs:305-311 | src/ReaLTaiizor/Controls/CheckBox/CheckBox.cs:95-100 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `src/ReaLTaiizor/Controls/Button/Button.cs:305` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (6 lines × 2) src/ReaLTaiizor/Controls/Button/HopeRoundButton.cs:102— src/ReaLTaiizor/Controls/Button/HopeRoundButton.cs:102-107 | src/ReaLTaiizor/Controls/Switch/HopeSwitch.cs:57-62 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (6 lines × 2) src/ReaLTaiizor/Controls/CheckBox/PoisonCheckBox.cs:151— src/ReaLTaiizor/Controls/CheckBox/PoisonCheckBox.cs:151-156 | src/ReaLTaiizor/Controls/RadioButton/PoisonRadioButton.cs:139-144 — before extracting anything, compare `src/ReaLTaiizor/Controls/CheckBox/PoisonCheckBox.cs` and `src/ReaLTaiizor/Controls/RadioButton/PoisonRadioButton.cs` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 167 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (6 lines × 2) src/ReaLTaiizor/Controls/Dialog/MaterialDialog.cs:161— src/ReaLTaiizor/Controls/Dialog/MaterialDialog.cs:161-166 | src/ReaLTaiizor/Controls/Dialog/MaterialDialog.cs:272-278 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/ReaLTaiizor/Controls/Dialog/MaterialDialog.cs:161` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (6 lines × 2) src/ReaLTaiizor/Controls/TrackBar/DungeonTrackBar.cs:205— src/ReaLTaiizor/Controls/TrackBar/DungeonTrackBar.cs:205-210 | src/ReaLTaiizor/Controls/TrackBar/TrackBar.cs:170-175 — before extracting anything, compare `src/ReaLTaiizor/Controls/TrackBar/DungeonTrackBar.cs` and `src/ReaLTaiizor/Controls/TrackBar/TrackBar.cs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 67 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/ReaLTaiizor/Controls/TrackBar/DungeonTrackBar.cs:205` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (6 lines × 2) src/ReaLTaiizor/Forms/Container/DungeonForm.cs:483— src/ReaLTaiizor/Forms/Container/DungeonForm.cs:483-488 | src/ReaLTaiizor/Forms/Container/ThemeForm.cs:491-496 — before extracting anything, compare `src/ReaLTaiizor/Forms/Container/DungeonForm.cs` and `src/ReaLTaiizor/Forms/Container/ThemeForm.cs` as WHOLE FILES: this scan already matched 17 separate duplicated blocks between them, totalling at least 286 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (6 lines × 2) src/ReaLTaiizor/Forms/Form/MaterialFlexibleForm.cs:836— src/ReaLTaiizor/Forms/Form/MaterialFlexibleForm.cs:836-841 | src/ReaLTaiizor/Forms/Form/MaterialFlexibleForm.cs:879-884 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (6 lines × 2) src/ReaLTaiizor/Controls/TabPage/TabPage.cs:260— src/ReaLTaiizor/Controls/TabPage/TabPage.cs:260-265 | src/ReaLTaiizor/Controls/TabPage/TabPage.cs:282-287 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (6 lines × 2) src/ReaLTaiizor/Controls/Button/HopeRoundButton.cs:148— src/ReaLTaiizor/Controls/Button/HopeRoundButton.cs:148-153 | src/ReaLTaiizor/Controls/Button/HopeSimpleButton.cs:154-159 — before extracting anything, compare `src/ReaLTaiizor/Controls/Button/HopeRoundButton.cs` and `src/ReaLTaiizor/Controls/Button/HopeSimpleButton.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 40 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (6 lines × 2) src/ReaLTaiizor/Controls/CheckBox/CyberCheckBox.cs:656— src/ReaLTaiizor/Controls/CheckBox/CyberCheckBox.cs:656-661 | src/ReaLTaiizor/Controls/RadioButton/CyberRadioButton.cs:710-715 — before extracting anything, compare `src/ReaLTaiizor/Controls/CheckBox/CyberCheckBox.cs` and `src/ReaLTaiizor/Controls/RadioButton/CyberRadioButton.cs` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 249 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (6 lines × 2) src/ReaLTaiizor/Controls/Panel/MaterialExpansionPanel.cs:306— src/ReaLTaiizor/Controls/Panel/MaterialExpansionPanel.cs:306-311 | src/ReaLTaiizor/Controls/TabSelector/MaterialTabSelector.cs:255-260 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (6 lines × 2) src/ReaLTaiizor/Controls/Separator/SpaceSeparatorHorizontal.cs:17— src/ReaLTaiizor/Controls/Separator/SpaceSeparatorHorizontal.cs:17-22 | src/ReaLTaiizor/Controls/Separator/SpaceSeparatorVertical.cs:17-22 — before extracting anything, compare `src/ReaLTaiizor/Controls/Separator/SpaceSeparatorHorizontal.cs` and `src/ReaLTaiizor/Controls/Separator/SpaceSeparatorVertical.cs` as WHOLE FILES: 84% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 3 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (6 lines × 2) src/ReaLTaiizor/Controls/Separator/SpaceSeparatorHorizontal.cs:30— src/ReaLTaiizor/Controls/Separator/SpaceSeparatorHorizontal.cs:30-35 | src/ReaLTaiizor/Controls/Separator/SpaceSeparatorVertical.cs:30-35 — before extracting anything, compare `src/ReaLTaiizor/Controls/Separator/SpaceSeparatorHorizontal.cs` and `src/ReaLTaiizor/Controls/Separator/SpaceSeparatorVertical.cs` as WHOLE FILES: 84% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 3 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (6 lines × 2) src/ReaLTaiizor/Controls/Separator/SpaceSeparatorHorizontal.cs:38— src/ReaLTaiizor/Controls/Separator/SpaceSeparatorHorizontal.cs:38-43 | src/ReaLTaiizor/Controls/Separator/SpaceSeparatorVertical.cs:38-43 — before extracting anything, compare `src/ReaLTaiizor/Controls/Separator/SpaceSeparatorHorizontal.cs` and `src/ReaLTaiizor/Controls/Separator/SpaceSeparatorVertical.cs` as WHOLE FILES: 84% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 3 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (6 lines × 2) src/ReaLTaiizor/Controls/Switch/HopeSwitch.cs:71— src/ReaLTaiizor/Controls/Switch/HopeSwitch.cs:71-76 | src/ReaLTaiizor/Controls/Toggle/HopeToggle.cs:75-80 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (7 lines × 2) src/ReaLTaiizor/Controls/CheckBox/AloneCheckBox.cs:151— src/ReaLTaiizor/Controls/CheckBox/AloneCheckBox.cs:151-157 | src/ReaLTaiizor/Controls/RadioButton/AloneRadioButton.cs:144-150 — before extracting anything, compare `src/ReaLTaiizor/Controls/CheckBox/AloneCheckBox.cs` and `src/ReaLTaiizor/Controls/RadioButton/AloneRadioButton.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 36 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/ReaLTaiizor/Controls/CheckBox/AloneCheckBox.cs:151` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (7 lines × 2) src/ReaLTaiizor/Controls/Button/MetroButton.cs:216— src/ReaLTaiizor/Controls/Button/MetroButton.cs:216-222 | src/ReaLTaiizor/Controls/Tile/MetroTile.cs:222-228 — before extracting anything, compare `src/ReaLTaiizor/Controls/Button/MetroButton.cs` and `src/ReaLTaiizor/Controls/Tile/MetroTile.cs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 50 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (7 lines × 2) src/ReaLTaiizor/Controls/CheckBox/MaterialCheckBox.cs:247— src/ReaLTaiizor/Controls/CheckBox/MaterialCheckBox.cs:247-253 | src/ReaLTaiizor/Controls/RadioButton/MaterialRadioButton.cs:221-227 — before extracting anything, compare `src/ReaLTaiizor/Controls/CheckBox/MaterialCheckBox.cs` and `src/ReaLTaiizor/Controls/RadioButton/MaterialRadioButton.cs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 99 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/ReaLTaiizor/Controls/CheckBox/MaterialCheckBox.cs:247` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (7 lines × 2) src/ReaLTaiizor/Controls/Graph/ParrotBarGraph.cs:261— src/ReaLTaiizor/Controls/Graph/ParrotBarGraph.cs:261-267 | src/ReaLTaiizor/Controls/Graph/ParrotBarGraph.cs:500-506 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/ReaLTaiizor/Controls/Graph/ParrotBarGraph.cs:261` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (7 lines × 2) src/ReaLTaiizor/Controls/Graph/ParrotBarGraph.cs:314— src/ReaLTaiizor/Controls/Graph/ParrotBarGraph.cs:314-320 | src/ReaLTaiizor/Controls/Graph/ParrotBarGraph.cs:535-541 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/ReaLTaiizor/Controls/Graph/ParrotBarGraph.cs:314` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (7 lines × 2) src/ReaLTaiizor/Controls/Stick/ParrotJoyStick.cs:352— src/ReaLTaiizor/Controls/Stick/ParrotJoyStick.cs:352-358 | src/ReaLTaiizor/Controls/Stick/ParrotJoyStick.cs:385-391 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/ReaLTaiizor/Controls/Stick/ParrotJoyStick.cs:352` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (7 lines × 2) src/ReaLTaiizor/Controls/ControlBox/ControlBox.cs:240— src/ReaLTaiizor/Controls/ControlBox/ControlBox.cs:240-246 | src/ReaLTaiizor/Controls/ControlBox/ControlBox.cs:298-304 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/ReaLTaiizor/Controls/ControlBox/ControlBox.cs:240` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `src/ReaLTaiizor/Controls/ControlBox/ControlBox.cs:295` calls `FillRectangle`, `SolidBrush`, `Rectangle` and `src/ReaLTaiizor/Controls/ControlBox/ControlBox.cs:237` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (7 lines × 2) src/ReaLTaiizor/Controls/RichTextBox/MaterialRichTextBox.cs:71— src/ReaLTaiizor/Controls/RichTextBox/MaterialRichTextBox.cs:71-77 | src/ReaLTaiizor/Controls/TextBox/MaterialMultiLineTextBox.cs:102-108 — before extracting anything, compare `src/ReaLTaiizor/Controls/RichTextBox/MaterialRichTextBox.cs` and `src/ReaLTaiizor/Controls/TextBox/MaterialMultiLineTextBox.cs` as WHOLE FILES: 87% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/ReaLTaiizor/Controls/RichTextBox/MaterialRichTextBox.cs:71` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (7 lines × 2) src/ReaLTaiizor/Forms/Form/MaterialFlexibleForm.cs:582— src/ReaLTaiizor/Forms/Form/MaterialFlexibleForm.cs:582-588 | src/ReaLTaiizor/Forms/Form/MaterialFlexibleForm.cs:596-602 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (7 lines × 2) REDACTED:136— REDACTED:136-142 | REDACTED:152-158 — before extracting anything, compare `REDACTED` and `REDACTED` as WHOLE FILES: 86% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 4 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (7 lines × 2) src/ReaLTaiizor/Controls/Bubble/ChatBubbleLeft.cs:89— src/ReaLTaiizor/Controls/Bubble/ChatBubbleLeft.cs:89-95 | src/ReaLTaiizor/Controls/Bubble/ChatBubbleRight.cs:99-105 — before extracting anything, compare `src/ReaLTaiizor/Controls/Bubble/ChatBubbleLeft.cs` and `src/ReaLTaiizor/Controls/Bubble/ChatBubbleRight.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 65 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `src/ReaLTaiizor/Controls/Bubble/ChatBubbleRight.cs:109` calls `OnResize` and `src/ReaLTaiizor/Controls/Bubble/ChatBubbleLeft.cs:99` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (7 lines × 2) src/ReaLTaiizor/Controls/Button/ForeverButton.cs:63— src/ReaLTaiizor/Controls/Button/ForeverButton.cs:63-69 | src/ReaLTaiizor/Controls/Button/ForeverButtonSticky.cs:101-107 — before extracting anything, compare `src/ReaLTaiizor/Controls/Button/ForeverButton.cs` and `src/ReaLTaiizor/Controls/Button/ForeverButtonSticky.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 94 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (7 lines × 2) src/ReaLTaiizor/Forms/Form/LostForm.cs:394— src/ReaLTaiizor/Forms/Form/LostForm.cs:394-400 | src/ReaLTaiizor/Forms/Form/LostForm.cs:403-409 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (7 lines × 2) src/ReaLTaiizor/Controls/Bubble/ChatBubbleRight.cs:115— src/ReaLTaiizor/Controls/Bubble/ChatBubbleRight.cs:115-122 | src/ReaLTaiizor/Controls/Button/ChatButtonRight.cs:229-235 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `src/ReaLTaiizor/Controls/Bubble/ChatBubbleRight.cs:115` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (7 lines × 2) src/ReaLTaiizor/Controls/CheckBox/DungeonCheckBox.cs:44— src/ReaLTaiizor/Controls/CheckBox/DungeonCheckBox.cs:44-50 | src/ReaLTaiizor/Controls/RadioButton/DungeonRadioButton.cs:39-45 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (7 lines × 2) src/ReaLTaiizor/Controls/ControlBox/NightControlBox.cs:200— src/ReaLTaiizor/Controls/ControlBox/NightControlBox.cs:200-206 | src/ReaLTaiizor/Forms/Container/NightForm.cs:101-107 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (7 lines × 2) src/ReaLTaiizor/Controls/Numeric/FoxNumeric.cs:125— src/ReaLTaiizor/Controls/Numeric/FoxNumeric.cs:125-131 | src/ReaLTaiizor/Controls/Numeric/FoxNumeric.cs:143-149 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (7 lines × 2) src/ReaLTaiizor/Controls/Picker/CyberColorPicker.cs:124— src/ReaLTaiizor/Controls/Picker/CyberColorPicker.cs:124-130 | src/ReaLTaiizor/Controls/Picker/CyberColorPicker.cs:136-142 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/ReaLTaiizor/Controls/Picker/CyberColorPicker.cs:124` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (7 lines × 2) src/ReaLTaiizor/Forms/Form/MaterialForm.cs:1329— src/ReaLTaiizor/Forms/Form/MaterialForm.cs:1329-1336 | src/ReaLTaiizor/Forms/Form/MaterialForm.cs:1342-1348 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/ReaLTaiizor/Forms/Form/MaterialForm.cs:1329` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (7 lines × 2) src/ReaLTaiizor/Native/DockContentDragFilter.cs:59— src/ReaLTaiizor/Native/DockContentDragFilter.cs:59-65 | src/ReaLTaiizor/Native/DockResizeFilter.cs:48-54 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (7 lines × 2) src/ReaLTaiizor/Controls/TabPage/HopeTabPage.cs:211— src/ReaLTaiizor/Controls/TabPage/HopeTabPage.cs:211-217 | src/ReaLTaiizor/Controls/TabPage/HopeTabPage.cs:218-224 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/ReaLTaiizor/Controls/TabPage/HopeTabPage.cs:211` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `src/ReaLTaiizor/Controls/TabPage/HopeTabPage.cs:220` calls `FillRectangle`, `GetTabRect` and `src/ReaLTaiizor/Controls/TabPage/HopeTabPage.cs:225` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (7 lines × 2) src/ReaLTaiizor/Animate/Poison/ExpandAnimation.cs:33— src/ReaLTaiizor/Animate/Poison/ExpandAnimation.cs:33-39 | src/ReaLTaiizor/Animate/Poison/MoveAnimation.cs:33-39 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (7 lines × 2) src/ReaLTaiizor/Controls/TextBox/MaterialMultiLineTextBox.cs:89— src/ReaLTaiizor/Controls/TextBox/MaterialMultiLineTextBox.cs:89-95 | src/ReaLTaiizor/Controls/TextBoxEdit/MaterialMultiLineTextBoxEdit.cs:1029-1035 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (7 lines × 2) src/ReaLTaiizor/Controls/TextBox/MaterialTextBox.cs:885— src/ReaLTaiizor/Controls/TextBox/MaterialTextBox.cs:885-891 | src/ReaLTaiizor/Controls/TextBoxEdit/MaterialTextBoxEdit.cs:1605-1611 — before extracting anything, compare `src/ReaLTaiizor/Controls/TextBox/MaterialTextBox.cs` and `src/ReaLTaiizor/Controls/TextBoxEdit/MaterialTextBoxEdit.cs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 174 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (7 lines × 2) src/ReaLTaiizor/Controls/TextBoxEdit/MaterialMultiLineTextBoxEdit.cs:815— src/ReaLTaiizor/Controls/TextBoxEdit/MaterialMultiLineTextBoxEdit.cs:815-821 | src/ReaLTaiizor/Controls/TextBoxEdit/MaterialTextBoxEdit.cs:969-975 — before extracting anything, compare `src/ReaLTaiizor/Controls/TextBoxEdit/MaterialMultiLineTextBoxEdit.cs` and `src/ReaLTaiizor/Controls/TextBoxEdit/MaterialTextBoxEdit.cs` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 171 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (10 lines × 2) src/ReaLTaiizor/Controls/Segment/ParrotSegment.cs:293— src/ReaLTaiizor/Controls/Segment/ParrotSegment.cs:293-302 | src/ReaLTaiizor/Controls/Segment/ParrotSegment.cs:323-332 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/ReaLTaiizor/Controls/Segment/ParrotSegment.cs:293` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (10 lines × 2) src/ReaLTaiizor/Controls/TextBoxEdit/MaterialTextBoxEdit.cs:1122— src/ReaLTaiizor/Controls/TextBoxEdit/MaterialTextBoxEdit.cs:1122-1131 | src/ReaLTaiizor/Controls/TextBoxEdit/MaterialTextBoxEdit.cs:1141-1150 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/ReaLTaiizor/Controls/TextBoxEdit/MaterialTextBoxEdit.cs:1122` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (10 lines × 2) src/ReaLTaiizor/Controls/TextBox/MaterialMaskedTextBox.cs:1164— src/ReaLTaiizor/Controls/TextBox/MaterialMaskedTextBox.cs:1164-1173 | src/ReaLTaiizor/Controls/TextBox/MaterialMaskedTextBox.cs:1182-1191 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/ReaLTaiizor/Controls/TextBox/MaterialMaskedTextBox.cs:1164` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (10 lines × 2) src/ReaLTaiizor/Controls/Button/ParrotButton.cs:415— src/ReaLTaiizor/Controls/Button/ParrotButton.cs:415-424 | src/ReaLTaiizor/Controls/Button/ParrotSuperButton.cs:338-347 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (10 lines × 2) src/ReaLTaiizor/Controls/Card/MaterialCard.cs:173— src/ReaLTaiizor/Controls/Card/MaterialCard.cs:173-182 | src/ReaLTaiizor/Controls/Panel/MaterialExpansionPanel.cs:544-553 — before extracting anything, compare `src/ReaLTaiizor/Controls/Card/MaterialCard.cs` and `src/ReaLTaiizor/Controls/Panel/MaterialExpansionPanel.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 36 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (10 lines × 2) src/ReaLTaiizor/Controls/CheckBox/FoxCheckBox.cs:60— src/ReaLTaiizor/Controls/CheckBox/FoxCheckBox.cs:60-69 | src/ReaLTaiizor/Controls/CheckBox/FoxCheckBox.cs:89-98 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/ReaLTaiizor/Controls/CheckBox/FoxCheckBox.cs:60` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (10 lines × 2) src/ReaLTaiizor/ReaLTaiizor.cs:84— src/ReaLTaiizor/ReaLTaiizor.cs:84-93 | src/ReaLTaiizor/ReaLTaiizor.cs:125-134 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/ReaLTaiizor/ReaLTaiizor.cs:84` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
Duplicated block (10 lines × 2) src/ReaLTaiizor/Controls/Button/ParrotButton.cs:344— src/ReaLTaiizor/Controls/Button/ParrotButton.cs:344-353 | src/ReaLTaiizor/Controls/Button/ParrotButton.cs:373-382 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/ReaLTaiizor/Controls/Button/ParrotButton.cs:344` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (10 lines × 2) src/ReaLTaiizor/Controls/Progress/RibbonProgressBarLeft.cs:241— src/ReaLTaiizor/Controls/Progress/RibbonProgressBarLeft.cs:241-250 | src/ReaLTaiizor/Controls/Progress/RibbonProgressBarRight.cs:241-250 — before extracting anything, compare `src/ReaLTaiizor/Controls/Progress/RibbonProgressBarLeft.cs` and `src/ReaLTaiizor/Controls/Progress/RibbonProgressBarRight.cs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 65 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (10 lines × 2) src/ReaLTaiizor/Controls/RichTextBox/MetroRichTextBox.cs:158— src/ReaLTaiizor/Controls/RichTextBox/MetroRichTextBox.cs:158-167 | src/ReaLTaiizor/Controls/TextBox/MetroTextBox.cs:175-184 — before extracting anything, compare `src/ReaLTaiizor/Controls/RichTextBox/MetroRichTextBox.cs` and `src/ReaLTaiizor/Controls/TextBox/MetroTextBox.cs` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 143 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/ReaLTaiizor/Controls/RichTextBox/MetroRichTextBox.cs:158` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (10 lines × 2) src/ReaLTaiizor/Controls/TrackBar/DungeonTrackBar.cs:188— src/ReaLTaiizor/Controls/TrackBar/DungeonTrackBar.cs:188-197 | src/ReaLTaiizor/Controls/TrackBar/TrackBar.cs:156-165 — before extracting anything, compare `src/ReaLTaiizor/Controls/TrackBar/DungeonTrackBar.cs` and `src/ReaLTaiizor/Controls/TrackBar/TrackBar.cs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 67 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (10 lines × 2) src/ReaLTaiizor/Util/Air.cs:705— src/ReaLTaiizor/Util/Air.cs:705-714 | src/ReaLTaiizor/Util/Air.cs:1764-1773 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (10 lines × 2) src/ReaLTaiizor/Util/Air.cs:948— src/ReaLTaiizor/Util/Air.cs:948-957 | src/ReaLTaiizor/Util/Air.cs:1927-1936 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (10 lines × 2) src/ReaLTaiizor/Util/Moon.cs:698— src/ReaLTaiizor/Util/Moon.cs:698-707 | src/ReaLTaiizor/Util/Moon.cs:1763-1772 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (10 lines × 2) src/ReaLTaiizor/Util/Moon.cs:941— src/ReaLTaiizor/Util/Moon.cs:941-950 | src/ReaLTaiizor/Util/Moon.cs:1926-1935 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (10 lines × 2) src/ReaLTaiizor/Util/Space.cs:700— src/ReaLTaiizor/Util/Space.cs:700-709 | src/ReaLTaiizor/Util/Space.cs:1761-1770 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (10 lines × 2) src/ReaLTaiizor/Util/Space.cs:943— src/ReaLTaiizor/Util/Space.cs:943-952 | src/ReaLTaiizor/Util/Space.cs:1924-1933 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (10 lines × 2) src/ReaLTaiizor/Controls/ListView/PoisonListView.cs:554— src/ReaLTaiizor/Controls/ListView/PoisonListView.cs:554-563 | src/ReaLTaiizor/Controls/ListView/PoisonListView.cs:652-661 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/ReaLTaiizor/Controls/ListView/PoisonListView.cs:554` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note first that the copies are not typed on the same thing: the declarations holding them bind `e` to `DrawListViewSubItemEventArgs` in one and `DrawListViewItemEventArgs` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
Duplicated block (10 lines × 2) src/ReaLTaiizor/Controls/RadioButton/MaterialRadioButton.cs:165— src/ReaLTaiizor/Controls/RadioButton/MaterialRadioButton.cs:165-176 | src/ReaLTaiizor/Controls/Switch/MaterialSwitch.cs:178-187 — before extracting anything, compare `src/ReaLTaiizor/Controls/RadioButton/MaterialRadioButton.cs` and `src/ReaLTaiizor/Controls/Switch/MaterialSwitch.cs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 166 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/ReaLTaiizor/Controls/RadioButton/MaterialRadioButton.cs:165` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (10 lines × 2) src/ReaLTaiizor/Controls/Separator/CrownSeparator.cs:33— src/ReaLTaiizor/Controls/Separator/CrownSeparator.cs:33-42 | src/ReaLTaiizor/Controls/Strip/CrownStatusStrip.cs:40-49 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `src/ReaLTaiizor/Controls/Separator/CrownSeparator.cs:33` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `src/ReaLTaiizor/Controls/Separator/CrownSeparator.cs:44` calls `OnPaintBackground` and `src/ReaLTaiizor/Controls/Strip/CrownStatusStrip.cs:52` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (10 lines × 2) src/ReaLTaiizor/Controls/TextBox/AloneTextBox.cs:201— src/ReaLTaiizor/Controls/TextBox/AloneTextBox.cs:201-210 | src/ReaLTaiizor/Controls/TextBox/FoxTextBox.cs:171-180 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `src/ReaLTaiizor/Controls/TextBox/AloneTextBox.cs:201` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (10 lines × 2) src/ReaLTaiizor/Forms/Panel/ParrotForm.cs:510— src/ReaLTaiizor/Forms/Panel/ParrotForm.cs:510-519 | src/ReaLTaiizor/Forms/Panel/ParrotForm.cs:634-643 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `src/ReaLTaiizor/Forms/Panel/ParrotForm.cs:644` calls `DrawEllipse`, `Pen`, `FromArgb` and `src/ReaLTaiizor/Forms/Panel/ParrotForm.cs:521` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (10 lines × 2) src/ReaLTaiizor/Controls/ScrollBar/MaterialScrollBar.cs:921— src/ReaLTaiizor/Controls/ScrollBar/MaterialScrollBar.cs:921-930 | src/ReaLTaiizor/Controls/ScrollBar/PoisonScrollBar.cs:1121-1130 — before extracting anything, compare `src/ReaLTaiizor/Controls/ScrollBar/MaterialScrollBar.cs` and `src/ReaLTaiizor/Controls/ScrollBar/PoisonScrollBar.cs` as WHOLE FILES: this scan already matched 15 separate duplicated blocks between them, totalling at least 423 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (9 lines × 2) src/ReaLTaiizor/Controls/Stick/ParrotJoyStick.cs:274— src/ReaLTaiizor/Controls/Stick/ParrotJoyStick.cs:274-282 | src/ReaLTaiizor/Controls/Stick/ParrotJoyStick.cs:307-315 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/ReaLTaiizor/Controls/Stick/ParrotJoyStick.cs:274` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (9 lines × 2) src/ReaLTaiizor/Controls/TabControl/MetroTabControl.cs:410— src/ReaLTaiizor/Controls/TabControl/MetroTabControl.cs:410-418 | src/ReaLTaiizor/Controls/TabControl/MetroTabControl.cs:431-439 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/ReaLTaiizor/Controls/TabControl/MetroTabControl.cs:410` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (9 lines × 2) src/ReaLTaiizor/Controls/ControlBox/ControlBox.cs:229— src/ReaLTaiizor/Controls/ControlBox/ControlBox.cs:229-237 | src/ReaLTaiizor/Controls/ControlBox/ControlBox.cs:286-294 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/ReaLTaiizor/Controls/ControlBox/ControlBox.cs:229` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (9 lines × 2) src/ReaLTaiizor/Controls/ControlBox/MetroControlBox.cs:114— src/ReaLTaiizor/Controls/ControlBox/MetroControlBox.cs:114-122 | src/ReaLTaiizor/Controls/ControlBox/MetroControlBox.cs:128-136 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (9 lines × 2) src/ReaLTaiizor/Controls/Stick/ParrotJoyStick.cs:352— src/ReaLTaiizor/Controls/Stick/ParrotJoyStick.cs:352-360 | src/ReaLTaiizor/Controls/Stick/ParrotJoyStick.cs:364-372 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/ReaLTaiizor/Controls/Stick/ParrotJoyStick.cs:352` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (9 lines × 2) src/ReaLTaiizor/Controls/TabPage/ForeverTabPage.cs:92— src/ReaLTaiizor/Controls/TabPage/ForeverTabPage.cs:92-100 | src/ReaLTaiizor/Controls/TabPage/ForeverTabPage.cs:126-134 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/ReaLTaiizor/Controls/TabPage/ForeverTabPage.cs:92` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (9 lines × 2) src/ReaLTaiizor/Controls/Button/HopeButton.cs:91— src/ReaLTaiizor/Controls/Button/HopeButton.cs:91-99 | src/ReaLTaiizor/Controls/Button/HopeRoundButton.cs:95-103 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (9 lines × 2) src/ReaLTaiizor/Controls/Button/LostAcceptButton.cs:54— src/ReaLTaiizor/Controls/Button/LostAcceptButton.cs:54-62 | src/ReaLTaiizor/Controls/Button/LostCancelButton.cs:54-62 — before extracting anything, compare `src/ReaLTaiizor/Controls/Button/LostAcceptButton.cs` and `src/ReaLTaiizor/Controls/Button/LostCancelButton.cs` as WHOLE FILES: 92% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 4 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (9 lines × 2) src/ReaLTaiizor/Controls/Button/MetroButton.cs:208— src/ReaLTaiizor/Controls/Button/MetroButton.cs:208-216 | src/ReaLTaiizor/Controls/Button/MetroButton.cs:224-232 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (9 lines × 2) src/ReaLTaiizor/Controls/CheckBox/FoxCheckBox.cs:73— src/ReaLTaiizor/Controls/CheckBox/FoxCheckBox.cs:73-81 | src/ReaLTaiizor/Controls/CheckBox/FoxCheckBox.cs:102-110 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/ReaLTaiizor/Controls/CheckBox/FoxCheckBox.cs:73` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (9 lines × 2) src/ReaLTaiizor/Controls/Stick/ParrotJoyStick.cs:191— src/ReaLTaiizor/Controls/Stick/ParrotJoyStick.cs:191-199 | src/ReaLTaiizor/Controls/Stick/ParrotJoyStick.cs:216-224 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (9 lines × 2) src/ReaLTaiizor/Forms/Form/LostForm.cs:26— src/ReaLTaiizor/Forms/Form/LostForm.cs:26-34 | src/ReaLTaiizor/Forms/Form/RoyalForm.cs:24-32 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (9 lines × 2) src/ReaLTaiizor/Util/Crown.cs:309— src/ReaLTaiizor/Util/Crown.cs:309-317 | src/ReaLTaiizor/Util/Crown.cs:340-348 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (9 lines × 2) src/ReaLTaiizor/Controls/Button/MaterialButton.cs:549— src/ReaLTaiizor/Controls/Button/MaterialButton.cs:549-558 | src/ReaLTaiizor/Controls/Button/MaterialButton.cs:561-569 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/ReaLTaiizor/Controls/Button/MaterialButton.cs:549` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (9 lines × 2) src/ReaLTaiizor/Controls/DatePicker/HopeDatePicker.cs:303— src/ReaLTaiizor/Controls/DatePicker/HopeDatePicker.cs:303-311 | src/ReaLTaiizor/Controls/RichTextBox/HopeRichTextBox.cs:122-130 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (9 lines × 2) src/ReaLTaiizor/Controls/Grid/PoisonDataGridView.cs:112— src/ReaLTaiizor/Controls/Grid/PoisonDataGridView.cs:112-120 | src/ReaLTaiizor/Controls/Strip/PoisonContextMenuStrip.cs:116-124 — before extracting anything, compare `src/ReaLTaiizor/Controls/Grid/PoisonDataGridView.cs` and `src/ReaLTaiizor/Controls/Strip/PoisonContextMenuStrip.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 43 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (9 lines × 2) src/ReaLTaiizor/Controls/ListView/PoisonListView.cs:570— src/ReaLTaiizor/Controls/ListView/PoisonListView.cs:570-578 | src/ReaLTaiizor/Controls/ListView/PoisonListView.cs:662-670 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/ReaLTaiizor/Controls/ListView/PoisonListView.cs:570` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. Note first that the copies are not typed on the same thing: the declarations holding them bind `e` to `DrawListViewSubItemEventArgs` in one and `DrawListViewItemEventArgs` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
Duplicated block (9 lines × 2) src/ReaLTaiizor/Controls/Numeric/DungeonNumeric.cs:222— src/ReaLTaiizor/Controls/Numeric/DungeonNumeric.cs:222-234 | src/ReaLTaiizor/Controls/Numeric/SkyNumeric.cs:163-171 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `src/ReaLTaiizor/Controls/Numeric/DungeonNumeric.cs:222` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (9 lines × 2) src/ReaLTaiizor/Controls/CheckBox/CrownCheckBox.cs:153— src/ReaLTaiizor/Controls/CheckBox/CrownCheckBox.cs:153-161 | src/ReaLTaiizor/Controls/RadioButton/CrownRadioButton.cs:150-158 — before extracting anything, compare `src/ReaLTaiizor/Controls/CheckBox/CrownCheckBox.cs` and `src/ReaLTaiizor/Controls/RadioButton/CrownRadioButton.cs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 95 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (9 lines × 2) src/ReaLTaiizor/Controls/ListBox/MaterialListBox.cs:186— src/ReaLTaiizor/Controls/ListBox/MaterialListBox.cs:186-194 | src/ReaLTaiizor/Controls/ListBox/MetroListBox.cs:381-389 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (9 lines × 2) src/ReaLTaiizor/Util/Moon.cs:2460— src/ReaLTaiizor/Util/Moon.cs:2460-2468 | src/ReaLTaiizor/Util/Space.cs:2458-2466 — before extracting anything, compare `src/ReaLTaiizor/Util/Moon.cs` and `src/ReaLTaiizor/Util/Space.cs` as WHOLE FILES: this scan already matched 42 separate duplicated blocks between them, totalling at least 688 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (8 lines × 2) src/ReaLTaiizor/Controls/Stick/ParrotJoyStick.cs:265— src/ReaLTaiizor/Controls/Stick/ParrotJoyStick.cs:265-272 | src/ReaLTaiizor/Controls/Stick/ParrotJoyStick.cs:343-350 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (8 lines × 2) src/ReaLTaiizor/Controls/CheckBox/RibbonCheckBox.cs:172— src/ReaLTaiizor/Controls/CheckBox/RibbonCheckBox.cs:172-179 | src/ReaLTaiizor/Controls/RadioButton/RibbonRadioButton.cs:176-183 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `src/ReaLTaiizor/Controls/CheckBox/RibbonCheckBox.cs:171` calls `OnPaint` and `src/ReaLTaiizor/Controls/RadioButton/RibbonRadioButton.cs:175` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (8 lines × 2) src/ReaLTaiizor/Controls/TextBox/BigTextBox.cs:235— src/ReaLTaiizor/Controls/TextBox/BigTextBox.cs:235-242 | src/ReaLTaiizor/Controls/TextBox/SmallTextBox.cs:213-220 — before extracting anything, compare `src/ReaLTaiizor/Controls/TextBox/BigTextBox.cs` and `src/ReaLTaiizor/Controls/TextBox/SmallTextBox.cs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 64 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (8 lines × 2) src/ReaLTaiizor/Controls/Button/AirButton.cs:18— src/ReaLTaiizor/Controls/Button/AirButton.cs:18-25 | src/ReaLTaiizor/Controls/CheckBox/AirCheckBox.cs:22-29 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (8 lines × 2) src/ReaLTaiizor/Controls/ListBox/MaterialListBox.cs:369— src/ReaLTaiizor/Controls/ListBox/MaterialListBox.cs:369-376 | src/ReaLTaiizor/Controls/ListBox/MaterialListBox.cs:379-386 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (8 lines × 2) src/ReaLTaiizor/Forms/Form/PoisonForm.cs:1302— src/ReaLTaiizor/Forms/Form/PoisonForm.cs:1302-1309 | src/ReaLTaiizor/Forms/Form/PoisonForm.cs:1420-1427 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (8 lines × 2) src/ReaLTaiizor/Controls/Button/DreamButton.cs:88— src/ReaLTaiizor/Controls/Button/DreamButton.cs:88-95 | src/ReaLTaiizor/Controls/TextBox/DreamTextBox.cs:51-58 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `src/ReaLTaiizor/Controls/Button/DreamButton.cs:88` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (8 lines × 2) src/ReaLTaiizor/Controls/Button/ForeverButton.cs:24— src/ReaLTaiizor/Controls/Button/ForeverButton.cs:24-31 | src/ReaLTaiizor/Controls/Button/ForeverButtonSticky.cs:78-85 — before extracting anything, compare `src/ReaLTaiizor/Controls/Button/ForeverButton.cs` and `src/ReaLTaiizor/Controls/Button/ForeverButtonSticky.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 94 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (8 lines × 2) src/ReaLTaiizor/Controls/ListBox/MetroListBox.cs:165— src/ReaLTaiizor/Controls/ListBox/MetroListBox.cs:165-172 | src/ReaLTaiizor/Controls/ListBox/MetroListBox.cs:179-186 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (8 lines × 2) src/ReaLTaiizor/Controls/ScrollBar/RoyalScrollBar.cs:150— src/ReaLTaiizor/Controls/ScrollBar/RoyalScrollBar.cs:150-157 | src/ReaLTaiizor/Controls/ScrollBar/RoyalScrollBar.cs:211-218 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/ReaLTaiizor/Controls/ScrollBar/RoyalScrollBar.cs:150` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (8 lines × 2) src/ReaLTaiizor/Forms/Form/MaterialForm.cs:1312— src/ReaLTaiizor/Forms/Form/MaterialForm.cs:1312-1319 | src/ReaLTaiizor/Forms/Form/MaterialForm.cs:1322-1330 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/ReaLTaiizor/Forms/Form/MaterialForm.cs:1312` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (8 lines × 2) src/ReaLTaiizor/Forms/Panel/ParrotForm.cs:459— src/ReaLTaiizor/Forms/Panel/ParrotForm.cs:459-466 | src/ReaLTaiizor/Forms/Panel/ParrotForm.cs:782-789 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (8 lines × 2) src/ReaLTaiizor/Forms/Panel/ParrotForm.cs:488— src/ReaLTaiizor/Forms/Panel/ParrotForm.cs:488-495 | src/ReaLTaiizor/Forms/Panel/ParrotForm.cs:757-764 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (8 lines × 2) src/ReaLTaiizor/Forms/Panel/ParrotForm.cs:514— src/ReaLTaiizor/Forms/Panel/ParrotForm.cs:514-521 | src/ReaLTaiizor/Forms/Panel/ParrotForm.cs:732-739 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (8 lines × 2) src/ReaLTaiizor/Forms/Container/DungeonForm.cs:501— src/ReaLTaiizor/Forms/Container/DungeonForm.cs:501-508 | src/ReaLTaiizor/Forms/Container/ThemeForm.cs:509-516 — before extracting anything, compare `src/ReaLTaiizor/Forms/Container/DungeonForm.cs` and `src/ReaLTaiizor/Forms/Container/ThemeForm.cs` as WHOLE FILES: this scan already matched 17 separate duplicated blocks between them, totalling at least 286 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (8 lines × 2) src/ReaLTaiizor/Util/Ribbon.cs:38— src/ReaLTaiizor/Util/Ribbon.cs:38-45 | src/ReaLTaiizor/Util/Sky.cs:28-35 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (8 lines × 2) src/ReaLTaiizor/Animate/Parrot/ObjectAnimator.cs:18— src/ReaLTaiizor/Animate/Parrot/ObjectAnimator.cs:18-25 | src/ReaLTaiizor/Controls/Sleeper/ParrotSleeper.cs:16-23 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (8 lines × 2) src/ReaLTaiizor/Controls/Button/RibbonButtonCenter.cs:177— src/ReaLTaiizor/Controls/Button/RibbonButtonCenter.cs:177-184 | src/ReaLTaiizor/Controls/Button/RibbonButtonRight.cs:177-184 — before extracting anything, compare `src/ReaLTaiizor/Controls/Button/RibbonButtonCenter.cs` and `src/ReaLTaiizor/Controls/Button/RibbonButtonRight.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 67 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (8 lines × 2) src/ReaLTaiizor/Controls/CheckBox/ThunderCheckBox.cs:81— src/ReaLTaiizor/Controls/CheckBox/ThunderCheckBox.cs:81-88 | src/ReaLTaiizor/Controls/RadioButton/ThunderRadioButton.cs:100-107 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (8 lines × 2) src/ReaLTaiizor/Controls/Banner/ParrotBanner.cs:80— src/ReaLTaiizor/Controls/Banner/ParrotBanner.cs:80-87 | src/ReaLTaiizor/Controls/Banner/ParrotBanner.cs:105-112 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (5 lines × 2) src/ReaLTaiizor/Controls/Numeric/MetroNumeric.cs:162— src/ReaLTaiizor/Controls/Numeric/MetroNumeric.cs:162-166 | src/ReaLTaiizor/Controls/Switch/MetroSwitch.cs:138-142 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `src/ReaLTaiizor/Controls/Switch/MetroSwitch.cs:136` calls `FromArgb` and `src/ReaLTaiizor/Controls/Numeric/MetroNumeric.cs:161` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (5 lines × 2) src/ReaLTaiizor/Controls/TrackBar/MetroTrackBar.cs:124— src/ReaLTaiizor/Controls/TrackBar/MetroTrackBar.cs:124-128 | src/ReaLTaiizor/Controls/TrackBar/MetroTrackBar.cs:135-139 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (5 lines × 2) src/ReaLTaiizor/Controls/Icon/InfoIcon.cs:44— src/ReaLTaiizor/Controls/Icon/InfoIcon.cs:44-48 | src/ReaLTaiizor/Controls/Icon/TickIcon.cs:44-48 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (5 lines × 2) src/ReaLTaiizor/Controls/RadioButton/ParrotRadioButton.cs:168— src/ReaLTaiizor/Controls/RadioButton/ParrotRadioButton.cs:168-172 | src/ReaLTaiizor/Controls/RadioButton/ParrotRadioButton.cs:176-180 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/ReaLTaiizor/Controls/RadioButton/ParrotRadioButton.cs:168` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (5 lines × 2) src/ReaLTaiizor/Controls/Button/MetroDefaultButton.cs:138— src/ReaLTaiizor/Controls/Button/MetroDefaultButton.cs:138-142 | src/ReaLTaiizor/Controls/Ellipse/MetroEllipse.cs:141-145 — before extracting anything, compare `src/ReaLTaiizor/Controls/Button/MetroDefaultButton.cs` and `src/ReaLTaiizor/Controls/Ellipse/MetroEllipse.cs` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 122 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/ReaLTaiizor/Controls/Button/MetroDefaultButton.cs:138` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (5 lines × 2) src/ReaLTaiizor/Controls/Button/MetroDefaultButton.cs:148— src/ReaLTaiizor/Controls/Button/MetroDefaultButton.cs:148-152 | src/ReaLTaiizor/Controls/Ellipse/MetroEllipse.cs:151-155 — before extracting anything, compare `src/ReaLTaiizor/Controls/Button/MetroDefaultButton.cs` and `src/ReaLTaiizor/Controls/Ellipse/MetroEllipse.cs` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 122 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/ReaLTaiizor/Controls/Button/MetroDefaultButton.cs:148` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (5 lines × 2) src/ReaLTaiizor/Controls/ControlBox/ThunderControlBox.cs:239— src/ReaLTaiizor/Controls/ControlBox/ThunderControlBox.cs:239-243 | src/ReaLTaiizor/Controls/ControlBox/ThunderControlBox.cs:248-252 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (5 lines × 2) src/ReaLTaiizor/Controls/Button/DreamButton.cs:65— src/ReaLTaiizor/Controls/Button/DreamButton.cs:65-69 | src/ReaLTaiizor/Controls/TextBox/DreamTextBox.cs:38-42 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (5 lines × 2) src/ReaLTaiizor/Controls/CheckBox/MaterialCheckBox.cs:239— src/ReaLTaiizor/Controls/CheckBox/MaterialCheckBox.cs:239-243 | src/ReaLTaiizor/Controls/RadioButton/MaterialRadioButton.cs:213-217 — before extracting anything, compare `src/ReaLTaiizor/Controls/CheckBox/MaterialCheckBox.cs` and `src/ReaLTaiizor/Controls/RadioButton/MaterialRadioButton.cs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 99 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (5 lines × 2) src/ReaLTaiizor/Controls/ListBox/ForeverListBox.cs:140— src/ReaLTaiizor/Controls/ListBox/ForeverListBox.cs:140-144 | src/ReaLTaiizor/Controls/ListBox/ForeverListBox.cs:148-152 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (5 lines × 2) src/ReaLTaiizor/Controls/Progress/HopePrgoressBar.cs:156— src/ReaLTaiizor/Controls/Progress/HopePrgoressBar.cs:156-160 | src/ReaLTaiizor/Controls/Progress/HopePrgoressBar.cs:166-170 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (5 lines × 2) src/ReaLTaiizor/Docking/Crown/CrownDockGroup.cs:191— src/ReaLTaiizor/Docking/Crown/CrownDockGroup.cs:191-195 | src/ReaLTaiizor/Docking/Crown/CrownDockGroup.cs:196-200 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/ReaLTaiizor/Docking/Crown/CrownDockGroup.cs:191` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (5 lines × 2) REDACTED:111— REDACTED:111-115 | REDACTED:127-131 — before extracting anything, compare `REDACTED` and `REDACTED` as WHOLE FILES: 86% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 4 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (5 lines × 2) REDACTED:119— REDACTED:119-123 | REDACTED:135-139 — before extracting anything, compare `REDACTED` and `REDACTED` as WHOLE FILES: 86% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 4 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (5 lines × 2) src/ReaLTaiizor/Controls/Label/DungeonLabel.cs:16— src/ReaLTaiizor/Controls/Label/DungeonLabel.cs:16-20 | src/ReaLTaiizor/Controls/Label/SmallLabel.cs:15-19 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (5 lines × 2) src/ReaLTaiizor/Controls/Panel/LostPanel.cs:47— src/ReaLTaiizor/Controls/Panel/LostPanel.cs:47-51 | src/ReaLTaiizor/Util/Lost.cs:179-183 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (5 lines × 2) src/ReaLTaiizor/Controls/TextBox/MaterialMaskedTextBox.cs:1521— src/ReaLTaiizor/Controls/TextBox/MaterialMaskedTextBox.cs:1521-1525 | src/ReaLTaiizor/Controls/TextBoxEdit/MaterialTextBoxEdit.cs:1477-1481 — before extracting anything, compare `src/ReaLTaiizor/Controls/TextBox/MaterialMaskedTextBox.cs` and `src/ReaLTaiizor/Controls/TextBoxEdit/MaterialTextBoxEdit.cs` as WHOLE FILES: this scan already matched 27 separate duplicated blocks between them, totalling at least 574 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (5 lines × 2) src/ReaLTaiizor/Controls/ComboBox/AloneComboBox.cs:80— src/ReaLTaiizor/Controls/ComboBox/AloneComboBox.cs:80-84 | src/ReaLTaiizor/Controls/ComboBox/AloneComboBox.cs:88-92 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/ReaLTaiizor/Controls/ComboBox/AloneComboBox.cs:80` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (5 lines × 2) src/ReaLTaiizor/Controls/GroupBox/ParrotGroupBox.cs:87— src/ReaLTaiizor/Controls/GroupBox/ParrotGroupBox.cs:87-91 | src/ReaLTaiizor/Controls/GroupBox/ParrotGroupBox.cs:94-98 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/ReaLTaiizor/Controls/GroupBox/ParrotGroupBox.cs:87` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (5 lines × 2) src/ReaLTaiizor/Controls/TreeView/ForeverTreeView.cs:33— src/ReaLTaiizor/Controls/TreeView/ForeverTreeView.cs:33-37 | src/ReaLTaiizor/Controls/TreeView/ForeverTreeView.cs:38-42 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/ReaLTaiizor/Controls/TreeView/ForeverTreeView.cs:33` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
AX2 · Stateful singletons· Process-global static state · ×17
Process-global static state: AppLocker ready/ReaLTaiizor.AppLocker/ReaLTaiizor.AppLocker/AppLocker.cs:10— `AppLocker` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (PProcs; e.g. `PProcs` at line 38). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt.
Process-global static state: Translate ready/ReaLTaiizor.Translate/ReaLTaiizor.Translate/Translate.cs:12— `Translate` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (Lang; e.g. `Lang` at line 28). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt.
Process-global static state: CyberButton src/ReaLTaiizor/Controls/Button/CyberButton.cs:19— `CyberButton` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (tmp_color_background_pen; e.g. `tmp_color_background_pen` at line 234). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt.
Process-global static state: CyberCheckBox src/ReaLTaiizor/Controls/CheckBox/CyberCheckBox.cs:19— `CyberCheckBox` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (tmp_color_background_pen; e.g. `tmp_color_background_pen` at line 193). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt.
Process-global static state: MaterialCheckBox src/ReaLTaiizor/Controls/CheckBox/MaterialCheckBox.cs:20— `MaterialCheckBox` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (CheckmarkLine; e.g. `CheckmarkLine` at line 445). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt.
Process-global static state: MetroMessageBox src/ReaLTaiizor/Controls/MessageBox/MetroMessageBox.cs:17— `MetroMessageBox` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (BackgroundColor, BorderColor, ForegroundColor; e.g. `BackgroundColor` at line 241). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt.
Process-global static state: RoyalMessageBox src/ReaLTaiizor/Controls/MessageBox/RoyalMessageBox.cs:14— `RoyalMessageBox` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (mode; e.g. `mode` at line 32). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt.
Process-global static state: CyberRadioButton src/ReaLTaiizor/Controls/RadioButton/CyberRadioButton.cs:19— `CyberRadioButton` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (tmp_color_background_pen; e.g. `tmp_color_background_pen` at line 209). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt.
Process-global static state: HopeRichTextBox src/ReaLTaiizor/Controls/RichTextBox/HopeRichTextBox.cs:18— `HopeRichTextBox` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (_currentControlStartSize; e.g. `_currentControlStartSize` at line 103). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt.
Process-global static state: MetroContextMenuStrip src/ReaLTaiizor/Controls/Strip/MetroContextMenuStrip.cs:20— `MetroContextMenuStrip` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (ForegroundColor, BackgroundColor, ArrowColor, SelectedItemBackColor, SelectedItemColor, SeparatorColor; e.g. `ForegroundColor` at line 104). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt.
Process-global static state: ThemeShareAir src/ReaLTaiizor/Util/Air.cs:2419— `ThemeShareAir` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (Invalidate, Frames; e.g. `Invalidate` at line 2437). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt.
Process-global static state: DrawEngine src/ReaLTaiizor/Util/Cyber.cs:19— `DrawEngine` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (Temp; e.g. `Temp` at line 129). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt.
Process-global static state: ThemeLost src/ReaLTaiizor/Util/Lost.cs:15— `ThemeLost` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (TitleFont, HeaderFont, BodyFont, FontColor, FontBrush, FontPen; e.g. `TitleFont` at line 42). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt.
Process-global static state: MaterialNativeTextRenderer src/ReaLTaiizor/Util/Material.cs:162— `MaterialNativeTextRenderer` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (_fontsCache; e.g. `_fontsCache` at line 401). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt.
Process-global static state: ThemeShareMoon src/ReaLTaiizor/Util/Moon.cs:2423— `ThemeShareMoon` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (Invalidate, Frames; e.g. `Invalidate` at line 2441). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt.
Process-global static state: ThemeShareSpace src/ReaLTaiizor/Util/Space.cs:2420— `ThemeShareSpace` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (Invalidate, Frames; e.g. `Invalidate` at line 2439). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt.
Process-global static state: Status ready/ReaLTaiizor.Nerator/ReaLTaiizor.Nerator/CS/Status.cs:5— `Status` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (ChangedStatus; e.g. `ChangedStatus` at line 16). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt.
FileTooLong: Util/Air.cs src/ReaLTaiizor/Util/Air.cs— FileTooLong — 1214 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 714 over it, 2.43× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: Util/Moon.cs src/ReaLTaiizor/Util/Moon.cs— FileTooLong — 1214 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 714 over it, 2.43× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: Util/Space.cs src/ReaLTaiizor/Util/Space.cs— FileTooLong — 1213 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 713 over it, 2.43× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: TextBox/MaterialMaskedTextBox.cs src/ReaLTaiizor/Controls/TextBox/MaterialMaskedTextBox.cs— FileTooLong — 896 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 396 over it, 1.79× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: TextBoxEdit/MaterialTextBoxEdit.cs src/ReaLTaiizor/Controls/TextBoxEdit/MaterialTextBoxEdit.cs— FileTooLong — 864 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 364 over it, 1.73× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: Form/PoisonForm.cs src/ReaLTaiizor/Forms/Form/PoisonForm.cs— FileTooLong — 808 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 308 over it, 1.62× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: Util/Material.cs src/ReaLTaiizor/Util/Material.cs— FileTooLong — 790 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 290 over it, 1.58× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: Form/MaterialForm.cs src/ReaLTaiizor/Forms/Form/MaterialForm.cs— FileTooLong — 772 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 272 over it, 1.54× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: TextBox/PoisonTextBox.cs src/ReaLTaiizor/Controls/TextBox/PoisonTextBox.cs— FileTooLong — 771 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 271 over it, 1.54× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: TreeView/CrownTreeView.cs src/ReaLTaiizor/Controls/TreeView/CrownTreeView.cs— FileTooLong — 656 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 156 over it, 1.31× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: ScrollBar/PoisonScrollBar.cs src/ReaLTaiizor/Controls/ScrollBar/PoisonScrollBar.cs— FileTooLong — 589 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 89 over it, 1.18× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: ListBox/MaterialListBox.cs src/ReaLTaiizor/Controls/ListBox/MaterialListBox.cs— FileTooLong — 587 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 87 over it, 1.17× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: Form/MaterialFlexibleForm.cs src/ReaLTaiizor/Forms/Form/MaterialFlexibleForm.cs— FileTooLong — 550 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 50 over it, 1.10× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: TextBoxEdit/MaterialMultiLineTextBoxEdit.cs src/ReaLTaiizor/Controls/TextBoxEdit/MaterialMultiLineTextBoxEdit.cs— FileTooLong — 545 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 45 over it, 1.09× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: Drawer/MaterialDrawer.cs src/ReaLTaiizor/Controls/Drawer/MaterialDrawer.cs— FileTooLong — 533 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 33 over it, 1.07× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: TextBox/MaterialTextBox.cs src/ReaLTaiizor/Controls/TextBox/MaterialTextBox.cs— FileTooLong — 530 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 30 over it, 1.06× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: Panel/ParrotForm.cs src/ReaLTaiizor/Forms/Panel/ParrotForm.cs— FileTooLong — 520 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 20 over it, 1.04× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
ClassTooLong: MaterialMaskedTextBox src/ReaLTaiizor/Controls/TextBox/MaterialMaskedTextBox.cs— ClassTooLong — 883 significant lines (blank, comment-only and punctuation-only lines excluded), 27 methods. The bar is 400 significant lines; this is 483 over it, 2.21× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: MaterialTextBoxEdit src/ReaLTaiizor/Controls/TextBoxEdit/MaterialTextBoxEdit.cs— ClassTooLong — 851 significant lines (blank, comment-only and punctuation-only lines excluded), 28 methods. The bar is 400 significant lines; this is 451 over it, 2.13× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: MaterialForm src/ReaLTaiizor/Forms/Form/MaterialForm.cs— ClassTooLong — 754 significant lines (blank, comment-only and punctuation-only lines excluded), 30 methods. The bar is 400 significant lines; this is 354 over it, 1.89× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: MaterialFlexibleForm src/ReaLTaiizor/Forms/Form/MaterialFlexibleForm.cs— ClassTooLong — 539 significant lines (blank, comment-only and punctuation-only lines excluded), 17 methods. The bar is 400 significant lines; this is 139 over it, 1.35× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: MaterialMultiLineTextBoxEdit src/ReaLTaiizor/Controls/TextBoxEdit/MaterialMultiLineTextBoxEdit.cs— ClassTooLong — 534 significant lines (blank, comment-only and punctuation-only lines excluded), 24 methods. The bar is 400 significant lines; this is 134 over it, 1.34× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: MaterialDrawer src/ReaLTaiizor/Controls/Drawer/MaterialDrawer.cs— ClassTooLong — 519 significant lines (blank, comment-only and punctuation-only lines excluded), 20 methods. The bar is 400 significant lines; this is 119 over it, 1.30× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: ParrotForm src/ReaLTaiizor/Forms/Panel/ParrotForm.cs— ClassTooLong — 511 significant lines (blank, comment-only and punctuation-only lines excluded), 14 methods. The bar is 400 significant lines; this is 111 over it, 1.28× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: MaterialTextBox src/ReaLTaiizor/Controls/TextBox/MaterialTextBox.cs— ClassTooLong — 489 significant lines (blank, comment-only and punctuation-only lines excluded), 22 methods. The bar is 400 significant lines; this is 89 over it, 1.22× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: CyberScrollBar src/ReaLTaiizor/Controls/ScrollBar/CyberScrollBar.cs— ClassTooLong — 477 significant lines (blank, comment-only and punctuation-only lines excluded), 10 methods. The bar is 400 significant lines; this is 77 over it, 1.19× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: PoisonForm src/ReaLTaiizor/Forms/Form/PoisonForm.cs— ClassTooLong — 440 significant lines (blank, comment-only and punctuation-only lines excluded), 26 methods. The bar is 400 significant lines; this is 40 over it, 1.10× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: CyberRadioButton src/ReaLTaiizor/Controls/RadioButton/CyberRadioButton.cs— ClassTooLong — 433 significant lines (blank, comment-only and punctuation-only lines excluded), 12 methods. The bar is 400 significant lines; this is 33 over it, 1.08× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: CyberProgressBar src/ReaLTaiizor/Controls/Progress/CyberProgressBar.cs— ClassTooLong — 430 significant lines (blank, comment-only and punctuation-only lines excluded), 7 methods. The bar is 400 significant lines; this is 30 over it, 1.08× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: MetroBadge src/ReaLTaiizor/Controls/Badge/MetroBadge.cs— ClassTooLong — 420 significant lines (blank, comment-only and punctuation-only lines excluded), 8 methods. The bar is 400 significant lines; this is 20 over it, 1.05× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: MetroListBox src/ReaLTaiizor/Controls/ListBox/MetroListBox.cs— ClassTooLong — 416 significant lines (blank, comment-only and punctuation-only lines excluded), 25 methods. The bar is 400 significant lines; this is 16 over it, 1.04× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: PoisonListView src/ReaLTaiizor/Controls/ListView/PoisonListView.cs— ClassTooLong — 405 significant lines (blank, comment-only and punctuation-only lines excluded), 27 methods. The bar is 400 significant lines; this is 5 over it, 1.01× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: MaterialExpansionPanel src/ReaLTaiizor/Controls/Panel/MaterialExpansionPanel.cs— ClassTooLong — 401 significant lines (blank, comment-only and punctuation-only lines excluded), 20 methods. The bar is 400 significant lines; this is 1 over it, 1.00× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: MoonLibrary src/ReaLTaiizor/Util/Moon.cs— TooManyMethods — 673 significant lines (blank, comment-only and punctuation-only lines excluded), 92 methods. The bar is 30 methods; this is 62 over it, 3.07× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: AirLibrary src/ReaLTaiizor/Util/Air.cs— TooManyMethods — 672 significant lines (blank, comment-only and punctuation-only lines excluded), 91 methods. The bar is 30 methods; this is 61 over it, 3.03× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: SpaceLibrary src/ReaLTaiizor/Util/Space.cs— TooManyMethods — 671 significant lines (blank, comment-only and punctuation-only lines excluded), 91 methods. The bar is 30 methods; this is 61 over it, 3.03× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: AirControl src/ReaLTaiizor/Util/Air.cs— TooManyMethods — 451 significant lines (blank, comment-only and punctuation-only lines excluded), 84 methods. The bar is 30 methods; this is 54 over it, 2.80× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: MoonControl src/ReaLTaiizor/Util/Moon.cs— TooManyMethods — 451 significant lines (blank, comment-only and punctuation-only lines excluded), 84 methods. The bar is 30 methods; this is 54 over it, 2.80× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: SpaceControl src/ReaLTaiizor/Util/Space.cs— TooManyMethods — 451 significant lines (blank, comment-only and punctuation-only lines excluded), 84 methods. The bar is 30 methods; this is 54 over it, 2.80× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: CrownTreeView src/ReaLTaiizor/Controls/TreeView/CrownTreeView.cs— TooManyMethods — 644 significant lines (blank, comment-only and punctuation-only lines excluded), 52 methods. The bar is 30 methods; this is 22 over it, 1.73× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: MetroRichTextBox src/ReaLTaiizor/Controls/RichTextBox/MetroRichTextBox.cs— TooManyMethods — 468 significant lines (blank, comment-only and punctuation-only lines excluded), 48 methods. The bar is 30 methods; this is 18 over it, 1.60× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: PoisonTextBox src/ReaLTaiizor/Controls/TextBox/PoisonTextBox.cs— TooManyMethods — 506 significant lines (blank, comment-only and punctuation-only lines excluded), 44 methods. The bar is 30 methods; this is 14 over it, 1.47× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: PoisonScrollBar src/ReaLTaiizor/Controls/ScrollBar/PoisonScrollBar.cs— TooManyMethods — 576 significant lines (blank, comment-only and punctuation-only lines excluded), 41 methods. The bar is 30 methods; this is 11 over it, 1.37× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: MaterialScrollBar src/ReaLTaiizor/Controls/ScrollBar/MaterialScrollBar.cs— TooManyMethods — 474 significant lines (blank, comment-only and punctuation-only lines excluded), 38 methods. The bar is 30 methods; this is 8 over it, 1.27× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: MaterialListBox src/ReaLTaiizor/Controls/ListBox/MaterialListBox.cs— TooManyMethods — 571 significant lines (blank, comment-only and punctuation-only lines excluded), 35 methods. The bar is 30 methods; this is 5 over it, 1.17× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: PoisonTabControl src/ReaLTaiizor/Controls/TabControl/PoisonTabControl.cs— TooManyMethods — 334 significant lines (blank, comment-only and punctuation-only lines excluded), 34 methods. The bar is 30 methods; this is 4 over it, 1.13× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: MetroTextBox src/ReaLTaiizor/Controls/TextBox/MetroTextBox.cs— TooManyMethods — 451 significant lines (blank, comment-only and punctuation-only lines excluded), 33 methods. The bar is 30 methods; this is 3 over it, 1.10× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: MaterialNativeTextRenderer src/ReaLTaiizor/Util/Material.cs— TooManyMethods — 231 significant lines (blank, comment-only and punctuation-only lines excluded), 33 methods. The bar is 30 methods; this is 3 over it, 1.10× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
Duplicated block (14 lines × 2) src/ReaLTaiizor/Controls/Badge/MetroBadge.cs:508— src/ReaLTaiizor/Controls/Badge/MetroBadge.cs:508-521 | src/ReaLTaiizor/Controls/Badge/MetroBadge.cs:530-543 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (14 lines × 2) src/ReaLTaiizor/Controls/Graph/ParrotBarGraph.cs:261— src/ReaLTaiizor/Controls/Graph/ParrotBarGraph.cs:261-274 | src/ReaLTaiizor/Controls/Graph/ParrotBarGraph.cs:314-327 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/ReaLTaiizor/Controls/Graph/ParrotBarGraph.cs:261` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (14 lines × 2) src/ReaLTaiizor/Controls/RichTextBox/MetroRichTextBox.cs:238— src/ReaLTaiizor/Controls/RichTextBox/MetroRichTextBox.cs:238-251 | src/ReaLTaiizor/Controls/TextBox/MetroTextBox.cs:262-275 — before extracting anything, compare `src/ReaLTaiizor/Controls/RichTextBox/MetroRichTextBox.cs` and `src/ReaLTaiizor/Controls/TextBox/MetroTextBox.cs` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 143 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/ReaLTaiizor/Controls/RichTextBox/MetroRichTextBox.cs:238` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (14 lines × 2) src/ReaLTaiizor/Controls/ListBox/MetroListBox.cs:196— src/ReaLTaiizor/Controls/ListBox/MetroListBox.cs:196-209 | src/ReaLTaiizor/Controls/ScrollBar/MetroScrollBar.cs:153-166 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `src/ReaLTaiizor/Controls/ListBox/MetroListBox.cs:196` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (14 lines × 2) src/ReaLTaiizor/Util/Air.cs:28— src/ReaLTaiizor/Util/Air.cs:28-41 | src/ReaLTaiizor/Util/Space.cs:28-41 — before extracting anything, compare `src/ReaLTaiizor/Util/Air.cs` and `src/ReaLTaiizor/Util/Space.cs` as WHOLE FILES: this scan already matched 41 separate duplicated blocks between them, totalling at least 675 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (14 lines × 2) ready/ReaLTaiizor.Portscan/ReaLTaiizor.Portscan/Portscan.cs:294— ready/ReaLTaiizor.Portscan/ReaLTaiizor.Portscan/Portscan.cs:294-307 | ready/ReaLTaiizor.Portscan/ReaLTaiizor.Portscan/Portscan.cs:317-330 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `ready/ReaLTaiizor.Portscan/ReaLTaiizor.Portscan/Portscan.cs:294` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (14 lines × 2) src/ReaLTaiizor/Controls/ControlBox/DungeonControlBox.cs:54— src/ReaLTaiizor/Controls/ControlBox/DungeonControlBox.cs:54-67 | src/ReaLTaiizor/Controls/ControlBox/DungeonControlBox.cs:70-83 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/ReaLTaiizor/Controls/ControlBox/DungeonControlBox.cs:54` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (14 lines × 2) src/ReaLTaiizor/Controls/CheckBox/CrownCheckBox.cs:189— src/ReaLTaiizor/Controls/CheckBox/CrownCheckBox.cs:189-202 | src/ReaLTaiizor/Controls/RadioButton/CrownRadioButton.cs:186-199 — before extracting anything, compare `src/ReaLTaiizor/Controls/CheckBox/CrownCheckBox.cs` and `src/ReaLTaiizor/Controls/RadioButton/CrownRadioButton.cs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 95 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (14 lines × 2) src/ReaLTaiizor/Controls/ComboBox/ForeverComboBox.cs:55— src/ReaLTaiizor/Controls/ComboBox/ForeverComboBox.cs:55-68 | src/ReaLTaiizor/Controls/Numeric/ForeverNumeric.cs:93-109 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (14 lines × 2) src/ReaLTaiizor/Controls/Ellipse/ParrotControlEllipse.cs:65— src/ReaLTaiizor/Controls/Ellipse/ParrotControlEllipse.cs:65-78 | src/ReaLTaiizor/Controls/Ellipse/ParrotObjectEllipse.cs:87-100 — before extracting anything, compare `src/ReaLTaiizor/Controls/Ellipse/ParrotControlEllipse.cs` and `src/ReaLTaiizor/Controls/Ellipse/ParrotObjectEllipse.cs` as WHOLE FILES: 86% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 2 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (14 lines × 2) src/ReaLTaiizor/Controls/Switch/HopeSwitch.cs:80— src/ReaLTaiizor/Controls/Switch/HopeSwitch.cs:80-93 | src/ReaLTaiizor/Controls/Toggle/HopeToggle.cs:84-97 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (14 lines × 2) src/ReaLTaiizor/Controls/TextBox/MaterialMaskedTextBox.cs:81— src/ReaLTaiizor/Controls/TextBox/MaterialMaskedTextBox.cs:81-94 | src/ReaLTaiizor/Controls/TextBoxEdit/MaterialTextBoxEdit.cs:86-99 — before extracting anything, compare `src/ReaLTaiizor/Controls/TextBox/MaterialMaskedTextBox.cs` and `src/ReaLTaiizor/Controls/TextBoxEdit/MaterialTextBoxEdit.cs` as WHOLE FILES: this scan already matched 27 separate duplicated blocks between them, totalling at least 574 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (8 lines × 3) src/ReaLTaiizor/Controls/Button/ChatButtonLeft.cs:213— src/ReaLTaiizor/Controls/Button/ChatButtonLeft.cs:213-220 | src/ReaLTaiizor/Controls/Button/ChatButtonRight.cs:200-207 | src/ReaLTaiizor/Controls/Button/DungeonButtonLeft.cs:213-220 — before extracting anything, compare `src/ReaLTaiizor/Controls/Button/ChatButtonLeft.cs` and `src/ReaLTaiizor/Controls/Button/ChatButtonRight.cs` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 217 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (8 lines × 3) src/ReaLTaiizor/Controls/Stick/ParrotJoyStick.cs:298— src/ReaLTaiizor/Controls/Stick/ParrotJoyStick.cs:298-305 | src/ReaLTaiizor/Controls/Stick/ParrotJoyStick.cs:331-338 | src/ReaLTaiizor/Controls/Stick/ParrotJoyStick.cs:376-383 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (8 lines × 3) src/ReaLTaiizor/Controls/Close/ForeverClose.cs:113— src/ReaLTaiizor/Controls/Close/ForeverClose.cs:113-120 | src/ReaLTaiizor/Controls/Maximize/ForeverMaximize.cs:121-128 | src/ReaLTaiizor/Controls/Minimize/ForeverMinimize.cs:121-128 — before extracting anything, compare `src/ReaLTaiizor/Controls/Close/ForeverClose.cs` and `src/ReaLTaiizor/Controls/Maximize/ForeverMaximize.cs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 61 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (8 lines × 3) src/ReaLTaiizor/Controls/Bubble/ChatBubbleRight.cs:108— src/ReaLTaiizor/Controls/Bubble/ChatBubbleRight.cs:108-116 | src/ReaLTaiizor/Controls/RichTextBox/DungeonRichTextBox.cs:118-125 | src/ReaLTaiizor/Controls/RichTextBoxEdit/RichTextBoxEdit.cs:173-180 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. Read the line range as the matched WINDOW rather than a finished unit: at `src/ReaLTaiizor/Controls/Bubble/ChatBubbleRight.cs:108` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note first that the copies are not typed on the same thing: the declarations holding them bind `e` to `EventArgs` in one and `System.EventArgs` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
Duplicated block (8 lines × 3) src/ReaLTaiizor/Controls/CheckBox/MaterialCheckBox.cs:248— src/ReaLTaiizor/Controls/CheckBox/MaterialCheckBox.cs:248-255 | src/ReaLTaiizor/Controls/RadioButton/MaterialRadioButton.cs:222-229 | src/ReaLTaiizor/Controls/Switch/MaterialSwitch.cs:234-241 — before extracting anything, compare `src/ReaLTaiizor/Controls/CheckBox/MaterialCheckBox.cs` and `src/ReaLTaiizor/Controls/RadioButton/MaterialRadioButton.cs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 99 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/ReaLTaiizor/Controls/CheckBox/MaterialCheckBox.cs:248` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (8 lines × 3) src/ReaLTaiizor/Controls/DatePicker/HopeDatePicker.cs:305— src/ReaLTaiizor/Controls/DatePicker/HopeDatePicker.cs:305-312 | src/ReaLTaiizor/Controls/Numeric/HopeNumeric.cs:180-187 | src/ReaLTaiizor/Controls/RichTextBox/HopeRichTextBox.cs:124-131 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `src/ReaLTaiizor/Controls/DatePicker/HopeDatePicker.cs:303` calls `OnPaint` and `src/ReaLTaiizor/Controls/Numeric/HopeNumeric.cs:179` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (8 lines × 3) src/ReaLTaiizor/Controls/Panel/ParrotGradientPanel.cs:175— src/ReaLTaiizor/Controls/Panel/ParrotGradientPanel.cs:175-182 | src/ReaLTaiizor/Controls/PictureBox/ParrotPictureBox.cs:181-188 | src/ReaLTaiizor/Controls/Progress/ParrotFlatProgressBar.cs:259-268 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `src/ReaLTaiizor/Controls/Panel/ParrotGradientPanel.cs:173` calls `OnPaint` and `src/ReaLTaiizor/Controls/Progress/ParrotFlatProgressBar.cs:257` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (8 lines × 3) src/ReaLTaiizor/Controls/Switch/ParrotSwitch.cs:152— src/ReaLTaiizor/Controls/Switch/ParrotSwitch.cs:152-159 | src/ReaLTaiizor/Controls/Switch/ParrotSwitch.cs:176-183 | src/ReaLTaiizor/Controls/Switch/ParrotSwitch.cs:226-233 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/ReaLTaiizor/Controls/Switch/ParrotSwitch.cs:152` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `src/ReaLTaiizor/Controls/Switch/ParrotSwitch.cs:226` calls `FillPie`, `SolidBrush`, `FromArgb` and `src/ReaLTaiizor/Controls/Switch/ParrotSwitch.cs:152` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (8 lines × 3) src/ReaLTaiizor/Forms/Panel/ParrotForm.cs:717— src/ReaLTaiizor/Forms/Panel/ParrotForm.cs:717-724 | src/ReaLTaiizor/Forms/Panel/ParrotForm.cs:743-750 | src/ReaLTaiizor/Forms/Panel/ParrotForm.cs:768-775 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/ReaLTaiizor/Forms/Panel/ParrotForm.cs:717` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `src/ReaLTaiizor/Forms/Panel/ParrotForm.cs:725` calls `DrawLine`, `Pen` and `src/ReaLTaiizor/Forms/Panel/ParrotForm.cs:777` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (8 lines × 3) src/ReaLTaiizor/Forms/Container/DungeonForm.cs:152— src/ReaLTaiizor/Forms/Container/DungeonForm.cs:152-159 | src/ReaLTaiizor/Forms/Container/FormTheme.cs:131-138 | src/ReaLTaiizor/Forms/Container/ThemeForm.cs:159-166 — before extracting anything, compare `src/ReaLTaiizor/Forms/Container/DungeonForm.cs` and `src/ReaLTaiizor/Forms/Container/FormTheme.cs` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 218 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (8 lines × 3) src/ReaLTaiizor/Util/Air.cs:842— src/ReaLTaiizor/Util/Air.cs:842-849 | src/ReaLTaiizor/Util/Moon.cs:835-842 | src/ReaLTaiizor/Util/Space.cs:837-844 — before extracting anything, compare `src/ReaLTaiizor/Util/Air.cs` and `src/ReaLTaiizor/Util/Moon.cs` as WHOLE FILES: this scan already matched 40 separate duplicated blocks between them, totalling at least 661 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (8 lines × 3) src/ReaLTaiizor/Util/Air.cs:1916— src/ReaLTaiizor/Util/Air.cs:1916-1923 | src/ReaLTaiizor/Util/Moon.cs:1915-1922 | src/ReaLTaiizor/Util/Space.cs:1913-1920 — before extracting anything, compare `src/ReaLTaiizor/Util/Air.cs` and `src/ReaLTaiizor/Util/Moon.cs` as WHOLE FILES: this scan already matched 40 separate duplicated blocks between them, totalling at least 661 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
X18 · Disposal-pattern correctness· Disposable created and abandoned in the method that made it · ×12
Disposable created and abandoned in the method that made it demo/ReaLTaiizor.UI/ReaLTaiizor.UI/Form15.cs:17— `FL` is a `FrameLost`, which implements `IDisposable`, and it is created here (line 17). Every use of it in `LostAcceptButton1_Click` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var FL = …;`), which releases it at the end of the scope on every path including a throw.
Disposable created and abandoned in the method that made it demo/ReaLTaiizor.UI/ReaLTaiizor.UI/Form15.cs:26— `TFL` is a `ToolFrameLost`, which implements `IDisposable`, and it is created here (line 26). Every use of it in `LostCancelButton1_Click` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var TFL = …;`), which releases it at the end of the scope on every path including a throw.
Disposable created and abandoned in the method that made it demo/ReaLTaiizor.UI/ReaLTaiizor.UI/Form17.cs:245— `SnackBarMessage` is a `MaterialSnackBar`, which implements `IDisposable`, and it is created here (line 245). Every use of it in `MaterialTextBox2_LeadingIconClick` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var SnackBarMessage = …;`), which releases it at the end of the scope on every path including a throw.
Disposable created and abandoned in the method that made it demo/ReaLTaiizor.UI/ReaLTaiizor.UI/Form17.cs:252— `SnackBarMessage` is a `MaterialSnackBar`, which implements `IDisposable`, and it is created here (line 252). Every use of it in `MaterialButton6_Click` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var SnackBarMessage = …;`), which releases it at the end of the scope on every path including a throw.
Disposable created and abandoned in the method that made it demo/ReaLTaiizor.UI/ReaLTaiizor.UI/Form17.cs:326— `SnackBarMessage` is a `MaterialSnackBar`, which implements `IDisposable`, and it is created here (line 326). Every use of it in `MaterialTextBox21_LeadingIconClick` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var SnackBarMessage = …;`), which releases it at the end of the scope on every path including a throw.
Disposable created and abandoned in the method that made it demo/ReaLTaiizor.UI/ReaLTaiizor.UI/Form17.cs:332— `SnackBarMessage` is a `MaterialSnackBar`, which implements `IDisposable`, and it is created here (line 332). Every use of it in `MaterialTextBox21_TrailingIconClick` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var SnackBarMessage = …;`), which releases it at the end of the scope on every path including a throw.
Disposable created and abandoned in the method that made it demo/ReaLTaiizor.UI/ReaLTaiizor.UI/Form17.cs:343— `materialDialog` is a `MaterialDialog`, which implements `IDisposable`, and it is created here (line 343). Every use of it in `MaterialButton25_Click` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var materialDialog = …;`), which releases it at the end of the scope on every path including a throw.
Disposable created and abandoned in the method that made it demo/ReaLTaiizor.UI/ReaLTaiizor.UI/Form17.cs:346— `SnackBarMessage` is a `MaterialSnackBar`, which implements `IDisposable`, and it is created here (line 346). Every use of it in `MaterialButton25_Click` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var SnackBarMessage = …;`), which releases it at the end of the scope on every path including a throw.
Disposable created and abandoned in the method that made it demo/ReaLTaiizor.UI/ReaLTaiizor.UI/Form21.cs:176— `test` is a `DialogControls`, which implements `IDisposable`, and it is created here (line 176). Every use of it in `Dialog_Click` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var test = …;`), which releases it at the end of the scope on every path including a throw.
Disposable created and abandoned in the method that made it demo/ReaLTaiizor.UI/ReaLTaiizor.UI/Forms/FormManager.cs:71— `newForm` is a `Form`, which implements `IDisposable`, and it is created here (line 71). Every use of it in `Button_Click` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var newForm = …;`), which releases it at the end of the scope on every path including a throw.
Disposable created and abandoned in the method that made it ready/ReaLTaiizor.AppLocker/ReaLTaiizor.AppLocker/AppLocker.cs:40— `AP` is a `AppPassword`, which implements `IDisposable`, and it is created here (line 40). Every use of it in `RAL_Tick` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var AP = …;`), which releases it at the end of the scope on every path including a throw.
Disposable created and abandoned in the method that made it ready/ReaLTaiizor.AppLocker/ReaLTaiizor.AppLocker/RunApp.cs:26— `AP` is a `AppPassword`, which implements `IDisposable`, and it is created here (line 26). Every use of it in `LOCK_Click` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var AP = …;`), which releases it at the end of the scope on every path including a throw.
MethodTooLong: ParrotForm.RefreshUI src/ReaLTaiizor/Forms/Panel/ParrotForm.cs:293— MethodTooLong — RefreshUI runs 259 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 159 over it, 2.59× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: ObjectAnimator.StandardAnimate src/ReaLTaiizor/Animate/Parrot/ObjectAnimator.cs:62— MethodTooLong — StandardAnimate runs 201 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 101 over it, 2.01× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: ParrotBarGraph.OnPaint src/ReaLTaiizor/Controls/Graph/ParrotBarGraph.cs:198— MethodTooLong — OnPaint runs 188 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 88 over it, 1.88× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: ThunderControlBox.OnPaint src/ReaLTaiizor/Controls/ControlBox/ThunderControlBox.cs:147— MethodTooLong — OnPaint runs 173 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 73 over it, 1.73× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: MaterialFlexibleForm.InitializeComponent src/ReaLTaiizor/Forms/Form/MaterialFlexibleForm.cs:65— MethodTooLong — InitializeComponent runs 161 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 61 over it, 1.61× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: MaterialForm.OnPaint src/ReaLTaiizor/Forms/Form/MaterialForm.cs:1232— MethodTooLong — OnPaint runs 135 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 35 over it, 1.35× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: MaterialTextBoxEdit.OnPaint src/ReaLTaiizor/Controls/TextBoxEdit/MaterialTextBoxEdit.cs:983— MethodTooLong — OnPaint runs 114 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 14 over it, 1.14× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: MetroBadge.ApplyTheme src/ReaLTaiizor/Controls/Badge/MetroBadge.cs:493— MethodTooLong — ApplyTheme runs 112 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 12 over it, 1.12× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: MaterialForm.AddDrawerOverlayForm src/ReaLTaiizor/Forms/Form/MaterialForm.cs:550— MethodTooLong — AddDrawerOverlayForm runs 110 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 10 over it, 1.10× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: MaterialMaskedTextBox.OnPaint src/ReaLTaiizor/Controls/TextBox/MaterialMaskedTextBox.cs:1032— MethodTooLong — OnPaint runs 109 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 9 over it, 1.09× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: MaterialTextBox.OnPaint src/ReaLTaiizor/Controls/TextBox/MaterialTextBox.cs:576— MethodTooLong — OnPaint runs 109 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 9 over it, 1.09× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
Duplicated block (13 lines × 2) src/ReaLTaiizor/Controls/Button/HopeRoundButton.cs:48— src/ReaLTaiizor/Controls/Button/HopeRoundButton.cs:48-60 | src/ReaLTaiizor/Controls/Button/HopeSimpleButton.cs:49-61 — before extracting anything, compare `src/ReaLTaiizor/Controls/Button/HopeRoundButton.cs` and `src/ReaLTaiizor/Controls/Button/HopeSimpleButton.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 40 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (13 lines × 2) src/ReaLTaiizor/Controls/Tile/MetroTile.cs:150— src/ReaLTaiizor/Controls/Tile/MetroTile.cs:150-162 | src/ReaLTaiizor/Controls/Tile/MetroTile.cs:168-180 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/ReaLTaiizor/Controls/Tile/MetroTile.cs:150` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (13 lines × 2) src/ReaLTaiizor/Util/Royal.cs:495— src/ReaLTaiizor/Util/Royal.cs:495-507 | src/ReaLTaiizor/Util/Royal.cs:531-543 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/ReaLTaiizor/Util/Royal.cs:495` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (13 lines × 2) src/ReaLTaiizor/Controls/CheckBox/CyberCheckBox.cs:692— src/ReaLTaiizor/Controls/CheckBox/CyberCheckBox.cs:692-704 | src/ReaLTaiizor/Controls/RadioButton/CyberRadioButton.cs:761-773 — before extracting anything, compare `src/ReaLTaiizor/Controls/CheckBox/CyberCheckBox.cs` and `src/ReaLTaiizor/Controls/RadioButton/CyberRadioButton.cs` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 249 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (13 lines × 2) src/ReaLTaiizor/Controls/ComboBox/PoisonComboBox.cs:684— src/ReaLTaiizor/Controls/ComboBox/PoisonComboBox.cs:684-696 | src/ReaLTaiizor/Controls/DateTime/PoisonDateTime.cs:673-685 — before extracting anything, compare `src/ReaLTaiizor/Controls/ComboBox/PoisonComboBox.cs` and `src/ReaLTaiizor/Controls/DateTime/PoisonDateTime.cs` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 124 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (13 lines × 2) src/ReaLTaiizor/Controls/Progress/ParrotFlatProgressBar.cs:282— src/ReaLTaiizor/Controls/Progress/ParrotFlatProgressBar.cs:282-294 | src/ReaLTaiizor/Controls/Slider/ParrotSlider.cs:379-392 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `src/ReaLTaiizor/Controls/Progress/ParrotFlatProgressBar.cs:282` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (13 lines × 2) src/ReaLTaiizor/Controls/TextBox/MaterialMaskedTextBox.cs:1572— src/ReaLTaiizor/Controls/TextBox/MaterialMaskedTextBox.cs:1572-1584 | src/ReaLTaiizor/Controls/TextBoxEdit/MaterialTextBoxEdit.cs:1530-1542 — before extracting anything, compare `src/ReaLTaiizor/Controls/TextBox/MaterialMaskedTextBox.cs` and `src/ReaLTaiizor/Controls/TextBoxEdit/MaterialTextBoxEdit.cs` as WHOLE FILES: this scan already matched 27 separate duplicated blocks between them, totalling at least 574 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/ReaLTaiizor/Controls/TextBox/MaterialMaskedTextBox.cs:1572` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (13 lines × 2) src/ReaLTaiizor/Controls/CheckBox/AloneCheckBox.cs:82— src/ReaLTaiizor/Controls/CheckBox/AloneCheckBox.cs:82-94 | src/ReaLTaiizor/Controls/RadioButton/AloneRadioButton.cs:77-89 — before extracting anything, compare `src/ReaLTaiizor/Controls/CheckBox/AloneCheckBox.cs` and `src/ReaLTaiizor/Controls/RadioButton/AloneRadioButton.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 36 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (13 lines × 2) src/ReaLTaiizor/Controls/ControlBox/ControlBox.cs:198— src/ReaLTaiizor/Controls/ControlBox/ControlBox.cs:198-210 | src/ReaLTaiizor/Controls/ControlBox/NightControlBox.cs:352-364 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (13 lines × 2) src/ReaLTaiizor/Controls/GroupBox/CyberGroupBox.cs:432— src/ReaLTaiizor/Controls/GroupBox/CyberGroupBox.cs:432-444 | src/ReaLTaiizor/Controls/Switch/CyberSwitch.cs:501-513 — before extracting anything, compare `src/ReaLTaiizor/Controls/GroupBox/CyberGroupBox.cs` and `src/ReaLTaiizor/Controls/Switch/CyberSwitch.cs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 132 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (13 lines × 2) src/ReaLTaiizor/Controls/TextBox/MaterialMaskedTextBox.cs:1588— src/ReaLTaiizor/Controls/TextBox/MaterialMaskedTextBox.cs:1588-1600 | src/ReaLTaiizor/Controls/TextBoxEdit/MaterialTextBoxEdit.cs:1546-1558 — before extracting anything, compare `src/ReaLTaiizor/Controls/TextBox/MaterialMaskedTextBox.cs` and `src/ReaLTaiizor/Controls/TextBoxEdit/MaterialTextBoxEdit.cs` as WHOLE FILES: this scan already matched 27 separate duplicated blocks between them, totalling at least 574 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (11 lines × 2) src/ReaLTaiizor/Forms/Container/DungeonForm.cs:453— src/ReaLTaiizor/Forms/Container/DungeonForm.cs:453-463 | src/ReaLTaiizor/Forms/Container/ThemeForm.cs:461-471 — before extracting anything, compare `src/ReaLTaiizor/Forms/Container/DungeonForm.cs` and `src/ReaLTaiizor/Forms/Container/ThemeForm.cs` as WHOLE FILES: this scan already matched 17 separate duplicated blocks between them, totalling at least 286 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/ReaLTaiizor/Forms/Container/DungeonForm.cs:453` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (11 lines × 2) src/ReaLTaiizor/Controls/Button/MetroButton.cs:196— src/ReaLTaiizor/Controls/Button/MetroButton.cs:196-206 | src/ReaLTaiizor/Controls/Tile/MetroTile.cs:202-212 — before extracting anything, compare `src/ReaLTaiizor/Controls/Button/MetroButton.cs` and `src/ReaLTaiizor/Controls/Tile/MetroTile.cs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 50 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/ReaLTaiizor/Controls/Button/MetroButton.cs:196` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (11 lines × 2) src/ReaLTaiizor/Controls/ScrollBar/MaterialScrollBar.cs:437— src/ReaLTaiizor/Controls/ScrollBar/MaterialScrollBar.cs:437-447 | src/ReaLTaiizor/Controls/ScrollBar/PoisonScrollBar.cs:638-648 — before extracting anything, compare `src/ReaLTaiizor/Controls/ScrollBar/MaterialScrollBar.cs` and `src/ReaLTaiizor/Controls/ScrollBar/PoisonScrollBar.cs` as WHOLE FILES: this scan already matched 15 separate duplicated blocks between them, totalling at least 423 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (11 lines × 2) src/ReaLTaiizor/Controls/Progress/ForeverProgressBar.cs:154— src/ReaLTaiizor/Controls/Progress/ForeverProgressBar.cs:154-164 | src/ReaLTaiizor/Controls/Progress/ForeverProgressBar.cs:193-203 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (11 lines × 2) src/ReaLTaiizor/Controls/Button/ChatButtonLeft.cs:213— src/ReaLTaiizor/Controls/Button/ChatButtonLeft.cs:213-223 | src/ReaLTaiizor/Controls/Button/ChatButtonRight.cs:200-210 — before extracting anything, compare `src/ReaLTaiizor/Controls/Button/ChatButtonLeft.cs` and `src/ReaLTaiizor/Controls/Button/ChatButtonRight.cs` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 217 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `src/ReaLTaiizor/Controls/Button/ChatButtonRight.cs:214` calls `OnResize` and `src/ReaLTaiizor/Controls/Button/ChatButtonLeft.cs:227` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (11 lines × 2) src/ReaLTaiizor/Controls/Button/ParrotButton.cs:47— src/ReaLTaiizor/Controls/Button/ParrotButton.cs:47-57 | src/ReaLTaiizor/Controls/Button/ParrotSuperButton.cs:37-47 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (11 lines × 2) src/ReaLTaiizor/Controls/RadioButton/AloneRadioButton.cs:130— src/ReaLTaiizor/Controls/RadioButton/AloneRadioButton.cs:130-140 | src/ReaLTaiizor/Controls/RadioButton/AloneRadioButton.cs:149-159 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/ReaLTaiizor/Controls/RadioButton/AloneRadioButton.cs:130` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (11 lines × 2) src/ReaLTaiizor/ReaLTaiizor.cs:413— src/ReaLTaiizor/ReaLTaiizor.cs:413-423 | src/ReaLTaiizor/ReaLTaiizor.cs:439-449 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (11 lines × 2) src/ReaLTaiizor/Controls/CheckBox/AloneCheckBox.cs:137— src/ReaLTaiizor/Controls/CheckBox/AloneCheckBox.cs:137-147 | src/ReaLTaiizor/Controls/CheckBox/AloneCheckBox.cs:156-166 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/ReaLTaiizor/Controls/CheckBox/AloneCheckBox.cs:137` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (11 lines × 2) src/ReaLTaiizor/Controls/TextBox/BigTextBox.cs:184— src/ReaLTaiizor/Controls/TextBox/BigTextBox.cs:184-194 | src/ReaLTaiizor/Controls/TextBox/SmallTextBox.cs:162-172 — before extracting anything, compare `src/ReaLTaiizor/Controls/TextBox/BigTextBox.cs` and `src/ReaLTaiizor/Controls/TextBox/SmallTextBox.cs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 64 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (11 lines × 2) src/ReaLTaiizor/Controls/TextBox/MaterialMultiLineTextBox.cs:57— src/ReaLTaiizor/Controls/TextBox/MaterialMultiLineTextBox.cs:57-67 | src/ReaLTaiizor/Controls/TextBox/MaterialTextBox.cs:211-221 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
IC1 · Incompleteness & stubs· Both branches open with the same statements · ×11
Both branches open with the same statements — the condition does not decide them src/ReaLTaiizor/Controls/Bar/ParrotNavigationBar.cs:43— The first 2 statements of the `if` and of the `else` are identical, so they run on both paths regardless of the condition. Lift them above the `if` — leaving them duplicated inside makes the branches read as though they handled this differently.
Both branches open with the same statements — the condition does not decide them src/ReaLTaiizor/Controls/ControlBox/MetroControlBox.cs:447— The first 2 statements of the `if` and of the `else` are identical, so they run on both paths regardless of the condition. Lift them above the `if` — leaving them duplicated inside makes the branches read as though they handled this differently.
Both branches open with the same statements — the condition does not decide them src/ReaLTaiizor/Controls/ControlBox/NightControlBox.cs:269— The first 2 statements of the `if` and of the `else` are identical, so they run on both paths regardless of the condition. Lift them above the `if` — leaving them duplicated inside makes the branches read as though they handled this differently.
Both branches open with the same statements — the condition does not decide them src/ReaLTaiizor/Controls/ControlBox/ThunderControlBox.cs:176— The first 2 statements of the `if` and of the `else` are identical, so they run on both paths regardless of the condition. Lift them above the `if` — leaving them duplicated inside makes the branches read as though they handled this differently.
Both branches open with the same statements — the condition does not decide them src/ReaLTaiizor/Controls/ControlBox/ThunderControlBox.cs:208— The first 3 statements of the `if` and of the `else` are identical, so they run on both paths regardless of the condition. Lift them above the `if` — leaving them duplicated inside makes the branches read as though they handled this differently.
Both branches open with the same statements — the condition does not decide them src/ReaLTaiizor/Controls/ControlBox/ThunderControlBox.cs:237— The first 3 statements of the `if` and of the `else` are identical, so they run on both paths regardless of the condition. Lift them above the `if` — leaving them duplicated inside makes the branches read as though they handled this differently.
Both branches open with the same statements — the condition does not decide them src/ReaLTaiizor/Controls/ControlBox/ThunderControlBox.cs:263— The first 4 statements of the `if` and of the `else` are identical, so they run on both paths regardless of the condition. Lift them above the `if` — leaving them duplicated inside makes the branches read as though they handled this differently.
Both branches open with the same statements — the condition does not decide them src/ReaLTaiizor/Controls/ControlBox/ThunderControlBox.cs:270— The first 3 statements of the `if` and of the `else` are identical, so they run on both paths regardless of the condition. Lift them above the `if` — leaving them duplicated inside makes the branches read as though they handled this differently.
Both branches open with the same statements — the condition does not decide them src/ReaLTaiizor/Controls/ControlBox/ThunderControlBox.cs:301— The first 3 statements of the `if` and of the `else` are identical, so they run on both paths regardless of the condition. Lift them above the `if` — leaving them duplicated inside makes the branches read as though they handled this differently.
Both branches open with the same statements — the condition does not decide them src/ReaLTaiizor/Controls/ControlBox/ThunderControlBox.cs:330— The first 3 statements of the `if` and of the `else` are identical, so they run on both paths regardless of the condition. Lift them above the `if` — leaving them duplicated inside makes the branches read as though they handled this differently.
Both branches open with the same statements — the condition does not decide them src/ReaLTaiizor/Controls/ControlBox/ThunderControlBox.cs:358— The first 3 statements of the `if` and of the `else` are identical, so they run on both paths regardless of the condition. Lift them above the `if` — leaving them duplicated inside makes the branches read as though they handled this differently.
IC1 · Incompleteness & stubs· Both branches are identical · ×11
Both branches are identical — the condition decides nothing src/ReaLTaiizor/Controls/Button/CrownButton.cs:342— Both arms of `_isDefault ? … : …` are `ThemeProvider.Theme.Colors.DarkBackground`, so no input can make the condition matter. Implement the distinction that was intended, or drop the condition.
Both branches are identical — the condition decides nothing src/ReaLTaiizor/Controls/Button/ParrotButton.cs:333— The `if` and its `else` contain the same 1 statement, so no input can make the condition matter. Implement the distinction that was intended, or drop the branch and keep the body.
Both branches are identical — the condition decides nothing src/ReaLTaiizor/Controls/Button/ParrotButton.cs:395— The `if` and its `else` contain the same 1 statement, so no input can make the condition matter. Implement the distinction that was intended, or drop the branch and keep the body.
Both branches are identical — the condition decides nothing src/ReaLTaiizor/Controls/Button/ParrotButton.cs:403— The `if` and its `else` contain the same 1 statement, so no input can make the condition matter. Implement the distinction that was intended, or drop the branch and keep the body.
Both branches are identical — the condition decides nothing src/ReaLTaiizor/Controls/CheckBox/CheckBox.cs:120— The `if` and its `else` contain the same 2 statements, so no input can make the condition matter. Implement the distinction that was intended, or drop the branch and keep the body.
Both branches are identical — the condition decides nothing src/ReaLTaiizor/Controls/Numeric/DungeonNumeric.cs:137— The `if` and its `else` contain the same 1 statement, so no input can make the condition matter. Implement the distinction that was intended, or drop the branch and keep the body.
Both branches are identical — the condition decides nothing src/ReaLTaiizor/Controls/TabPage/TabPage.cs:265— Both arms of `TabIndex == 0 ? … : …` are `1`, so no input can make the condition matter. Implement the distinction that was intended, or drop the condition.
Both branches are identical — the condition decides nothing src/ReaLTaiizor/Controls/TabPage/TabPage.cs:287— Both arms of `TabIndex == 0 ? … : …` are `1`, so no input can make the condition matter. Implement the distinction that was intended, or drop the condition.
Both branches are identical — the condition decides nothing src/ReaLTaiizor/Manager/MaterialSkinManager.cs:351— Both arms of `Theme == Themes.LIGHT ? … : …` are `BACKGROUND_HOVER_RED`, so no input can make the condition matter. Implement the distinction that was intended, or drop the condition.
Both branches are identical — the condition decides nothing src/ReaLTaiizor/Manager/MaterialSkinManager.cs:352— Both arms of `Theme == Themes.LIGHT ? … : …` are `BACKGROUND_HOVER_RED_BRUSH`, so no input can make the condition matter. Implement the distinction that was intended, or drop the condition.
Both branches are identical — the condition decides nothing src/ReaLTaiizor/Manager/MaterialSkinManager.cs:353— Both arms of `Theme == Themes.LIGHT ? … : …` are `BACKGROUND_DOWN_RED_BRUSH`, so no input can make the condition matter. Implement the distinction that was intended, or drop the condition.
Stateful shared instance: DelayedCall src/ReaLTaiizor/Animate/Poison/DelayedCall.cs:13— `DelayedCall` keeps one instance of itself in the static `dcList`, so that one instance serves the whole process and is shared by every thread that reaches it — and it mutates instance state outside any lock (oldData; e.g. `oldData` at line 82).
Stateful shared instance: PoisonTaskWindow src/ReaLTaiizor/Controls/Window/PoisonTaskWindow.cs:20— `PoisonTaskWindow` keeps one instance of itself in the static `singletonWindow`, so that one instance serves the whole process and is shared by every thread that reaches it — and it mutates instance state outside any lock (isInitialized, timer, elapsedTime, progressWidth; e.g. `isInitialized` at line 169).
Stateful shared instance: MaterialSkinManager src/ReaLTaiizor/Manager/MaterialSkinManager.cs:24— `MaterialSkinManager` keeps one instance of itself in the static `<Instance>k__BackingField`, so that one instance serves the whole process and is shared by every thread that reaches it — and it mutates instance state outside any lock (_formsToManage; e.g. `_formsToManage` at line 546).
Stateful shared instance: PrecisionTimerAir src/ReaLTaiizor/Util/Air.cs:2536— `PrecisionTimerAir` is not registered, but `ThemeShareAir` creates it and keeps it in the static `ThemeTimer`, so that one instance serves the whole process and is shared by every thread that reaches it — and it mutates instance state outside any lock (TimerCallback, Handle, Enabled; e.g. `TimerCallback` at line 2558).
Stateful shared instance: MaterialMouseWheelRedirector src/ReaLTaiizor/Util/Material.cs:1325— `MaterialMouseWheelRedirector` keeps one instance of itself in the static `instance`, so that one instance serves the whole process and is shared by every thread that reaches it — and it mutates instance state outside any lock (currentControl; e.g. `currentControl` at line 1393).
Stateful shared instance: PrecisionTimerMoon src/ReaLTaiizor/Util/Moon.cs:2541— `PrecisionTimerMoon` is not registered, but `ThemeShareMoon` creates it and keeps it in the static `ThemeTimer`, so that one instance serves the whole process and is shared by every thread that reaches it — and it mutates instance state outside any lock (TimerCallback, Handle, Enabled; e.g. `TimerCallback` at line 2563).
Stateful shared instance: PrecisionTimerSpace src/ReaLTaiizor/Util/Space.cs:2540— `PrecisionTimerSpace` is not registered, but `ThemeShareSpace` creates it and keeps it in the static `ThemeTimer`, so that one instance serves the whole process and is shared by every thread that reaches it — and it mutates instance state outside any lock (TimerCallback, Handle, Enabled; e.g. `TimerCallback` at line 2562).
Stateful shared instance: PoisonPanel src/ReaLTaiizor/Controls/Panel/PoisonPanel.cs:21— `PoisonPanel` is not registered, but the singleton `PoisonTaskWindow` creates it and keeps it in `controlContainer`, so one instance outlives every request and is shared by every caller that reaches it — and it mutates instance state outside any lock (HorizontalScrollbar, VerticalScrollbar; e.g. `HorizontalScrollbar` at line 198).
Stateful shared instance: PoisonScrollBar src/ReaLTaiizor/Controls/ScrollBar/PoisonScrollBar.cs:22— `PoisonScrollBar` is not registered, but the singleton `PoisonPanel` creates it and keeps it in `VerticalPoisonScrollbar`, so one instance outlives every request and is shared by every caller that reaches it — and it mutates instance state outside any lock (isFirstScrollEventHorizontal, isFirstScrollEventVertical, scrollOrientation, curValue, largeChange, dontUpdateColor; e.g. `isFirstScrollEventHorizontal` at line 163).
D4 · Code Duplication· Members sharing a duplicated core (6 members, 50+ identical tokens) · ×9
Members sharing a duplicated core (6 members, 50+ identical tokens) src/ReaLTaiizor/Controls/GroupBox/CyberGroupBox.cs:517— src/ReaLTaiizor/Controls/GroupBox/CyberGroupBox.cs:517-537 | src/ReaLTaiizor/Controls/Progress/CyberProgressBar.cs:677-709 | src/ReaLTaiizor/Controls/RichTextBox/CyberRichTextBox.cs:524-540 | src/ReaLTaiizor/Controls/ScrollBar/CyberScrollBar.cs:770-793 | src/ReaLTaiizor/Controls/Switch/CyberSwitch.cs:598-621 | src/ReaLTaiizor/Controls/TextBox/CyberTextBox.cs:573-589 — These 6 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 6 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 6 times.
Members sharing a duplicated core (6 members, 50+ identical tokens) src/ReaLTaiizor/Forms/Container/DungeonForm.cs:226— src/ReaLTaiizor/Forms/Container/DungeonForm.cs:226-239 | src/ReaLTaiizor/Forms/Container/FormTheme.cs:205-218 | src/ReaLTaiizor/Forms/Container/ThemeForm.cs:234-247 | src/ReaLTaiizor/Util/Air.cs:150-164 | src/ReaLTaiizor/Util/Moon.cs:148-162 | src/ReaLTaiizor/Util/Space.cs:150-164 — These 6 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 6 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 6 times.
Members sharing a duplicated core (6 members, 50+ identical tokens) src/ReaLTaiizor/Forms/Container/DungeonForm.cs:343— src/ReaLTaiizor/Forms/Container/DungeonForm.cs:343-349 | src/ReaLTaiizor/Forms/Container/FormTheme.cs:322-328 | src/ReaLTaiizor/Forms/Container/ThemeForm.cs:352-358 | src/ReaLTaiizor/Util/Air.cs:413-419 | src/ReaLTaiizor/Util/Moon.cs:406-412 | src/ReaLTaiizor/Util/Space.cs:408-414 — These 6 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 6 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 6 times.
Members sharing a duplicated core (6 members, 50+ identical tokens) src/ReaLTaiizor/Forms/Container/DungeonForm.cs:352— src/ReaLTaiizor/Forms/Container/DungeonForm.cs:352-390 | src/ReaLTaiizor/Forms/Container/FormTheme.cs:331-369 | src/ReaLTaiizor/Forms/Container/ThemeForm.cs:361-399 | src/ReaLTaiizor/Util/Air.cs:422-460 | src/ReaLTaiizor/Util/Moon.cs:415-453 | src/ReaLTaiizor/Util/Space.cs:417-455 — These 6 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 6 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 6 times.
Members sharing a duplicated core (6 members, 50+ identical tokens) src/ReaLTaiizor/Util/Air.cs:736— src/ReaLTaiizor/Util/Air.cs:736-762 | src/ReaLTaiizor/Util/Air.cs:1795-1821 | src/ReaLTaiizor/Util/Moon.cs:729-755 | src/ReaLTaiizor/Util/Moon.cs:1794-1820 | src/ReaLTaiizor/Util/Space.cs:731-757 | src/ReaLTaiizor/Util/Space.cs:1792-1818 — These 6 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 6 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 6 times.
Members sharing a duplicated core (6 members, 50+ identical tokens) src/ReaLTaiizor/Util/Air.cs:1123— src/ReaLTaiizor/Util/Air.cs:1123-1144 | src/ReaLTaiizor/Util/Air.cs:2096-2117 | src/ReaLTaiizor/Util/Moon.cs:1117-1138 | src/ReaLTaiizor/Util/Moon.cs:2098-2119 | src/ReaLTaiizor/Util/Space.cs:1119-1140 | src/ReaLTaiizor/Util/Space.cs:2095-2116 — These 6 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 6 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 6 times.
Members sharing a duplicated core (6 members, 50+ identical tokens) src/ReaLTaiizor/Util/Air.cs:1188— src/ReaLTaiizor/Util/Air.cs:1188-1209 | src/ReaLTaiizor/Util/Air.cs:2161-2182 | src/ReaLTaiizor/Util/Moon.cs:1181-1202 | src/ReaLTaiizor/Util/Moon.cs:2163-2184 | src/ReaLTaiizor/Util/Space.cs:1184-1205 | src/ReaLTaiizor/Util/Space.cs:2160-2181 — These 6 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 6 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 6 times.
Members sharing a duplicated core (6 members, 50+ identical tokens) src/ReaLTaiizor/Util/Air.cs:1376— src/ReaLTaiizor/Util/Air.cs:1376-1394 | src/ReaLTaiizor/Util/Air.cs:2349-2367 | src/ReaLTaiizor/Util/Moon.cs:1369-1387 | src/ReaLTaiizor/Util/Moon.cs:2353-2371 | src/ReaLTaiizor/Util/Space.cs:1373-1391 | src/ReaLTaiizor/Util/Space.cs:2350-2368 — These 6 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 6 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 6 times.
Members sharing a duplicated core (6 members, 50+ identical tokens) src/ReaLTaiizor/Util/Air.cs:1432— src/ReaLTaiizor/Util/Air.cs:1432-1440 | src/ReaLTaiizor/Util/Air.cs:2405-2413 | src/ReaLTaiizor/Util/Moon.cs:1426-1434 | src/ReaLTaiizor/Util/Moon.cs:2410-2418 | src/ReaLTaiizor/Util/Space.cs:1430-1438 | src/ReaLTaiizor/Util/Space.cs:2407-2415 — These 6 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 6 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 6 times.
Duplicated block (15 lines × 2) src/ReaLTaiizor/Controls/Button/PoisonButton.cs:236— src/ReaLTaiizor/Controls/Button/PoisonButton.cs:236-250 | src/ReaLTaiizor/Controls/Label/PoisonLabel.cs:244-258 — before extracting anything, compare `src/ReaLTaiizor/Controls/Button/PoisonButton.cs` and `src/ReaLTaiizor/Controls/Label/PoisonLabel.cs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 86 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/ReaLTaiizor/Controls/Button/PoisonButton.cs:236` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (15 lines × 2) src/ReaLTaiizor/Controls/ScrollBar/MaterialScrollBar.cs:887— src/ReaLTaiizor/Controls/ScrollBar/MaterialScrollBar.cs:887-901 | src/ReaLTaiizor/Controls/ScrollBar/PoisonScrollBar.cs:1087-1101 — before extracting anything, compare `src/ReaLTaiizor/Controls/ScrollBar/MaterialScrollBar.cs` and `src/ReaLTaiizor/Controls/ScrollBar/PoisonScrollBar.cs` as WHOLE FILES: this scan already matched 15 separate duplicated blocks between them, totalling at least 423 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/ReaLTaiizor/Controls/ScrollBar/MaterialScrollBar.cs:887` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
Duplicated block (15 lines × 2) src/ReaLTaiizor/Controls/Graph/ParrotBarGraph.cs:402— src/ReaLTaiizor/Controls/Graph/ParrotBarGraph.cs:402-416 | src/ReaLTaiizor/Controls/Graph/ParrotBarGraph.cs:438-452 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/ReaLTaiizor/Controls/Graph/ParrotBarGraph.cs:402` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (15 lines × 2) src/ReaLTaiizor/Controls/TextBox/BigTextBox.cs:291— src/ReaLTaiizor/Controls/TextBox/BigTextBox.cs:291-305 | src/ReaLTaiizor/Controls/TextBoxEdit/TextBoxEdit.cs:281-295 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `src/ReaLTaiizor/Controls/TextBox/BigTextBox.cs:291` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (15 lines × 2) ready/ReaLTaiizor.Hashing/ReaLTaiizor.Hashing/Hashing.cs:91— ready/ReaLTaiizor.Hashing/ReaLTaiizor.Hashing/Hashing.cs:91-105 | ready/ReaLTaiizor.Hashing/ReaLTaiizor.Hashing/Hashing.cs:141-155 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `ready/ReaLTaiizor.Hashing/ReaLTaiizor.Hashing/Hashing.cs:91` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (15 lines × 2) src/ReaLTaiizor/Controls/CheckBox/CyberCheckBox.cs:674— src/ReaLTaiizor/Controls/CheckBox/CyberCheckBox.cs:674-688 | src/ReaLTaiizor/Controls/RadioButton/CyberRadioButton.cs:743-757 — before extracting anything, compare `src/ReaLTaiizor/Controls/CheckBox/CyberCheckBox.cs` and `src/ReaLTaiizor/Controls/RadioButton/CyberRadioButton.cs` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 249 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (15 lines × 2) src/ReaLTaiizor/Controls/CheckBox/MetroCheckBox.cs:147— src/ReaLTaiizor/Controls/CheckBox/MetroCheckBox.cs:147-161 | src/ReaLTaiizor/Controls/RadioButton/MetroRadioButton.cs:147-161 — before extracting anything, compare `src/ReaLTaiizor/Controls/CheckBox/MetroCheckBox.cs` and `src/ReaLTaiizor/Controls/RadioButton/MetroRadioButton.cs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 90 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/ReaLTaiizor/Controls/CheckBox/MetroCheckBox.cs:147` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (15 lines × 2) src/ReaLTaiizor/Controls/RichTextBox/CyberRichTextBox.cs:321— src/ReaLTaiizor/Controls/RichTextBox/CyberRichTextBox.cs:321-335 | src/ReaLTaiizor/Controls/TextBox/CyberTextBox.cs:360-374 — before extracting anything, compare `src/ReaLTaiizor/Controls/RichTextBox/CyberRichTextBox.cs` and `src/ReaLTaiizor/Controls/TextBox/CyberTextBox.cs` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 202 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (15 lines × 2) src/ReaLTaiizor/Controls/CheckBox/CrownCheckBox.cs:213— src/ReaLTaiizor/Controls/CheckBox/CrownCheckBox.cs:213-227 | src/ReaLTaiizor/Controls/RadioButton/CrownRadioButton.cs:210-224 — before extracting anything, compare `src/ReaLTaiizor/Controls/CheckBox/CrownCheckBox.cs` and `src/ReaLTaiizor/Controls/RadioButton/CrownRadioButton.cs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 95 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (16 lines × 3) src/ReaLTaiizor/Controls/Notify/ForeverNotification.cs:219— src/ReaLTaiizor/Controls/Notify/ForeverNotification.cs:219-234 | src/ReaLTaiizor/Controls/Notify/ForeverNotification.cs:247-262 | src/ReaLTaiizor/Controls/Notify/ForeverNotification.cs:275-290 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (16 lines × 3) src/ReaLTaiizor/Controls/Badge/MetroBadge.cs:495— src/ReaLTaiizor/Controls/Badge/MetroBadge.cs:495-510 | src/ReaLTaiizor/Controls/Button/MetroDefaultButton.cs:170-185 | src/ReaLTaiizor/Controls/Ellipse/MetroEllipse.cs:183-198 — before extracting anything, compare `src/ReaLTaiizor/Controls/Badge/MetroBadge.cs` and `src/ReaLTaiizor/Controls/Button/MetroDefaultButton.cs` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 124 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/ReaLTaiizor/Controls/Badge/MetroBadge.cs:495` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (16 lines × 3) src/ReaLTaiizor/Controls/Close/ForeverClose.cs:142— src/ReaLTaiizor/Controls/Close/ForeverClose.cs:142-157 | src/ReaLTaiizor/Controls/Maximize/ForeverMaximize.cs:157-172 | src/ReaLTaiizor/Controls/Minimize/ForeverMinimize.cs:150-165 — before extracting anything, compare `src/ReaLTaiizor/Controls/Close/ForeverClose.cs` and `src/ReaLTaiizor/Controls/Maximize/ForeverMaximize.cs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 61 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/ReaLTaiizor/Controls/Close/ForeverClose.cs:142` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (16 lines × 3) src/ReaLTaiizor/Controls/TextBox/MaterialMaskedTextBox.cs:1271— src/ReaLTaiizor/Controls/TextBox/MaterialMaskedTextBox.cs:1271-1286 | src/ReaLTaiizor/Controls/TextBoxEdit/MaterialMultiLineTextBoxEdit.cs:952-967 | src/ReaLTaiizor/Controls/TextBoxEdit/MaterialTextBoxEdit.cs:1230-1245 — before extracting anything, compare `src/ReaLTaiizor/Controls/TextBox/MaterialMaskedTextBox.cs` and `src/ReaLTaiizor/Controls/TextBoxEdit/MaterialMultiLineTextBoxEdit.cs` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 164 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (16 lines × 3) src/ReaLTaiizor/Util/Air.cs:125— src/ReaLTaiizor/Util/Air.cs:125-140 | src/ReaLTaiizor/Util/Moon.cs:123-138 | src/ReaLTaiizor/Util/Space.cs:125-140 — before extracting anything, compare `src/ReaLTaiizor/Util/Air.cs` and `src/ReaLTaiizor/Util/Moon.cs` as WHOLE FILES: this scan already matched 40 separate duplicated blocks between them, totalling at least 661 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (16 lines × 3) src/ReaLTaiizor/Util/Air.cs:929— src/ReaLTaiizor/Util/Air.cs:929-944 | src/ReaLTaiizor/Util/Moon.cs:922-937 | src/ReaLTaiizor/Util/Space.cs:924-939 — before extracting anything, compare `src/ReaLTaiizor/Util/Air.cs` and `src/ReaLTaiizor/Util/Moon.cs` as WHOLE FILES: this scan already matched 40 separate duplicated blocks between them, totalling at least 661 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (16 lines × 3) src/ReaLTaiizor/Util/Air.cs:1520— src/ReaLTaiizor/Util/Air.cs:1520-1535 | src/ReaLTaiizor/Util/Moon.cs:1519-1534 | src/ReaLTaiizor/Util/Space.cs:1517-1532 — before extracting anything, compare `src/ReaLTaiizor/Util/Air.cs` and `src/ReaLTaiizor/Util/Moon.cs` as WHOLE FILES: this scan already matched 40 separate duplicated blocks between them, totalling at least 661 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (16 lines × 3) src/ReaLTaiizor/Util/Air.cs:2437— src/ReaLTaiizor/Util/Air.cs:2437-2452 | src/ReaLTaiizor/Util/Moon.cs:2441-2456 | src/ReaLTaiizor/Util/Space.cs:2439-2454 — before extracting anything, compare `src/ReaLTaiizor/Util/Air.cs` and `src/ReaLTaiizor/Util/Moon.cs` as WHOLE FILES: this scan already matched 40 separate duplicated blocks between them, totalling at least 661 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (16 lines × 3) src/ReaLTaiizor/Util/Air.cs:2437— src/ReaLTaiizor/Util/Air.cs:2437-2452 | src/ReaLTaiizor/Util/Moon.cs:2441-2456 | src/ReaLTaiizor/Util/Space.cs:2439-2454 — before extracting anything, compare `src/ReaLTaiizor/Util/Air.cs` and `src/ReaLTaiizor/Util/Moon.cs` as WHOLE FILES: this scan already matched 40 separate duplicated blocks between them, totalling at least 661 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
D4 · Code Duplication· Members sharing a duplicated core (5 members, 50+ identical tokens) · ×8
Members sharing a duplicated core (5 members, 50+ identical tokens) src/ReaLTaiizor/Controls/Button/Button.cs:33— src/ReaLTaiizor/Controls/Button/Button.cs:33-62 | src/ReaLTaiizor/Controls/Button/ChatButtonLeft.cs:36-65 | src/ReaLTaiizor/Controls/Button/ChatButtonRight.cs:34-62 | src/ReaLTaiizor/Controls/Button/DungeonButtonLeft.cs:35-64 | src/ReaLTaiizor/Controls/Button/DungeonButtonRight.cs:35-64 — These 5 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 5 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 5 times.
Members sharing a duplicated core (5 members, 50+ identical tokens) src/ReaLTaiizor/Controls/Button/Button.cs:65— src/ReaLTaiizor/Controls/Button/Button.cs:65-107 | src/ReaLTaiizor/Controls/Button/ChatButtonLeft.cs:68-110 | src/ReaLTaiizor/Controls/Button/ChatButtonRight.cs:65-107 | src/ReaLTaiizor/Controls/Button/DungeonButtonLeft.cs:67-109 | src/ReaLTaiizor/Controls/Button/DungeonButtonRight.cs:67-109 — These 5 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 5 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 5 times.
Members sharing a duplicated core (5 members, 50+ identical tokens) src/ReaLTaiizor/Controls/Button/Button.cs:291— src/ReaLTaiizor/Controls/Button/Button.cs:291-311 | src/ReaLTaiizor/Controls/CheckBox/CheckBox.cs:88-100 | src/ReaLTaiizor/Controls/Numeric/DungeonNumeric.cs:119-129 | src/ReaLTaiizor/Controls/Panel/Panel.cs:50-59 | src/ReaLTaiizor/Controls/TextBoxEdit/TextBoxEdit.cs:186-203 — These 5 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 5 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 5 times.
Members sharing a duplicated core (5 members, 50+ identical tokens) src/ReaLTaiizor/Controls/Button/Button.cs:314— src/ReaLTaiizor/Controls/Button/Button.cs:314-398 | src/ReaLTaiizor/Controls/Button/ChatButtonLeft.cs:251-303 | src/ReaLTaiizor/Controls/Button/ChatButtonRight.cs:238-290 | src/ReaLTaiizor/Controls/Button/DungeonButtonLeft.cs:252-310 | src/ReaLTaiizor/Controls/Button/DungeonButtonRight.cs:252-310 — These 5 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 5 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 5 times.
Members sharing a duplicated core (5 members, 50+ identical tokens) src/ReaLTaiizor/Controls/Button/SpaceButton.cs:16— src/ReaLTaiizor/Controls/Button/SpaceButton.cs:16-28 | src/ReaLTaiizor/Controls/Close/SpaceClose.cs:36-48 | src/ReaLTaiizor/Controls/Maximize/SpaceMaximize.cs:39-51 | src/ReaLTaiizor/Controls/Minimize/SpaceMinimize.cs:38-50 | src/ReaLTaiizor/Controls/Quest/SpaceQuest.cs:36-48 — These 5 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 5 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 5 times.
Members sharing a duplicated core (5 members, 50+ identical tokens) src/ReaLTaiizor/Controls/Button/SpaceButton.cs:51— src/ReaLTaiizor/Controls/Button/SpaceButton.cs:51-61 | src/ReaLTaiizor/Controls/Close/SpaceClose.cs:77-87 | src/ReaLTaiizor/Controls/Maximize/SpaceMaximize.cs:88-98 | src/ReaLTaiizor/Controls/Minimize/SpaceMinimize.cs:79-89 | src/ReaLTaiizor/Controls/Quest/SpaceQuest.cs:77-87 — These 5 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 5 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 5 times.
Members sharing a duplicated core (5 members, 50+ identical tokens) src/ReaLTaiizor/Controls/Close/ForeverClose.cs:123— src/ReaLTaiizor/Controls/Close/ForeverClose.cs:123-157 | src/ReaLTaiizor/Controls/ListBox/ForeverListBox.cs:203-227 | src/ReaLTaiizor/Controls/Maximize/ForeverMaximize.cs:131-172 | src/ReaLTaiizor/Controls/Minimize/ForeverMinimize.cs:131-165 | src/ReaLTaiizor/Controls/TreeView/ForeverTreeView.cs:76-97 — These 5 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 5 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 5 times.
Members sharing a duplicated core (5 members, 50+ identical tokens) src/ReaLTaiizor/Util/Royal.cs:351— src/ReaLTaiizor/Util/Royal.cs:351-367 | src/ReaLTaiizor/Util/Royal.cs:370-386 | src/ReaLTaiizor/Util/Royal.cs:389-405 | src/ReaLTaiizor/Util/Royal.cs:408-424 | src/ReaLTaiizor/Util/Royal.cs:427-443 — These 5 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 5 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 5 times.
Duplicated block (5 lines × 3) src/ReaLTaiizor/Controls/CheckBox/MetroCheckBox.cs:126— src/ReaLTaiizor/Controls/CheckBox/MetroCheckBox.cs:126-130 | src/ReaLTaiizor/Controls/ComboBox/MetroComboBox.cs:308-312 | src/ReaLTaiizor/Controls/RadioButton/MetroRadioButton.cs:126-130 — before extracting anything, compare `src/ReaLTaiizor/Controls/CheckBox/MetroCheckBox.cs` and `src/ReaLTaiizor/Controls/RadioButton/MetroRadioButton.cs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 90 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (5 lines × 3) src/ReaLTaiizor/Controls/TextBox/BigTextBox.cs:209— src/ReaLTaiizor/Controls/TextBox/BigTextBox.cs:209-213 | src/ReaLTaiizor/Controls/TextBox/DungeonTextBox.cs:171-175 | src/ReaLTaiizor/Controls/TextBox/SmallTextBox.cs:186-190 — before extracting anything, compare `src/ReaLTaiizor/Controls/TextBox/BigTextBox.cs` and `src/ReaLTaiizor/Controls/TextBox/SmallTextBox.cs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 64 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (5 lines × 3) src/ReaLTaiizor/Controls/ListView/PoisonListView.cs:570— src/ReaLTaiizor/Controls/ListView/PoisonListView.cs:570-574 | src/ReaLTaiizor/Controls/ListView/PoisonListView.cs:662-666 | src/ReaLTaiizor/Controls/ListView/PoisonListView.cs:778-783 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/ReaLTaiizor/Controls/ListView/PoisonListView.cs:570` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note first that the copies are not typed on the same thing: the declarations holding them bind `e` to `DrawListViewSubItemEventArgs` in one and `DrawListViewItemEventArgs` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
Duplicated block (5 lines × 3) src/ReaLTaiizor/Forms/Form/MaterialFlexibleForm.cs:814— src/ReaLTaiizor/Forms/Form/MaterialFlexibleForm.cs:814-818 | src/ReaLTaiizor/Forms/Form/MaterialFlexibleForm.cs:836-840 | src/ReaLTaiizor/Forms/Form/MaterialFlexibleForm.cs:879-883 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (5 lines × 3) src/ReaLTaiizor/ReaLTaiizor.cs:77— src/ReaLTaiizor/ReaLTaiizor.cs:77-81 | src/ReaLTaiizor/ReaLTaiizor.cs:97-102 | src/ReaLTaiizor/ReaLTaiizor.cs:118-122 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (5 lines × 3) src/ReaLTaiizor/Controls/Button/FoxButton.cs:30— src/ReaLTaiizor/Controls/Button/FoxButton.cs:30-34 | src/ReaLTaiizor/Controls/CheckBoxEdit/FoxCheckBoxEdit.cs:34-38 | src/ReaLTaiizor/Controls/RadioButton/FoxRadioButton.cs:31-35 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (5 lines × 3) src/ReaLTaiizor/Controls/Progress/RibbonProgressBarCenter.cs:238— src/ReaLTaiizor/Controls/Progress/RibbonProgressBarCenter.cs:238-242 | src/ReaLTaiizor/Controls/Progress/RibbonProgressBarLeft.cs:233-237 | src/ReaLTaiizor/Controls/Progress/RibbonProgressBarRight.cs:233-237 — before extracting anything, compare `src/ReaLTaiizor/Controls/Progress/RibbonProgressBarCenter.cs` and `src/ReaLTaiizor/Controls/Progress/RibbonProgressBarLeft.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 55 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (5 lines × 3) src/ReaLTaiizor/Controls/Slider/ParrotSlider.cs:353— src/ReaLTaiizor/Controls/Slider/ParrotSlider.cs:353-357 | src/ReaLTaiizor/Controls/Slider/ParrotSlider.cs:361-365 | src/ReaLTaiizor/Controls/Slider/ParrotSlider.cs:370-374 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/ReaLTaiizor/Controls/Slider/ParrotSlider.cs:353` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (16 lines × 2) src/ReaLTaiizor/Controls/CheckBox/AloneCheckBox.cs:123— src/ReaLTaiizor/Controls/CheckBox/AloneCheckBox.cs:123-138 | src/ReaLTaiizor/Controls/RadioButton/AloneRadioButton.cs:116-131 — before extracting anything, compare `src/ReaLTaiizor/Controls/CheckBox/AloneCheckBox.cs` and `src/ReaLTaiizor/Controls/RadioButton/AloneRadioButton.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 36 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/ReaLTaiizor/Controls/CheckBox/AloneCheckBox.cs:123` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (16 lines × 2) src/ReaLTaiizor/Controls/ComboBox/PoisonComboBox.cs:443— src/ReaLTaiizor/Controls/ComboBox/PoisonComboBox.cs:443-458 | src/ReaLTaiizor/Controls/DateTime/PoisonDateTime.cs:334-349 — before extracting anything, compare `src/ReaLTaiizor/Controls/ComboBox/PoisonComboBox.cs` and `src/ReaLTaiizor/Controls/DateTime/PoisonDateTime.cs` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 124 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/ReaLTaiizor/Controls/ComboBox/PoisonComboBox.cs:443` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (16 lines × 2) src/ReaLTaiizor/Extension/Metro/Methods.cs:29— src/ReaLTaiizor/Extension/Metro/Methods.cs:29-44 | src/ReaLTaiizor/Extension/Metro/Methods.cs:52-67 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `src/ReaLTaiizor/Extension/Metro/Methods.cs:51` calls `ImageFromBase64` and `src/ReaLTaiizor/Extension/Metro/Methods.cs:28` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (16 lines × 2) src/ReaLTaiizor/Controls/Graph/ParrotLineGraph.cs:313— src/ReaLTaiizor/Controls/Graph/ParrotLineGraph.cs:313-328 | src/ReaLTaiizor/Controls/Graph/ParrotLineGraph.cs:362-377 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/ReaLTaiizor/Controls/Graph/ParrotLineGraph.cs:313` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (16 lines × 2) src/ReaLTaiizor/Docking/Crown/CrownDockGroup.cs:769— src/ReaLTaiizor/Docking/Crown/CrownDockGroup.cs:769-784 | src/ReaLTaiizor/Docking/Crown/CrownDockGroup.cs:838-853 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (16 lines × 2) src/ReaLTaiizor/Controls/ScrollBar/MaterialScrollBar.cs:270— src/ReaLTaiizor/Controls/ScrollBar/MaterialScrollBar.cs:270-285 | src/ReaLTaiizor/Controls/ScrollBar/PoisonScrollBar.cs:374-389 — before extracting anything, compare `src/ReaLTaiizor/Controls/ScrollBar/MaterialScrollBar.cs` and `src/ReaLTaiizor/Controls/ScrollBar/PoisonScrollBar.cs` as WHOLE FILES: this scan already matched 15 separate duplicated blocks between them, totalling at least 423 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (16 lines × 2) src/ReaLTaiizor/Controls/TextBox/BigTextBox.cs:83— src/ReaLTaiizor/Controls/TextBox/BigTextBox.cs:83-99 | src/ReaLTaiizor/Controls/TextBox/SmallTextBox.cs:78-93 — before extracting anything, compare `src/ReaLTaiizor/Controls/TextBox/BigTextBox.cs` and `src/ReaLTaiizor/Controls/TextBox/SmallTextBox.cs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 64 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (9 lines × 3) src/ReaLTaiizor/Controls/Switch/ParrotSwitch.cs:140— src/ReaLTaiizor/Controls/Switch/ParrotSwitch.cs:140-148 | src/ReaLTaiizor/Controls/Switch/ParrotSwitch.cs:166-174 | src/ReaLTaiizor/Controls/Switch/ParrotSwitch.cs:214-222 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/ReaLTaiizor/Controls/Switch/ParrotSwitch.cs:140` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (9 lines × 3) src/ReaLTaiizor/Controls/ControlBox/ThunderControlBox.cs:251— src/ReaLTaiizor/Controls/ControlBox/ThunderControlBox.cs:251-259 | src/ReaLTaiizor/Controls/ControlBox/ThunderControlBox.cs:340-348 | src/ReaLTaiizor/Controls/ControlBox/ThunderControlBox.cs:368-376 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/ReaLTaiizor/Controls/ControlBox/ThunderControlBox.cs:251` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (9 lines × 3) src/ReaLTaiizor/Controls/Stick/ParrotJoyStick.cs:274— src/ReaLTaiizor/Controls/Stick/ParrotJoyStick.cs:274-282 | src/ReaLTaiizor/Controls/Stick/ParrotJoyStick.cs:286-294 | src/ReaLTaiizor/Controls/Stick/ParrotJoyStick.cs:307-315 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/ReaLTaiizor/Controls/Stick/ParrotJoyStick.cs:274` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (9 lines × 3) src/ReaLTaiizor/Controls/Button/MaterialButton.cs:506— src/ReaLTaiizor/Controls/Button/MaterialButton.cs:506-514 | src/ReaLTaiizor/Controls/Card/MaterialCard.cs:171-179 | src/ReaLTaiizor/Controls/Panel/MaterialExpansionPanel.cs:542-550 — before extracting anything, compare `src/ReaLTaiizor/Controls/Card/MaterialCard.cs` and `src/ReaLTaiizor/Controls/Panel/MaterialExpansionPanel.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 36 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `src/ReaLTaiizor/Controls/Button/MaterialButton.cs:505` calls `GetProgress` and `src/ReaLTaiizor/Controls/Card/MaterialCard.cs:171` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (9 lines × 3) src/ReaLTaiizor/Controls/Stick/ParrotJoyStick.cs:352— src/ReaLTaiizor/Controls/Stick/ParrotJoyStick.cs:352-360 | src/ReaLTaiizor/Controls/Stick/ParrotJoyStick.cs:364-372 | src/ReaLTaiizor/Controls/Stick/ParrotJoyStick.cs:385-393 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/ReaLTaiizor/Controls/Stick/ParrotJoyStick.cs:352` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (9 lines × 3) src/ReaLTaiizor/Controls/TabPage/AirTabPage.cs:138— src/ReaLTaiizor/Controls/TabPage/AirTabPage.cs:138-146 | src/ReaLTaiizor/Controls/TabPage/ForeverTabPage.cs:90-100 | src/ReaLTaiizor/Controls/TabPage/ForeverTabPage.cs:124-134 — there are 3 copies across 2 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 3 sites; resolving a subset leaves the remainder to drift apart. Read the line range as the matched WINDOW rather than a finished unit: at `src/ReaLTaiizor/Controls/TabPage/AirTabPage.cs:138` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (9 lines × 3) src/ReaLTaiizor/Forms/Panel/ParrotForm.cs:586— src/ReaLTaiizor/Forms/Panel/ParrotForm.cs:586-594 | src/ReaLTaiizor/Forms/Panel/ParrotForm.cs:612-620 | src/ReaLTaiizor/Forms/Panel/ParrotForm.cs:636-644 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `src/ReaLTaiizor/Forms/Panel/ParrotForm.cs:647` calls `DrawLine`, `Pen`, `FromArgb` and `src/ReaLTaiizor/Forms/Panel/ParrotForm.cs:623` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (10 lines × 3) src/ReaLTaiizor/Controls/Button/MetroDefaultButton.cs:202— src/ReaLTaiizor/Controls/Button/MetroDefaultButton.cs:202-211 | src/ReaLTaiizor/Controls/Ellipse/MetroEllipse.cs:215-224 | src/ReaLTaiizor/Controls/Tile/MetroTile.cs:234-243 — before extracting anything, compare `src/ReaLTaiizor/Controls/Button/MetroDefaultButton.cs` and `src/ReaLTaiizor/Controls/Ellipse/MetroEllipse.cs` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 122 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/ReaLTaiizor/Controls/Button/MetroDefaultButton.cs:202` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (10 lines × 3) src/ReaLTaiizor/Controls/Numeric/MetroNumeric.cs:159— src/ReaLTaiizor/Controls/Numeric/MetroNumeric.cs:159-168 | src/ReaLTaiizor/Controls/RichTextBox/MetroRichTextBox.cs:214-223 | src/ReaLTaiizor/Controls/TextBox/MetroTextBox.cs:238-247 — before extracting anything, compare `src/ReaLTaiizor/Controls/Numeric/MetroNumeric.cs` and `src/ReaLTaiizor/Controls/RichTextBox/MetroRichTextBox.cs` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 106 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (10 lines × 3) src/ReaLTaiizor/Controls/TextBox/MaterialMaskedTextBox.cs:1634— src/ReaLTaiizor/Controls/TextBox/MaterialMaskedTextBox.cs:1634-1643 | src/ReaLTaiizor/Controls/TextBoxEdit/MaterialMultiLineTextBoxEdit.cs:1016-1025 | src/ReaLTaiizor/Controls/TextBoxEdit/MaterialTextBoxEdit.cs:1592-1601 — before extracting anything, compare `src/ReaLTaiizor/Controls/TextBox/MaterialMaskedTextBox.cs` and `src/ReaLTaiizor/Controls/TextBoxEdit/MaterialMultiLineTextBoxEdit.cs` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 164 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (10 lines × 3) src/ReaLTaiizor/Controls/LinkLabel/PoisonLinkLabel.cs:450— src/ReaLTaiizor/Controls/LinkLabel/PoisonLinkLabel.cs:450-459 | src/ReaLTaiizor/Controls/LinkLabel/PoisonLinkLabel.cs:471-481 | src/ReaLTaiizor/Controls/TextBox/PoisonTextBox.cs:1342-1351 — before extracting anything, compare `src/ReaLTaiizor/Controls/LinkLabel/PoisonLinkLabel.cs` and `src/ReaLTaiizor/Controls/TextBox/PoisonTextBox.cs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 90 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/ReaLTaiizor/Controls/LinkLabel/PoisonLinkLabel.cs:450` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (10 lines × 3) src/ReaLTaiizor/Controls/TextBox/MaterialMaskedTextBox.cs:1241— src/ReaLTaiizor/Controls/TextBox/MaterialMaskedTextBox.cs:1241-1250 | src/ReaLTaiizor/Controls/TextBox/MaterialTextBox.cs:796-805 | src/ReaLTaiizor/Controls/TextBoxEdit/MaterialTextBoxEdit.cs:1201-1210 — before extracting anything, compare `src/ReaLTaiizor/Controls/TextBox/MaterialMaskedTextBox.cs` and `src/ReaLTaiizor/Controls/TextBox/MaterialTextBox.cs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 167 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/ReaLTaiizor/Controls/TextBox/MaterialMaskedTextBox.cs:1241` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (10 lines × 3) src/ReaLTaiizor/Util/Air.cs:172— src/ReaLTaiizor/Util/Air.cs:172-181 | src/ReaLTaiizor/Util/Moon.cs:169-178 | src/ReaLTaiizor/Util/Space.cs:171-180 — before extracting anything, compare `src/ReaLTaiizor/Util/Air.cs` and `src/ReaLTaiizor/Util/Moon.cs` as WHOLE FILES: this scan already matched 40 separate duplicated blocks between them, totalling at least 661 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (10 lines × 3) src/ReaLTaiizor/Util/Air.cs:211— src/ReaLTaiizor/Util/Air.cs:211-220 | src/ReaLTaiizor/Util/Moon.cs:208-217 | src/ReaLTaiizor/Util/Space.cs:210-219 — before extracting anything, compare `src/ReaLTaiizor/Util/Air.cs` and `src/ReaLTaiizor/Util/Moon.cs` as WHOLE FILES: this scan already matched 40 separate duplicated blocks between them, totalling at least 661 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (7 lines × 3) src/ReaLTaiizor/Controls/GroupBox/CyberGroupBox.cs:339— src/ReaLTaiizor/Controls/GroupBox/CyberGroupBox.cs:339-345 | src/ReaLTaiizor/Controls/RichTextBox/CyberRichTextBox.cs:326-332 | src/ReaLTaiizor/Controls/TextBox/CyberTextBox.cs:365-371 — before extracting anything, compare `src/ReaLTaiizor/Controls/GroupBox/CyberGroupBox.cs` and `src/ReaLTaiizor/Controls/RichTextBox/CyberRichTextBox.cs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 118 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `src/ReaLTaiizor/Controls/RichTextBox/CyberRichTextBox.cs:325` calls `FromArgb` and `src/ReaLTaiizor/Controls/GroupBox/CyberGroupBox.cs:338` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (7 lines × 3) src/ReaLTaiizor/Controls/RichTextBox/HopeRichTextBox.cs:637— src/ReaLTaiizor/Controls/RichTextBox/HopeRichTextBox.cs:637-643 | src/ReaLTaiizor/Controls/TextBox/HopeTextBox.cs:627-633 | src/ReaLTaiizor/Controls/TextBox/MaterialSingleTextBox.cs:597-603 — before extracting anything, compare `src/ReaLTaiizor/Controls/RichTextBox/HopeRichTextBox.cs` and `src/ReaLTaiizor/Controls/TextBox/HopeTextBox.cs` as WHOLE FILES: 90% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 2 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (7 lines × 3) src/ReaLTaiizor/Controls/ControlBox/ThunderControlBox.cs:232— src/ReaLTaiizor/Controls/ControlBox/ThunderControlBox.cs:232-238 | src/ReaLTaiizor/Controls/ControlBox/ThunderControlBox.cs:265-271 | src/ReaLTaiizor/Controls/ControlBox/ThunderControlBox.cs:296-302 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/ReaLTaiizor/Controls/ControlBox/ThunderControlBox.cs:232` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (7 lines × 3) src/ReaLTaiizor/Controls/Stick/ParrotJoyStick.cs:193— src/ReaLTaiizor/Controls/Stick/ParrotJoyStick.cs:193-199 | src/ReaLTaiizor/Controls/Stick/ParrotJoyStick.cs:218-224 | src/ReaLTaiizor/Controls/Stick/ParrotJoyStick.cs:234-240 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (7 lines × 3) src/ReaLTaiizor/Controls/CheckBox/MaterialCheckBox.cs:214— src/ReaLTaiizor/Controls/CheckBox/MaterialCheckBox.cs:214-223 | src/ReaLTaiizor/Controls/RadioButton/MaterialRadioButton.cs:189-195 | src/ReaLTaiizor/Controls/Switch/MaterialSwitch.cs:194-202 — before extracting anything, compare `src/ReaLTaiizor/Controls/CheckBox/MaterialCheckBox.cs` and `src/ReaLTaiizor/Controls/RadioButton/MaterialRadioButton.cs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 99 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/ReaLTaiizor/Controls/CheckBox/MaterialCheckBox.cs:214` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (7 lines × 3) src/ReaLTaiizor/Controls/ComboBox/SkyComboBox.cs:101— src/ReaLTaiizor/Controls/ComboBox/SkyComboBox.cs:101-107 | src/ReaLTaiizor/Controls/Numeric/SkyNumeric.cs:203-209 | src/ReaLTaiizor/Controls/TextBox/SkyTextBox.cs:141-147 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `src/ReaLTaiizor/Controls/ComboBox/SkyComboBox.cs:107` calls `FromArgb` and `src/ReaLTaiizor/Controls/Numeric/SkyNumeric.cs:209` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (7 lines × 3) src/ReaLTaiizor/Controls/Panel/PoisonPanel.cs:351— src/ReaLTaiizor/Controls/Panel/PoisonPanel.cs:351-357 | src/ReaLTaiizor/Controls/TabControl/PoisonTabControl.cs:400-406 | src/ReaLTaiizor/Controls/TabPage/PoisonTabPage.cs:348-354 — before extracting anything, compare `src/ReaLTaiizor/Controls/Panel/PoisonPanel.cs` and `src/ReaLTaiizor/Controls/TabControl/PoisonTabControl.cs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 102 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
TodoComment src/ReaLTaiizor/Controls/ComboBox/MaterialComboBox.cs:255— // TODO: The arrow coordinates use magic numbers; consider refactoring while preserving the current visual layout. — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment src/ReaLTaiizor/Controls/TextBox/MoonTextBox.cs:32— // TODO: might not be correct. Was : Exit Select — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment src/ReaLTaiizor/Controls/TextBox/MoonTextBox.cs:35— // TODO: might not be correct. Was : Exit Select — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment src/ReaLTaiizor/Util/Air.cs:2039— //TODO: Potential issues during multi-threading. — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment src/ReaLTaiizor/Util/Moon.cs:2039— //TODO: Potential issues during multi-threading. — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment src/ReaLTaiizor/Util/Space.cs:2037— //TODO: Potential issues during multi-threading. — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
D4 · Code Duplication· Members sharing a duplicated core (4 members, 50+ identical tokens) · ×6
Members sharing a duplicated core (4 members, 50+ identical tokens) src/ReaLTaiizor/Controls/Button/CyberButton.cs:579— src/ReaLTaiizor/Controls/Button/CyberButton.cs:579-595 | src/ReaLTaiizor/Controls/GroupBox/CyberGroupBox.cs:467-483 | src/ReaLTaiizor/Controls/RichTextBox/CyberRichTextBox.cs:474-490 | src/ReaLTaiizor/Controls/TextBox/CyberTextBox.cs:523-539 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
Members sharing a duplicated core (4 members, 50+ identical tokens) src/ReaLTaiizor/Controls/Button/MaterialButton.cs:400— src/ReaLTaiizor/Controls/Button/MaterialButton.cs:400-489 | src/ReaLTaiizor/Controls/TextBox/MaterialMaskedTextBox.cs:1363-1517 | src/ReaLTaiizor/Controls/TextBox/MaterialTextBox.cs:389-524 | src/ReaLTaiizor/Controls/TextBoxEdit/MaterialTextBoxEdit.cs:1318-1472 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
Members sharing a duplicated core (4 members, 50+ identical tokens) src/ReaLTaiizor/Controls/Button/RibbonButtonCenter.cs:187— src/ReaLTaiizor/Controls/Button/RibbonButtonCenter.cs:187-237 | src/ReaLTaiizor/Controls/Button/RibbonButtonLeft.cs:187-237 | src/ReaLTaiizor/Controls/Button/RibbonButtonRight.cs:187-237 | src/ReaLTaiizor/Controls/GroupBox/ThunderGroupBox.cs:39-63 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
Members sharing a duplicated core (4 members, 50+ identical tokens) src/ReaLTaiizor/Controls/Panel/ParrotGradientPanel.cs:172— src/ReaLTaiizor/Controls/Panel/ParrotGradientPanel.cs:172-210 | src/ReaLTaiizor/Controls/PictureBox/ParrotPictureBox.cs:178-231 | src/ReaLTaiizor/Controls/Progress/ParrotFlatProgressBar.cs:257-305 | src/ReaLTaiizor/Controls/Slider/ParrotSlider.cs:320-399 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
Members sharing a duplicated core (4 members, 50+ identical tokens) src/ReaLTaiizor/Controls/TextBox/MaterialMaskedTextBox.cs:1033— src/ReaLTaiizor/Controls/TextBox/MaterialMaskedTextBox.cs:1033-1208 | src/ReaLTaiizor/Controls/TextBox/MaterialTextBox.cs:577-758 | src/ReaLTaiizor/Controls/TextBoxEdit/MaterialMultiLineTextBoxEdit.cs:831-883 | src/ReaLTaiizor/Controls/TextBoxEdit/MaterialTextBoxEdit.cs:984-1168 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
Members sharing a duplicated core (4 members, 50+ identical tokens) src/ReaLTaiizor/Controls/TextBox/MaterialMaskedTextBox.cs:1608— src/ReaLTaiizor/Controls/TextBox/MaterialMaskedTextBox.cs:1608-1630 | src/ReaLTaiizor/Controls/TextBox/MaterialSingleTextBox.cs:681-703 | src/ReaLTaiizor/Controls/TextBoxEdit/MaterialMultiLineTextBoxEdit.cs:990-1012 | src/ReaLTaiizor/Controls/TextBoxEdit/MaterialTextBoxEdit.cs:1566-1588 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
Duplicated block (18 lines × 2) src/ReaLTaiizor/Helper/Crown.cs:39— src/ReaLTaiizor/Helper/Crown.cs:39-56 | src/ReaLTaiizor/Helper/Crown.cs:81-98 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/ReaLTaiizor/Helper/Crown.cs:39` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (18 lines × 2) src/ReaLTaiizor/Util/Material.cs:994— src/ReaLTaiizor/Util/Material.cs:994-1011 | src/ReaLTaiizor/Util/Material.cs:1074-1091 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/ReaLTaiizor/Util/Material.cs:994` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (18 lines × 2) src/ReaLTaiizor/Util/Moon.cs:268— src/ReaLTaiizor/Util/Moon.cs:268-285 | src/ReaLTaiizor/Util/Space.cs:270-287 — before extracting anything, compare `src/ReaLTaiizor/Util/Moon.cs` and `src/ReaLTaiizor/Util/Space.cs` as WHOLE FILES: this scan already matched 42 separate duplicated blocks between them, totalling at least 688 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/ReaLTaiizor/Util/Moon.cs:268` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (18 lines × 2) src/ReaLTaiizor/Controls/LinkLabel/PoisonLinkLabel.cs:451— src/ReaLTaiizor/Controls/LinkLabel/PoisonLinkLabel.cs:451-468 | src/ReaLTaiizor/Controls/TextBox/PoisonTextBox.cs:1343-1360 — before extracting anything, compare `src/ReaLTaiizor/Controls/LinkLabel/PoisonLinkLabel.cs` and `src/ReaLTaiizor/Controls/TextBox/PoisonTextBox.cs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 90 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (18 lines × 2) src/ReaLTaiizor/Controls/Progress/CyberProgressBar.cs:628— src/ReaLTaiizor/Controls/Progress/CyberProgressBar.cs:628-645 | src/ReaLTaiizor/Controls/ScrollBar/CyberScrollBar.cs:721-738 — before extracting anything, compare `src/ReaLTaiizor/Controls/Progress/CyberProgressBar.cs` and `src/ReaLTaiizor/Controls/ScrollBar/CyberScrollBar.cs` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 183 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (18 lines × 2) src/ReaLTaiizor/Controls/Ellipse/ParrotFormEllipse.cs:68— src/ReaLTaiizor/Controls/Ellipse/ParrotFormEllipse.cs:68-85 | src/ReaLTaiizor/Controls/Ellipse/ParrotObjectEllipse.cs:104-121 — before extracting anything, compare `src/ReaLTaiizor/Controls/Ellipse/ParrotFormEllipse.cs` and `src/ReaLTaiizor/Controls/Ellipse/ParrotObjectEllipse.cs` as WHOLE FILES: 88% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (13 lines × 3) src/ReaLTaiizor/Controls/Button/ChatButtonLeft.cs:17— src/ReaLTaiizor/Controls/Button/ChatButtonLeft.cs:17-29 | src/ReaLTaiizor/Controls/Button/DungeonButtonLeft.cs:17-29 | src/ReaLTaiizor/Controls/Button/DungeonButtonRight.cs:17-29 — before extracting anything, compare `src/ReaLTaiizor/Controls/Button/ChatButtonLeft.cs` and `src/ReaLTaiizor/Controls/Button/DungeonButtonLeft.cs` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 228 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (13 lines × 3) src/ReaLTaiizor/Forms/Container/DungeonForm.cs:194— src/ReaLTaiizor/Forms/Container/DungeonForm.cs:194-206 | src/ReaLTaiizor/Forms/Container/FormTheme.cs:173-185 | src/ReaLTaiizor/Forms/Container/ThemeForm.cs:202-214 — before extracting anything, compare `src/ReaLTaiizor/Forms/Container/DungeonForm.cs` and `src/ReaLTaiizor/Forms/Container/FormTheme.cs` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 218 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (13 lines × 3) src/ReaLTaiizor/Controls/Badge/MetroBadge.cs:602— src/ReaLTaiizor/Controls/Badge/MetroBadge.cs:602-614 | src/ReaLTaiizor/Controls/Button/MetroButton.cs:273-285 | src/ReaLTaiizor/Controls/Button/MetroDefaultButton.cs:247-259 — before extracting anything, compare `src/ReaLTaiizor/Controls/Badge/MetroBadge.cs` and `src/ReaLTaiizor/Controls/Button/MetroButton.cs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 97 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/ReaLTaiizor/Controls/Badge/MetroBadge.cs:602` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (13 lines × 3) src/ReaLTaiizor/Controls/TextBox/MaterialMaskedTextBox.cs:209— src/ReaLTaiizor/Controls/TextBox/MaterialMaskedTextBox.cs:209-221 | src/ReaLTaiizor/Controls/TextBoxEdit/MaterialMultiLineTextBoxEdit.cs:94-106 | src/ReaLTaiizor/Controls/TextBoxEdit/MaterialTextBoxEdit.cs:221-235 — before extracting anything, compare `src/ReaLTaiizor/Controls/TextBox/MaterialMaskedTextBox.cs` and `src/ReaLTaiizor/Controls/TextBoxEdit/MaterialMultiLineTextBoxEdit.cs` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 164 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (13 lines × 3) src/ReaLTaiizor/Util/Air.cs:600— src/ReaLTaiizor/Util/Air.cs:600-612 | src/ReaLTaiizor/Util/Moon.cs:593-605 | src/ReaLTaiizor/Util/Space.cs:595-607 — before extracting anything, compare `src/ReaLTaiizor/Util/Air.cs` and `src/ReaLTaiizor/Util/Moon.cs` as WHOLE FILES: this scan already matched 40 separate duplicated blocks between them, totalling at least 661 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (13 lines × 3) src/ReaLTaiizor/Util/Air.cs:631— src/ReaLTaiizor/Util/Air.cs:631-643 | src/ReaLTaiizor/Util/Moon.cs:624-636 | src/ReaLTaiizor/Util/Space.cs:626-638 — before extracting anything, compare `src/ReaLTaiizor/Util/Air.cs` and `src/ReaLTaiizor/Util/Moon.cs` as WHOLE FILES: this scan already matched 40 separate duplicated blocks between them, totalling at least 661 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (12 lines × 2) src/ReaLTaiizor/Controls/ScrollBar/MaterialScrollBar.cs:807— src/ReaLTaiizor/Controls/ScrollBar/MaterialScrollBar.cs:807-818 | src/ReaLTaiizor/Controls/ScrollBar/PoisonScrollBar.cs:1007-1018 — before extracting anything, compare `src/ReaLTaiizor/Controls/ScrollBar/MaterialScrollBar.cs` and `src/ReaLTaiizor/Controls/ScrollBar/PoisonScrollBar.cs` as WHOLE FILES: this scan already matched 15 separate duplicated blocks between them, totalling at least 423 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/ReaLTaiizor/Controls/ScrollBar/MaterialScrollBar.cs:807` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (12 lines × 2) src/ReaLTaiizor/Controls/Button/SpaceButton.cs:65— src/ReaLTaiizor/Controls/Button/SpaceButton.cs:65-76 | src/ReaLTaiizor/Controls/Quest/SpaceQuest.cs:91-102 — before extracting anything, compare `src/ReaLTaiizor/Controls/Button/SpaceButton.cs` and `src/ReaLTaiizor/Controls/Quest/SpaceQuest.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 32 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (12 lines × 2) src/ReaLTaiizor/Controls/CheckBox/ParrotCheckBox.cs:226— src/ReaLTaiizor/Controls/CheckBox/ParrotCheckBox.cs:226-237 | src/ReaLTaiizor/Controls/RadioButton/ParrotRadioButton.cs:181-192 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `src/ReaLTaiizor/Controls/CheckBox/ParrotCheckBox.cs:226` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (12 lines × 2) src/ReaLTaiizor/Controls/Graph/ParrotBarGraph.cs:500— src/ReaLTaiizor/Controls/Graph/ParrotBarGraph.cs:500-511 | src/ReaLTaiizor/Controls/Graph/ParrotBarGraph.cs:535-546 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/ReaLTaiizor/Controls/Graph/ParrotBarGraph.cs:500` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (12 lines × 2) src/ReaLTaiizor/Controls/Dialog/MaterialDialog.cs:241— src/ReaLTaiizor/Controls/Dialog/MaterialDialog.cs:241-252 | src/ReaLTaiizor/Controls/SnackBar/MaterialSnackBar.cs:279-290 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `src/ReaLTaiizor/Controls/Dialog/MaterialDialog.cs:241` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (12 lines × 2) src/ReaLTaiizor/Controls/TextBox/DungeonTextBox.cs:239— src/ReaLTaiizor/Controls/TextBox/DungeonTextBox.cs:239-250 | src/ReaLTaiizor/Controls/TextBox/SmallTextBox.cs:251-262 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `src/ReaLTaiizor/Controls/TextBox/DungeonTextBox.cs:239` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (11 lines × 3) src/ReaLTaiizor/Controls/CheckBox/MetroCheckBox.cs:145— src/ReaLTaiizor/Controls/CheckBox/MetroCheckBox.cs:145-155 | src/ReaLTaiizor/Controls/ComboBox/MetroComboBox.cs:331-341 | src/ReaLTaiizor/Controls/RadioButton/MetroRadioButton.cs:145-155 — before extracting anything, compare `src/ReaLTaiizor/Controls/CheckBox/MetroCheckBox.cs` and `src/ReaLTaiizor/Controls/RadioButton/MetroRadioButton.cs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 90 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/ReaLTaiizor/Controls/CheckBox/MetroCheckBox.cs:145` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (11 lines × 3) src/ReaLTaiizor/Controls/TextBox/MaterialMaskedTextBox.cs:1105— src/ReaLTaiizor/Controls/TextBox/MaterialMaskedTextBox.cs:1105-1115 | src/ReaLTaiizor/Controls/TextBoxEdit/MaterialMultiLineTextBoxEdit.cs:872-882 | src/ReaLTaiizor/Controls/TextBoxEdit/MaterialTextBoxEdit.cs:1058-1068 — before extracting anything, compare `src/ReaLTaiizor/Controls/TextBox/MaterialMaskedTextBox.cs` and `src/ReaLTaiizor/Controls/TextBoxEdit/MaterialMultiLineTextBoxEdit.cs` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 164 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/ReaLTaiizor/Controls/TextBox/MaterialMaskedTextBox.cs:1105` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (11 lines × 3) src/ReaLTaiizor/Controls/Button/CyberButton.cs:420— src/ReaLTaiizor/Controls/Button/CyberButton.cs:420-430 | src/ReaLTaiizor/Controls/Progress/CyberProgressBar.cs:483-493 | src/ReaLTaiizor/Controls/ScrollBar/CyberScrollBar.cs:513-523 — before extracting anything, compare `src/ReaLTaiizor/Controls/Button/CyberButton.cs` and `src/ReaLTaiizor/Controls/Progress/CyberProgressBar.cs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 125 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (11 lines × 3) src/ReaLTaiizor/Controls/Close/ForeverClose.cs:99— src/ReaLTaiizor/Controls/Close/ForeverClose.cs:99-109 | src/ReaLTaiizor/Controls/Maximize/ForeverMaximize.cs:101-111 | src/ReaLTaiizor/Controls/Minimize/ForeverMinimize.cs:101-111 — before extracting anything, compare `src/ReaLTaiizor/Controls/Close/ForeverClose.cs` and `src/ReaLTaiizor/Controls/Maximize/ForeverMaximize.cs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 61 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (11 lines × 3) src/ReaLTaiizor/Controls/TextBox/MaterialMaskedTextBox.cs:344— src/ReaLTaiizor/Controls/TextBox/MaterialMaskedTextBox.cs:344-354 | src/ReaLTaiizor/Controls/TextBoxEdit/MaterialMultiLineTextBoxEdit.cs:195-205 | src/ReaLTaiizor/Controls/TextBoxEdit/MaterialTextBoxEdit.cs:316-326 — before extracting anything, compare `src/ReaLTaiizor/Controls/TextBox/MaterialMaskedTextBox.cs` and `src/ReaLTaiizor/Controls/TextBoxEdit/MaterialMultiLineTextBoxEdit.cs` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 164 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (11 lines × 3) src/ReaLTaiizor/Util/Air.cs:857— src/ReaLTaiizor/Util/Air.cs:857-867 | src/ReaLTaiizor/Util/Moon.cs:850-860 | src/ReaLTaiizor/Util/Space.cs:852-862 — before extracting anything, compare `src/ReaLTaiizor/Util/Air.cs` and `src/ReaLTaiizor/Util/Moon.cs` as WHOLE FILES: this scan already matched 40 separate duplicated blocks between them, totalling at least 661 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (24 lines × 2) src/ReaLTaiizor/Animate/Parrot/ObjectAnimator.cs:238— src/ReaLTaiizor/Animate/Parrot/ObjectAnimator.cs:238-261 | src/ReaLTaiizor/Animate/Parrot/ObjectAnimator.cs:274-297 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/ReaLTaiizor/Animate/Parrot/ObjectAnimator.cs:238` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (24 lines × 2) src/ReaLTaiizor/Forms/Container/DungeonForm.cs:122— src/ReaLTaiizor/Forms/Container/DungeonForm.cs:122-145 | src/ReaLTaiizor/Forms/Container/ThemeForm.cs:129-152 — before extracting anything, compare `src/ReaLTaiizor/Forms/Container/DungeonForm.cs` and `src/ReaLTaiizor/Forms/Container/ThemeForm.cs` as WHOLE FILES: this scan already matched 17 separate duplicated blocks between them, totalling at least 286 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/ReaLTaiizor/Forms/Container/DungeonForm.cs:122` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (24 lines × 2) src/ReaLTaiizor/Controls/ScrollBar/MaterialScrollBar.cs:221— src/ReaLTaiizor/Controls/ScrollBar/MaterialScrollBar.cs:221-244 | src/ReaLTaiizor/Controls/ScrollBar/PoisonScrollBar.cs:326-349 — before extracting anything, compare `src/ReaLTaiizor/Controls/ScrollBar/MaterialScrollBar.cs` and `src/ReaLTaiizor/Controls/ScrollBar/PoisonScrollBar.cs` as WHOLE FILES: this scan already matched 15 separate duplicated blocks between them, totalling at least 423 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (24 lines × 2) src/ReaLTaiizor/Controls/Toggle/PoisonToggle.cs:210— src/ReaLTaiizor/Controls/Toggle/PoisonToggle.cs:210-233 | src/ReaLTaiizor/Controls/TrackBar/PoisonTrackBar.cs:283-306 — before extracting anything, compare `src/ReaLTaiizor/Controls/Toggle/PoisonToggle.cs` and `src/ReaLTaiizor/Controls/TrackBar/PoisonTrackBar.cs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 76 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (24 lines × 2) src/ReaLTaiizor/Util/Material.cs:998— src/ReaLTaiizor/Util/Material.cs:998-1021 | src/ReaLTaiizor/Util/Material.cs:1028-1051 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (17 lines × 2) src/ReaLTaiizor/Controls/TextBox/MaterialMaskedTextBox.cs:878— src/ReaLTaiizor/Controls/TextBox/MaterialMaskedTextBox.cs:878-894 | src/ReaLTaiizor/Controls/TextBoxEdit/MaterialTextBoxEdit.cs:830-846 — before extracting anything, compare `src/ReaLTaiizor/Controls/TextBox/MaterialMaskedTextBox.cs` and `src/ReaLTaiizor/Controls/TextBoxEdit/MaterialTextBoxEdit.cs` as WHOLE FILES: this scan already matched 27 separate duplicated blocks between them, totalling at least 574 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (17 lines × 2) src/ReaLTaiizor/Controls/Dialog/MaterialDialog.cs:336— src/ReaLTaiizor/Controls/Dialog/MaterialDialog.cs:336-352 | src/ReaLTaiizor/Controls/SnackBar/MaterialSnackBar.cs:342-358 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (17 lines × 2) src/ReaLTaiizor/Controls/Grid/PoisonDataGridView.cs:58— src/ReaLTaiizor/Controls/Grid/PoisonDataGridView.cs:58-74 | src/ReaLTaiizor/Controls/Strip/PoisonContextMenuStrip.cs:58-74 — before extracting anything, compare `src/ReaLTaiizor/Controls/Grid/PoisonDataGridView.cs` and `src/ReaLTaiizor/Controls/Strip/PoisonContextMenuStrip.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 43 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (17 lines × 2) src/ReaLTaiizor/Controls/Grid/PoisonDataGridView.cs:84— src/ReaLTaiizor/Controls/Grid/PoisonDataGridView.cs:84-100 | src/ReaLTaiizor/Controls/Strip/PoisonContextMenuStrip.cs:84-100 — before extracting anything, compare `src/ReaLTaiizor/Controls/Grid/PoisonDataGridView.cs` and `src/ReaLTaiizor/Controls/Strip/PoisonContextMenuStrip.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 43 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (17 lines × 2) demo/ReaLTaiizor.UI/ReaLTaiizor.UI/Form21.cs:208— demo/ReaLTaiizor.UI/ReaLTaiizor.UI/Form21.cs:208-224 | demo/ReaLTaiizor.UI/ReaLTaiizor.UI/Form21.cs:236-252 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `demo/ReaLTaiizor.UI/ReaLTaiizor.UI/Form21.cs:208` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (15 lines × 3) src/ReaLTaiizor/Controls/Progress/PoisonProgressBar.cs:299— src/ReaLTaiizor/Controls/Progress/PoisonProgressBar.cs:299-313 | src/ReaLTaiizor/Controls/Progress/PoisonProgressSpinner.cs:332-346 | src/ReaLTaiizor/Controls/ScrollBar/PoisonScrollBar.cs:549-563 — before extracting anything, compare `src/ReaLTaiizor/Controls/Progress/PoisonProgressBar.cs` and `src/ReaLTaiizor/Controls/Progress/PoisonProgressSpinner.cs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 67 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/ReaLTaiizor/Controls/Progress/PoisonProgressBar.cs:299` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (15 lines × 3) src/ReaLTaiizor/Util/Air.cs:1189— src/ReaLTaiizor/Util/Air.cs:1189-1203 | src/ReaLTaiizor/Util/Moon.cs:1182-1196 | src/ReaLTaiizor/Util/Space.cs:1185-1199 — before extracting anything, compare `src/ReaLTaiizor/Util/Air.cs` and `src/ReaLTaiizor/Util/Moon.cs` as WHOLE FILES: this scan already matched 40 separate duplicated blocks between them, totalling at least 661 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/ReaLTaiizor/Util/Air.cs:1189` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (15 lines × 3) src/ReaLTaiizor/Util/Air.cs:2162— src/ReaLTaiizor/Util/Air.cs:2162-2176 | src/ReaLTaiizor/Util/Moon.cs:2164-2178 | src/ReaLTaiizor/Util/Space.cs:2161-2175 — before extracting anything, compare `src/ReaLTaiizor/Util/Air.cs` and `src/ReaLTaiizor/Util/Moon.cs` as WHOLE FILES: this scan already matched 40 separate duplicated blocks between them, totalling at least 661 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/ReaLTaiizor/Util/Air.cs:2162` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (15 lines × 3) src/ReaLTaiizor/Controls/Button/MetroButton.cs:110— src/ReaLTaiizor/Controls/Button/MetroButton.cs:110-125 | src/ReaLTaiizor/Controls/Button/MetroDefaultButton.cs:92-106 | src/ReaLTaiizor/Controls/Ellipse/MetroEllipse.cs:94-108 — before extracting anything, compare `src/ReaLTaiizor/Controls/Button/MetroButton.cs` and `src/ReaLTaiizor/Controls/Button/MetroDefaultButton.cs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 141 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (15 lines × 3) src/ReaLTaiizor/Controls/Progress/RibbonProgressBarCenter.cs:79— src/ReaLTaiizor/Controls/Progress/RibbonProgressBarCenter.cs:79-93 | src/ReaLTaiizor/Controls/Progress/RibbonProgressBarLeft.cs:74-88 | src/ReaLTaiizor/Controls/Progress/RibbonProgressBarRight.cs:74-88 — before extracting anything, compare `src/ReaLTaiizor/Controls/Progress/RibbonProgressBarCenter.cs` and `src/ReaLTaiizor/Controls/Progress/RibbonProgressBarLeft.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 55 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (14 lines × 3) src/ReaLTaiizor/Controls/Button/CyberButton.cs:510— src/ReaLTaiizor/Controls/Button/CyberButton.cs:510-523 | src/ReaLTaiizor/Controls/CheckBox/CyberCheckBox.cs:479-492 | src/ReaLTaiizor/Controls/RadioButton/CyberRadioButton.cs:534-547 — before extracting anything, compare `src/ReaLTaiizor/Controls/Button/CyberButton.cs` and `src/ReaLTaiizor/Controls/CheckBox/CyberCheckBox.cs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 119 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (14 lines × 3) src/ReaLTaiizor/Controls/Badge/MetroBadge.cs:519— src/ReaLTaiizor/Controls/Badge/MetroBadge.cs:519-532 | src/ReaLTaiizor/Controls/Button/MetroDefaultButton.cs:188-201 | src/ReaLTaiizor/Controls/Ellipse/MetroEllipse.cs:201-214 — before extracting anything, compare `src/ReaLTaiizor/Controls/Badge/MetroBadge.cs` and `src/ReaLTaiizor/Controls/Button/MetroDefaultButton.cs` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 124 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (14 lines × 3) src/ReaLTaiizor/Controls/TrackBar/DungeonTrackBar.cs:61— src/ReaLTaiizor/Controls/TrackBar/DungeonTrackBar.cs:61-75 | src/ReaLTaiizor/Controls/TrackBar/TrackBar.cs:49-63 | src/ReaLTaiizor/Controls/TrackBarEdit/TrackBarEdit.cs:52-65 — before extracting anything, compare `src/ReaLTaiizor/Controls/TrackBar/DungeonTrackBar.cs` and `src/ReaLTaiizor/Controls/TrackBar/TrackBar.cs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 67 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (14 lines × 3) src/ReaLTaiizor/Controls/TrackBar/DungeonTrackBar.cs:82— src/ReaLTaiizor/Controls/TrackBar/DungeonTrackBar.cs:82-96 | src/ReaLTaiizor/Controls/TrackBar/TrackBar.cs:70-84 | src/ReaLTaiizor/Controls/TrackBarEdit/TrackBarEdit.cs:73-86 — before extracting anything, compare `src/ReaLTaiizor/Controls/TrackBar/DungeonTrackBar.cs` and `src/ReaLTaiizor/Controls/TrackBar/TrackBar.cs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 67 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (14 lines × 3) src/ReaLTaiizor/Util/Air.cs:2571— src/ReaLTaiizor/Util/Air.cs:2571-2584 | src/ReaLTaiizor/Util/Moon.cs:2576-2589 | src/ReaLTaiizor/Util/Space.cs:2575-2588 — before extracting anything, compare `src/ReaLTaiizor/Util/Air.cs` and `src/ReaLTaiizor/Util/Moon.cs` as WHOLE FILES: this scan already matched 40 separate duplicated blocks between them, totalling at least 661 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `src/ReaLTaiizor/Util/Air.cs:2588` calls `Exception`, `Format`, `GetLastWin32Error` and `src/ReaLTaiizor/Util/Moon.cs:2594` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Low cohesion: Form17 (LCOM4 29) demo/ReaLTaiizor.UI/ReaLTaiizor.UI/Form17.cs:13— Form17's methods fall into 29 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 29 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: PoisonDataGridView (LCOM4 8) src/ReaLTaiizor/Controls/Grid/PoisonDataGridView.cs:19— PoisonDataGridView's methods fall into 8 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 8 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: PoisonListView (LCOM4 7) src/ReaLTaiizor/Controls/ListView/PoisonListView.cs:21— PoisonListView's methods fall into 7 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 7 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: MaterialSkinManager (LCOM4 5) src/ReaLTaiizor/Manager/MaterialSkinManager.cs:24— MaterialSkinManager's methods fall into 5 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 5 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: PoisonMessageBoxControl (LCOM4 4) src/ReaLTaiizor/Child/Poison/PoisonMessageBoxControl.cs:17— PoisonMessageBoxControl's methods fall into 4 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 4 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
async void method: Language_CheckedChanged ready/ReaLTaiizor.Translate/ReaLTaiizor.Translate/Translate.cs:23— `async void` can't be awaited and its exceptions crash the process instead of propagating. Return `Task` — or, where the delegate contract requires void (timer/event/callback registrations), make this a thin void shim that awaits a Task-returning inner method inside try/catch so exceptions are contained.
async void method: ForeverToggle1_CheckedChanged ready/ReaLTaiizor.Translate/ReaLTaiizor.Translate/Translate.cs:33— `async void` can't be awaited and its exceptions crash the process instead of propagating. Return `Task` — or, where the delegate contract requires void (timer/event/callback registrations), make this a thin void shim that awaits a Task-returning inner method inside try/catch so exceptions are contained.
async void method: ForeverTextBox1_TextChanged ready/ReaLTaiizor.Translate/ReaLTaiizor.Translate/Translate.cs:42— `async void` can't be awaited and its exceptions crash the process instead of propagating. Return `Task` — or, where the delegate contract requires void (timer/event/callback registrations), make this a thin void shim that awaits a Task-returning inner method inside try/catch so exceptions are contained.
async void method: ForeverButton1_Click ready/ReaLTaiizor.Translate/ReaLTaiizor.Translate/Translate.cs:50— `async void` can't be awaited and its exceptions crash the process instead of propagating. Return `Task` — or, where the delegate contract requires void (timer/event/callback registrations), make this a thin void shim that awaits a Task-returning inner method inside try/catch so exceptions are contained.
async void method: SCN_F ready/ReaLTaiizor.Portscan/ReaLTaiizor.Portscan/Portscan.cs:309— `async void` can't be awaited and its exceptions crash the process instead of propagating. Return `Task` — or, where the delegate contract requires void (timer/event/callback registrations), make this a thin void shim that awaits a Task-returning inner method inside try/catch so exceptions are contained.
Change-coupling hub: MaterialRadioButton.cs → MaterialButton.cs, MaterialFloatingActionButton.cs, MaterialCheckBox.cs, MaterialComboBox.cs, MaterialDrawer.cs, MaterialListView.cs, MaterialContextMenuStrip.cs, MaterialSwitch.cs, MaterialTabSelector.cs, MaterialTextBox.cs src/ReaLTaiizor/Controls/RadioButton/MaterialRadioButton.cs— `src/ReaLTaiizor/Controls/RadioButton/MaterialRadioButton.cs` changes together with 10 other files — `src/ReaLTaiizor/Controls/Button/MaterialButton.cs`, `src/ReaLTaiizor/Controls/Button/MaterialFloatingActionButton.cs`, `src/ReaLTaiizor/Controls/CheckBox/MaterialCheckBox.cs`, `src/ReaLTaiizor/Controls/ComboBox/MaterialComboBox.cs`, `src/ReaLTaiizor/Controls/Drawer/MaterialDrawer.cs`, `src/ReaLTaiizor/Controls/ListView/MaterialListView.cs`, `src/ReaLTaiizor/Controls/Strip/MaterialContextMenuStrip.cs`, `src/ReaLTaiizor/Controls/Switch/MaterialSwitch.cs`, `src/ReaLTaiizor/Controls/TabSelector/MaterialTabSelector.cs`, `src/ReaLTaiizor/Controls/TextBox/MaterialTextBox.cs` — none of which declares a dependency on it: one file is the hub of 10 separate couplings, not 10 unrelated pairs. Read the hub first: if the others each duplicate a part of what it does, the shared concern belongs in ONE unit and extracting it clears every edge at once; if the hub is a registry, dispatcher or barrel that must name each of them, the coupling is structural and the question is whether that list can be discovered instead of enumerated. Fixing the hub is one change; breaking the couplings one pair at a time is 10.
Change-coupling hub: MaterialButton.cs → MaterialCheckBox.cs, MaterialSwitch.cs, MaterialTextBox.cs, MaterialTextBoxEdit.cs src/ReaLTaiizor/Controls/Button/MaterialButton.cs— `src/ReaLTaiizor/Controls/Button/MaterialButton.cs` changes together with 4 other files — `src/ReaLTaiizor/Controls/CheckBox/MaterialCheckBox.cs`, `src/ReaLTaiizor/Controls/Switch/MaterialSwitch.cs`, `src/ReaLTaiizor/Controls/TextBox/MaterialTextBox.cs`, `src/ReaLTaiizor/Controls/TextBoxEdit/MaterialTextBoxEdit.cs` — none of which declares a dependency on it: one file is the hub of 4 separate couplings, not 4 unrelated pairs. Read the hub first: if the others each duplicate a part of what it does, the shared concern belongs in ONE unit and extracting it clears every edge at once; if the hub is a registry, dispatcher or barrel that must name each of them, the coupling is structural and the question is whether that list can be discovered instead of enumerated. Fixing the hub is one change; breaking the couplings one pair at a time is 4.
Change-coupling hub: MaterialFloatingActionButton.cs → MaterialCheckBox.cs, MaterialComboBox.cs, MaterialSwitch.cs, MaterialTabSelector.cs, MaterialTextBox.cs src/ReaLTaiizor/Controls/Button/MaterialFloatingActionButton.cs— `src/ReaLTaiizor/Controls/Button/MaterialFloatingActionButton.cs` changes together with 5 other files — `src/ReaLTaiizor/Controls/CheckBox/MaterialCheckBox.cs`, `src/ReaLTaiizor/Controls/ComboBox/MaterialComboBox.cs`, `src/ReaLTaiizor/Controls/Switch/MaterialSwitch.cs`, `src/ReaLTaiizor/Controls/TabSelector/MaterialTabSelector.cs`, `src/ReaLTaiizor/Controls/TextBox/MaterialTextBox.cs` — none of which declares a dependency on it: one file is the hub of 5 separate couplings, not 5 unrelated pairs. Read the hub first: if the others each duplicate a part of what it does, the shared concern belongs in ONE unit and extracting it clears every edge at once; if the hub is a registry, dispatcher or barrel that must name each of them, the coupling is structural and the question is whether that list can be discovered instead of enumerated. Fixing the hub is one change; breaking the couplings one pair at a time is 5.
Change-coupling hub: MaterialTextBox.cs → MaterialCheckBox.cs, MaterialListView.cs, MaterialSwitch.cs src/ReaLTaiizor/Controls/TextBox/MaterialTextBox.cs— `src/ReaLTaiizor/Controls/TextBox/MaterialTextBox.cs` changes together with 3 other files — `src/ReaLTaiizor/Controls/CheckBox/MaterialCheckBox.cs`, `src/ReaLTaiizor/Controls/ListView/MaterialListView.cs`, `src/ReaLTaiizor/Controls/Switch/MaterialSwitch.cs` — none of which declares a dependency on it: one file is the hub of 3 separate couplings, not 3 unrelated pairs. Read the hub first: if the others each duplicate a part of what it does, the shared concern belongs in ONE unit and extracting it clears every edge at once; if the hub is a registry, dispatcher or barrel that must name each of them, the coupling is structural and the question is whether that list can be discovered instead of enumerated. Fixing the hub is one change; breaking the couplings one pair at a time is 3.
Duplicated block (23 lines × 2) src/ReaLTaiizor/Controls/Graph/ParrotBarGraph.cs:213— src/ReaLTaiizor/Controls/Graph/ParrotBarGraph.cs:213-235 | src/ReaLTaiizor/Controls/Graph/ParrotBarGraph.cs:466-488 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/ReaLTaiizor/Controls/Graph/ParrotBarGraph.cs:213` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (23 lines × 2) src/ReaLTaiizor/Controls/CheckBox/CrownCheckBox.cs:127— src/ReaLTaiizor/Controls/CheckBox/CrownCheckBox.cs:127-149 | src/ReaLTaiizor/Controls/RadioButton/CrownRadioButton.cs:124-146 — before extracting anything, compare `src/ReaLTaiizor/Controls/CheckBox/CrownCheckBox.cs` and `src/ReaLTaiizor/Controls/RadioButton/CrownRadioButton.cs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 95 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (23 lines × 2) src/ReaLTaiizor/Controls/ScrollBar/MaterialScrollBar.cs:848— src/ReaLTaiizor/Controls/ScrollBar/MaterialScrollBar.cs:848-870 | src/ReaLTaiizor/Controls/ScrollBar/PoisonScrollBar.cs:1048-1070 — before extracting anything, compare `src/ReaLTaiizor/Controls/ScrollBar/MaterialScrollBar.cs` and `src/ReaLTaiizor/Controls/ScrollBar/PoisonScrollBar.cs` as WHOLE FILES: this scan already matched 15 separate duplicated blocks between them, totalling at least 423 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (23 lines × 2) src/ReaLTaiizor/Controls/ScrollBar/MaterialScrollBar.cs:561— src/ReaLTaiizor/Controls/ScrollBar/MaterialScrollBar.cs:561-583 | src/ReaLTaiizor/Controls/ScrollBar/PoisonScrollBar.cs:761-783 — before extracting anything, compare `src/ReaLTaiizor/Controls/ScrollBar/MaterialScrollBar.cs` and `src/ReaLTaiizor/Controls/ScrollBar/PoisonScrollBar.cs` as WHOLE FILES: this scan already matched 15 separate duplicated blocks between them, totalling at least 423 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/ReaLTaiizor/Controls/ScrollBar/PoisonScrollBar.cs:761` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (20 lines × 2) src/ReaLTaiizor/Util/Material.cs:1022— src/ReaLTaiizor/Util/Material.cs:1022-1041 | src/ReaLTaiizor/Util/Material.cs:1102-1121 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/ReaLTaiizor/Util/Material.cs:1022` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (20 lines × 2) src/ReaLTaiizor/Controls/Progress/PoisonProgressSpinner.cs:326— src/ReaLTaiizor/Controls/Progress/PoisonProgressSpinner.cs:326-345 | src/ReaLTaiizor/Controls/ScrollBar/PoisonScrollBar.cs:543-562 — before extracting anything, compare `src/ReaLTaiizor/Controls/Progress/PoisonProgressSpinner.cs` and `src/ReaLTaiizor/Controls/ScrollBar/PoisonScrollBar.cs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 87 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/ReaLTaiizor/Controls/Progress/PoisonProgressSpinner.cs:326` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (20 lines × 2) src/ReaLTaiizor/Controls/TextBox/MaterialMaskedTextBox.cs:1236— src/ReaLTaiizor/Controls/TextBox/MaterialMaskedTextBox.cs:1236-1255 | src/ReaLTaiizor/Controls/TextBoxEdit/MaterialTextBoxEdit.cs:1196-1215 — before extracting anything, compare `src/ReaLTaiizor/Controls/TextBox/MaterialMaskedTextBox.cs` and `src/ReaLTaiizor/Controls/TextBoxEdit/MaterialTextBoxEdit.cs` as WHOLE FILES: this scan already matched 27 separate duplicated blocks between them, totalling at least 574 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (20 lines × 2) src/ReaLTaiizor/Controls/TextBox/MaterialMaskedTextBox.cs:1529— src/ReaLTaiizor/Controls/TextBox/MaterialMaskedTextBox.cs:1529-1548 | src/ReaLTaiizor/Controls/TextBoxEdit/MaterialTextBoxEdit.cs:1485-1504 — before extracting anything, compare `src/ReaLTaiizor/Controls/TextBox/MaterialMaskedTextBox.cs` and `src/ReaLTaiizor/Controls/TextBoxEdit/MaterialTextBoxEdit.cs` as WHOLE FILES: this scan already matched 27 separate duplicated blocks between them, totalling at least 574 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/ReaLTaiizor/Controls/TextBox/MaterialMaskedTextBox.cs:1529` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (21 lines × 3) src/ReaLTaiizor/Forms/Container/DungeonForm.cs:164— src/ReaLTaiizor/Forms/Container/DungeonForm.cs:164-184 | src/ReaLTaiizor/Forms/Container/FormTheme.cs:143-163 | src/ReaLTaiizor/Forms/Container/ThemeForm.cs:172-192 — before extracting anything, compare `src/ReaLTaiizor/Forms/Container/DungeonForm.cs` and `src/ReaLTaiizor/Forms/Container/FormTheme.cs` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 218 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/ReaLTaiizor/Forms/Container/DungeonForm.cs:164` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `src/ReaLTaiizor/Forms/Container/ThemeForm.cs:171` calls `Focus` and `src/ReaLTaiizor/Forms/Container/DungeonForm.cs:163` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (21 lines × 3) src/ReaLTaiizor/Util/Air.cs:1472— src/ReaLTaiizor/Util/Air.cs:1472-1492 | src/ReaLTaiizor/Util/Moon.cs:1471-1491 | src/ReaLTaiizor/Util/Space.cs:1468-1488 — before extracting anything, compare `src/ReaLTaiizor/Util/Air.cs` and `src/ReaLTaiizor/Util/Moon.cs` as WHOLE FILES: this scan already matched 40 separate duplicated blocks between them, totalling at least 661 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (21 lines × 3) src/ReaLTaiizor/Controls/Button/HopeButton.cs:111— src/ReaLTaiizor/Controls/Button/HopeButton.cs:111-131 | src/ReaLTaiizor/Controls/Button/HopeRoundButton.cs:118-138 | src/ReaLTaiizor/Controls/Button/HopeSimpleButton.cs:113-133 — before extracting anything, compare `src/ReaLTaiizor/Controls/Button/HopeRoundButton.cs` and `src/ReaLTaiizor/Controls/Button/HopeSimpleButton.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 40 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `src/ReaLTaiizor/Controls/Button/HopeButton.cs:110` calls `CreateRoundRect` and `src/ReaLTaiizor/Controls/Button/HopeRoundButton.cs:117` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (21 lines × 3) src/ReaLTaiizor/Extension/Poison/PoisonFonts.cs:734— src/ReaLTaiizor/Extension/Poison/PoisonFonts.cs:734-754 | src/ReaLTaiizor/Extension/Poison/PoisonFonts.cs:756-776 | src/ReaLTaiizor/Extension/Poison/PoisonFonts.cs:777-797 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/ReaLTaiizor/Extension/Poison/PoisonFonts.cs:734` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (19 lines × 2) src/ReaLTaiizor/Controls/CheckBox/ForeverCheckBox.cs:143— src/ReaLTaiizor/Controls/CheckBox/ForeverCheckBox.cs:143-161 | src/ReaLTaiizor/Controls/CheckBox/ForeverCheckBox.cs:178-196 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/ReaLTaiizor/Controls/CheckBox/ForeverCheckBox.cs:143` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `src/ReaLTaiizor/Controls/CheckBox/ForeverCheckBox.cs:177` calls `FillRectangle`, `SolidBrush`, `FromArgb` and `src/ReaLTaiizor/Controls/CheckBox/ForeverCheckBox.cs:142` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (19 lines × 2) ready/ReaLTaiizor.Hashing/ReaLTaiizor.Hashing/Hashing.cs:119— ready/ReaLTaiizor.Hashing/ReaLTaiizor.Hashing/Hashing.cs:119-137 | ready/ReaLTaiizor.Hashing/ReaLTaiizor.Hashing/Hashing.cs:169-187 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `ready/ReaLTaiizor.Hashing/ReaLTaiizor.Hashing/Hashing.cs:119` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (19 lines × 2) src/ReaLTaiizor/Controls/Badge/MetroBadge.cs:603— src/ReaLTaiizor/Controls/Badge/MetroBadge.cs:603-621 | src/ReaLTaiizor/Controls/Button/MetroButton.cs:274-292 — before extracting anything, compare `src/ReaLTaiizor/Controls/Badge/MetroBadge.cs` and `src/ReaLTaiizor/Controls/Button/MetroButton.cs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 97 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/ReaLTaiizor/Controls/Badge/MetroBadge.cs:603` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (19 lines × 2) src/ReaLTaiizor/Controls/ScrollBar/MaterialScrollBar.cs:91— src/ReaLTaiizor/Controls/ScrollBar/MaterialScrollBar.cs:91-109 | src/ReaLTaiizor/Controls/ScrollBar/PoisonScrollBar.cs:185-203 — before extracting anything, compare `src/ReaLTaiizor/Controls/ScrollBar/MaterialScrollBar.cs` and `src/ReaLTaiizor/Controls/ScrollBar/PoisonScrollBar.cs` as WHOLE FILES: this scan already matched 15 separate duplicated blocks between them, totalling at least 423 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (13 lines × 6) src/ReaLTaiizor/Design/Poison/PoisonButtonDesigner.cs:18— src/ReaLTaiizor/Design/Poison/PoisonButtonDesigner.cs:18-30 | src/ReaLTaiizor/Design/Poison/PoisonLabelDesigner.cs:18-30 | src/ReaLTaiizor/Design/Poison/PoisonProgressBarDesigner.cs:18-30 | src/ReaLTaiizor/Design/Poison/PoisonProgressSpinnerDesigner.cs:18-30 | src/ReaLTaiizor/Design/Poison/PoisonTabControlDesigner.cs:174-186 | src/ReaLTaiizor/Design/Poison/PoisonTileDesigner.cs:24-36 — before extracting anything, compare `src/ReaLTaiizor/Design/Poison/PoisonButtonDesigner.cs` and `src/ReaLTaiizor/Design/Poison/PoisonLabelDesigner.cs` as WHOLE FILES: 92% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 2 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (13 lines × 6) src/ReaLTaiizor/Util/Air.cs:1197— src/ReaLTaiizor/Util/Air.cs:1197-1209 | src/ReaLTaiizor/Util/Air.cs:2170-2182 | src/ReaLTaiizor/Util/Moon.cs:1190-1202 | src/ReaLTaiizor/Util/Moon.cs:2172-2184 | src/ReaLTaiizor/Util/Space.cs:1193-1205 | src/ReaLTaiizor/Util/Space.cs:2169-2181 — before extracting anything, compare `src/ReaLTaiizor/Util/Air.cs` and `src/ReaLTaiizor/Util/Moon.cs` as WHOLE FILES: this scan already matched 40 separate duplicated blocks between them, totalling at least 661 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/ReaLTaiizor/Util/Air.cs:1197` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (13 lines × 6) src/ReaLTaiizor/Util/Air.cs:1248— src/ReaLTaiizor/Util/Air.cs:1248-1260 | src/ReaLTaiizor/Util/Air.cs:2221-2233 | src/ReaLTaiizor/Util/Moon.cs:1241-1253 | src/ReaLTaiizor/Util/Moon.cs:2224-2236 | src/ReaLTaiizor/Util/Space.cs:1244-1256 | src/ReaLTaiizor/Util/Space.cs:2221-2233 — before extracting anything, compare `src/ReaLTaiizor/Util/Air.cs` and `src/ReaLTaiizor/Util/Moon.cs` as WHOLE FILES: this scan already matched 40 separate duplicated blocks between them, totalling at least 661 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/ReaLTaiizor/Util/Air.cs:1248` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (13 lines × 6) src/ReaLTaiizor/Controls/TextBox/FoxTextBox.cs:46— src/ReaLTaiizor/Controls/TextBox/FoxTextBox.cs:46-58 | src/ReaLTaiizor/Util/Fox.cs:138-150 | src/ReaLTaiizor/Util/Fox.cs:231-243 | src/ReaLTaiizor/Util/Fox.cs:327-339 | src/ReaLTaiizor/Util/Fox.cs:435-447 | src/ReaLTaiizor/Util/Fox.cs:595-607 — there are 6 copies across 2 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 6 sites; resolving a subset leaves the remainder to drift apart. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (12 lines × 3) src/ReaLTaiizor/Util/Air.cs:2538— src/ReaLTaiizor/Util/Air.cs:2538-2549 | src/ReaLTaiizor/Util/Moon.cs:2543-2554 | src/ReaLTaiizor/Util/Space.cs:2542-2553 — before extracting anything, compare `src/ReaLTaiizor/Util/Air.cs` and `src/ReaLTaiizor/Util/Moon.cs` as WHOLE FILES: this scan already matched 40 separate duplicated blocks between them, totalling at least 661 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (12 lines × 3) src/ReaLTaiizor/Controls/RichTextBox/CyberRichTextBox.cs:328— src/ReaLTaiizor/Controls/RichTextBox/CyberRichTextBox.cs:328-339 | src/ReaLTaiizor/Controls/Switch/CyberSwitch.cs:409-420 | src/ReaLTaiizor/Controls/TextBox/CyberTextBox.cs:367-378 — before extracting anything, compare `src/ReaLTaiizor/Controls/RichTextBox/CyberRichTextBox.cs` and `src/ReaLTaiizor/Controls/Switch/CyberSwitch.cs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 117 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (12 lines × 3) src/ReaLTaiizor/Controls/TextBox/MaterialMaskedTextBox.cs:283— src/ReaLTaiizor/Controls/TextBox/MaterialMaskedTextBox.cs:283-294 | src/ReaLTaiizor/Controls/TextBoxEdit/MaterialMultiLineTextBoxEdit.cs:143-154 | src/ReaLTaiizor/Controls/TextBoxEdit/MaterialTextBoxEdit.cs:264-275 — before extracting anything, compare `src/ReaLTaiizor/Controls/TextBox/MaterialMaskedTextBox.cs` and `src/ReaLTaiizor/Controls/TextBoxEdit/MaterialMultiLineTextBoxEdit.cs` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 164 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (12 lines × 3) src/ReaLTaiizor/Util/Air.cs:1680— src/ReaLTaiizor/Util/Air.cs:1680-1691 | src/ReaLTaiizor/Util/Moon.cs:1679-1690 | src/ReaLTaiizor/Util/Space.cs:1677-1688 — before extracting anything, compare `src/ReaLTaiizor/Util/Air.cs` and `src/ReaLTaiizor/Util/Moon.cs` as WHOLE FILES: this scan already matched 40 separate duplicated blocks between them, totalling at least 661 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (7 lines × 4) src/ReaLTaiizor/Controls/Badge/MetroBadge.cs:518— src/ReaLTaiizor/Controls/Badge/MetroBadge.cs:518-524 | src/ReaLTaiizor/Controls/Button/MetroDefaultButton.cs:187-193 | src/ReaLTaiizor/Controls/Ellipse/MetroEllipse.cs:200-206 | src/ReaLTaiizor/Controls/Tile/MetroTile.cs:219-225 — before extracting anything, compare `src/ReaLTaiizor/Controls/Badge/MetroBadge.cs` and `src/ReaLTaiizor/Controls/Button/MetroDefaultButton.cs` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 124 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (7 lines × 4) src/ReaLTaiizor/Controls/ControlBox/ThunderControlBox.cs:204— src/ReaLTaiizor/Controls/ControlBox/ThunderControlBox.cs:204-210 | src/ReaLTaiizor/Controls/ControlBox/ThunderControlBox.cs:266-272 | src/ReaLTaiizor/Controls/ControlBox/ThunderControlBox.cs:326-332 | src/ReaLTaiizor/Controls/ControlBox/ThunderControlBox.cs:354-360 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/ReaLTaiizor/Controls/ControlBox/ThunderControlBox.cs:204` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (7 lines × 4) src/ReaLTaiizor/Controls/Bubble/ChatBubbleLeft.cs:104— src/ReaLTaiizor/Controls/Bubble/ChatBubbleLeft.cs:104-112 | src/ReaLTaiizor/Controls/Button/ChatButtonLeft.cs:241-248 | src/ReaLTaiizor/Controls/Button/DungeonButtonLeft.cs:243-249 | src/ReaLTaiizor/Controls/Button/DungeonButtonRight.cs:243-249 — before extracting anything, compare `src/ReaLTaiizor/Controls/Button/ChatButtonLeft.cs` and `src/ReaLTaiizor/Controls/Button/DungeonButtonLeft.cs` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 228 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/ReaLTaiizor/Controls/Bubble/ChatBubbleLeft.cs:104` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (7 lines × 4) src/ReaLTaiizor/Controls/RichTextBox/HopeRichTextBox.cs:637— src/ReaLTaiizor/Controls/RichTextBox/HopeRichTextBox.cs:637-643 | src/ReaLTaiizor/Controls/RichTextBox/MaterialRichTextBox.cs:28-37 | src/ReaLTaiizor/Controls/TextBox/HopeTextBox.cs:627-633 | src/ReaLTaiizor/Controls/TextBox/MaterialSingleTextBox.cs:597-603 — before extracting anything, compare `src/ReaLTaiizor/Controls/RichTextBox/HopeRichTextBox.cs` and `src/ReaLTaiizor/Controls/TextBox/HopeTextBox.cs` as WHOLE FILES: 90% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 2 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (6 lines × 4) src/ReaLTaiizor/Controls/Button/MetroButton.cs:204— src/ReaLTaiizor/Controls/Button/MetroButton.cs:204-209 | src/ReaLTaiizor/Controls/Button/MetroButton.cs:220-225 | src/ReaLTaiizor/Controls/Tile/MetroTile.cs:210-215 | src/ReaLTaiizor/Controls/Tile/MetroTile.cs:226-231 — before extracting anything, compare `src/ReaLTaiizor/Controls/Button/MetroButton.cs` and `src/ReaLTaiizor/Controls/Tile/MetroTile.cs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 50 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (6 lines × 4) src/ReaLTaiizor/Controls/Numeric/MetroNumeric.cs:161— src/ReaLTaiizor/Controls/Numeric/MetroNumeric.cs:161-166 | src/ReaLTaiizor/Controls/RichTextBox/MetroRichTextBox.cs:216-221 | src/ReaLTaiizor/Controls/ScrollBar/MetroScrollBar.cs:134-139 | src/ReaLTaiizor/Controls/TextBox/MetroTextBox.cs:240-245 — before extracting anything, compare `src/ReaLTaiizor/Controls/Numeric/MetroNumeric.cs` and `src/ReaLTaiizor/Controls/RichTextBox/MetroRichTextBox.cs` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 106 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (6 lines × 4) src/ReaLTaiizor/Forms/Container/DungeonForm.cs:468— src/ReaLTaiizor/Forms/Container/DungeonForm.cs:468-474 | src/ReaLTaiizor/Forms/Container/DungeonForm.cs:475-480 | src/ReaLTaiizor/Forms/Container/ThemeForm.cs:476-482 | src/ReaLTaiizor/Forms/Container/ThemeForm.cs:483-488 — before extracting anything, compare `src/ReaLTaiizor/Forms/Container/DungeonForm.cs` and `src/ReaLTaiizor/Forms/Container/ThemeForm.cs` as WHOLE FILES: this scan already matched 17 separate duplicated blocks between them, totalling at least 286 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (6 lines × 4) src/ReaLTaiizor/Forms/Form/MaterialForm.cs:1330— src/ReaLTaiizor/Forms/Form/MaterialForm.cs:1330-1336 | src/ReaLTaiizor/Forms/Form/MaterialForm.cs:1337-1342 | src/ReaLTaiizor/Forms/Form/MaterialForm.cs:1343-1348 | src/ReaLTaiizor/Forms/Form/MaterialForm.cs:1349-1354 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/ReaLTaiizor/Forms/Form/MaterialForm.cs:1330` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (5 lines × 4) src/ReaLTaiizor/Controls/MessageBox/RoyalMessageBox.cs:263— src/ReaLTaiizor/Controls/MessageBox/RoyalMessageBox.cs:263-267 | src/ReaLTaiizor/Controls/MessageBox/RoyalMessageBox.cs:271-275 | src/ReaLTaiizor/Controls/MessageBox/RoyalMessageBox.cs:279-283 | src/ReaLTaiizor/Controls/MessageBox/RoyalMessageBox.cs:287-291 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/ReaLTaiizor/Controls/MessageBox/RoyalMessageBox.cs:263` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (5 lines × 4) src/ReaLTaiizor/Controls/CheckBox/CheckBox.cs:93— src/ReaLTaiizor/Controls/CheckBox/CheckBox.cs:93-97 | src/ReaLTaiizor/Controls/Numeric/DungeonNumeric.cs:123-127 | src/ReaLTaiizor/Controls/Panel/Panel.cs:53-57 | src/ReaLTaiizor/Controls/TextBoxEdit/TextBoxEdit.cs:197-201 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 4 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 4 times.
Duplicated block (5 lines × 4) src/ReaLTaiizor/Controls/TextBox/MaterialMaskedTextBox.cs:1042— src/ReaLTaiizor/Controls/TextBox/MaterialMaskedTextBox.cs:1042-1046 | src/ReaLTaiizor/Controls/TextBox/MaterialTextBox.cs:591-595 | src/ReaLTaiizor/Controls/TextBoxEdit/MaterialMultiLineTextBoxEdit.cs:842-846 | src/ReaLTaiizor/Controls/TextBoxEdit/MaterialTextBoxEdit.cs:995-999 — before extracting anything, compare `src/ReaLTaiizor/Controls/TextBox/MaterialMaskedTextBox.cs` and `src/ReaLTaiizor/Controls/TextBox/MaterialTextBox.cs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 167 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/ReaLTaiizor/Controls/TextBox/MaterialMaskedTextBox.cs:1042` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (5 lines × 4) src/ReaLTaiizor/Forms/Container/DungeonForm.cs:483— src/ReaLTaiizor/Forms/Container/DungeonForm.cs:483-489 | src/ReaLTaiizor/Forms/Container/DungeonForm.cs:490-494 | src/ReaLTaiizor/Forms/Container/ThemeForm.cs:491-497 | src/ReaLTaiizor/Forms/Container/ThemeForm.cs:498-502 — before extracting anything, compare `src/ReaLTaiizor/Forms/Container/DungeonForm.cs` and `src/ReaLTaiizor/Forms/Container/ThemeForm.cs` as WHOLE FILES: this scan already matched 17 separate duplicated blocks between them, totalling at least 286 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Change coupling: HopeTextBox.cs ↔ MaterialSingleTextBox.cs src/ReaLTaiizor/Controls/TextBox/HopeTextBox.cs:1— `src/ReaLTaiizor/Controls/TextBox/HopeTextBox.cs` and `src/ReaLTaiizor/Controls/TextBox/MaterialSingleTextBox.cs` change together 73% of the time (8 of the 11 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets). They sit in the same directory, and in this ecosystem sibling files there normally share one namespace/package — so a direct reference between them needs no import and this pass cannot see whether one exists. Read the pair before acting: if one file only DECLARES what the other consumes (a constants/types file beside its user), the co-change is definitional and the question is whether the split earns its keep; if they duplicate structure, extract the common part into a shared function or type they both call; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 8 shared commits counted here, the most recent 3 are `e2044f65` Update Packages; `0b5c90b4` .NET 8 Support; `19b8dc3d` #55 Bug Fixes — run `git show` on any of them.
Change coupling: MaterialCheckBox.cs ↔ MaterialTextBoxEdit.cs src/ReaLTaiizor/Controls/CheckBox/MaterialCheckBox.cs:1— `src/ReaLTaiizor/Controls/CheckBox/MaterialCheckBox.cs` and `src/ReaLTaiizor/Controls/TextBoxEdit/MaterialTextBoxEdit.cs` change together 58% of the time (7 of the 12 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets). They sit in different directories, but in this ecosystem the namespace is declared in the FILE, not by the folder — so the two may well share one namespace and reference each other with no import for this pass to see. Read the pair before acting: if one derives from or overrides the other, the dependency is explicit in the type declaration and the co-change is definitional; if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE and the thing to add is a comment saying so; if they simply belong together, co-locate them; if none of these holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 7 shared commits counted here, the most recent 3 are `8ef7d447` Use expression-bodied setters and minor cleanups; `43b93049` This push provides more supported controls and improvements.; `e301df46` This code push upgraded the scaling logic and improved the stability … — run `git show` on any of them.
Change coupling: MaterialContextMenuStrip.cs ↔ MaterialForm.cs src/ReaLTaiizor/Controls/Strip/MaterialContextMenuStrip.cs:1— `src/ReaLTaiizor/Controls/Strip/MaterialContextMenuStrip.cs` and `src/ReaLTaiizor/Forms/Form/MaterialForm.cs` change together 52% of the time (11 of the 21 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets). They sit in different directories, but in this ecosystem the namespace is declared in the FILE, not by the folder — so the two may well share one namespace and reference each other with no import for this pass to see. Read the pair before acting: if one derives from or overrides the other, the dependency is explicit in the type declaration and the co-change is definitional; if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE and the thing to add is a comment saying so; if they simply belong together, co-locate them; if none of these holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 11 shared commits counted here, the most recent 3 are `8ef7d447` Use expression-bodied setters and minor cleanups; `e301df46` This code push upgraded the scaling logic and improved the stability …; `69be4bd5` Thanks to @Copilot, this patch applied a new method to manage LFont o… — run `git show` on any of them.
D4 · Code Duplication· Members sharing a duplicated core (9 members, 50+ identical tokens) · ×3
Members sharing a duplicated core (9 members, 50+ identical tokens) src/ReaLTaiizor/Controls/Button/CyberButton.cs:58— src/ReaLTaiizor/Controls/Button/CyberButton.cs:58-84 | src/ReaLTaiizor/Controls/CheckBox/CyberCheckBox.cs:67-93 | src/ReaLTaiizor/Controls/GroupBox/CyberGroupBox.cs:55-81 | src/ReaLTaiizor/Controls/Progress/CyberProgressBar.cs:115-141 | src/ReaLTaiizor/Controls/RadioButton/CyberRadioButton.cs:84-110 | src/ReaLTaiizor/Controls/RichTextBox/CyberRichTextBox.cs:55-81 | src/ReaLTaiizor/Controls/ScrollBar/CyberScrollBar.cs:137-163 | src/ReaLTaiizor/Controls/Switch/CyberSwitch.cs:53-79 | src/ReaLTaiizor/Controls/TextBox/CyberTextBox.cs:55-81 — These 9 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 9 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 9 times.
Members sharing a duplicated core (9 members, 50+ identical tokens) src/ReaLTaiizor/Controls/Button/CyberButton.cs:596— src/ReaLTaiizor/Controls/Button/CyberButton.cs:596-626 | src/ReaLTaiizor/Controls/CheckBox/CyberCheckBox.cs:592-616 | src/ReaLTaiizor/Controls/GroupBox/CyberGroupBox.cs:485-515 | src/ReaLTaiizor/Controls/Progress/CyberProgressBar.cs:646-676 | src/ReaLTaiizor/Controls/RadioButton/CyberRadioButton.cs:646-670 | src/ReaLTaiizor/Controls/RichTextBox/CyberRichTextBox.cs:492-522 | src/ReaLTaiizor/Controls/ScrollBar/CyberScrollBar.cs:739-769 | src/ReaLTaiizor/Controls/Switch/CyberSwitch.cs:567-597 | src/ReaLTaiizor/Controls/TextBox/CyberTextBox.cs:541-571 — These 9 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 9 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 9 times.
Members sharing a duplicated core (9 members, 50+ identical tokens) src/ReaLTaiizor/Design/Poison/PoisonButtonDesigner.cs:17— src/ReaLTaiizor/Design/Poison/PoisonButtonDesigner.cs:17-38 | src/ReaLTaiizor/Design/Poison/PoisonCheckBoxDesigner.cs:15-35 | src/ReaLTaiizor/Design/Poison/PoisonLabelDesigner.cs:17-38 | src/ReaLTaiizor/Design/Poison/PoisonProgressBarDesigner.cs:17-43 | src/ReaLTaiizor/Design/Poison/PoisonProgressSpinnerDesigner.cs:17-42 | src/ReaLTaiizor/Design/Poison/PoisonRadioButtonDesigner.cs:15-35 | src/ReaLTaiizor/Design/Poison/PoisonTabControlDesigner.cs:173-196 | src/ReaLTaiizor/Design/Poison/PoisonTileDesigner.cs:23-46 | src/ReaLTaiizor/Design/Poison/PoisonToggleDesigner.cs:15-35 — These 9 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 9 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 9 times.
D4 · Code Duplication· Members sharing a duplicated core (7 members, 50+ identical tokens) · ×3
Members sharing a duplicated core (7 members, 50+ identical tokens) src/ReaLTaiizor/Colors/Material.cs:26— src/ReaLTaiizor/Colors/Material.cs:26-47 | src/ReaLTaiizor/Colors/Material.cs:50-75 | src/ReaLTaiizor/Colors/Material.cs:78-103 | src/ReaLTaiizor/Colors/Material.cs:106-127 | src/ReaLTaiizor/Colors/Material.cs:130-151 | src/ReaLTaiizor/Colors/Material.cs:154-175 | src/ReaLTaiizor/Colors/Material.cs:178-199 — These 7 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 7 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 7 times.
Members sharing a duplicated core (7 members, 50+ identical tokens) src/ReaLTaiizor/Controls/ComboBox/PoisonComboBox.cs:381— src/ReaLTaiizor/Controls/ComboBox/PoisonComboBox.cs:381-405 | src/ReaLTaiizor/Controls/DateTime/PoisonDateTime.cs:274-298 | src/ReaLTaiizor/Controls/LinkLabel/PoisonLinkLabel.cs:271-295 | src/ReaLTaiizor/Controls/Panel/PoisonPanel.cs:256-280 | src/ReaLTaiizor/Controls/TabControl/PoisonTabControl.cs:208-232 | src/ReaLTaiizor/Controls/TabPage/PoisonTabPage.cs:251-275 | src/ReaLTaiizor/Controls/UserControl/PoisonUserControl.cs:136-160 — These 7 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 7 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 7 times.
Members sharing a duplicated core (7 members, 50+ identical tokens) src/ReaLTaiizor/Forms/Panel/ParrotForm.cs:294— src/ReaLTaiizor/Forms/Panel/ParrotForm.cs:294-680 | src/ReaLTaiizor/Forms/Panel/ParrotForm.cs:717-728 | src/ReaLTaiizor/Forms/Panel/ParrotForm.cs:731-740 | src/ReaLTaiizor/Forms/Panel/ParrotForm.cs:743-753 | src/ReaLTaiizor/Forms/Panel/ParrotForm.cs:756-765 | src/ReaLTaiizor/Forms/Panel/ParrotForm.cs:768-778 | src/ReaLTaiizor/Forms/Panel/ParrotForm.cs:781-790 — These 7 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 7 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 7 times.
Duplicated block (29 lines × 3) src/ReaLTaiizor/Controls/Badge/MetroBadge.cs:556— src/ReaLTaiizor/Controls/Badge/MetroBadge.cs:556-584 | src/ReaLTaiizor/Controls/Button/MetroButton.cs:245-273 | src/ReaLTaiizor/Controls/Button/MetroDefaultButton.cs:219-247 — before extracting anything, compare `src/ReaLTaiizor/Controls/Badge/MetroBadge.cs` and `src/ReaLTaiizor/Controls/Button/MetroButton.cs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 97 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/ReaLTaiizor/Controls/Badge/MetroBadge.cs:556` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (29 lines × 3) src/ReaLTaiizor/Forms/Container/DungeonForm.cs:311— src/ReaLTaiizor/Forms/Container/DungeonForm.cs:311-339 | src/ReaLTaiizor/Forms/Container/FormTheme.cs:290-318 | src/ReaLTaiizor/Forms/Container/ThemeForm.cs:319-347 — before extracting anything, compare `src/ReaLTaiizor/Forms/Container/DungeonForm.cs` and `src/ReaLTaiizor/Forms/Container/FormTheme.cs` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 218 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (29 lines × 3) src/ReaLTaiizor/Controls/Progress/CyberProgressBar.cs:525— src/ReaLTaiizor/Controls/Progress/CyberProgressBar.cs:525-553 | src/ReaLTaiizor/Controls/ScrollBar/CyberScrollBar.cs:551-579 | src/ReaLTaiizor/Controls/Switch/CyberSwitch.cs:441-469 — before extracting anything, compare `src/ReaLTaiizor/Controls/Progress/CyberProgressBar.cs` and `src/ReaLTaiizor/Controls/ScrollBar/CyberScrollBar.cs` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 183 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/ReaLTaiizor/Controls/Progress/CyberProgressBar.cs:525` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `src/ReaLTaiizor/Controls/Progress/CyberProgressBar.cs:555` calls `Bool` and `src/ReaLTaiizor/Controls/ScrollBar/CyberScrollBar.cs:581` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (14 lines × 5) src/ReaLTaiizor/Design/Poison/PoisonButtonDesigner.cs:25— src/ReaLTaiizor/Design/Poison/PoisonButtonDesigner.cs:25-38 | src/ReaLTaiizor/Design/Poison/PoisonCheckBoxDesigner.cs:22-35 | src/ReaLTaiizor/Design/Poison/PoisonLabelDesigner.cs:25-38 | src/ReaLTaiizor/Design/Poison/PoisonRadioButtonDesigner.cs:22-35 | src/ReaLTaiizor/Design/Poison/PoisonToggleDesigner.cs:22-35 — before extracting anything, compare `src/ReaLTaiizor/Design/Poison/PoisonButtonDesigner.cs` and `src/ReaLTaiizor/Design/Poison/PoisonCheckBoxDesigner.cs` as WHOLE FILES: 91% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/ReaLTaiizor/Design/Poison/PoisonButtonDesigner.cs:25` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (14 lines × 5) src/ReaLTaiizor/Util/Royal.cs:354— src/ReaLTaiizor/Util/Royal.cs:354-367 | src/ReaLTaiizor/Util/Royal.cs:373-386 | src/ReaLTaiizor/Util/Royal.cs:392-405 | src/ReaLTaiizor/Util/Royal.cs:411-424 | src/ReaLTaiizor/Util/Royal.cs:430-443 — all 5 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/ReaLTaiizor/Util/Royal.cs:354` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (14 lines × 5) src/ReaLTaiizor/Controls/Button/Button.cs:38— src/ReaLTaiizor/Controls/Button/Button.cs:38-52 | src/ReaLTaiizor/Controls/Button/ChatButtonLeft.cs:41-55 | src/ReaLTaiizor/Controls/Button/ChatButtonRight.cs:39-52 | src/ReaLTaiizor/Controls/Button/DungeonButtonLeft.cs:40-54 | src/ReaLTaiizor/Controls/Button/DungeonButtonRight.cs:40-54 — before extracting anything, compare `src/ReaLTaiizor/Controls/Button/Button.cs` and `src/ReaLTaiizor/Controls/Button/ChatButtonLeft.cs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 90 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/ReaLTaiizor/Controls/Button/Button.cs:38` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (12–13 lines × 2) src/ReaLTaiizor/Controls/Numeric/DungeonNumeric.cs:36— src/ReaLTaiizor/Controls/Numeric/DungeonNumeric.cs:36-48 | src/ReaLTaiizor/Controls/Progress/DungeonProgressBar.cs:41-52 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `src/ReaLTaiizor/Controls/Progress/DungeonProgressBar.cs:56` calls `FromArgb` and `src/ReaLTaiizor/Controls/Numeric/DungeonNumeric.cs:52` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (12–13 lines × 2) src/ReaLTaiizor/Controls/Palette/ForeverPalette.cs:72— src/ReaLTaiizor/Controls/Palette/ForeverPalette.cs:72-83 | src/ReaLTaiizor/Controls/TabPage/ForeverTabPage.cs:56-68 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `src/ReaLTaiizor/Controls/Palette/ForeverPalette.cs:72` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (12–13 lines × 2) src/ReaLTaiizor/Controls/TabPage/TabPage.cs:268— src/ReaLTaiizor/Controls/TabPage/TabPage.cs:268-279 | src/ReaLTaiizor/Controls/TabPage/TabPage.cs:290-302 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/ReaLTaiizor/Controls/TabPage/TabPage.cs:268` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (10 lines × 4) src/ReaLTaiizor/Controls/ComboBox/MetroComboBox.cs:319— src/ReaLTaiizor/Controls/ComboBox/MetroComboBox.cs:319-328 | src/ReaLTaiizor/Controls/Numeric/MetroNumeric.cs:171-180 | src/ReaLTaiizor/Controls/RichTextBox/MetroRichTextBox.cs:226-235 | src/ReaLTaiizor/Controls/TextBox/MetroTextBox.cs:250-259 — before extracting anything, compare `src/ReaLTaiizor/Controls/ComboBox/MetroComboBox.cs` and `src/ReaLTaiizor/Controls/Numeric/MetroNumeric.cs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 71 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/ReaLTaiizor/Controls/ComboBox/MetroComboBox.cs:319` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (10 lines × 4) src/ReaLTaiizor/Controls/Badge/MetroBadge.cs:428— src/ReaLTaiizor/Controls/Badge/MetroBadge.cs:428-437 | src/ReaLTaiizor/Controls/Badge/MetroBadge.cs:444-453 | src/ReaLTaiizor/Controls/Badge/MetroBadge.cs:460-469 | src/ReaLTaiizor/Controls/Badge/MetroBadge.cs:476-485 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (10 lines × 4) src/ReaLTaiizor/Controls/TextBox/MaterialMaskedTextBox.cs:1164— src/ReaLTaiizor/Controls/TextBox/MaterialMaskedTextBox.cs:1164-1173 | src/ReaLTaiizor/Controls/TextBox/MaterialMaskedTextBox.cs:1182-1191 | src/ReaLTaiizor/Controls/TextBoxEdit/MaterialTextBoxEdit.cs:1122-1131 | src/ReaLTaiizor/Controls/TextBoxEdit/MaterialTextBoxEdit.cs:1141-1150 — before extracting anything, compare `src/ReaLTaiizor/Controls/TextBox/MaterialMaskedTextBox.cs` and `src/ReaLTaiizor/Controls/TextBoxEdit/MaterialTextBoxEdit.cs` as WHOLE FILES: this scan already matched 27 separate duplicated blocks between them, totalling at least 574 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/ReaLTaiizor/Controls/TextBox/MaterialMaskedTextBox.cs:1164` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `src/ReaLTaiizor/Controls/TextBoxEdit/MaterialTextBoxEdit.cs:1134` calls `GetTextBoxFontBySize` and `src/ReaLTaiizor/Controls/TextBox/MaterialMaskedTextBox.cs:1176` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (9 lines × 4) src/ReaLTaiizor/Controls/Badge/MetroBadge.cs:540— src/ReaLTaiizor/Controls/Badge/MetroBadge.cs:540-548 | src/ReaLTaiizor/Controls/Button/MetroDefaultButton.cs:203-211 | src/ReaLTaiizor/Controls/Ellipse/MetroEllipse.cs:216-224 | src/ReaLTaiizor/Controls/Tile/MetroTile.cs:235-243 — before extracting anything, compare `src/ReaLTaiizor/Controls/Badge/MetroBadge.cs` and `src/ReaLTaiizor/Controls/Button/MetroDefaultButton.cs` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 124 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/ReaLTaiizor/Controls/Badge/MetroBadge.cs:540` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (9 lines × 4) src/ReaLTaiizor/Controls/ComboBox/MetroComboBox.cs:305— src/ReaLTaiizor/Controls/ComboBox/MetroComboBox.cs:305-313 | src/ReaLTaiizor/Controls/Numeric/MetroNumeric.cs:159-167 | src/ReaLTaiizor/Controls/RichTextBox/MetroRichTextBox.cs:214-222 | src/ReaLTaiizor/Controls/TextBox/MetroTextBox.cs:238-246 — before extracting anything, compare `src/ReaLTaiizor/Controls/ComboBox/MetroComboBox.cs` and `src/ReaLTaiizor/Controls/Numeric/MetroNumeric.cs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 71 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (9 lines × 4) src/ReaLTaiizor/Controls/CheckBox/MetroCheckBox.cs:262— src/ReaLTaiizor/Controls/CheckBox/MetroCheckBox.cs:262-271 | src/ReaLTaiizor/Controls/ListBox/MetroListBox.cs:727-735 | src/ReaLTaiizor/Controls/Numeric/MetroNumeric.cs:387-396 | src/ReaLTaiizor/Controls/RadioButton/MetroRadioButton.cs:263-272 — before extracting anything, compare `src/ReaLTaiizor/Controls/CheckBox/MetroCheckBox.cs` and `src/ReaLTaiizor/Controls/RadioButton/MetroRadioButton.cs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 90 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (8 lines × 6) src/ReaLTaiizor/Controls/Button/MetroDefaultButton.cs:183— src/ReaLTaiizor/Controls/Button/MetroDefaultButton.cs:183-190 | src/ReaLTaiizor/Controls/Button/MetroDefaultButton.cs:199-206 | src/ReaLTaiizor/Controls/Ellipse/MetroEllipse.cs:196-203 | src/ReaLTaiizor/Controls/Ellipse/MetroEllipse.cs:212-219 | src/ReaLTaiizor/Controls/Tile/MetroTile.cs:215-222 | src/ReaLTaiizor/Controls/Tile/MetroTile.cs:231-238 — before extracting anything, compare `src/ReaLTaiizor/Controls/Button/MetroDefaultButton.cs` and `src/ReaLTaiizor/Controls/Ellipse/MetroEllipse.cs` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 122 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (8 lines × 6) src/ReaLTaiizor/Util/Air.cs:1433— src/ReaLTaiizor/Util/Air.cs:1433-1440 | src/ReaLTaiizor/Util/Air.cs:2406-2413 | src/ReaLTaiizor/Util/Moon.cs:1427-1434 | src/ReaLTaiizor/Util/Moon.cs:2411-2418 | src/ReaLTaiizor/Util/Space.cs:1431-1438 | src/ReaLTaiizor/Util/Space.cs:2408-2415 — before extracting anything, compare `src/ReaLTaiizor/Util/Air.cs` and `src/ReaLTaiizor/Util/Moon.cs` as WHOLE FILES: this scan already matched 40 separate duplicated blocks between them, totalling at least 661 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (8 lines × 6) src/ReaLTaiizor/Forms/Panel/ParrotForm.cs:457— src/ReaLTaiizor/Forms/Panel/ParrotForm.cs:457-464 | src/ReaLTaiizor/Forms/Panel/ParrotForm.cs:486-493 | src/ReaLTaiizor/Forms/Panel/ParrotForm.cs:512-519 | src/ReaLTaiizor/Forms/Panel/ParrotForm.cs:586-593 | src/ReaLTaiizor/Forms/Panel/ParrotForm.cs:612-619 | src/ReaLTaiizor/Forms/Panel/ParrotForm.cs:636-643 — all 6 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `src/ReaLTaiizor/Forms/Panel/ParrotForm.cs:594` calls `DrawEllipse`, `Pen`, `FromArgb` and `src/ReaLTaiizor/Forms/Panel/ParrotForm.cs:466` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication· Near-duplicate member family (3 members, 13 shared lines) · ×2
Near-duplicate member family (3 members, 13 shared lines) src/ReaLTaiizor/Util/Air.cs:1240— src/ReaLTaiizor/Util/Air.cs:1240-1260 | src/ReaLTaiizor/Util/Moon.cs:1233-1253 | src/ReaLTaiizor/Util/Space.cs:1236-1256 — These 3 members are variants of one another: a block of 13 lines reported below appears in every one of them, and the pairwise near-duplicate rows they would otherwise produce are collapsed into this row. Read them as one construct written 3 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 3 times.
Near-duplicate member family (3 members, 13 shared lines) src/ReaLTaiizor/Util/Air.cs:2213— src/ReaLTaiizor/Util/Air.cs:2213-2233 | src/ReaLTaiizor/Util/Moon.cs:2216-2236 | src/ReaLTaiizor/Util/Space.cs:2213-2233 — These 3 members are variants of one another: a block of 13 lines reported below appears in every one of them, and the pairwise near-duplicate rows they would otherwise produce are collapsed into this row. Read them as one construct written 3 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 3 times.
D4 · Code Duplication· Members sharing a duplicated core (10 members, 50+ identical tokens) · ×2
Members sharing a duplicated core (10 members, 50+ identical tokens) src/ReaLTaiizor/Controls/Badge/MetroBadge.cs:494— src/ReaLTaiizor/Controls/Badge/MetroBadge.cs:494-621 | src/ReaLTaiizor/Controls/Button/MetroButton.cs:195-292 | src/ReaLTaiizor/Controls/Button/MetroDefaultButton.cs:169-266 | src/ReaLTaiizor/Controls/ComboBox/MetroComboBox.cs:290-371 | src/ReaLTaiizor/Controls/ListBox/MetroListBox.cs:155-236 | src/ReaLTaiizor/Controls/Numeric/MetroNumeric.cs:146-217 | src/ReaLTaiizor/Controls/RichTextBox/MetroRichTextBox.cs:201-272 | src/ReaLTaiizor/Controls/ScrollBar/MetroScrollBar.cs:122-178 | src/ReaLTaiizor/Controls/Strip/MetroContextMenuStrip.cs:95-166 | src/ReaLTaiizor/Controls/TextBox/MetroTextBox.cs:225-297 — These 10 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 10 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 10 times.
Members sharing a duplicated core (10 members, 50+ identical tokens) src/ReaLTaiizor/Controls/Button/CyberButton.cs:395— src/ReaLTaiizor/Controls/Button/CyberButton.cs:395-482 | src/ReaLTaiizor/Controls/CheckBox/CyberCheckBox.cs:375-454 | src/ReaLTaiizor/Controls/ComboBox/CyberComboBox.cs:263-317 | src/ReaLTaiizor/Controls/GroupBox/CyberGroupBox.cs:326-404 | src/ReaLTaiizor/Controls/Progress/CyberProgressBar.cs:461-562 | src/ReaLTaiizor/Controls/RadioButton/CyberRadioButton.cs:427-509 | src/ReaLTaiizor/Controls/RichTextBox/CyberRichTextBox.cs:311-373 | src/ReaLTaiizor/Controls/ScrollBar/CyberScrollBar.cs:488-587 | src/ReaLTaiizor/Controls/Switch/CyberSwitch.cs:384-476 | src/ReaLTaiizor/Controls/TextBox/CyberTextBox.cs:347-414 — These 10 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 10 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 10 times.
Duplicated block (79 lines × 2) src/ReaLTaiizor/Controls/Button/ForeverButton.cs:81— src/ReaLTaiizor/Controls/Button/ForeverButton.cs:81-159 | src/ReaLTaiizor/Controls/Button/ForeverButtonSticky.cs:123-201 — before extracting anything, compare `src/ReaLTaiizor/Controls/Button/ForeverButton.cs` and `src/ReaLTaiizor/Controls/Button/ForeverButtonSticky.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 94 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/ReaLTaiizor/Controls/Button/ForeverButton.cs:81` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (79 lines × 2) src/ReaLTaiizor/Controls/RadioButton/MaterialRadioButton.cs:285— src/ReaLTaiizor/Controls/RadioButton/MaterialRadioButton.cs:285-363 | src/ReaLTaiizor/Controls/Switch/MaterialSwitch.cs:338-416 — before extracting anything, compare `src/ReaLTaiizor/Controls/RadioButton/MaterialRadioButton.cs` and `src/ReaLTaiizor/Controls/Switch/MaterialSwitch.cs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 166 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/ReaLTaiizor/Controls/RadioButton/MaterialRadioButton.cs:285` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (48 lines × 3) src/ReaLTaiizor/Forms/Container/DungeonForm.cs:258— src/ReaLTaiizor/Forms/Container/DungeonForm.cs:258-305 | src/ReaLTaiizor/Forms/Container/FormTheme.cs:237-284 | src/ReaLTaiizor/Forms/Container/ThemeForm.cs:266-313 — before extracting anything, compare `src/ReaLTaiizor/Forms/Container/DungeonForm.cs` and `src/ReaLTaiizor/Forms/Container/FormTheme.cs` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 218 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (48 lines × 3) src/ReaLTaiizor/Util/Air.cs:327— src/ReaLTaiizor/Util/Air.cs:327-374 | src/ReaLTaiizor/Util/Moon.cs:320-367 | src/ReaLTaiizor/Util/Space.cs:322-369 — before extracting anything, compare `src/ReaLTaiizor/Util/Air.cs` and `src/ReaLTaiizor/Util/Moon.cs` as WHOLE FILES: this scan already matched 40 separate duplicated blocks between them, totalling at least 661 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (31 lines × 3) src/ReaLTaiizor/Util/Air.cs:45— src/ReaLTaiizor/Util/Air.cs:45-75 | src/ReaLTaiizor/Util/Moon.cs:44-74 | src/ReaLTaiizor/Util/Space.cs:45-75 — before extracting anything, compare `src/ReaLTaiizor/Util/Air.cs` and `src/ReaLTaiizor/Util/Moon.cs` as WHOLE FILES: this scan already matched 40 separate duplicated blocks between them, totalling at least 661 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (31 lines × 3) src/ReaLTaiizor/Util/Air.cs:80— src/ReaLTaiizor/Util/Air.cs:80-110 | src/ReaLTaiizor/Util/Moon.cs:79-109 | src/ReaLTaiizor/Util/Space.cs:80-110 — before extracting anything, compare `src/ReaLTaiizor/Util/Air.cs` and `src/ReaLTaiizor/Util/Moon.cs` as WHOLE FILES: this scan already matched 40 separate duplicated blocks between them, totalling at least 661 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (30 lines × 3) src/ReaLTaiizor/Controls/CheckBox/MaterialCheckBox.cs:319— src/ReaLTaiizor/Controls/CheckBox/MaterialCheckBox.cs:319-348 | src/ReaLTaiizor/Controls/RadioButton/MaterialRadioButton.cs:271-300 | src/ReaLTaiizor/Controls/Switch/MaterialSwitch.cs:324-353 — before extracting anything, compare `src/ReaLTaiizor/Controls/CheckBox/MaterialCheckBox.cs` and `src/ReaLTaiizor/Controls/RadioButton/MaterialRadioButton.cs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 99 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/ReaLTaiizor/Controls/CheckBox/MaterialCheckBox.cs:319` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (30 lines × 3) src/ReaLTaiizor/Util/Air.cs:380— src/ReaLTaiizor/Util/Air.cs:380-409 | src/ReaLTaiizor/Util/Moon.cs:373-402 | src/ReaLTaiizor/Util/Space.cs:375-404 — before extracting anything, compare `src/ReaLTaiizor/Util/Air.cs` and `src/ReaLTaiizor/Util/Moon.cs` as WHOLE FILES: this scan already matched 40 separate duplicated blocks between them, totalling at least 661 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (29 lines × 2) src/ReaLTaiizor/Controls/RichTextBox/MetroRichTextBox.cs:202— src/ReaLTaiizor/Controls/RichTextBox/MetroRichTextBox.cs:202-230 | src/ReaLTaiizor/Controls/TextBox/MetroTextBox.cs:226-254 — before extracting anything, compare `src/ReaLTaiizor/Controls/RichTextBox/MetroRichTextBox.cs` and `src/ReaLTaiizor/Controls/TextBox/MetroTextBox.cs` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 143 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/ReaLTaiizor/Controls/RichTextBox/MetroRichTextBox.cs:202` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (29 lines × 2) src/ReaLTaiizor/Controls/ScrollBar/MaterialScrollBar.cs:184— src/ReaLTaiizor/Controls/ScrollBar/MaterialScrollBar.cs:184-212 | src/ReaLTaiizor/Controls/ScrollBar/PoisonScrollBar.cs:290-318 — before extracting anything, compare `src/ReaLTaiizor/Controls/ScrollBar/MaterialScrollBar.cs` and `src/ReaLTaiizor/Controls/ScrollBar/PoisonScrollBar.cs` as WHOLE FILES: this scan already matched 15 separate duplicated blocks between them, totalling at least 423 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (18 lines × 3) src/ReaLTaiizor/Controls/Graph/ParrotBarGraph.cs:208— src/ReaLTaiizor/Controls/Graph/ParrotBarGraph.cs:208-225 | src/ReaLTaiizor/Controls/Graph/ParrotBarGraph.cs:343-360 | src/ReaLTaiizor/Controls/Graph/ParrotBarGraph.cs:461-478 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (18 lines × 3) src/ReaLTaiizor/Forms/Container/DungeonForm.cs:131— src/ReaLTaiizor/Forms/Container/DungeonForm.cs:131-148 | src/ReaLTaiizor/Forms/Container/FormTheme.cs:110-127 | src/ReaLTaiizor/Forms/Container/ThemeForm.cs:138-155 — before extracting anything, compare `src/ReaLTaiizor/Forms/Container/DungeonForm.cs` and `src/ReaLTaiizor/Forms/Container/FormTheme.cs` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 218 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/ReaLTaiizor/Forms/Container/DungeonForm.cs:131` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (22 lines × 3) src/ReaLTaiizor/Forms/Container/DungeonForm.cs:395— src/ReaLTaiizor/Forms/Container/DungeonForm.cs:395-416 | src/ReaLTaiizor/Forms/Container/FormTheme.cs:374-395 | src/ReaLTaiizor/Forms/Container/ThemeForm.cs:404-425 — before extracting anything, compare `src/ReaLTaiizor/Forms/Container/DungeonForm.cs` and `src/ReaLTaiizor/Forms/Container/FormTheme.cs` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 218 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (22 lines × 3) src/ReaLTaiizor/Util/Air.cs:487— src/ReaLTaiizor/Util/Air.cs:487-508 | src/ReaLTaiizor/Util/Moon.cs:480-501 | src/ReaLTaiizor/Util/Space.cs:482-503 — before extracting anything, compare `src/ReaLTaiizor/Util/Air.cs` and `src/ReaLTaiizor/Util/Moon.cs` as WHOLE FILES: this scan already matched 40 separate duplicated blocks between them, totalling at least 661 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (22 lines × 2) src/ReaLTaiizor/Controls/Ellipse/ParrotControlEllipse.cs:28— src/ReaLTaiizor/Controls/Ellipse/ParrotControlEllipse.cs:28-49 | src/ReaLTaiizor/Controls/Ellipse/ParrotObjectEllipse.cs:29-50 — before extracting anything, compare `src/ReaLTaiizor/Controls/Ellipse/ParrotControlEllipse.cs` and `src/ReaLTaiizor/Controls/Ellipse/ParrotObjectEllipse.cs` as WHOLE FILES: 86% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 2 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/ReaLTaiizor/Controls/Ellipse/ParrotControlEllipse.cs:28` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (22 lines × 2) src/ReaLTaiizor/Controls/Button/MaterialButton.cs:461— src/ReaLTaiizor/Controls/Button/MaterialButton.cs:461-483 | src/ReaLTaiizor/Controls/TextBox/MaterialTextBox.cs:438-459 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (21 lines × 2) src/ReaLTaiizor/Controls/TextBox/MaterialMaskedTextBox.cs:1212— src/ReaLTaiizor/Controls/TextBox/MaterialMaskedTextBox.cs:1212-1232 | src/ReaLTaiizor/Controls/TextBoxEdit/MaterialTextBoxEdit.cs:1172-1192 — before extracting anything, compare `src/ReaLTaiizor/Controls/TextBox/MaterialMaskedTextBox.cs` and `src/ReaLTaiizor/Controls/TextBoxEdit/MaterialTextBoxEdit.cs` as WHOLE FILES: this scan already matched 27 separate duplicated blocks between them, totalling at least 574 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (21 lines × 2) src/ReaLTaiizor/Controls/TrackBar/DungeonTrackBar.cs:113— src/ReaLTaiizor/Controls/TrackBar/DungeonTrackBar.cs:113-133 | src/ReaLTaiizor/Controls/TrackBar/TrackBar.cs:101-121 — before extracting anything, compare `src/ReaLTaiizor/Controls/TrackBar/DungeonTrackBar.cs` and `src/ReaLTaiizor/Controls/TrackBar/TrackBar.cs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 67 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (18 lines × 4) src/ReaLTaiizor/Controls/Button/CyberButton.cs:465— src/ReaLTaiizor/Controls/Button/CyberButton.cs:465-482 | src/ReaLTaiizor/Controls/CheckBox/CyberCheckBox.cs:437-454 | src/ReaLTaiizor/Controls/GroupBox/CyberGroupBox.cs:387-404 | src/ReaLTaiizor/Controls/RadioButton/CyberRadioButton.cs:492-509 — before extracting anything, compare `src/ReaLTaiizor/Controls/Button/CyberButton.cs` and `src/ReaLTaiizor/Controls/CheckBox/CyberCheckBox.cs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 119 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/ReaLTaiizor/Controls/Button/CyberButton.cs:465` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (18 lines × 4) src/ReaLTaiizor/Controls/ComboBox/MetroComboBox.cs:350— src/ReaLTaiizor/Controls/ComboBox/MetroComboBox.cs:350-367 | src/ReaLTaiizor/Controls/Numeric/MetroNumeric.cs:196-213 | src/ReaLTaiizor/Controls/RichTextBox/MetroRichTextBox.cs:251-268 | src/ReaLTaiizor/Controls/TextBox/MetroTextBox.cs:278-295 — before extracting anything, compare `src/ReaLTaiizor/Controls/ComboBox/MetroComboBox.cs` and `src/ReaLTaiizor/Controls/Numeric/MetroNumeric.cs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 71 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/ReaLTaiizor/Controls/ComboBox/MetroComboBox.cs:350` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `src/ReaLTaiizor/Controls/ComboBox/MetroComboBox.cs:369` calls `ArgumentOutOfRangeException`, `nameof` and `src/ReaLTaiizor/Controls/TextBox/MetroTextBox.cs:296` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (18–19 lines × 2) src/ReaLTaiizor/Controls/Drawer/MaterialDrawer.cs:353— src/ReaLTaiizor/Controls/Drawer/MaterialDrawer.cs:353-371 | src/ReaLTaiizor/Controls/Drawer/MaterialDrawer.cs:374-391 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (18–19 lines × 2) src/ReaLTaiizor/Controls/ListView/PoisonListView.cs:556— src/ReaLTaiizor/Controls/ListView/PoisonListView.cs:556-573 | src/ReaLTaiizor/Controls/ListView/PoisonListView.cs:764-782 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/ReaLTaiizor/Controls/ListView/PoisonListView.cs:556` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (16–17 lines × 2) src/ReaLTaiizor/Controls/TextBox/BigTextBox.cs:197— src/ReaLTaiizor/Controls/TextBox/BigTextBox.cs:197-213 | src/ReaLTaiizor/Controls/TextBox/SmallTextBox.cs:175-190 — before extracting anything, compare `src/ReaLTaiizor/Controls/TextBox/BigTextBox.cs` and `src/ReaLTaiizor/Controls/TextBox/SmallTextBox.cs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 64 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/ReaLTaiizor/Controls/TextBox/BigTextBox.cs:197` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (16–17 lines × 2) src/ReaLTaiizor/Controls/TextBox/MaterialMaskedTextBox.cs:1130— src/ReaLTaiizor/Controls/TextBox/MaterialMaskedTextBox.cs:1130-1145 | src/ReaLTaiizor/Controls/TextBoxEdit/MaterialTextBoxEdit.cs:1085-1101 — before extracting anything, compare `src/ReaLTaiizor/Controls/TextBox/MaterialMaskedTextBox.cs` and `src/ReaLTaiizor/Controls/TextBoxEdit/MaterialTextBoxEdit.cs` as WHOLE FILES: this scan already matched 27 separate duplicated blocks between them, totalling at least 574 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/ReaLTaiizor/Controls/TextBox/MaterialMaskedTextBox.cs:1130` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `src/ReaLTaiizor/Controls/TextBoxEdit/MaterialTextBoxEdit.cs:1104` calls `GetLogFontByType` and `src/ReaLTaiizor/Controls/TextBox/MaterialMaskedTextBox.cs:1148` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (11 lines × 4) src/ReaLTaiizor/Controls/Button/ChatButtonLeft.cs:227— src/ReaLTaiizor/Controls/Button/ChatButtonLeft.cs:227-237 | src/ReaLTaiizor/Controls/Button/ChatButtonRight.cs:215-225 | src/ReaLTaiizor/Controls/Button/DungeonButtonLeft.cs:229-239 | src/ReaLTaiizor/Controls/Button/DungeonButtonRight.cs:229-239 — before extracting anything, compare `src/ReaLTaiizor/Controls/Button/ChatButtonLeft.cs` and `src/ReaLTaiizor/Controls/Button/ChatButtonRight.cs` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 217 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `src/ReaLTaiizor/Controls/Button/ChatButtonRight.cs:214` calls `OnResize` and `src/ReaLTaiizor/Controls/Button/ChatButtonLeft.cs:226` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (11 lines × 4) src/ReaLTaiizor/Controls/Button/ChatButtonLeft.cs:197— src/ReaLTaiizor/Controls/Button/ChatButtonLeft.cs:197-207 | src/ReaLTaiizor/Controls/Button/ChatButtonRight.cs:184-194 | src/ReaLTaiizor/Controls/Button/DungeonButtonLeft.cs:165-175 | src/ReaLTaiizor/Controls/Button/DungeonButtonRight.cs:165-175 — before extracting anything, compare `src/ReaLTaiizor/Controls/Button/ChatButtonLeft.cs` and `src/ReaLTaiizor/Controls/Button/ChatButtonRight.cs` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 217 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (10 lines × 5) src/ReaLTaiizor/Controls/Button/SpaceButton.cs:19— src/ReaLTaiizor/Controls/Button/SpaceButton.cs:19-28 | src/ReaLTaiizor/Controls/Close/SpaceClose.cs:39-48 | src/ReaLTaiizor/Controls/Maximize/SpaceMaximize.cs:42-51 | src/ReaLTaiizor/Controls/Minimize/SpaceMinimize.cs:41-50 | src/ReaLTaiizor/Controls/Quest/SpaceQuest.cs:39-48 — before extracting anything, compare `src/ReaLTaiizor/Controls/Button/SpaceButton.cs` and `src/ReaLTaiizor/Controls/Quest/SpaceQuest.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 32 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/ReaLTaiizor/Controls/Button/SpaceButton.cs:19` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (10 lines × 5) src/ReaLTaiizor/Controls/Button/SpaceButton.cs:52— src/ReaLTaiizor/Controls/Button/SpaceButton.cs:52-61 | src/ReaLTaiizor/Controls/Close/SpaceClose.cs:78-87 | src/ReaLTaiizor/Controls/Maximize/SpaceMaximize.cs:89-98 | src/ReaLTaiizor/Controls/Minimize/SpaceMinimize.cs:80-89 | src/ReaLTaiizor/Controls/Quest/SpaceQuest.cs:78-87 — before extracting anything, compare `src/ReaLTaiizor/Controls/Button/SpaceButton.cs` and `src/ReaLTaiizor/Controls/Quest/SpaceQuest.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 32 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (6 lines × 3) src/ReaLTaiizor/Controls/TextBox/MaterialMaskedTextBox.cs:1223— src/ReaLTaiizor/Controls/TextBox/MaterialMaskedTextBox.cs:1223-1228 | src/ReaLTaiizor/Controls/TextBox/MaterialTextBox.cs:783-788 | src/ReaLTaiizor/Controls/TextBoxEdit/MaterialTextBoxEdit.cs:1183-1188 — before extracting anything, compare `src/ReaLTaiizor/Controls/TextBox/MaterialMaskedTextBox.cs` and `src/ReaLTaiizor/Controls/TextBox/MaterialTextBox.cs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 167 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/ReaLTaiizor/Controls/TextBox/MaterialMaskedTextBox.cs:1223` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (6 lines × 3) src/ReaLTaiizor/Controls/Button/LostAcceptButton.cs:58— src/ReaLTaiizor/Controls/Button/LostAcceptButton.cs:58-63 | src/ReaLTaiizor/Controls/Button/LostButton.cs:45-50 | src/ReaLTaiizor/Controls/Button/LostCancelButton.cs:58-63 — before extracting anything, compare `src/ReaLTaiizor/Controls/Button/LostAcceptButton.cs` and `src/ReaLTaiizor/Controls/Button/LostCancelButton.cs` as WHOLE FILES: 92% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 4 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/ReaLTaiizor/Controls/Button/LostAcceptButton.cs:58` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (8 lines × 4) src/ReaLTaiizor/Controls/TabPage/AirTabPage.cs:140— src/ReaLTaiizor/Controls/TabPage/AirTabPage.cs:140-147 | src/ReaLTaiizor/Controls/TabPage/AirTabPage.cs:183-190 | src/ReaLTaiizor/Controls/TabPage/ForeverTabPage.cs:93-102 | src/ReaLTaiizor/Controls/TabPage/ForeverTabPage.cs:127-136 — there are 4 copies across 2 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 4 sites; resolving a subset leaves the remainder to drift apart. Read the line range as the matched WINDOW rather than a finished unit: at `src/ReaLTaiizor/Controls/TabPage/AirTabPage.cs:140` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `src/ReaLTaiizor/Controls/TabPage/ForeverTabPage.cs:124` calls `FillRectangle`, `SolidBrush` and `src/ReaLTaiizor/Controls/TabPage/AirTabPage.cs:182` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (8 lines × 4) src/ReaLTaiizor/Util/Forever.cs:32— src/ReaLTaiizor/Util/Forever.cs:32-39 | src/ReaLTaiizor/Util/Ribbon.cs:26-33 | src/ReaLTaiizor/Util/Sky.cs:15-22 | src/ReaLTaiizor/Util/Thunder.cs:23-30 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 4 call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `src/ReaLTaiizor/Util/Forever.cs:32` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (7 lines × 6) src/ReaLTaiizor/Forms/Panel/ParrotForm.cs:588— src/ReaLTaiizor/Forms/Panel/ParrotForm.cs:588-594 | src/ReaLTaiizor/Forms/Panel/ParrotForm.cs:614-620 | src/ReaLTaiizor/Forms/Panel/ParrotForm.cs:638-644 | src/ReaLTaiizor/Forms/Panel/ParrotForm.cs:718-724 | src/ReaLTaiizor/Forms/Panel/ParrotForm.cs:744-750 | src/ReaLTaiizor/Forms/Panel/ParrotForm.cs:769-775 — all 6 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `src/ReaLTaiizor/Forms/Panel/ParrotForm.cs:647` calls `DrawLine`, `Pen`, `FromArgb` and `src/ReaLTaiizor/Forms/Panel/ParrotForm.cs:623` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (7 lines × 6) src/ReaLTaiizor/Util/Air.cs:1277— src/ReaLTaiizor/Util/Air.cs:1277-1283 | src/ReaLTaiizor/Util/Air.cs:2250-2256 | src/ReaLTaiizor/Util/Moon.cs:1270-1276 | src/ReaLTaiizor/Util/Moon.cs:2253-2259 | src/ReaLTaiizor/Util/Space.cs:1273-1279 | src/ReaLTaiizor/Util/Space.cs:2250-2256 — before extracting anything, compare `src/ReaLTaiizor/Util/Air.cs` and `src/ReaLTaiizor/Util/Moon.cs` as WHOLE FILES: this scan already matched 40 separate duplicated blocks between them, totalling at least 661 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (5 lines × 5) src/ReaLTaiizor/Controls/Button/LostAcceptButton.cs:95— src/ReaLTaiizor/Controls/Button/LostAcceptButton.cs:95-99 | src/ReaLTaiizor/Controls/Button/LostButton.cs:68-72 | src/ReaLTaiizor/Controls/Button/LostCancelButton.cs:95-99 | src/ReaLTaiizor/Controls/CheckBox/LostCheckBox.cs:79-83 | src/ReaLTaiizor/Controls/Progress/LostProgressBar.cs:57-61 — before extracting anything, compare `src/ReaLTaiizor/Controls/Button/LostAcceptButton.cs` and `src/ReaLTaiizor/Controls/Button/LostCancelButton.cs` as WHOLE FILES: 92% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 4 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (5 lines × 5) src/ReaLTaiizor/Controls/Button/LostAcceptButton.cs:103— src/ReaLTaiizor/Controls/Button/LostAcceptButton.cs:103-107 | src/ReaLTaiizor/Controls/Button/LostButton.cs:76-80 | src/ReaLTaiizor/Controls/Button/LostCancelButton.cs:103-107 | src/ReaLTaiizor/Controls/CheckBox/LostCheckBox.cs:87-91 | src/ReaLTaiizor/Controls/Progress/LostProgressBar.cs:65-69 — before extracting anything, compare `src/ReaLTaiizor/Controls/Button/LostAcceptButton.cs` and `src/ReaLTaiizor/Controls/Button/LostCancelButton.cs` as WHOLE FILES: 92% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 4 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (13 lines × 4) src/ReaLTaiizor/Controls/Close/ForeverClose.cs:38— src/ReaLTaiizor/Controls/Close/ForeverClose.cs:38-50 | src/ReaLTaiizor/Controls/ControlBox/ThunderControlBox.cs:69-81 | src/ReaLTaiizor/Controls/Maximize/ForeverMaximize.cs:38-50 | src/ReaLTaiizor/Controls/Minimize/ForeverMinimize.cs:38-50 — before extracting anything, compare `src/ReaLTaiizor/Controls/Close/ForeverClose.cs` and `src/ReaLTaiizor/Controls/Maximize/ForeverMaximize.cs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 61 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (13 lines × 4) src/ReaLTaiizor/Util/Air.cs:1455— src/ReaLTaiizor/Util/Air.cs:1455-1468 | src/ReaLTaiizor/Util/Moon.cs:28-40 | src/ReaLTaiizor/Util/Moon.cs:1454-1467 | src/ReaLTaiizor/Util/Space.cs:1451-1464 — before extracting anything, compare `src/ReaLTaiizor/Util/Air.cs` and `src/ReaLTaiizor/Util/Moon.cs` as WHOLE FILES: this scan already matched 40 separate duplicated blocks between them, totalling at least 661 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
X27 · Collection changed while being enumerated· Collection is structurally changed while it is being enumerated · ×2
Collection is structurally changed while it is being enumerated src/ReaLTaiizor/Animate/Poison/DelayedCall.cs:232— The loop walks `dcList`, and line 234 calls `dc.Cancel(…)`, which reaches `Unregister(this)` in `DelayedCall.Cancel` — a structural change to that same `List` while the loop's enumerator is live. The next `MoveNext` throws `InvalidOperationException: Collection was modified; enumeration operation may not execute`, so every pass that reaches this call ends the loop by exception instead of by running out of items, and the remaining items are never seen.
Collection is structurally changed while it is being enumerated src/ReaLTaiizor/Animate/Poison/DelayedCall.cs:243— The loop walks `dcList`, and line 245 calls `dc.Fire(…)`, which reaches `FireNow()` in `DelayedCall.Fire` — a structural change to that same `List` while the loop's enumerator is live. The next `MoveNext` throws `InvalidOperationException: Collection was modified; enumeration operation may not execute`, so every pass that reaches this call ends the loop by exception instead of by running out of items, and the remaining items are never seen.
C1 · Data Protection· No data-protection/encryption · ×1
No data-protection/encryption — No data-protection or encryption usage (ASP.NET Data Protection, AES, column encryption, PBKDF2) was found — sensitive data at rest may be unprotected. If TDE/KMS/vault is delegated to infrastructure, ignore.
MaterialMaskedTextBox.OnPaint (cyclomatic 77) src/ReaLTaiizor/Controls/TextBox/MaterialMaskedTextBox.cs:1032— MaterialMaskedTextBox.OnPaint has cyclomatic complexity 77 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
MaterialTextBoxEdit.OnPaint (cyclomatic 77) src/ReaLTaiizor/Controls/TextBoxEdit/MaterialTextBoxEdit.cs:983— MaterialTextBoxEdit.OnPaint has cyclomatic complexity 77 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
MaterialTextBox.OnPaint (cyclomatic 56) src/ReaLTaiizor/Controls/TextBox/MaterialTextBox.cs:576— MaterialTextBox.OnPaint has cyclomatic complexity 56 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
RoyalForm.WndProc (cyclomatic 51) src/ReaLTaiizor/Forms/Form/RoyalForm.cs:94— RoyalForm.WndProc has cyclomatic complexity 51 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
MaterialButton.OnPaint (cyclomatic 46) src/ReaLTaiizor/Controls/Button/MaterialButton.cs:495— MaterialButton.OnPaint has cyclomatic complexity 46 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
ObjectAnimator.StandardAnimate (cyclomatic 45) src/ReaLTaiizor/Animate/Parrot/ObjectAnimator.cs:62— ObjectAnimator.StandardAnimate has cyclomatic complexity 45 (threshold 15). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
AnimationManager.AnimationTimerOnTick (cyclomatic 42) src/ReaLTaiizor/Util/Material.cs:789— AnimationManager.AnimationTimerOnTick has cyclomatic complexity 42 (threshold 15). Of this number, 23 points are the body's own statements and 19 belong to one function literal inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
MaterialComboBox.OnPaint (cyclomatic 39) src/ReaLTaiizor/Controls/ComboBox/MaterialComboBox.cs:223— MaterialComboBox.OnPaint has cyclomatic complexity 39 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
MaterialListBox.OnPaint (cyclomatic 39) src/ReaLTaiizor/Controls/ListBox/MaterialListBox.cs:494— MaterialListBox.OnPaint has cyclomatic complexity 39 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
ParrotBarGraph.OnPaint (cyclomatic 38) src/ReaLTaiizor/Controls/Graph/ParrotBarGraph.cs:198— ParrotBarGraph.OnPaint has cyclomatic complexity 38 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
MaterialForm.OnPaint (cyclomatic 38) src/ReaLTaiizor/Forms/Form/MaterialForm.cs:1232— MaterialForm.OnPaint has cyclomatic complexity 38 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
MaterialForm.UpdateButtons (cyclomatic 37) src/ReaLTaiizor/Forms/Form/MaterialForm.cs:765— MaterialForm.UpdateButtons has cyclomatic complexity 37 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
MaterialForm.OnMouseMove (cyclomatic 37) src/ReaLTaiizor/Forms/Form/MaterialForm.cs:1131— MaterialForm.OnMouseMove has cyclomatic complexity 37 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
ParrotJoyStick.MoveObject (cyclomatic 31) src/ReaLTaiizor/Controls/Stick/ParrotJoyStick.cs:257— ParrotJoyStick.MoveObject has cyclomatic complexity 31 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
CrownTreeView.DrawNode (cyclomatic 31) src/ReaLTaiizor/Controls/TreeView/CrownTreeView.cs:1380— CrownTreeView.DrawNode has cyclomatic complexity 31 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
PoisonCheckBox.OnPaintForeground (cyclomatic 30) src/ReaLTaiizor/Controls/CheckBox/PoisonCheckBox.cs:255— PoisonCheckBox.OnPaintForeground has cyclomatic complexity 30 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
MaterialDrawer.Paint (cyclomatic 30) src/ReaLTaiizor/Controls/Drawer/MaterialDrawer.cs:630— MaterialDrawer.Paint has cyclomatic complexity 30 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
PoisonTile.OnPaintForeground (cyclomatic 30) src/ReaLTaiizor/Controls/Tile/PoisonTile.cs:262— PoisonTile.OnPaintForeground has cyclomatic complexity 30 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
ParrotPalette.OnMouseDown (cyclomatic 29) src/ReaLTaiizor/Controls/Palette/ParrotPalette.cs:252— ParrotPalette.OnMouseDown has cyclomatic complexity 29 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
LostForm.WndProc (cyclomatic 28) src/ReaLTaiizor/Forms/Form/LostForm.cs:109— LostForm.WndProc has cyclomatic complexity 28 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
MaterialMultiLineTextBoxEdit.OnPaint (cyclomatic 27) src/ReaLTaiizor/Controls/TextBoxEdit/MaterialMultiLineTextBoxEdit.cs:830— MaterialMultiLineTextBoxEdit.OnPaint has cyclomatic complexity 27 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
MetroBadge.ApplyTheme (cyclomatic 26) src/ReaLTaiizor/Controls/Badge/MetroBadge.cs:493— MetroBadge.ApplyTheme has cyclomatic complexity 26 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
ParrotLineGraph.OnPaint (cyclomatic 26) src/ReaLTaiizor/Controls/Graph/ParrotLineGraph.cs:283— ParrotLineGraph.OnPaint has cyclomatic complexity 26 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
MaterialCheckBox.OnPaint (cyclomatic 25) src/ReaLTaiizor/Controls/CheckBox/MaterialCheckBox.cs:213— MaterialCheckBox.OnPaint has cyclomatic complexity 25 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
MaterialTabSelector.OnPaint (cyclomatic 25) src/ReaLTaiizor/Controls/TabSelector/MaterialTabSelector.cs:262— MaterialTabSelector.OnPaint has cyclomatic complexity 25 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
CrownTreeView.OnKeyDown (cyclomatic 25) src/ReaLTaiizor/Controls/TreeView/CrownTreeView.cs:391— CrownTreeView.OnKeyDown has cyclomatic complexity 25 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
MaterialForm.WndProc (cyclomatic 25) src/ReaLTaiizor/Forms/Form/MaterialForm.cs:1002— MaterialForm.WndProc has cyclomatic complexity 25 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
ParrotButton.OnPaint (cyclomatic 24) src/ReaLTaiizor/Controls/Button/ParrotButton.cs:318— ParrotButton.OnPaint has cyclomatic complexity 24 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
ThunderControlBox.OnPaint (cyclomatic 24) src/ReaLTaiizor/Controls/ControlBox/ThunderControlBox.cs:147— ThunderControlBox.OnPaint has cyclomatic complexity 24 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
PoisonListView.PoisonListView_DrawItem (cyclomatic 24) src/ReaLTaiizor/Controls/ListView/PoisonListView.cs:633— PoisonListView.PoisonListView_DrawItem has cyclomatic complexity 24 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
PoisonLinkLabel.DrawIcon (cyclomatic 23) src/ReaLTaiizor/Controls/LinkLabel/PoisonLinkLabel.cs:359— PoisonLinkLabel.DrawIcon has cyclomatic complexity 23 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
MaterialRadioButton.OnPaint (cyclomatic 23) src/ReaLTaiizor/Controls/RadioButton/MaterialRadioButton.cs:188— MaterialRadioButton.OnPaint has cyclomatic complexity 23 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
MaterialSwitch.OnPaint (cyclomatic 22) src/ReaLTaiizor/Controls/Switch/MaterialSwitch.cs:193— MaterialSwitch.OnPaint has cyclomatic complexity 22 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
PoisonToggle.OnPaintForeground (cyclomatic 22) src/ReaLTaiizor/Controls/Toggle/PoisonToggle.cs:253— PoisonToggle.OnPaintForeground has cyclomatic complexity 22 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
Interpolation.ValueAt (cyclomatic 21) src/ReaLTaiizor/Animate/Metro/Interpolation.cs:14— Interpolation.ValueAt has cyclomatic complexity 21 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
PoisonDateTime.OnPaintForeground (cyclomatic 21) src/ReaLTaiizor/Controls/DateTime/PoisonDateTime.cs:318— PoisonDateTime.OnPaintForeground has cyclomatic complexity 21 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
MaterialDrawer.OnMouseMove (cyclomatic 21) src/ReaLTaiizor/Controls/Drawer/MaterialDrawer.cs:868— MaterialDrawer.OnMouseMove has cyclomatic complexity 21 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
HopeForm.OnPaint (cyclomatic 21) src/ReaLTaiizor/Forms/Container/HopeForm.cs:255— HopeForm.OnPaint has cyclomatic complexity 21 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
CrownButton.OnPaint (cyclomatic 20) src/ReaLTaiizor/Controls/Button/CrownButton.cs:318— CrownButton.OnPaint has cyclomatic complexity 20 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
MetroButton.ApplyTheme (cyclomatic 20) src/ReaLTaiizor/Controls/Button/MetroButton.cs:194— MetroButton.ApplyTheme has cyclomatic complexity 20 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
MetroDefaultButton.ApplyTheme (cyclomatic 20) src/ReaLTaiizor/Controls/Button/MetroDefaultButton.cs:168— MetroDefaultButton.ApplyTheme has cyclomatic complexity 20 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
MetroEllipse.ApplyTheme (cyclomatic 20) src/ReaLTaiizor/Controls/Ellipse/MetroEllipse.cs:181— MetroEllipse.ApplyTheme has cyclomatic complexity 20 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
RoyalMessageBox.OnPaint (cyclomatic 20) src/ReaLTaiizor/Controls/MessageBox/RoyalMessageBox.cs:208— RoyalMessageBox.OnPaint has cyclomatic complexity 20 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
PoisonRadioButton.OnPaintForeground (cyclomatic 20) src/ReaLTaiizor/Controls/RadioButton/PoisonRadioButton.cs:226— PoisonRadioButton.OnPaintForeground has cyclomatic complexity 20 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
MetroTile.ApplyTheme (cyclomatic 20) src/ReaLTaiizor/Controls/Tile/MetroTile.cs:200— MetroTile.ApplyTheme has cyclomatic complexity 20 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
PoisonForm.WndProc (cyclomatic 20) src/ReaLTaiizor/Forms/Form/PoisonForm.cs:490— PoisonForm.WndProc has cyclomatic complexity 20 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
DockContentDragFilter.HandleDrag (cyclomatic 20) src/ReaLTaiizor/Native/DockContentDragFilter.cs:168— DockContentDragFilter.HandleDrag has cyclomatic complexity 20 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
AnimationManager.DecrementProgress (cyclomatic 20) src/ReaLTaiizor/Util/Material.cs:1065— AnimationManager.DecrementProgress has cyclomatic complexity 20 (threshold 15). Of this number, 13 points are the body's own statements and 7 belong to one function literal inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
AnimationManager.IncrementProgress (cyclomatic 19) src/ReaLTaiizor/Util/Material.cs:985— AnimationManager.IncrementProgress has cyclomatic complexity 19 (threshold 15). Of this number, 12 points are the body's own statements and 7 belong to one function literal inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
RoundInt.IntRound (cyclomatic 19) src/ReaLTaiizor/Util/Parrot.cs:194— RoundInt.IntRound has cyclomatic complexity 19 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
ObjectAnimator.ColorAnimate (cyclomatic 18) src/ReaLTaiizor/Animate/Parrot/ObjectAnimator.cs:413— ObjectAnimator.ColorAnimate has cyclomatic complexity 18 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
MaterialFloatingActionButton.OnPaint (cyclomatic 18) src/ReaLTaiizor/Controls/Button/MaterialFloatingActionButton.cs:257— MaterialFloatingActionButton.OnPaint has cyclomatic complexity 18 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
MaterialCheckBox.OnCreateControl (cyclomatic 18) src/ReaLTaiizor/Controls/CheckBox/MaterialCheckBox.cs:317— MaterialCheckBox.OnCreateControl has cyclomatic complexity 18 (threshold 15). Most of this is not in the body itself: 2 of the 18 points are its own statements and the rest belongs to 7 function literals inside it that branch (lines 382, 410, 328, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
DungeonControlBox.OnPaint (cyclomatic 18) src/ReaLTaiizor/Controls/ControlBox/DungeonControlBox.cs:212— DungeonControlBox.OnPaint has cyclomatic complexity 18 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
PoisonListView.PoisonListView_DrawSubItem (cyclomatic 18) src/ReaLTaiizor/Controls/ListView/PoisonListView.cs:537— PoisonListView.PoisonListView_DrawSubItem has cyclomatic complexity 18 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
HopeProgressBar.OnPaint (cyclomatic 18) src/ReaLTaiizor/Controls/Progress/HopePrgoressBar.cs:91— HopeProgressBar.OnPaint has cyclomatic complexity 18 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
ParrotJoyStick.OnMouseMove (cyclomatic 18) src/ReaLTaiizor/Controls/Stick/ParrotJoyStick.cs:101— ParrotJoyStick.OnMouseMove has cyclomatic complexity 18 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
CrownTreeView.CheckNodeClick (cyclomatic 18) src/ReaLTaiizor/Controls/TreeView/CrownTreeView.cs:810— CrownTreeView.CheckNodeClick has cyclomatic complexity 18 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
MetroForm.ApplyTheme (cyclomatic 18) src/ReaLTaiizor/Forms/Form/MetroForm.cs:573— MetroForm.ApplyTheme has cyclomatic complexity 18 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
CrownScrollBase.DragTimer_Tick (cyclomatic 17) src/ReaLTaiizor/Child/Crown/CrownScrollBase.cs:393— CrownScrollBase.DragTimer_Tick has cyclomatic complexity 17 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
MetroControlBox.ApplyTheme (cyclomatic 17) src/ReaLTaiizor/Controls/ControlBox/MetroControlBox.cs:104— MetroControlBox.ApplyTheme has cyclomatic complexity 17 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
MetroLinkLabel.ApplyTheme (cyclomatic 17) src/ReaLTaiizor/Controls/LinkLabel/MetroLinkLabel.cs:106— MetroLinkLabel.ApplyTheme has cyclomatic complexity 17 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
MetroListBox.OnPaint (cyclomatic 17) src/ReaLTaiizor/Controls/ListBox/MetroListBox.cs:247— MetroListBox.OnPaint has cyclomatic complexity 17 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
MaterialExpansionPanel.OnPaint (cyclomatic 17) src/ReaLTaiizor/Controls/Panel/MaterialExpansionPanel.cs:533— MaterialExpansionPanel.OnPaint has cyclomatic complexity 17 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
CrownDockGroup.BuildTabs (cyclomatic 17) src/ReaLTaiizor/Docking/Crown/CrownDockGroup.cs:214— CrownDockGroup.BuildTabs has cyclomatic complexity 17 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
ForeverForm.GetResizeDirection (cyclomatic 17) src/ReaLTaiizor/Forms/Container/ForeverForm.cs:126— ForeverForm.GetResizeDirection has cyclomatic complexity 17 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
MaterialFlexibleForm.SetButtonsPosition (cyclomatic 17) src/ReaLTaiizor/Forms/Form/MaterialFlexibleForm.cs:798— MaterialFlexibleForm.SetButtonsPosition has cyclomatic complexity 17 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
DockResizeFilter.PreFilterMessage (cyclomatic 17) src/ReaLTaiizor/Native/DockResizeFilter.cs:45— DockResizeFilter.PreFilterMessage has cyclomatic complexity 17 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
AnimationManager.StartNewAnimation (cyclomatic 17) src/ReaLTaiizor/Util/Material.cs:908— AnimationManager.StartNewAnimation has cyclomatic complexity 17 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
Strength.CheckScore1 (cyclomatic 17) ready/ReaLTaiizor.Nerator/ReaLTaiizor.Nerator/CS/Strength.cs:24— Strength.CheckScore1 has cyclomatic complexity 17 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
ParrotNavigationBar.OnPaint (cyclomatic 16) src/ReaLTaiizor/Controls/Bar/ParrotNavigationBar.cs:240— ParrotNavigationBar.OnPaint has cyclomatic complexity 16 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
PoisonButton.OnPaintForeground (cyclomatic 16) src/ReaLTaiizor/Controls/Button/PoisonButton.cs:270— PoisonButton.OnPaintForeground has cyclomatic complexity 16 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
MetroComboBox.ApplyTheme (cyclomatic 16) src/ReaLTaiizor/Controls/ComboBox/MetroComboBox.cs:289— MetroComboBox.ApplyTheme has cyclomatic complexity 16 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
HopeDatePicker.OnMouseMove (cyclomatic 16) src/ReaLTaiizor/Controls/DatePicker/HopeDatePicker.cs:117— HopeDatePicker.OnMouseMove has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
MetroListBox.ApplyTheme (cyclomatic 16) src/ReaLTaiizor/Controls/ListBox/MetroListBox.cs:154— MetroListBox.ApplyTheme has cyclomatic complexity 16 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
CrownScrollBar.OnMouseDown (cyclomatic 16) src/ReaLTaiizor/Controls/ScrollBar/CrownScrollBar.cs:183— CrownScrollBar.OnMouseDown has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
CyberSwitch.Draw_Checked (cyclomatic 16) src/ReaLTaiizor/Controls/Switch/CyberSwitch.cs:628— CyberSwitch.Draw_Checked has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
PoisonFonts.WaterMark (cyclomatic 16) src/ReaLTaiizor/Extension/Poison/PoisonFonts.cs:730— PoisonFonts.WaterMark has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
MetroForm.ResizeForm (cyclomatic 16) src/ReaLTaiizor/Forms/Form/MetroForm.cs:432— MetroForm.ResizeForm has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
ParrotForm.RefreshUI (cyclomatic 16) src/ReaLTaiizor/Forms/Panel/ParrotForm.cs:293— ParrotForm.RefreshUI has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
ParrotBarGraph.OnPaint (cognitive 139) src/ReaLTaiizor/Controls/Graph/ParrotBarGraph.cs:198— ParrotBarGraph.OnPaint has cognitive complexity 139 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
MaterialMaskedTextBox.OnPaint (cognitive 126) src/ReaLTaiizor/Controls/TextBox/MaterialMaskedTextBox.cs:1032— MaterialMaskedTextBox.OnPaint has cognitive complexity 126 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
MaterialTextBoxEdit.OnPaint (cognitive 126) src/ReaLTaiizor/Controls/TextBoxEdit/MaterialTextBoxEdit.cs:983— MaterialTextBoxEdit.OnPaint has cognitive complexity 126 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
ParrotJoyStick.MoveObject (cognitive 112) src/ReaLTaiizor/Controls/Stick/ParrotJoyStick.cs:257— ParrotJoyStick.MoveObject has cognitive complexity 112 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
MaterialTextBox.OnPaint (cognitive 102) src/ReaLTaiizor/Controls/TextBox/MaterialTextBox.cs:576— MaterialTextBox.OnPaint has cognitive complexity 102 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
MaterialButton.OnPaint (cognitive 92) src/ReaLTaiizor/Controls/Button/MaterialButton.cs:495— MaterialButton.OnPaint has cognitive complexity 92 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
ObjectAnimator.StandardAnimate (cognitive 86) src/ReaLTaiizor/Animate/Parrot/ObjectAnimator.cs:62— ObjectAnimator.StandardAnimate has cognitive complexity 86 (threshold 15). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
MaterialListBox.OnPaint (cognitive 67) src/ReaLTaiizor/Controls/ListBox/MaterialListBox.cs:494— MaterialListBox.OnPaint has cognitive complexity 67 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
MaterialTabSelector.OnPaint (cognitive 65) src/ReaLTaiizor/Controls/TabSelector/MaterialTabSelector.cs:262— MaterialTabSelector.OnPaint has cognitive complexity 65 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
MaterialForm.OnPaint (cognitive 61) src/ReaLTaiizor/Forms/Form/MaterialForm.cs:1232— MaterialForm.OnPaint has cognitive complexity 61 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
RoyalForm.WndProc (cognitive 59) src/ReaLTaiizor/Forms/Form/RoyalForm.cs:94— RoyalForm.WndProc has cognitive complexity 59 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ThunderControlBox.OnPaint (cognitive 58) src/ReaLTaiizor/Controls/ControlBox/ThunderControlBox.cs:147— ThunderControlBox.OnPaint has cognitive complexity 58 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
MaterialDrawer.Paint (cognitive 57) src/ReaLTaiizor/Controls/Drawer/MaterialDrawer.cs:630— MaterialDrawer.Paint has cognitive complexity 57 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
PoisonListView.PoisonListView_DrawItem (cognitive 57) src/ReaLTaiizor/Controls/ListView/PoisonListView.cs:633— PoisonListView.PoisonListView_DrawItem has cognitive complexity 57 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
CrownTreeView.OnKeyDown (cognitive 56) src/ReaLTaiizor/Controls/TreeView/CrownTreeView.cs:391— CrownTreeView.OnKeyDown has cognitive complexity 56 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
AnimationManager.AnimationTimerOnTick (cognitive 56) src/ReaLTaiizor/Util/Material.cs:789— AnimationManager.AnimationTimerOnTick has cognitive complexity 56 (threshold 15). Of this number, 32 points are the body's own statements and 24 belong to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
MaterialComboBox.OnPaint (cognitive 55) src/ReaLTaiizor/Controls/ComboBox/MaterialComboBox.cs:223— MaterialComboBox.OnPaint has cognitive complexity 55 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ParrotLineGraph.OnPaint (cognitive 54) src/ReaLTaiizor/Controls/Graph/ParrotLineGraph.cs:283— ParrotLineGraph.OnPaint has cognitive complexity 54 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
MaterialMultiLineTextBoxEdit.OnPaint (cognitive 49) src/ReaLTaiizor/Controls/TextBoxEdit/MaterialMultiLineTextBoxEdit.cs:830— MaterialMultiLineTextBoxEdit.OnPaint has cognitive complexity 49 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
AnimationManager.DecrementProgress (cognitive 48) src/ReaLTaiizor/Util/Material.cs:1065— AnimationManager.DecrementProgress has cognitive complexity 48 (threshold 15). Of this number, 31 points are the body's own statements and 17 belong to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
PoisonDateTime.OnPaintForeground (cognitive 47) src/ReaLTaiizor/Controls/DateTime/PoisonDateTime.cs:318— PoisonDateTime.OnPaintForeground has cognitive complexity 47 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
AnimationManager.IncrementProgress (cognitive 47) src/ReaLTaiizor/Util/Material.cs:985— AnimationManager.IncrementProgress has cognitive complexity 47 (threshold 15). Of this number, 30 points are the body's own statements and 17 belong to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
MaterialForm.UpdateButtons (cognitive 45) src/ReaLTaiizor/Forms/Form/MaterialForm.cs:765— MaterialForm.UpdateButtons has cognitive complexity 45 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
DockContentDragFilter.HandleDrag (cognitive 45) src/ReaLTaiizor/Native/DockContentDragFilter.cs:168— DockContentDragFilter.HandleDrag has cognitive complexity 45 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
MaterialCheckBox.OnPaint (cognitive 44) src/ReaLTaiizor/Controls/CheckBox/MaterialCheckBox.cs:213— MaterialCheckBox.OnPaint has cognitive complexity 44 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
RoyalMessageBox.OnPaint (cognitive 44) src/ReaLTaiizor/Controls/MessageBox/RoyalMessageBox.cs:208— RoyalMessageBox.OnPaint has cognitive complexity 44 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
LostForm.OnMouseUp (cognitive 44) src/ReaLTaiizor/Forms/Form/LostForm.cs:211— LostForm.OnMouseUp has cognitive complexity 44 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
ParrotJoyStick.OnMouseMove (cognitive 42) src/ReaLTaiizor/Controls/Stick/ParrotJoyStick.cs:101— ParrotJoyStick.OnMouseMove has cognitive complexity 42 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
CrownTreeView.CheckNodeClick (cognitive 41) src/ReaLTaiizor/Controls/TreeView/CrownTreeView.cs:810— CrownTreeView.CheckNodeClick has cognitive complexity 41 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
PoisonLabel.OnPaintForeground (cognitive 38) src/ReaLTaiizor/Controls/Label/PoisonLabel.cs:278— PoisonLabel.OnPaintForeground has cognitive complexity 38 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
CrownDockGroup.BuildTabs (cognitive 38) src/ReaLTaiizor/Docking/Crown/CrownDockGroup.cs:214— CrownDockGroup.BuildTabs has cognitive complexity 38 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
LostForm.WndProc (cognitive 38) src/ReaLTaiizor/Forms/Form/LostForm.cs:109— LostForm.WndProc has cognitive complexity 38 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ParrotButton.OnPaint (cognitive 37) src/ReaLTaiizor/Controls/Button/ParrotButton.cs:318— ParrotButton.OnPaint has cognitive complexity 37 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
MaterialDrawer.OnMouseMove (cognitive 37) src/ReaLTaiizor/Controls/Drawer/MaterialDrawer.cs:868— MaterialDrawer.OnMouseMove has cognitive complexity 37 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
PoisonLabel.UpdateBaseTextBox (cognitive 37) src/ReaLTaiizor/Controls/Label/PoisonLabel.cs:495— PoisonLabel.UpdateBaseTextBox has cognitive complexity 37 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
PoisonLinkLabel.DrawIcon (cognitive 36) src/ReaLTaiizor/Controls/LinkLabel/PoisonLinkLabel.cs:359— PoisonLinkLabel.DrawIcon has cognitive complexity 36 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
HopeForm.OnPaint (cognitive 36) src/ReaLTaiizor/Forms/Container/HopeForm.cs:255— HopeForm.OnPaint has cognitive complexity 36 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
RoundInt.IntRound (cognitive 36) src/ReaLTaiizor/Util/Parrot.cs:194— RoundInt.IntRound has cognitive complexity 36 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
MaterialRadioButton.OnPaint (cognitive 35) src/ReaLTaiizor/Controls/RadioButton/MaterialRadioButton.cs:188— MaterialRadioButton.OnPaint has cognitive complexity 35 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
PoisonListView.PoisonListView_DrawSubItem (cognitive 34) src/ReaLTaiizor/Controls/ListView/PoisonListView.cs:537— PoisonListView.PoisonListView_DrawSubItem has cognitive complexity 34 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
ParrotSegment.OnPaint (cognitive 34) src/ReaLTaiizor/Controls/Segment/ParrotSegment.cs:237— ParrotSegment.OnPaint has cognitive complexity 34 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
CrownDockGroup.OnMouseMove (cognitive 34) src/ReaLTaiizor/Docking/Crown/CrownDockGroup.cs:446— CrownDockGroup.OnMouseMove has cognitive complexity 34 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
ForeverProgressBar.OnPaint (cognitive 33) src/ReaLTaiizor/Controls/Progress/ForeverProgressBar.cs:114— ForeverProgressBar.OnPaint has cognitive complexity 33 (threshold 15). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
CrownTreeView.DrawNode (cognitive 32) src/ReaLTaiizor/Controls/TreeView/CrownTreeView.cs:1380— CrownTreeView.DrawNode has cognitive complexity 32 (threshold 15). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
MaterialScrollBar.OnMouseMove (cognitive 31) src/ReaLTaiizor/Controls/ScrollBar/MaterialScrollBar.cs:603— MaterialScrollBar.OnMouseMove has cognitive complexity 31 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
PoisonScrollBar.OnMouseMove (cognitive 31) src/ReaLTaiizor/Controls/ScrollBar/PoisonScrollBar.cs:803— PoisonScrollBar.OnMouseMove has cognitive complexity 31 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
AirTabPage.OnPaint (cognitive 31) src/ReaLTaiizor/Controls/TabPage/AirTabPage.cs:113— AirTabPage.OnPaint has cognitive complexity 31 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ForeverTabPage.OnPaint (cognitive 31) src/ReaLTaiizor/Controls/TabPage/ForeverTabPage.cs:55— ForeverTabPage.OnPaint has cognitive complexity 31 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
LostForm.OnMouseDown (cognitive 31) src/ReaLTaiizor/Forms/Form/LostForm.cs:173— LostForm.OnMouseDown has cognitive complexity 31 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
HopeProgressBar.OnPaint (cognitive 30) src/ReaLTaiizor/Controls/Progress/HopePrgoressBar.cs:91— HopeProgressBar.OnPaint has cognitive complexity 30 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Adapter.SetRegistryMAC (cognitive 30) REDACTED:84— Adapter.SetRegistryMAC has cognitive complexity 30 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
ControlBox.OnPaint (cognitive 29) src/ReaLTaiizor/Controls/ControlBox/ControlBox.cs:212— ControlBox.OnPaint has cognitive complexity 29 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
MaterialSwitch.OnPaint (cognitive 29) src/ReaLTaiizor/Controls/Switch/MaterialSwitch.cs:193— MaterialSwitch.OnPaint has cognitive complexity 29 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
MetroTabControl.OnPaint (cognitive 29) src/ReaLTaiizor/Controls/TabControl/MetroTabControl.cs:385— MetroTabControl.OnPaint has cognitive complexity 29 (threshold 15). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
CrownScrollBase.DragTimer_Tick (cognitive 28) src/ReaLTaiizor/Child/Crown/CrownScrollBase.cs:393— CrownScrollBase.DragTimer_Tick has cognitive complexity 28 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
CrownButton.OnPaint (cognitive 28) src/ReaLTaiizor/Controls/Button/CrownButton.cs:318— CrownButton.OnPaint has cognitive complexity 28 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ParrotPalette.OnMouseDown (cognitive 28) src/ReaLTaiizor/Controls/Palette/ParrotPalette.cs:252— ParrotPalette.OnMouseDown has cognitive complexity 28 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
MetroForm.ApplyTheme (cognitive 28) src/ReaLTaiizor/Forms/Form/MetroForm.cs:573— MetroForm.ApplyTheme has cognitive complexity 28 (threshold 15). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
PoisonFonts.WaterMark (cognitive 27) src/ReaLTaiizor/Extension/Poison/PoisonFonts.cs:730— PoisonFonts.WaterMark has cognitive complexity 27 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
MetroForm.ResizeForm (cognitive 27) src/ReaLTaiizor/Forms/Form/MetroForm.cs:432— MetroForm.ResizeForm has cognitive complexity 27 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
PoisonForm.WndProc (cognitive 27) src/ReaLTaiizor/Forms/Form/PoisonForm.cs:490— PoisonForm.WndProc has cognitive complexity 27 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
MetroEllipse.ApplyTheme (cognitive 26) src/ReaLTaiizor/Controls/Ellipse/MetroEllipse.cs:181— MetroEllipse.ApplyTheme has cognitive complexity 26 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
MaterialListBox.OnMouseDown (cognitive 26) src/ReaLTaiizor/Controls/ListBox/MaterialListBox.cs:837— MaterialListBox.OnMouseDown has cognitive complexity 26 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
CrownScrollBar.OnMouseDown (cognitive 26) src/ReaLTaiizor/Controls/ScrollBar/CrownScrollBar.cs:183— CrownScrollBar.OnMouseDown has cognitive complexity 26 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ParrotSwitch.OnPaint (cognitive 26) src/ReaLTaiizor/Controls/Switch/ParrotSwitch.cs:135— ParrotSwitch.OnPaint has cognitive complexity 26 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
MetroTile.ApplyTheme (cognitive 26) src/ReaLTaiizor/Controls/Tile/MetroTile.cs:200— MetroTile.ApplyTheme has cognitive complexity 26 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
PoisonCheckBox.OnPaintForeground (cognitive 25) src/ReaLTaiizor/Controls/CheckBox/PoisonCheckBox.cs:255— PoisonCheckBox.OnPaintForeground has cognitive complexity 25 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ParrotSlidingPanel.CollapseChanged (cognitive 25) src/ReaLTaiizor/Controls/Panel/ParrotSlidingPanel.cs:105— ParrotSlidingPanel.CollapseChanged has cognitive complexity 25 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
LostForm.OnPaint (cognitive 25) src/ReaLTaiizor/Forms/Form/LostForm.cs:352— LostForm.OnPaint has cognitive complexity 25 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
MaterialForm.OnMouseMove (cognitive 25) src/ReaLTaiizor/Forms/Form/MaterialForm.cs:1131— MaterialForm.OnMouseMove has cognitive complexity 25 (threshold 15). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
ObjectAnimator.ColorAnimate (cognitive 24) src/ReaLTaiizor/Animate/Parrot/ObjectAnimator.cs:413— ObjectAnimator.ColorAnimate has cognitive complexity 24 (threshold 15). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
HopeSimpleButton.OnPaint (cognitive 24) src/ReaLTaiizor/Controls/Button/HopeSimpleButton.cs:96— HopeSimpleButton.OnPaint has cognitive complexity 24 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
DungeonControlBox.OnPaint (cognitive 24) src/ReaLTaiizor/Controls/ControlBox/DungeonControlBox.cs:212— DungeonControlBox.OnPaint has cognitive complexity 24 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
PoisonDateTime.OnMouseDown (cognitive 24) src/ReaLTaiizor/Controls/DateTime/PoisonDateTime.cs:597— PoisonDateTime.OnMouseDown has cognitive complexity 24 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
CrownTreeView.DragTimer_Tick (cognitive 24) src/ReaLTaiizor/Controls/TreeView/CrownTreeView.cs:497— CrownTreeView.DragTimer_Tick has cognitive complexity 24 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
CrownDockPanel.RestoreDockPanelState (cognitive 24) src/ReaLTaiizor/Docking/Crown/CrownDockPanel.cs:286— CrownDockPanel.RestoreDockPanelState has cognitive complexity 24 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
LostForm.OnMouseMove (cognitive 24) src/ReaLTaiizor/Forms/Form/LostForm.cs:279— LostForm.OnMouseMove has cognitive complexity 24 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
CyberComboBox.WndProc (cognitive 23) src/ReaLTaiizor/Controls/ComboBox/CyberComboBox.cs:342— CyberComboBox.WndProc has cognitive complexity 23 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
CrownListView.OnKeyDown (cognitive 23) src/ReaLTaiizor/Controls/ListView/CrownListView.cs:206— CrownListView.OnKeyDown has cognitive complexity 23 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
CrownListView.ToggleItem (cognitive 23) src/ReaLTaiizor/Controls/ListView/CrownListView.cs:310— CrownListView.ToggleItem has cognitive complexity 23 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
PoisonMessageBox.Show (cognitive 23) src/ReaLTaiizor/Controls/MessageBox/PoisonMessageBox.cs:62— PoisonMessageBox.Show has cognitive complexity 23 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
MaterialExpansionPanel.OnPaint (cognitive 23) src/ReaLTaiizor/Controls/Panel/MaterialExpansionPanel.cs:533— MaterialExpansionPanel.OnPaint has cognitive complexity 23 (threshold 15). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
MaterialSlider.OnPaint (cognitive 23) src/ReaLTaiizor/Controls/Slider/MaterialSlider.cs:459— MaterialSlider.OnPaint has cognitive complexity 23 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
MaterialTabSelector.UpdateTabRects (cognitive 23) src/ReaLTaiizor/Controls/TabSelector/MaterialTabSelector.cs:499— MaterialTabSelector.UpdateTabRects has cognitive complexity 23 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
CrownTreeView.ToggleNode (cognitive 23) src/ReaLTaiizor/Controls/TreeView/CrownTreeView.cs:969— CrownTreeView.ToggleNode has cognitive complexity 23 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ParrotForm.RefreshUI (cognitive 23) src/ReaLTaiizor/Forms/Panel/ParrotForm.cs:293— ParrotForm.RefreshUI has cognitive complexity 23 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
HopeDatePicker.OnMouseMove (cognitive 22) src/ReaLTaiizor/Controls/DatePicker/HopeDatePicker.cs:117— HopeDatePicker.OnMouseMove has cognitive complexity 22 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
PoisonRadioButton.OnPaintForeground (cognitive 22) src/ReaLTaiizor/Controls/RadioButton/PoisonRadioButton.cs:226— PoisonRadioButton.OnPaintForeground has cognitive complexity 22 (threshold 15). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
CrownTreeView.CanMoveNodes (cognitive 22) src/ReaLTaiizor/Controls/TreeView/CrownTreeView.cs:1301— CrownTreeView.CanMoveNodes has cognitive complexity 22 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
MaterialDrawer.DrawerHideTabName.set (cognitive 21) src/ReaLTaiizor/Controls/Drawer/MaterialDrawer.cs:230— MaterialDrawer.DrawerHideTabName.set has cognitive complexity 21 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
PoisonToggle.OnPaintForeground (cognitive 21) src/ReaLTaiizor/Controls/Toggle/PoisonToggle.cs:253— PoisonToggle.OnPaintForeground has cognitive complexity 21 (threshold 15). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
PoisonFonts.Tile (cognitive 21) src/ReaLTaiizor/Extension/Poison/PoisonFonts.cs:215— PoisonFonts.Tile has cognitive complexity 21 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This shape REPEATS in the file: 9 other methods here (PoisonFonts.LinkLabel, PoisonFonts.ComboBox, PoisonFonts.DateTime, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 10 times rather than 10 independent problems. Splitting this body alone leaves the other 9 exactly as they are. Where these are variations on one operation, the change that clears all 10 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
PoisonFonts.LinkLabel (cognitive 21) src/ReaLTaiizor/Extension/Poison/PoisonFonts.cs:274— PoisonFonts.LinkLabel has cognitive complexity 21 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This shape REPEATS in the file: 9 other methods here (PoisonFonts.Tile, PoisonFonts.ComboBox, PoisonFonts.DateTime, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 10 times rather than 10 independent problems. Splitting this body alone leaves the other 9 exactly as they are. Where these are variations on one operation, the change that clears all 10 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
PoisonFonts.ComboBox (cognitive 21) src/ReaLTaiizor/Extension/Poison/PoisonFonts.cs:331— PoisonFonts.ComboBox has cognitive complexity 21 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This shape REPEATS in the file: 9 other methods here (PoisonFonts.Tile, PoisonFonts.LinkLabel, PoisonFonts.DateTime, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 10 times rather than 10 independent problems. Splitting this body alone leaves the other 9 exactly as they are. Where these are variations on one operation, the change that clears all 10 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
PoisonFonts.DateTime (cognitive 21) src/ReaLTaiizor/Extension/Poison/PoisonFonts.cs:388— PoisonFonts.DateTime has cognitive complexity 21 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This shape REPEATS in the file: 9 other methods here (PoisonFonts.Tile, PoisonFonts.LinkLabel, PoisonFonts.ComboBox, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 10 times rather than 10 independent problems. Splitting this body alone leaves the other 9 exactly as they are. Where these are variations on one operation, the change that clears all 10 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
PoisonFonts.Label (cognitive 21) src/ReaLTaiizor/Extension/Poison/PoisonFonts.cs:445— PoisonFonts.Label has cognitive complexity 21 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This shape REPEATS in the file: 9 other methods here (PoisonFonts.Tile, PoisonFonts.LinkLabel, PoisonFonts.ComboBox, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 10 times rather than 10 independent problems. Splitting this body alone leaves the other 9 exactly as they are. Where these are variations on one operation, the change that clears all 10 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
PoisonFonts.TextBox (cognitive 21) src/ReaLTaiizor/Extension/Poison/PoisonFonts.cs:502— PoisonFonts.TextBox has cognitive complexity 21 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This shape REPEATS in the file: 9 other methods here (PoisonFonts.Tile, PoisonFonts.LinkLabel, PoisonFonts.ComboBox, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 10 times rather than 10 independent problems. Splitting this body alone leaves the other 9 exactly as they are. Where these are variations on one operation, the change that clears all 10 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
PoisonFonts.ProgressBar (cognitive 21) src/ReaLTaiizor/Extension/Poison/PoisonFonts.cs:559— PoisonFonts.ProgressBar has cognitive complexity 21 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This shape REPEATS in the file: 9 other methods here (PoisonFonts.Tile, PoisonFonts.LinkLabel, PoisonFonts.ComboBox, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 10 times rather than 10 independent problems. Splitting this body alone leaves the other 9 exactly as they are. Where these are variations on one operation, the change that clears all 10 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
PoisonFonts.TabControl (cognitive 21) src/ReaLTaiizor/Extension/Poison/PoisonFonts.cs:616— PoisonFonts.TabControl has cognitive complexity 21 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This shape REPEATS in the file: 9 other methods here (PoisonFonts.Tile, PoisonFonts.LinkLabel, PoisonFonts.ComboBox, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 10 times rather than 10 independent problems. Splitting this body alone leaves the other 9 exactly as they are. Where these are variations on one operation, the change that clears all 10 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
PoisonFonts.CheckBox (cognitive 21) src/ReaLTaiizor/Extension/Poison/PoisonFonts.cs:673— PoisonFonts.CheckBox has cognitive complexity 21 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This shape REPEATS in the file: 9 other methods here (PoisonFonts.Tile, PoisonFonts.LinkLabel, PoisonFonts.ComboBox, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 10 times rather than 10 independent problems. Splitting this body alone leaves the other 9 exactly as they are. Where these are variations on one operation, the change that clears all 10 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
PoisonFonts.Button (cognitive 21) src/ReaLTaiizor/Extension/Poison/PoisonFonts.cs:802— PoisonFonts.Button has cognitive complexity 21 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This shape REPEATS in the file: 9 other methods here (PoisonFonts.Tile, PoisonFonts.LinkLabel, PoisonFonts.ComboBox, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 10 times rather than 10 independent problems. Splitting this body alone leaves the other 9 exactly as they are. Where these are variations on one operation, the change that clears all 10 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
MaterialForm.WndProc (cognitive 21) src/ReaLTaiizor/Forms/Form/MaterialForm.cs:1002— MaterialForm.WndProc has cognitive complexity 21 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
MetroListBox.OnPaint (cognitive 20) src/ReaLTaiizor/Controls/ListBox/MetroListBox.cs:247— MetroListBox.OnPaint has cognitive complexity 20 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
PoisonProgressSpinner.OnPaintForeground (cognitive 20) src/ReaLTaiizor/Controls/Progress/PoisonProgressSpinner.cs:366— PoisonProgressSpinner.OnPaintForeground has cognitive complexity 20 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
RoyalScrollBar.OnMouseDown (cognitive 20) src/ReaLTaiizor/Controls/ScrollBar/RoyalScrollBar.cs:207— RoyalScrollBar.OnMouseDown has cognitive complexity 20 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
TabPage.OnPaint (cognitive 20) src/ReaLTaiizor/Controls/TabPage/TabPage.cs:231— TabPage.OnPaint has cognitive complexity 20 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
PoisonTile.OnPaintForeground (cognitive 20) src/ReaLTaiizor/Controls/Tile/PoisonTile.cs:262— PoisonTile.OnPaintForeground has cognitive complexity 20 (threshold 15). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
CrownDockGroup.PaintDocumentTab (cognitive 20) src/ReaLTaiizor/Docking/Crown/CrownDockGroup.cs:755— CrownDockGroup.PaintDocumentTab has cognitive complexity 20 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ForeverForm.GetResizeDirection (cognitive 20) src/ReaLTaiizor/Forms/Container/ForeverForm.cs:126— ForeverForm.GetResizeDirection has cognitive complexity 20 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
PoisonDataGridHelper._scrollbar_Scroll (cognitive 20) src/ReaLTaiizor/Helper/Poison.cs:74— PoisonDataGridHelper._scrollbar_Scroll has cognitive complexity 20 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
MetroStyleManager.UpdateControls (cognitive 20) src/ReaLTaiizor/Manager/MetroStyleManager.cs:98— MetroStyleManager.UpdateControls has cognitive complexity 20 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
AnimationManager.StartNewAnimation (cognitive 20) src/ReaLTaiizor/Util/Material.cs:908— AnimationManager.StartNewAnimation has cognitive complexity 20 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
HopeButton.OnPaint (cognitive 19) src/ReaLTaiizor/Controls/Button/HopeButton.cs:89— HopeButton.OnPaint has cognitive complexity 19 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
CrownListView.Items_CollectionChanged (cognitive 19) src/ReaLTaiizor/Controls/ListView/CrownListView.cs:99— CrownListView.Items_CollectionChanged has cognitive complexity 19 (threshold 15). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
ParrotPictureBox.OnPaint (cognitive 19) src/ReaLTaiizor/Controls/PictureBox/ParrotPictureBox.cs:177— ParrotPictureBox.OnPaint has cognitive complexity 19 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
CyberButton.Draw_Background (cognitive 18) src/ReaLTaiizor/Controls/Button/CyberButton.cs:576— CyberButton.Draw_Background has cognitive complexity 18 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
AloneComboBox.OnPaint (cognitive 18) src/ReaLTaiizor/Controls/ComboBox/AloneComboBox.cs:67— AloneComboBox.OnPaint has cognitive complexity 18 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
MaterialScrollBar.OnMouseDown (cognitive 18) src/ReaLTaiizor/Controls/ScrollBar/MaterialScrollBar.cs:511— MaterialScrollBar.OnMouseDown has cognitive complexity 18 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
PoisonScrollBar.OnMouseDown (cognitive 18) src/ReaLTaiizor/Controls/ScrollBar/PoisonScrollBar.cs:712— PoisonScrollBar.OnMouseDown has cognitive complexity 18 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
MaterialForm.AddDrawerOverlayForm (cognitive 18) src/ReaLTaiizor/Forms/Form/MaterialForm.cs:550— MaterialForm.AddDrawerOverlayForm has cognitive complexity 18 (threshold 15). Of this number, 10 points are the body's own statements and 8 belong to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
MaterialNativeTextRenderer.DrawTransparentText (cognitive 18) src/ReaLTaiizor/Util/Material.cs:268— MaterialNativeTextRenderer.DrawTransparentText has cognitive complexity 18 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Strength.CheckScore1 (cognitive 18) ready/ReaLTaiizor.Nerator/ReaLTaiizor.Nerator/CS/Strength.cs:24— Strength.CheckScore1 has cognitive complexity 18 (threshold 15). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
HopeRoundButton.OnPaint (cognitive 17) src/ReaLTaiizor/Controls/Button/HopeRoundButton.cs:93— HopeRoundButton.OnPaint has cognitive complexity 17 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
MaterialFloatingActionButton.OnPaint (cognitive 17) src/ReaLTaiizor/Controls/Button/MaterialFloatingActionButton.cs:257— MaterialFloatingActionButton.OnPaint has cognitive complexity 17 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
CyberCheckBox.Draw_Background (cognitive 17) src/ReaLTaiizor/Controls/CheckBox/CyberCheckBox.cs:572— CyberCheckBox.Draw_Background has cognitive complexity 17 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
MetroCheckBox.ApplyTheme (cognitive 17) src/ReaLTaiizor/Controls/CheckBox/MetroCheckBox.cs:111— MetroCheckBox.ApplyTheme has cognitive complexity 17 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ControlBox.OnMouseMove (cognitive 17) src/ReaLTaiizor/Controls/ControlBox/ControlBox.cs:89— ControlBox.OnMouseMove has cognitive complexity 17 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
MetroDivider.ApplyTheme (cognitive 17) src/ReaLTaiizor/Controls/Divider/MetroDivider.cs:101— MetroDivider.ApplyTheme has cognitive complexity 17 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
CrownDropDownList.Items_CollectionChanged (cognitive 17) src/ReaLTaiizor/Controls/List/CrownDropDownList.cs:225— CrownDropDownList.Items_CollectionChanged has cognitive complexity 17 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
RoyalListBox.OnPaint (cognitive 17) src/ReaLTaiizor/Controls/ListBox/RoyalListBox.cs:200— RoyalListBox.OnPaint has cognitive complexity 17 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
CyberProgressBar.Draw_Background (cognitive 17) src/ReaLTaiizor/Controls/Progress/CyberProgressBar.cs:625— CyberProgressBar.Draw_Background has cognitive complexity 17 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
CyberRadioButton.Draw_Background (cognitive 17) src/ReaLTaiizor/Controls/RadioButton/CyberRadioButton.cs:626— CyberRadioButton.Draw_Background has cognitive complexity 17 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
CyberSwitch.Draw_Checked (cognitive 17) src/ReaLTaiizor/Controls/Switch/CyberSwitch.cs:628— CyberSwitch.Draw_Checked has cognitive complexity 17 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
MetroTabControl.ApplyTheme (cognitive 17) src/ReaLTaiizor/Controls/TabControl/MetroTabControl.cs:121— MetroTabControl.ApplyTheme has cognitive complexity 17 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
DockResizeFilter.PreFilterMessage (cognitive 17) src/ReaLTaiizor/Native/DockResizeFilter.cs:45— DockResizeFilter.PreFilterMessage has cognitive complexity 17 (threshold 15). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
Interpolation.ValueAt (cognitive 16) src/ReaLTaiizor/Animate/Metro/Interpolation.cs:14— Interpolation.ValueAt has cognitive complexity 16 (threshold 15). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
PoisonMessageBoxControl.SetDefaultButton (cognitive 16) src/ReaLTaiizor/Child/Poison/PoisonMessageBoxControl.cs:191— PoisonMessageBoxControl.SetDefaultButton has cognitive complexity 16 (threshold 15). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
NightButton.RoundedRect (cognitive 16) src/ReaLTaiizor/Controls/Button/NightButton.cs:173— NightButton.RoundedRect has cognitive complexity 16 (threshold 15). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
MaterialCheckBox.OnCreateControl (cognitive 16) src/ReaLTaiizor/Controls/CheckBox/MaterialCheckBox.cs:317— MaterialCheckBox.OnCreateControl has cognitive complexity 16 (threshold 15). Most of this is not in the body itself: 1 of the 16 points is its own statement and the rest belongs to 7 function literals inside it that branch (lines 382, 410, 328, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
MaterialCheckListBox.OnCreateControl (cognitive 16) src/ReaLTaiizor/Controls/CheckListBox/MaterialCheckListBox.cs:71— MaterialCheckListBox.OnCreateControl has cognitive complexity 16 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
DungeonControlBox.OnMouseUp (cognitive 16) src/ReaLTaiizor/Controls/ControlBox/DungeonControlBox.cs:41— DungeonControlBox.OnMouseUp has cognitive complexity 16 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
MetroControlBox.OnPaint (cognitive 16) src/ReaLTaiizor/Controls/ControlBox/MetroControlBox.cs:364— MetroControlBox.OnPaint has cognitive complexity 16 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
MetroLinkLabel.ApplyTheme (cognitive 16) src/ReaLTaiizor/Controls/LinkLabel/MetroLinkLabel.cs:106— MetroLinkLabel.ApplyTheme has cognitive complexity 16 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
ForeverNotification.OnPaint (cognitive 16) src/ReaLTaiizor/Controls/Notify/ForeverNotification.cs:184— ForeverNotification.OnPaint has cognitive complexity 16 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
MaterialSingleTextBox.OnPaint (cognitive 16) src/ReaLTaiizor/Controls/TextBox/MaterialSingleTextBox.cs:551— MaterialSingleTextBox.OnPaint has cognitive complexity 16 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D4 · Code Duplication· Near-duplicate member family (4 members, 30 shared lines) · ×1
Near-duplicate member family (4 members, 30 shared lines) src/ReaLTaiizor/Controls/Badge/MetroBadge.cs:494— src/ReaLTaiizor/Controls/Badge/MetroBadge.cs:494-621 | src/ReaLTaiizor/Controls/Button/MetroDefaultButton.cs:169-266 | src/ReaLTaiizor/Controls/Ellipse/MetroEllipse.cs:182-288 | src/ReaLTaiizor/Controls/Tile/MetroTile.cs:201-307 — These 4 members are variants of one another: a block of 30 lines reported below appears in every one of them, and the pairwise near-duplicate rows they would otherwise produce are collapsed into this row. Read them as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
D4 · Code Duplication· Near-duplicate member family (4 members, 8 shared lines) · ×1
Near-duplicate member family (4 members, 8 shared lines) src/ReaLTaiizor/Util/Forever.cs:32— src/ReaLTaiizor/Util/Forever.cs:32-41 | src/ReaLTaiizor/Util/Ribbon.cs:26-35 | src/ReaLTaiizor/Util/Sky.cs:15-24 | src/ReaLTaiizor/Util/Thunder.cs:23-32 — These 4 members are variants of one another: a block of 8 lines reported below appears in every one of them, and the pairwise near-duplicate rows they would otherwise produce are collapsed into this row. Read them as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
Near-duplicate member pair (50 shared lines) src/ReaLTaiizor/Forms/Container/DungeonForm.cs:439— src/ReaLTaiizor/Forms/Container/DungeonForm.cs:439-522 | src/ReaLTaiizor/Forms/Container/ThemeForm.cs:454-532 — These two members are variants of one another: 50 of their lines are already reported as duplicated blocks below, spread through both bodies rather than gathered into one. Read them as a single construct written twice. The repair is at the members' grain — factor the shared pipeline into one implementation the two call with their differences as parameters or as an injected step, or, where the difference is systematic (sync against async, one transport against another), generate one from the other. Extracting the individual blocks below is not the same fix: it leaves the two bodies in place and the next edit still has to be made twice.
Near-duplicate member pair (29 shared lines) src/ReaLTaiizor/Controls/CheckBox/MaterialCheckBox.cs:214— src/ReaLTaiizor/Controls/CheckBox/MaterialCheckBox.cs:214-302 | src/ReaLTaiizor/Controls/RadioButton/MaterialRadioButton.cs:189-260 — These two members are variants of one another: 29 of their lines are already reported as duplicated blocks below, spread through both bodies rather than gathered into one. Read them as a single construct written twice. The repair is at the members' grain — factor the shared pipeline into one implementation the two call with their differences as parameters or as an injected step, or, where the difference is systematic (sync against async, one transport against another), generate one from the other. Extracting the individual blocks below is not the same fix: it leaves the two bodies in place and the next edit still has to be made twice.
Near-duplicate member pair (16 shared lines) src/ReaLTaiizor/Controls/Button/MetroDefaultButton.cs:113— src/ReaLTaiizor/Controls/Button/MetroDefaultButton.cs:113-162 | src/ReaLTaiizor/Controls/Ellipse/MetroEllipse.cs:115-175 — These two members are variants of one another: 16 of their lines are already reported as duplicated blocks below, spread through both bodies rather than gathered into one. Read them as a single construct written twice. The repair is at the members' grain — factor the shared pipeline into one implementation the two call with their differences as parameters or as an injected step, or, where the difference is systematic (sync against async, one transport against another), generate one from the other. Extracting the individual blocks below is not the same fix: it leaves the two bodies in place and the next edit still has to be made twice.
D4 · Code Duplication· Edited copy of a member (11 corresponding lines) · ×1
Edited copy of a member (11 corresponding lines) src/ReaLTaiizor/Util/Ribbon.cs:37— src/ReaLTaiizor/Util/Ribbon.cs:37-47 | src/ReaLTaiizor/Util/Sky.cs:27-37 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Members sharing a duplicated core (22 members, 50+ identical tokens) · ×1
Members sharing a duplicated core (22 members, 50+ identical tokens) src/ReaLTaiizor/Child/Metro/MetroTabPage.cs:29— src/ReaLTaiizor/Child/Metro/MetroTabPage.cs:29-47 | src/ReaLTaiizor/Controls/Badge/MetroBadge.cs:38-56 | src/ReaLTaiizor/Controls/Button/MetroButton.cs:53-72 | src/ReaLTaiizor/Controls/Button/MetroDefaultButton.cs:36-54 | src/ReaLTaiizor/Controls/CheckBox/MetroCheckBox.cs:37-55 | src/ReaLTaiizor/Controls/ControlBox/MetroControlBox.cs:35-53 | src/ReaLTaiizor/Controls/Divider/MetroDivider.cs:34-52 | src/ReaLTaiizor/Controls/Ellipse/MetroEllipse.cs:37-55 | src/ReaLTaiizor/Controls/Label/MetroLabel.cs:34-52 | src/ReaLTaiizor/Controls/LinkLabel/MetroLinkLabel.cs:34-52 | src/ReaLTaiizor/Controls/Numeric/MetroNumeric.cs:37-55 | src/ReaLTaiizor/Controls/Panel/MetroPanel.cs:31-49 | src/ReaLTaiizor/Controls/Progress/MetroProgressBar.cs:35-53 | src/ReaLTaiizor/Controls/RadioButton/MetroRadioButton.cs:39-57 | src/ReaLTaiizor/Controls/RichTextBox/MetroRichTextBox.cs:36-54 | src/ReaLTaiizor/Controls/ScrollBar/MetroScrollBar.cs:33-51 | src/ReaLTaiizor/Controls/Strip/MetroContextMenuStrip.cs:33-51 | src/ReaLTaiizor/Controls/Switch/MetroSwitch.cs:37-55 | src/ReaLTaiizor/Controls/TabControl/MetroTabControl.cs:38-56 | src/ReaLTaiizor/Controls/TextBox/MetroTextBox.cs:37-55 | src/ReaLTaiizor/Controls/Tile/MetroTile.cs:36-54 | src/ReaLTaiizor/Controls/TrackBar/MetroTrackBar.cs:35-53 — These 22 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 22 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 22 times.
D4 · Code Duplication· Members sharing a duplicated core (11 members, 50+ identical tokens) · ×1
Members sharing a duplicated core (11 members, 50+ identical tokens) src/ReaLTaiizor/Controls/Bubble/ChatBubbleLeft.cs:98— src/ReaLTaiizor/Controls/Bubble/ChatBubbleLeft.cs:98-112 | src/ReaLTaiizor/Controls/Bubble/ChatBubbleRight.cs:108-122 | src/ReaLTaiizor/Controls/Button/ChatButtonLeft.cs:226-248 | src/ReaLTaiizor/Controls/Button/ChatButtonRight.cs:213-235 | src/ReaLTaiizor/Controls/Button/DungeonButtonLeft.cs:227-249 | src/ReaLTaiizor/Controls/Button/DungeonButtonRight.cs:227-249 | src/ReaLTaiizor/Controls/RichTextBox/DungeonRichTextBox.cs:118-128 | src/ReaLTaiizor/Controls/RichTextBoxEdit/RichTextBoxEdit.cs:173-183 | src/ReaLTaiizor/Controls/TextBox/BigTextBox.cs:197-216 | src/ReaLTaiizor/Controls/TextBox/DungeonTextBox.cs:160-178 | src/ReaLTaiizor/Controls/TextBox/SmallTextBox.cs:175-193 — These 11 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 11 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 11 times.
D4 · Code Duplication· Members sharing a duplicated core (8 members, 50+ identical tokens) · ×1
Members sharing a duplicated core (8 members, 50+ identical tokens) src/ReaLTaiizor/Controls/CheckBox/MetroCheckBox.cs:112— src/ReaLTaiizor/Controls/CheckBox/MetroCheckBox.cs:112-184 | src/ReaLTaiizor/Controls/ComboBox/MetroComboBox.cs:290-371 | src/ReaLTaiizor/Controls/Numeric/MetroNumeric.cs:146-217 | src/ReaLTaiizor/Controls/RadioButton/MetroRadioButton.cs:112-173 | src/ReaLTaiizor/Controls/RichTextBox/MetroRichTextBox.cs:201-272 | src/ReaLTaiizor/Controls/ScrollBar/MetroScrollBar.cs:122-178 | src/ReaLTaiizor/Controls/Switch/MetroSwitch.cs:120-198 | src/ReaLTaiizor/Controls/TextBox/MetroTextBox.cs:225-297 — These 8 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 8 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 8 times.
Duplicated block (67–331 lines × 2) src/ReaLTaiizor/Native/User32.cs:259— src/ReaLTaiizor/Native/User32.cs:259-589 | src/ReaLTaiizor/Native/WinApi.cs:215-281 — before extracting anything, compare `src/ReaLTaiizor/Native/User32.cs` and `src/ReaLTaiizor/Native/WinApi.cs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 739 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (28–132 lines × 2) src/ReaLTaiizor/Native/User32.cs:874— src/ReaLTaiizor/Native/User32.cs:874-1005 | src/ReaLTaiizor/Native/WinApi.cs:349-376 — before extracting anything, compare `src/ReaLTaiizor/Native/User32.cs` and `src/ReaLTaiizor/Native/WinApi.cs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 739 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (22–106 lines × 2) src/ReaLTaiizor/Native/User32.cs:629— src/ReaLTaiizor/Native/User32.cs:629-734 | src/ReaLTaiizor/Native/WinApi.cs:293-314 — before extracting anything, compare `src/ReaLTaiizor/Native/User32.cs` and `src/ReaLTaiizor/Native/WinApi.cs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 739 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (22–90 lines × 2) src/ReaLTaiizor/Native/User32.cs:1005— src/ReaLTaiizor/Native/User32.cs:1005-1094 | src/ReaLTaiizor/Native/WinApi.cs:380-401 — before extracting anything, compare `src/ReaLTaiizor/Native/User32.cs` and `src/ReaLTaiizor/Native/WinApi.cs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 739 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (17–80 lines × 2) src/ReaLTaiizor/Native/User32.cs:140— src/ReaLTaiizor/Native/User32.cs:140-219 | src/ReaLTaiizor/Native/WinApi.cs:191-207 — before extracting anything, compare `src/ReaLTaiizor/Native/User32.cs` and `src/ReaLTaiizor/Native/WinApi.cs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 739 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/ReaLTaiizor/Native/User32.cs:140` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (72–73 lines × 2) src/ReaLTaiizor/Controls/TextBox/MaterialMaskedTextBox.cs:1054— src/ReaLTaiizor/Controls/TextBox/MaterialMaskedTextBox.cs:1054-1125 | src/ReaLTaiizor/Controls/TextBoxEdit/MaterialTextBoxEdit.cs:1007-1079 — before extracting anything, compare `src/ReaLTaiizor/Controls/TextBox/MaterialMaskedTextBox.cs` and `src/ReaLTaiizor/Controls/TextBoxEdit/MaterialTextBoxEdit.cs` as WHOLE FILES: this scan already matched 27 separate duplicated blocks between them, totalling at least 574 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/ReaLTaiizor/Controls/TextBox/MaterialMaskedTextBox.cs:1054` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `src/ReaLTaiizor/Controls/TextBoxEdit/MaterialTextBoxEdit.cs:1081` calls `GetLogFontByType` and `src/ReaLTaiizor/Controls/TextBox/MaterialMaskedTextBox.cs:1128` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (62 lines × 2) src/ReaLTaiizor/Controls/ScrollBar/MaterialScrollBar.cs:616— src/ReaLTaiizor/Controls/ScrollBar/MaterialScrollBar.cs:616-677 | src/ReaLTaiizor/Controls/ScrollBar/PoisonScrollBar.cs:816-877 — before extracting anything, compare `src/ReaLTaiizor/Controls/ScrollBar/MaterialScrollBar.cs` and `src/ReaLTaiizor/Controls/ScrollBar/PoisonScrollBar.cs` as WHOLE FILES: this scan already matched 15 separate duplicated blocks between them, totalling at least 423 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/ReaLTaiizor/Controls/ScrollBar/MaterialScrollBar.cs:616` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (62 lines × 3) src/ReaLTaiizor/Controls/TextBox/MaterialMaskedTextBox.cs:1364— src/ReaLTaiizor/Controls/TextBox/MaterialMaskedTextBox.cs:1364-1425 | src/ReaLTaiizor/Controls/TextBox/MaterialTextBox.cs:390-451 | src/ReaLTaiizor/Controls/TextBoxEdit/MaterialTextBoxEdit.cs:1319-1380 — before extracting anything, compare `src/ReaLTaiizor/Controls/TextBox/MaterialMaskedTextBox.cs` and `src/ReaLTaiizor/Controls/TextBox/MaterialTextBox.cs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 167 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/ReaLTaiizor/Controls/TextBox/MaterialMaskedTextBox.cs:1364` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (59 lines × 2) src/ReaLTaiizor/Forms/Form/LostForm.cs:111— src/ReaLTaiizor/Forms/Form/LostForm.cs:111-169 | src/ReaLTaiizor/Forms/Form/RoyalForm.cs:98-156 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `src/ReaLTaiizor/Forms/Form/RoyalForm.cs:96` calls `WndProc` and `src/ReaLTaiizor/Forms/Form/LostForm.cs:110` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (53 lines × 2) src/ReaLTaiizor/Controls/ScrollBar/MaterialScrollBar.cs:960— src/ReaLTaiizor/Controls/ScrollBar/MaterialScrollBar.cs:960-1012 | src/ReaLTaiizor/Controls/ScrollBar/PoisonScrollBar.cs:1160-1212 — before extracting anything, compare `src/ReaLTaiizor/Controls/ScrollBar/MaterialScrollBar.cs` and `src/ReaLTaiizor/Controls/ScrollBar/PoisonScrollBar.cs` as WHOLE FILES: this scan already matched 15 separate duplicated blocks between them, totalling at least 423 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/ReaLTaiizor/Controls/ScrollBar/MaterialScrollBar.cs:960` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (51 lines × 2) src/ReaLTaiizor/Controls/ScrollBar/MaterialScrollBar.cs:732— src/ReaLTaiizor/Controls/ScrollBar/MaterialScrollBar.cs:732-782 | src/ReaLTaiizor/Controls/ScrollBar/PoisonScrollBar.cs:932-982 — before extracting anything, compare `src/ReaLTaiizor/Controls/ScrollBar/MaterialScrollBar.cs` and `src/ReaLTaiizor/Controls/ScrollBar/PoisonScrollBar.cs` as WHOLE FILES: this scan already matched 15 separate duplicated blocks between them, totalling at least 423 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/ReaLTaiizor/Controls/ScrollBar/MaterialScrollBar.cs:732` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (52 lines × 2) src/ReaLTaiizor/Controls/Bubble/ChatBubbleLeft.cs:131— src/ReaLTaiizor/Controls/Bubble/ChatBubbleLeft.cs:131-182 | src/ReaLTaiizor/Controls/Bubble/ChatBubbleRight.cs:152-203 — before extracting anything, compare `src/ReaLTaiizor/Controls/Bubble/ChatBubbleLeft.cs` and `src/ReaLTaiizor/Controls/Bubble/ChatBubbleRight.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 65 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/ReaLTaiizor/Controls/Bubble/ChatBubbleLeft.cs:131` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (44–50 lines × 4) src/ReaLTaiizor/Controls/Button/ChatButtonLeft.cs:251— src/ReaLTaiizor/Controls/Button/ChatButtonLeft.cs:251-294 | src/ReaLTaiizor/Controls/Button/ChatButtonRight.cs:238-281 | src/ReaLTaiizor/Controls/Button/DungeonButtonLeft.cs:252-301 | src/ReaLTaiizor/Controls/Button/DungeonButtonRight.cs:252-301 — before extracting anything, compare `src/ReaLTaiizor/Controls/Button/ChatButtonLeft.cs` and `src/ReaLTaiizor/Controls/Button/ChatButtonRight.cs` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 217 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/ReaLTaiizor/Controls/Button/ChatButtonLeft.cs:251` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `src/ReaLTaiizor/Controls/Button/ChatButtonLeft.cs:247` calls `OnResize` and `src/ReaLTaiizor/Controls/Button/ChatButtonRight.cs:234` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (50 lines × 3) src/ReaLTaiizor/Controls/Button/RibbonButtonCenter.cs:188— src/ReaLTaiizor/Controls/Button/RibbonButtonCenter.cs:188-237 | src/ReaLTaiizor/Controls/Button/RibbonButtonLeft.cs:188-237 | src/ReaLTaiizor/Controls/Button/RibbonButtonRight.cs:188-237 — before extracting anything, compare `src/ReaLTaiizor/Controls/Button/RibbonButtonCenter.cs` and `src/ReaLTaiizor/Controls/Button/RibbonButtonLeft.cs` as WHOLE FILES: 90% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 2 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (46–47 lines × 2) src/ReaLTaiizor/Controls/Button/MetroButton.cs:132— src/ReaLTaiizor/Controls/Button/MetroButton.cs:132-178 | src/ReaLTaiizor/Controls/Button/MetroDefaultButton.cs:113-158 — before extracting anything, compare `src/ReaLTaiizor/Controls/Button/MetroButton.cs` and `src/ReaLTaiizor/Controls/Button/MetroDefaultButton.cs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 141 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/ReaLTaiizor/Controls/Button/MetroButton.cs:132` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (44–45 lines × 5) src/ReaLTaiizor/Controls/TextBox/MaterialMaskedTextBox.cs:1412— src/ReaLTaiizor/Controls/TextBox/MaterialMaskedTextBox.cs:1412-1455 | src/ReaLTaiizor/Controls/TextBox/MaterialMaskedTextBox.cs:1469-1513 | src/ReaLTaiizor/Controls/TextBox/MaterialTextBox.cs:476-520 | src/ReaLTaiizor/Controls/TextBoxEdit/MaterialTextBoxEdit.cs:1367-1410 | src/ReaLTaiizor/Controls/TextBoxEdit/MaterialTextBoxEdit.cs:1424-1468 — before extracting anything, compare `src/ReaLTaiizor/Controls/TextBox/MaterialMaskedTextBox.cs` and `src/ReaLTaiizor/Controls/TextBox/MaterialTextBox.cs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 167 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (42 lines × 2) src/ReaLTaiizor/Util/Material.cs:797— src/ReaLTaiizor/Util/Material.cs:797-838 | src/ReaLTaiizor/Util/Material.cs:845-886 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (42 lines × 5) src/ReaLTaiizor/Controls/Button/Button.cs:66— src/ReaLTaiizor/Controls/Button/Button.cs:66-107 | src/ReaLTaiizor/Controls/Button/ChatButtonLeft.cs:69-110 | src/ReaLTaiizor/Controls/Button/ChatButtonRight.cs:66-107 | src/ReaLTaiizor/Controls/Button/DungeonButtonLeft.cs:68-109 | src/ReaLTaiizor/Controls/Button/DungeonButtonRight.cs:68-109 — before extracting anything, compare `src/ReaLTaiizor/Controls/Button/Button.cs` and `src/ReaLTaiizor/Controls/Button/ChatButtonLeft.cs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 90 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (41 lines × 2) src/ReaLTaiizor/Child/Material/MaterialBaseTextBox.cs:108— src/ReaLTaiizor/Child/Material/MaterialBaseTextBox.cs:108-148 | src/ReaLTaiizor/Child/Material/MaterialBaseTextBox.cs:243-283 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (40 lines × 2) src/ReaLTaiizor/Controls/ScrollBar/MaterialScrollBar.cs:306— src/ReaLTaiizor/Controls/ScrollBar/MaterialScrollBar.cs:306-345 | src/ReaLTaiizor/Controls/ScrollBar/PoisonScrollBar.cs:409-448 — before extracting anything, compare `src/ReaLTaiizor/Controls/ScrollBar/MaterialScrollBar.cs` and `src/ReaLTaiizor/Controls/ScrollBar/PoisonScrollBar.cs` as WHOLE FILES: this scan already matched 15 separate duplicated blocks between them, totalling at least 423 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (39 lines × 3) src/ReaLTaiizor/Controls/TextBox/MaterialMaskedTextBox.cs:1322— src/ReaLTaiizor/Controls/TextBox/MaterialMaskedTextBox.cs:1322-1360 | src/ReaLTaiizor/Controls/TextBox/MaterialTextBox.cs:348-386 | src/ReaLTaiizor/Controls/TextBoxEdit/MaterialTextBoxEdit.cs:1277-1315 — before extracting anything, compare `src/ReaLTaiizor/Controls/TextBox/MaterialMaskedTextBox.cs` and `src/ReaLTaiizor/Controls/TextBox/MaterialTextBox.cs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 167 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (39 lines × 2) src/ReaLTaiizor/Forms/Form/PoisonForm.cs:1316— src/ReaLTaiizor/Forms/Form/PoisonForm.cs:1316-1354 | src/ReaLTaiizor/Forms/Form/PoisonForm.cs:1434-1472 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (38 lines × 6) src/ReaLTaiizor/Forms/Container/DungeonForm.cs:353— src/ReaLTaiizor/Forms/Container/DungeonForm.cs:353-390 | src/ReaLTaiizor/Forms/Container/FormTheme.cs:332-369 | src/ReaLTaiizor/Forms/Container/ThemeForm.cs:362-399 | src/ReaLTaiizor/Util/Air.cs:423-460 | src/ReaLTaiizor/Util/Moon.cs:416-453 | src/ReaLTaiizor/Util/Space.cs:418-455 — before extracting anything, compare `src/ReaLTaiizor/Forms/Container/DungeonForm.cs` and `src/ReaLTaiizor/Forms/Container/FormTheme.cs` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 218 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (36–37 lines × 3) src/ReaLTaiizor/Controls/TextBox/MaterialMaskedTextBox.cs:979— src/ReaLTaiizor/Controls/TextBox/MaterialMaskedTextBox.cs:979-1015 | src/ReaLTaiizor/Controls/TextBoxEdit/MaterialMultiLineTextBoxEdit.cs:774-809 | src/ReaLTaiizor/Controls/TextBoxEdit/MaterialTextBoxEdit.cs:928-964 — before extracting anything, compare `src/ReaLTaiizor/Controls/TextBox/MaterialMaskedTextBox.cs` and `src/ReaLTaiizor/Controls/TextBoxEdit/MaterialMultiLineTextBoxEdit.cs` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 164 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (34 lines × 2) src/ReaLTaiizor/Controls/CheckBox/CrownCheckBox.cs:272— src/ReaLTaiizor/Controls/CheckBox/CrownCheckBox.cs:272-305 | src/ReaLTaiizor/Controls/RadioButton/CrownRadioButton.cs:237-270 — before extracting anything, compare `src/ReaLTaiizor/Controls/CheckBox/CrownCheckBox.cs` and `src/ReaLTaiizor/Controls/RadioButton/CrownRadioButton.cs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 95 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (35 lines × 2) src/ReaLTaiizor/Controls/ScrollBar/MaterialScrollBar.cs:51— src/ReaLTaiizor/Controls/ScrollBar/MaterialScrollBar.cs:51-85 | src/ReaLTaiizor/Controls/ScrollBar/PoisonScrollBar.cs:145-179 — before extracting anything, compare `src/ReaLTaiizor/Controls/ScrollBar/MaterialScrollBar.cs` and `src/ReaLTaiizor/Controls/ScrollBar/PoisonScrollBar.cs` as WHOLE FILES: this scan already matched 15 separate duplicated blocks between them, totalling at least 423 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (33 lines × 2) src/ReaLTaiizor/Controls/CheckBox/PoisonCheckBox.cs:257— src/ReaLTaiizor/Controls/CheckBox/PoisonCheckBox.cs:257-289 | src/ReaLTaiizor/Controls/RadioButton/PoisonRadioButton.cs:228-260 — before extracting anything, compare `src/ReaLTaiizor/Controls/CheckBox/PoisonCheckBox.cs` and `src/ReaLTaiizor/Controls/RadioButton/PoisonRadioButton.cs` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 167 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/ReaLTaiizor/Controls/CheckBox/PoisonCheckBox.cs:257` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (32–34 lines × 2) src/ReaLTaiizor/Controls/ListBox/MaterialListBox.cs:956— src/ReaLTaiizor/Controls/ListBox/MaterialListBox.cs:956-989 | src/ReaLTaiizor/Controls/ListBox/MetroListBox.cs:659-690 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (30 lines × 2) src/ReaLTaiizor/Controls/CheckBox/MetroCheckBox.cs:113— src/ReaLTaiizor/Controls/CheckBox/MetroCheckBox.cs:113-142 | src/ReaLTaiizor/Controls/RadioButton/MetroRadioButton.cs:113-142 — before extracting anything, compare `src/ReaLTaiizor/Controls/CheckBox/MetroCheckBox.cs` and `src/ReaLTaiizor/Controls/RadioButton/MetroRadioButton.cs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 90 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/ReaLTaiizor/Controls/CheckBox/MetroCheckBox.cs:113` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (31 lines × 2) src/ReaLTaiizor/Controls/CheckBox/CyberCheckBox.cs:617— src/ReaLTaiizor/Controls/CheckBox/CyberCheckBox.cs:617-647 | src/ReaLTaiizor/Controls/RadioButton/CyberRadioButton.cs:671-701 — before extracting anything, compare `src/ReaLTaiizor/Controls/CheckBox/CyberCheckBox.cs` and `src/ReaLTaiizor/Controls/RadioButton/CyberRadioButton.cs` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 249 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (30–31 lines × 2) src/ReaLTaiizor/Controls/RichTextBox/CyberRichTextBox.cs:344— src/ReaLTaiizor/Controls/RichTextBox/CyberRichTextBox.cs:344-373 | src/ReaLTaiizor/Controls/TextBox/CyberTextBox.cs:384-414 — before extracting anything, compare `src/ReaLTaiizor/Controls/RichTextBox/CyberRichTextBox.cs` and `src/ReaLTaiizor/Controls/TextBox/CyberTextBox.cs` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 202 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/ReaLTaiizor/Controls/RichTextBox/CyberRichTextBox.cs:344` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `src/ReaLTaiizor/Controls/TextBox/CyberTextBox.cs:383` calls `Bool` and `src/ReaLTaiizor/Controls/RichTextBox/CyberRichTextBox.cs:343` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (29–30 lines × 4) src/ReaLTaiizor/Controls/Button/ChatButtonLeft.cs:36— src/ReaLTaiizor/Controls/Button/ChatButtonLeft.cs:36-65 | src/ReaLTaiizor/Controls/Button/ChatButtonRight.cs:34-62 | src/ReaLTaiizor/Controls/Button/DungeonButtonLeft.cs:35-64 | src/ReaLTaiizor/Controls/Button/DungeonButtonRight.cs:35-64 — before extracting anything, compare `src/ReaLTaiizor/Controls/Button/ChatButtonLeft.cs` and `src/ReaLTaiizor/Controls/Button/ChatButtonRight.cs` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 217 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `src/ReaLTaiizor/Controls/Button/ChatButtonLeft.cs:29` calls `FromArgb` and `src/ReaLTaiizor/Controls/Button/ChatButtonRight.cs:28` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (28 lines × 2) src/ReaLTaiizor/Controls/CheckBox/PoisonCheckBox.cs:208— src/ReaLTaiizor/Controls/CheckBox/PoisonCheckBox.cs:208-235 | src/ReaLTaiizor/Controls/RadioButton/PoisonRadioButton.cs:179-206 — before extracting anything, compare `src/ReaLTaiizor/Controls/CheckBox/PoisonCheckBox.cs` and `src/ReaLTaiizor/Controls/RadioButton/PoisonRadioButton.cs` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 167 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (33–35 lines × 3) src/ReaLTaiizor/Controls/Progress/RibbonProgressBarCenter.cs:252— src/ReaLTaiizor/Controls/Progress/RibbonProgressBarCenter.cs:252-284 | src/ReaLTaiizor/Controls/Progress/RibbonProgressBarLeft.cs:247-281 | src/ReaLTaiizor/Controls/Progress/RibbonProgressBarRight.cs:247-281 — before extracting anything, compare `src/ReaLTaiizor/Controls/Progress/RibbonProgressBarCenter.cs` and `src/ReaLTaiizor/Controls/Progress/RibbonProgressBarLeft.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 55 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/ReaLTaiizor/Controls/Progress/RibbonProgressBarCenter.cs:252` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (26 lines × 9) src/ReaLTaiizor/Controls/Button/CyberButton.cs:59— src/ReaLTaiizor/Controls/Button/CyberButton.cs:59-84 | src/ReaLTaiizor/Controls/CheckBox/CyberCheckBox.cs:68-93 | src/ReaLTaiizor/Controls/GroupBox/CyberGroupBox.cs:56-81 | src/ReaLTaiizor/Controls/Progress/CyberProgressBar.cs:116-141 | src/ReaLTaiizor/Controls/RadioButton/CyberRadioButton.cs:85-110 | src/ReaLTaiizor/Controls/RichTextBox/CyberRichTextBox.cs:56-81 | src/ReaLTaiizor/Controls/ScrollBar/CyberScrollBar.cs:138-163 | src/ReaLTaiizor/Controls/Switch/CyberSwitch.cs:54-79 | src/ReaLTaiizor/Controls/TextBox/CyberTextBox.cs:56-81 — before extracting anything, compare `src/ReaLTaiizor/Controls/Button/CyberButton.cs` and `src/ReaLTaiizor/Controls/CheckBox/CyberCheckBox.cs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 119 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `src/ReaLTaiizor/Controls/TextBox/CyberTextBox.cs:85` calls `DefaultValue` and `src/ReaLTaiizor/Controls/Button/CyberButton.cs:88` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (22–27 lines × 3) src/ReaLTaiizor/Controls/CheckBox/MaterialCheckBox.cs:354— src/ReaLTaiizor/Controls/CheckBox/MaterialCheckBox.cs:354-375 | src/ReaLTaiizor/Controls/RadioButton/MaterialRadioButton.cs:300-326 | src/ReaLTaiizor/Controls/Switch/MaterialSwitch.cs:353-379 — before extracting anything, compare `src/ReaLTaiizor/Controls/CheckBox/MaterialCheckBox.cs` and `src/ReaLTaiizor/Controls/RadioButton/MaterialRadioButton.cs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 99 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/ReaLTaiizor/Controls/CheckBox/MaterialCheckBox.cs:354` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (27 lines × 2) src/ReaLTaiizor/Controls/Close/ForeverClose.cs:127— src/ReaLTaiizor/Controls/Close/ForeverClose.cs:127-153 | src/ReaLTaiizor/Controls/Minimize/ForeverMinimize.cs:135-161 — before extracting anything, compare `src/ReaLTaiizor/Controls/Close/ForeverClose.cs` and `src/ReaLTaiizor/Controls/Minimize/ForeverMinimize.cs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 88 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (25 lines × 2) src/ReaLTaiizor/Controls/TextBox/MaterialMaskedTextBox.cs:934— src/ReaLTaiizor/Controls/TextBox/MaterialMaskedTextBox.cs:934-958 | src/ReaLTaiizor/Controls/TextBoxEdit/MaterialTextBoxEdit.cs:883-907 — before extracting anything, compare `src/ReaLTaiizor/Controls/TextBox/MaterialMaskedTextBox.cs` and `src/ReaLTaiizor/Controls/TextBoxEdit/MaterialTextBoxEdit.cs` as WHOLE FILES: this scan already matched 27 separate duplicated blocks between them, totalling at least 574 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (63–65 lines × 2) src/ReaLTaiizor/Controls/CheckBox/CyberCheckBox.cs:386— src/ReaLTaiizor/Controls/CheckBox/CyberCheckBox.cs:386-448 | src/ReaLTaiizor/Controls/RadioButton/CyberRadioButton.cs:439-503 — before extracting anything, compare `src/ReaLTaiizor/Controls/CheckBox/CyberCheckBox.cs` and `src/ReaLTaiizor/Controls/RadioButton/CyberRadioButton.cs` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 249 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/ReaLTaiizor/Controls/CheckBox/CyberCheckBox.cs:386` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (23–25 lines × 7) src/ReaLTaiizor/Controls/Button/CyberButton.cs:433— src/ReaLTaiizor/Controls/Button/CyberButton.cs:433-456 | src/ReaLTaiizor/Controls/CheckBox/CyberCheckBox.cs:411-433 | src/ReaLTaiizor/Controls/GroupBox/CyberGroupBox.cs:355-378 | src/ReaLTaiizor/Controls/Progress/CyberProgressBar.cs:501-525 | src/ReaLTaiizor/Controls/RadioButton/CyberRadioButton.cs:464-488 | src/ReaLTaiizor/Controls/ScrollBar/CyberScrollBar.cs:528-551 | src/ReaLTaiizor/Controls/Switch/CyberSwitch.cs:418-441 — before extracting anything, compare `src/ReaLTaiizor/Controls/Button/CyberButton.cs` and `src/ReaLTaiizor/Controls/CheckBox/CyberCheckBox.cs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 119 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/ReaLTaiizor/Controls/Button/CyberButton.cs:433` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `src/ReaLTaiizor/Controls/CheckBox/CyberCheckBox.cs:434` calls `ColorArgb`, `Int` and `src/ReaLTaiizor/Controls/Button/CyberButton.cs:457` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (24 lines × 7) src/ReaLTaiizor/Controls/ComboBox/PoisonComboBox.cs:382— src/ReaLTaiizor/Controls/ComboBox/PoisonComboBox.cs:382-405 | src/ReaLTaiizor/Controls/DateTime/PoisonDateTime.cs:275-298 | src/ReaLTaiizor/Controls/LinkLabel/PoisonLinkLabel.cs:272-295 | src/ReaLTaiizor/Controls/Panel/PoisonPanel.cs:257-280 | src/ReaLTaiizor/Controls/TabControl/PoisonTabControl.cs:209-232 | src/ReaLTaiizor/Controls/TabPage/PoisonTabPage.cs:252-275 | src/ReaLTaiizor/Controls/UserControl/PoisonUserControl.cs:137-160 — before extracting anything, compare `src/ReaLTaiizor/Controls/ComboBox/PoisonComboBox.cs` and `src/ReaLTaiizor/Controls/DateTime/PoisonDateTime.cs` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 124 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `src/ReaLTaiizor/Controls/TabPage/PoisonTabPage.cs:279` calls `OnPaint` and `src/ReaLTaiizor/Controls/ComboBox/PoisonComboBox.cs:409` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (23–25 lines × 3) src/ReaLTaiizor/Controls/TextBox/MaterialMaskedTextBox.cs:1033— src/ReaLTaiizor/Controls/TextBox/MaterialMaskedTextBox.cs:1033-1055 | src/ReaLTaiizor/Controls/TextBoxEdit/MaterialMultiLineTextBoxEdit.cs:831-855 | src/ReaLTaiizor/Controls/TextBoxEdit/MaterialTextBoxEdit.cs:984-1008 — before extracting anything, compare `src/ReaLTaiizor/Controls/TextBox/MaterialMaskedTextBox.cs` and `src/ReaLTaiizor/Controls/TextBoxEdit/MaterialMultiLineTextBoxEdit.cs` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 164 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/ReaLTaiizor/Controls/TextBox/MaterialMaskedTextBox.cs:1033` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (22 lines × 4) src/ReaLTaiizor/Controls/TextBox/MaterialMaskedTextBox.cs:1609— src/ReaLTaiizor/Controls/TextBox/MaterialMaskedTextBox.cs:1609-1630 | src/ReaLTaiizor/Controls/TextBox/MaterialSingleTextBox.cs:682-703 | src/ReaLTaiizor/Controls/TextBoxEdit/MaterialMultiLineTextBoxEdit.cs:991-1012 | src/ReaLTaiizor/Controls/TextBoxEdit/MaterialTextBoxEdit.cs:1567-1588 — before extracting anything, compare `src/ReaLTaiizor/Controls/TextBox/MaterialMaskedTextBox.cs` and `src/ReaLTaiizor/Controls/TextBoxEdit/MaterialMultiLineTextBoxEdit.cs` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 164 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (22–23 lines × 2) src/ReaLTaiizor/Controls/ComboBox/CyberComboBox.cs:283— src/ReaLTaiizor/Controls/ComboBox/CyberComboBox.cs:283-305 | src/ReaLTaiizor/Controls/RichTextBox/CyberRichTextBox.cs:334-355 — before extracting anything, compare `src/ReaLTaiizor/Controls/ComboBox/CyberComboBox.cs` and `src/ReaLTaiizor/Controls/RichTextBox/CyberRichTextBox.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 49 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/ReaLTaiizor/Controls/ComboBox/CyberComboBox.cs:283` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (22 lines × 7) src/ReaLTaiizor/Controls/Button/CyberButton.cs:596— src/ReaLTaiizor/Controls/Button/CyberButton.cs:596-617 | src/ReaLTaiizor/Controls/GroupBox/CyberGroupBox.cs:485-506 | src/ReaLTaiizor/Controls/Progress/CyberProgressBar.cs:646-667 | src/ReaLTaiizor/Controls/RichTextBox/CyberRichTextBox.cs:492-513 | src/ReaLTaiizor/Controls/ScrollBar/CyberScrollBar.cs:739-760 | src/ReaLTaiizor/Controls/Switch/CyberSwitch.cs:567-588 | src/ReaLTaiizor/Controls/TextBox/CyberTextBox.cs:541-562 — before extracting anything, compare `src/ReaLTaiizor/Controls/Button/CyberButton.cs` and `src/ReaLTaiizor/Controls/GroupBox/CyberGroupBox.cs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 143 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/ReaLTaiizor/Controls/Button/CyberButton.cs:596` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (21 lines × 6) src/ReaLTaiizor/Util/Air.cs:1124— src/ReaLTaiizor/Util/Air.cs:1124-1144 | src/ReaLTaiizor/Util/Air.cs:2097-2117 | src/ReaLTaiizor/Util/Moon.cs:1118-1138 | src/ReaLTaiizor/Util/Moon.cs:2099-2119 | src/ReaLTaiizor/Util/Space.cs:1120-1140 | src/ReaLTaiizor/Util/Space.cs:2096-2116 — before extracting anything, compare `src/ReaLTaiizor/Util/Air.cs` and `src/ReaLTaiizor/Util/Moon.cs` as WHOLE FILES: this scan already matched 40 separate duplicated blocks between them, totalling at least 661 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (19–21 lines × 11) src/ReaLTaiizor/Controls/Button/Button.cs:325— src/ReaLTaiizor/Controls/Button/Button.cs:325-344 | src/ReaLTaiizor/Controls/Button/Button.cs:349-369 | src/ReaLTaiizor/Controls/Button/Button.cs:374-394 | src/ReaLTaiizor/Controls/Button/ChatButtonLeft.cs:260-278 | src/ReaLTaiizor/Controls/Button/ChatButtonLeft.cs:281-300 | src/ReaLTaiizor/Controls/Button/ChatButtonRight.cs:248-266 | src/ReaLTaiizor/Controls/Button/ChatButtonRight.cs:269-287 | src/ReaLTaiizor/Controls/Button/DungeonButtonLeft.cs:263-282 | src/ReaLTaiizor/Controls/Button/DungeonButtonLeft.cs:287-307 | src/ReaLTaiizor/Controls/Button/DungeonButtonRight.cs:263-282 | src/ReaLTaiizor/Controls/Button/DungeonButtonRight.cs:287-307 — before extracting anything, compare `src/ReaLTaiizor/Controls/Button/Button.cs` and `src/ReaLTaiizor/Controls/Button/ChatButtonLeft.cs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 90 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (19 lines × 6) src/ReaLTaiizor/Util/Air.cs:744— src/ReaLTaiizor/Util/Air.cs:744-762 | src/ReaLTaiizor/Util/Air.cs:1803-1821 | src/ReaLTaiizor/Util/Moon.cs:737-755 | src/ReaLTaiizor/Util/Moon.cs:1802-1820 | src/ReaLTaiizor/Util/Space.cs:739-757 | src/ReaLTaiizor/Util/Space.cs:1800-1818 — before extracting anything, compare `src/ReaLTaiizor/Util/Air.cs` and `src/ReaLTaiizor/Util/Moon.cs` as WHOLE FILES: this scan already matched 40 separate duplicated blocks between them, totalling at least 661 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/ReaLTaiizor/Util/Air.cs:744` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (19 lines × 3) src/ReaLTaiizor/Controls/ControlBox/ThunderControlBox.cs:265— src/ReaLTaiizor/Controls/ControlBox/ThunderControlBox.cs:265-283 | src/ReaLTaiizor/Controls/ControlBox/ThunderControlBox.cs:325-343 | src/ReaLTaiizor/Controls/ControlBox/ThunderControlBox.cs:353-371 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (19–21 lines × 2) src/ReaLTaiizor/Controls/Numeric/ForeverNumeric.cs:207— src/ReaLTaiizor/Controls/Numeric/ForeverNumeric.cs:207-225 | src/ReaLTaiizor/Controls/StatusBar/ForeverStatusBar.cs:81-101 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `src/ReaLTaiizor/Controls/Numeric/ForeverNumeric.cs:207` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (20 lines × 3) src/ReaLTaiizor/Controls/CheckBox/PoisonCheckBox.cs:282— src/ReaLTaiizor/Controls/CheckBox/PoisonCheckBox.cs:282-301 | src/ReaLTaiizor/Controls/RadioButton/PoisonRadioButton.cs:253-272 | src/ReaLTaiizor/Controls/Toggle/PoisonToggle.cs:257-276 — before extracting anything, compare `src/ReaLTaiizor/Controls/CheckBox/PoisonCheckBox.cs` and `src/ReaLTaiizor/Controls/RadioButton/PoisonRadioButton.cs` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 167 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (19 lines × 9) src/ReaLTaiizor/Controls/Button/CyberButton.cs:608— src/ReaLTaiizor/Controls/Button/CyberButton.cs:608-626 | src/ReaLTaiizor/Controls/CheckBox/CyberCheckBox.cs:598-616 | src/ReaLTaiizor/Controls/GroupBox/CyberGroupBox.cs:497-515 | src/ReaLTaiizor/Controls/Progress/CyberProgressBar.cs:658-676 | src/ReaLTaiizor/Controls/RadioButton/CyberRadioButton.cs:652-670 | src/ReaLTaiizor/Controls/RichTextBox/CyberRichTextBox.cs:504-522 | src/ReaLTaiizor/Controls/ScrollBar/CyberScrollBar.cs:751-769 | src/ReaLTaiizor/Controls/Switch/CyberSwitch.cs:579-597 | src/ReaLTaiizor/Controls/TextBox/CyberTextBox.cs:553-571 — before extracting anything, compare `src/ReaLTaiizor/Controls/Button/CyberButton.cs` and `src/ReaLTaiizor/Controls/CheckBox/CyberCheckBox.cs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 119 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/ReaLTaiizor/Controls/Button/CyberButton.cs:608` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
Duplicated block (18 lines × 6) src/ReaLTaiizor/Util/Air.cs:1377— src/ReaLTaiizor/Util/Air.cs:1377-1394 | src/ReaLTaiizor/Util/Air.cs:2350-2367 | src/ReaLTaiizor/Util/Moon.cs:1370-1387 | src/ReaLTaiizor/Util/Moon.cs:2354-2371 | src/ReaLTaiizor/Util/Space.cs:1374-1391 | src/ReaLTaiizor/Util/Space.cs:2351-2368 — before extracting anything, compare `src/ReaLTaiizor/Util/Air.cs` and `src/ReaLTaiizor/Util/Moon.cs` as WHOLE FILES: this scan already matched 40 separate duplicated blocks between them, totalling at least 661 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (4–19 lines × 3) src/ReaLTaiizor/Controls/ControlBox/DungeonControlBox.cs:230— src/ReaLTaiizor/Controls/ControlBox/DungeonControlBox.cs:230-248 | src/ReaLTaiizor/Controls/ControlBox/DungeonControlBox.cs:265-283 | src/ReaLTaiizor/Controls/ControlBox/DungeonControlBox.cs:317-320 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/ReaLTaiizor/Controls/ControlBox/DungeonControlBox.cs:230` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (18 lines × 22) src/ReaLTaiizor/Child/Metro/MetroTabPage.cs:30— src/ReaLTaiizor/Child/Metro/MetroTabPage.cs:30-47 | src/ReaLTaiizor/Controls/Badge/MetroBadge.cs:39-56 | src/ReaLTaiizor/Controls/Button/MetroButton.cs:54-72 | src/ReaLTaiizor/Controls/Button/MetroDefaultButton.cs:37-54 | src/ReaLTaiizor/Controls/CheckBox/MetroCheckBox.cs:38-55 | src/ReaLTaiizor/Controls/ControlBox/MetroControlBox.cs:36-53 | src/ReaLTaiizor/Controls/Divider/MetroDivider.cs:35-52 | src/ReaLTaiizor/Controls/Ellipse/MetroEllipse.cs:38-55 | src/ReaLTaiizor/Controls/Label/MetroLabel.cs:35-52 | src/ReaLTaiizor/Controls/LinkLabel/MetroLinkLabel.cs:35-52 | src/ReaLTaiizor/Controls/Numeric/MetroNumeric.cs:38-55 | src/ReaLTaiizor/Controls/Panel/MetroPanel.cs:32-49 | src/ReaLTaiizor/Controls/Progress/MetroProgressBar.cs:36-53 | src/ReaLTaiizor/Controls/RadioButton/MetroRadioButton.cs:40-57 | src/ReaLTaiizor/Controls/RichTextBox/MetroRichTextBox.cs:37-54 | src/ReaLTaiizor/Controls/ScrollBar/MetroScrollBar.cs:34-51 | src/ReaLTaiizor/Controls/Strip/MetroContextMenuStrip.cs:34-51 | src/ReaLTaiizor/Controls/Switch/MetroSwitch.cs:38-55 | src/ReaLTaiizor/Controls/TabControl/MetroTabControl.cs:39-56 | src/ReaLTaiizor/Controls/TextBox/MetroTextBox.cs:38-55 | src/ReaLTaiizor/Controls/Tile/MetroTile.cs:37-54 | src/ReaLTaiizor/Controls/TrackBar/MetroTrackBar.cs:36-53 — before extracting anything, compare `src/ReaLTaiizor/Controls/Badge/MetroBadge.cs` and `src/ReaLTaiizor/Controls/Button/MetroButton.cs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 97 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `src/ReaLTaiizor/Child/Metro/MetroTabPage.cs:50` calls `Browsable` and `src/ReaLTaiizor/Controls/CheckBox/MetroCheckBox.cs:58` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (17–18 lines × 2) src/ReaLTaiizor/Controls/ComboBox/ForeverComboBox.cs:117— src/ReaLTaiizor/Controls/ComboBox/ForeverComboBox.cs:117-134 | src/ReaLTaiizor/Controls/ComboBox/HopeComboBox.cs:75-91 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `src/ReaLTaiizor/Controls/ComboBox/ForeverComboBox.cs:117` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (16 lines × 5) src/ReaLTaiizor/Controls/ComboBox/MetroComboBox.cs:356— src/ReaLTaiizor/Controls/ComboBox/MetroComboBox.cs:356-371 | src/ReaLTaiizor/Controls/Numeric/MetroNumeric.cs:202-217 | src/ReaLTaiizor/Controls/RichTextBox/MetroRichTextBox.cs:257-272 | src/ReaLTaiizor/Controls/ScrollBar/MetroScrollBar.cs:163-178 | src/ReaLTaiizor/Controls/Strip/MetroContextMenuStrip.cs:151-166 — before extracting anything, compare `src/ReaLTaiizor/Controls/ComboBox/MetroComboBox.cs` and `src/ReaLTaiizor/Controls/Numeric/MetroNumeric.cs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 71 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/ReaLTaiizor/Controls/ComboBox/MetroComboBox.cs:356` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (17 lines × 4) src/ReaLTaiizor/Controls/Button/CyberButton.cs:579— src/ReaLTaiizor/Controls/Button/CyberButton.cs:579-595 | src/ReaLTaiizor/Controls/GroupBox/CyberGroupBox.cs:467-483 | src/ReaLTaiizor/Controls/RichTextBox/CyberRichTextBox.cs:474-490 | src/ReaLTaiizor/Controls/TextBox/CyberTextBox.cs:523-539 — before extracting anything, compare `src/ReaLTaiizor/Controls/Button/CyberButton.cs` and `src/ReaLTaiizor/Controls/GroupBox/CyberGroupBox.cs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 143 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (14 lines × 4) src/ReaLTaiizor/Util/Material.cs:998— src/ReaLTaiizor/Util/Material.cs:998-1011 | src/ReaLTaiizor/Util/Material.cs:1028-1041 | src/ReaLTaiizor/Util/Material.cs:1078-1091 | src/ReaLTaiizor/Util/Material.cs:1108-1121 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (15–17 lines × 2) src/ReaLTaiizor/Forms/Panel/ParrotForm.cs:526— src/ReaLTaiizor/Forms/Panel/ParrotForm.cs:526-542 | src/ReaLTaiizor/Forms/Panel/ParrotForm.cs:651-665 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (14 lines × 7) src/ReaLTaiizor/Colors/Material.cs:34— src/ReaLTaiizor/Colors/Material.cs:34-47 | src/ReaLTaiizor/Colors/Material.cs:62-75 | src/ReaLTaiizor/Colors/Material.cs:90-103 | src/ReaLTaiizor/Colors/Material.cs:114-127 | src/ReaLTaiizor/Colors/Material.cs:138-151 | src/ReaLTaiizor/Colors/Material.cs:162-175 | src/ReaLTaiizor/Colors/Material.cs:186-199 — all 7 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/ReaLTaiizor/Colors/Material.cs:34` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `src/ReaLTaiizor/Colors/Material.cs:60` calls `ToColor` and `src/ReaLTaiizor/Colors/Material.cs:88` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (15–16 lines × 7) src/ReaLTaiizor/Controls/Button/CyberButton.cs:449— src/ReaLTaiizor/Controls/Button/CyberButton.cs:449-463 | src/ReaLTaiizor/Controls/GroupBox/CyberGroupBox.cs:371-385 | src/ReaLTaiizor/Controls/Progress/CyberProgressBar.cs:517-532 | src/ReaLTaiizor/Controls/RichTextBox/CyberRichTextBox.cs:348-362 | src/ReaLTaiizor/Controls/ScrollBar/CyberScrollBar.cs:543-558 | src/ReaLTaiizor/Controls/Switch/CyberSwitch.cs:433-448 | src/ReaLTaiizor/Controls/TextBox/CyberTextBox.cs:388-403 — before extracting anything, compare `src/ReaLTaiizor/Controls/Button/CyberButton.cs` and `src/ReaLTaiizor/Controls/GroupBox/CyberGroupBox.cs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 143 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/ReaLTaiizor/Controls/Button/CyberButton.cs:449` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (13–16 lines × 3) src/ReaLTaiizor/Controls/Progress/PoisonProgressBar.cs:109— src/ReaLTaiizor/Controls/Progress/PoisonProgressBar.cs:109-124 | src/ReaLTaiizor/Controls/ScrollBar/PoisonScrollBar.cs:111-123 | src/ReaLTaiizor/Controls/TrackBar/PoisonTrackBar.cs:107-119 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times.
Duplicated block (14–15 lines × 6) src/ReaLTaiizor/Forms/Container/DungeonForm.cs:226— src/ReaLTaiizor/Forms/Container/DungeonForm.cs:226-239 | src/ReaLTaiizor/Forms/Container/FormTheme.cs:205-218 | src/ReaLTaiizor/Forms/Container/ThemeForm.cs:234-247 | src/ReaLTaiizor/Util/Air.cs:150-164 | src/ReaLTaiizor/Util/Moon.cs:148-162 | src/ReaLTaiizor/Util/Space.cs:150-164 — before extracting anything, compare `src/ReaLTaiizor/Forms/Container/DungeonForm.cs` and `src/ReaLTaiizor/Forms/Container/FormTheme.cs` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 218 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (14–15 lines × 3) src/ReaLTaiizor/Controls/ComboBox/CyberComboBox.cs:292— src/ReaLTaiizor/Controls/ComboBox/CyberComboBox.cs:292-306 | src/ReaLTaiizor/Controls/RichTextBox/CyberRichTextBox.cs:343-356 | src/ReaLTaiizor/Controls/TextBox/CyberTextBox.cs:383-397 — before extracting anything, compare `src/ReaLTaiizor/Controls/ComboBox/CyberComboBox.cs` and `src/ReaLTaiizor/Controls/RichTextBox/CyberRichTextBox.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 49 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `src/ReaLTaiizor/Controls/TextBox/CyberTextBox.cs:383` calls `Bool` and `src/ReaLTaiizor/Controls/ComboBox/CyberComboBox.cs:292` does not — after which the two agree again for 5 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (11–13 lines × 5) src/ReaLTaiizor/Controls/Close/ForeverClose.cs:123— src/ReaLTaiizor/Controls/Close/ForeverClose.cs:123-133 | src/ReaLTaiizor/Controls/ListBox/ForeverListBox.cs:203-215 | src/ReaLTaiizor/Controls/Maximize/ForeverMaximize.cs:131-141 | src/ReaLTaiizor/Controls/Minimize/ForeverMinimize.cs:131-141 | src/ReaLTaiizor/Controls/TreeView/ForeverTreeView.cs:76-86 — before extracting anything, compare `src/ReaLTaiizor/Controls/Close/ForeverClose.cs` and `src/ReaLTaiizor/Controls/Maximize/ForeverMaximize.cs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 61 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/ReaLTaiizor/Controls/Close/ForeverClose.cs:123` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (11 lines × 7) src/ReaLTaiizor/Controls/Button/CyberButton.cs:428— src/ReaLTaiizor/Controls/Button/CyberButton.cs:428-438 | src/ReaLTaiizor/Controls/CheckBox/CyberCheckBox.cs:406-416 | src/ReaLTaiizor/Controls/ComboBox/CyberComboBox.cs:281-291 | src/ReaLTaiizor/Controls/RadioButton/CyberRadioButton.cs:459-469 | src/ReaLTaiizor/Controls/RichTextBox/CyberRichTextBox.cs:332-342 | src/ReaLTaiizor/Controls/Switch/CyberSwitch.cs:413-423 | src/ReaLTaiizor/Controls/TextBox/CyberTextBox.cs:371-381 — before extracting anything, compare `src/ReaLTaiizor/Controls/Button/CyberButton.cs` and `src/ReaLTaiizor/Controls/CheckBox/CyberCheckBox.cs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 119 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `src/ReaLTaiizor/Controls/Button/CyberButton.cs:426` calls `FromArgb` and `src/ReaLTaiizor/Controls/RichTextBox/CyberRichTextBox.cs:331` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (11–12 lines × 2) src/ReaLTaiizor/Controls/CheckBox/MaterialCheckBox.cs:220— src/ReaLTaiizor/Controls/CheckBox/MaterialCheckBox.cs:220-230 | src/ReaLTaiizor/Controls/RadioButton/MaterialRadioButton.cs:192-203 — before extracting anything, compare `src/ReaLTaiizor/Controls/CheckBox/MaterialCheckBox.cs` and `src/ReaLTaiizor/Controls/RadioButton/MaterialRadioButton.cs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 99 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (10 lines × 7) src/ReaLTaiizor/Controls/Badge/MetroBadge.cs:602— src/ReaLTaiizor/Controls/Badge/MetroBadge.cs:602-611 | src/ReaLTaiizor/Controls/Button/MetroButton.cs:273-282 | src/ReaLTaiizor/Controls/Button/MetroDefaultButton.cs:247-256 | src/ReaLTaiizor/Controls/ComboBox/MetroComboBox.cs:350-359 | src/ReaLTaiizor/Controls/Numeric/MetroNumeric.cs:196-205 | src/ReaLTaiizor/Controls/RichTextBox/MetroRichTextBox.cs:251-260 | src/ReaLTaiizor/Controls/TextBox/MetroTextBox.cs:278-287 — before extracting anything, compare `src/ReaLTaiizor/Controls/Badge/MetroBadge.cs` and `src/ReaLTaiizor/Controls/Button/MetroButton.cs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 97 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (11 lines × 6) src/ReaLTaiizor/Controls/GroupBox/CyberGroupBox.cs:517— src/ReaLTaiizor/Controls/GroupBox/CyberGroupBox.cs:517-527 | src/ReaLTaiizor/Controls/Progress/CyberProgressBar.cs:677-687 | src/ReaLTaiizor/Controls/RichTextBox/CyberRichTextBox.cs:524-534 | src/ReaLTaiizor/Controls/ScrollBar/CyberScrollBar.cs:770-780 | src/ReaLTaiizor/Controls/Switch/CyberSwitch.cs:598-608 | src/ReaLTaiizor/Controls/TextBox/CyberTextBox.cs:573-583 — before extracting anything, compare `src/ReaLTaiizor/Controls/GroupBox/CyberGroupBox.cs` and `src/ReaLTaiizor/Controls/Progress/CyberProgressBar.cs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 119 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/ReaLTaiizor/Controls/GroupBox/CyberGroupBox.cs:517` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (10 lines × 17) src/ReaLTaiizor/Controls/Button/PoisonButton.cs:112— src/ReaLTaiizor/Controls/Button/PoisonButton.cs:112-121 | src/ReaLTaiizor/Controls/CheckBox/PoisonCheckBox.cs:111-120 | src/ReaLTaiizor/Controls/ComboBox/PoisonComboBox.cs:113-122 | src/ReaLTaiizor/Controls/DateTime/PoisonDateTime.cs:110-119 | src/ReaLTaiizor/Controls/Label/PoisonLabel.cs:112-121 | src/ReaLTaiizor/Controls/ListView/PoisonListView.cs:113-122 | src/ReaLTaiizor/Controls/Panel/PoisonPanel.cs:116-125 | src/ReaLTaiizor/Controls/Progress/PoisonProgressSpinner.cs:111-120 | src/ReaLTaiizor/Controls/RadioButton/PoisonRadioButton.cs:112-121 | src/ReaLTaiizor/Controls/TabControl/PoisonTabControl.cs:120-129 | src/ReaLTaiizor/Controls/TabPage/PoisonTabPage.cs:112-121 | src/ReaLTaiizor/Controls/TextBox/PoisonTextBox.cs:111-120 | src/ReaLTaiizor/Controls/TextBox/PoisonTextBox.cs:1211-1220 | src/ReaLTaiizor/Controls/Tile/PoisonTile.cs:111-120 | src/ReaLTaiizor/Controls/Toggle/PoisonToggle.cs:112-121 | src/ReaLTaiizor/Controls/UserControl/PoisonUserControl.cs:107-116 | src/ReaLTaiizor/Forms/Form/PoisonForm.cs:889-898 — before extracting anything, compare `src/ReaLTaiizor/Controls/Button/PoisonButton.cs` and `src/ReaLTaiizor/Controls/CheckBox/PoisonCheckBox.cs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 80 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (8 lines × 5) src/ReaLTaiizor/Controls/ComboBox/MetroComboBox.cs:321— src/ReaLTaiizor/Controls/ComboBox/MetroComboBox.cs:321-328 | src/ReaLTaiizor/Controls/Numeric/MetroNumeric.cs:173-180 | src/ReaLTaiizor/Controls/RichTextBox/MetroRichTextBox.cs:228-235 | src/ReaLTaiizor/Controls/ScrollBar/MetroScrollBar.cs:143-150 | src/ReaLTaiizor/Controls/TextBox/MetroTextBox.cs:252-259 — before extracting anything, compare `src/ReaLTaiizor/Controls/ComboBox/MetroComboBox.cs` and `src/ReaLTaiizor/Controls/Numeric/MetroNumeric.cs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 71 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/ReaLTaiizor/Controls/ComboBox/MetroComboBox.cs:321` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (7–10 lines × 2) src/ReaLTaiizor/Controls/Panel/ParrotGradientPanel.cs:172— src/ReaLTaiizor/Controls/Panel/ParrotGradientPanel.cs:172-178 | src/ReaLTaiizor/Controls/Slider/ParrotSlider.cs:320-329 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `src/ReaLTaiizor/Controls/Panel/ParrotGradientPanel.cs:172` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (9 lines × 18) src/ReaLTaiizor/Controls/Button/PoisonButton.cs:110— src/ReaLTaiizor/Controls/Button/PoisonButton.cs:110-118 | src/ReaLTaiizor/Controls/CheckBox/PoisonCheckBox.cs:109-117 | src/ReaLTaiizor/Controls/ComboBox/PoisonComboBox.cs:111-119 | src/ReaLTaiizor/Controls/DateTime/PoisonDateTime.cs:108-116 | src/ReaLTaiizor/Controls/Label/PoisonLabel.cs:110-118 | src/ReaLTaiizor/Controls/LinkLabel/PoisonLinkLabel.cs:128-136 | src/ReaLTaiizor/Controls/ListView/PoisonListView.cs:111-119 | src/ReaLTaiizor/Controls/Panel/PoisonPanel.cs:114-122 | src/ReaLTaiizor/Controls/Progress/PoisonProgressSpinner.cs:109-117 | src/ReaLTaiizor/Controls/RadioButton/PoisonRadioButton.cs:110-118 | src/ReaLTaiizor/Controls/TabControl/PoisonTabControl.cs:118-126 | src/ReaLTaiizor/Controls/TabPage/PoisonTabPage.cs:110-118 | src/ReaLTaiizor/Controls/TextBox/PoisonTextBox.cs:109-117 | src/ReaLTaiizor/Controls/TextBox/PoisonTextBox.cs:1209-1217 | src/ReaLTaiizor/Controls/Tile/PoisonTile.cs:109-117 | src/ReaLTaiizor/Controls/Toggle/PoisonToggle.cs:110-118 | src/ReaLTaiizor/Controls/UserControl/PoisonUserControl.cs:105-113 | src/ReaLTaiizor/Forms/Form/PoisonForm.cs:887-895 — before extracting anything, compare `src/ReaLTaiizor/Controls/Button/PoisonButton.cs` and `src/ReaLTaiizor/Controls/CheckBox/PoisonCheckBox.cs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 80 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (7–9 lines × 4) src/ReaLTaiizor/Controls/Button/RibbonButtonCenter.cs:187— src/ReaLTaiizor/Controls/Button/RibbonButtonCenter.cs:187-195 | src/ReaLTaiizor/Controls/Button/RibbonButtonLeft.cs:187-195 | src/ReaLTaiizor/Controls/Button/RibbonButtonRight.cs:187-195 | src/ReaLTaiizor/Controls/GroupBox/ThunderGroupBox.cs:39-45 — before extracting anything, compare `src/ReaLTaiizor/Controls/Button/RibbonButtonCenter.cs` and `src/ReaLTaiizor/Controls/Button/RibbonButtonLeft.cs` as WHOLE FILES: 90% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 2 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/ReaLTaiizor/Controls/Button/RibbonButtonCenter.cs:187` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (7–9 lines × 3) src/ReaLTaiizor/Controls/Panel/ParrotGradientPanel.cs:174— src/ReaLTaiizor/Controls/Panel/ParrotGradientPanel.cs:174-180 | src/ReaLTaiizor/Controls/Progress/ParrotFlatProgressBar.cs:258-265 | src/ReaLTaiizor/Controls/Slider/ParrotSlider.cs:323-331 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `src/ReaLTaiizor/Controls/Panel/ParrotGradientPanel.cs:173` calls `OnPaint` and `src/ReaLTaiizor/Controls/Progress/ParrotFlatProgressBar.cs:257` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (7 lines × 5) src/ReaLTaiizor/Controls/ControlBox/ThunderControlBox.cs:171— src/ReaLTaiizor/Controls/ControlBox/ThunderControlBox.cs:171-177 | src/ReaLTaiizor/Controls/ControlBox/ThunderControlBox.cs:232-238 | src/ReaLTaiizor/Controls/ControlBox/ThunderControlBox.cs:265-271 | src/ReaLTaiizor/Controls/ControlBox/ThunderControlBox.cs:325-331 | src/ReaLTaiizor/Controls/ControlBox/ThunderControlBox.cs:353-359 — all 5 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/ReaLTaiizor/Controls/ControlBox/ThunderControlBox.cs:171` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `src/ReaLTaiizor/Controls/ControlBox/ThunderControlBox.cs:240` calls `FromArgb` and `src/ReaLTaiizor/Controls/ControlBox/ThunderControlBox.cs:178` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (4–8 lines × 5) src/ReaLTaiizor/Controls/Button/DreamButton.cs:54— src/ReaLTaiizor/Controls/Button/DreamButton.cs:54-61 | src/ReaLTaiizor/Controls/ComboBox/DungeonComboBox.cs:45-51 | src/ReaLTaiizor/Controls/Progress/DreamProgressBar.cs:47-55 | src/ReaLTaiizor/Controls/TextBox/DreamTextBox.cs:23-26 | src/ReaLTaiizor/Forms/GroupBox/DreamForm.cs:72-75 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 5 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 5 times. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `src/ReaLTaiizor/Forms/GroupBox/DreamForm.cs:75` calls `FromArgb` and `src/ReaLTaiizor/Controls/TextBox/DreamTextBox.cs:26` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (4–8 lines × 3) src/ReaLTaiizor/Controls/ControlBox/DungeonControlBox.cs:222— src/ReaLTaiizor/Controls/ControlBox/DungeonControlBox.cs:222-229 | src/ReaLTaiizor/Controls/ControlBox/DungeonControlBox.cs:257-264 | src/ReaLTaiizor/Controls/ControlBox/DungeonControlBox.cs:291-294 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/ReaLTaiizor/Controls/ControlBox/DungeonControlBox.cs:222` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (7 lines × 10) src/ReaLTaiizor/Controls/Badge/MetroBadge.cs:505— src/ReaLTaiizor/Controls/Badge/MetroBadge.cs:505-511 | src/ReaLTaiizor/Controls/Badge/MetroBadge.cs:527-533 | src/ReaLTaiizor/Controls/Button/MetroButton.cs:206-212 | src/ReaLTaiizor/Controls/Button/MetroButton.cs:222-228 | src/ReaLTaiizor/Controls/Button/MetroDefaultButton.cs:180-186 | src/ReaLTaiizor/Controls/Button/MetroDefaultButton.cs:196-202 | src/ReaLTaiizor/Controls/Ellipse/MetroEllipse.cs:193-199 | src/ReaLTaiizor/Controls/Ellipse/MetroEllipse.cs:209-215 | src/ReaLTaiizor/Controls/Tile/MetroTile.cs:212-218 | src/ReaLTaiizor/Controls/Tile/MetroTile.cs:228-234 — before extracting anything, compare `src/ReaLTaiizor/Controls/Badge/MetroBadge.cs` and `src/ReaLTaiizor/Controls/Button/MetroButton.cs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 97 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (6 lines × 6) src/ReaLTaiizor/Forms/Container/DungeonForm.cs:344— src/ReaLTaiizor/Forms/Container/DungeonForm.cs:344-349 | src/ReaLTaiizor/Forms/Container/FormTheme.cs:323-328 | src/ReaLTaiizor/Forms/Container/ThemeForm.cs:353-358 | src/ReaLTaiizor/Util/Air.cs:414-419 | src/ReaLTaiizor/Util/Moon.cs:407-412 | src/ReaLTaiizor/Util/Space.cs:409-414 — before extracting anything, compare `src/ReaLTaiizor/Forms/Container/DungeonForm.cs` and `src/ReaLTaiizor/Forms/Container/FormTheme.cs` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 218 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (6 lines × 5) src/ReaLTaiizor/Controls/Button/CyberButton.cs:425— src/ReaLTaiizor/Controls/Button/CyberButton.cs:425-430 | src/ReaLTaiizor/Controls/CheckBox/CyberCheckBox.cs:403-408 | src/ReaLTaiizor/Controls/Progress/CyberProgressBar.cs:488-493 | src/ReaLTaiizor/Controls/RadioButton/CyberRadioButton.cs:456-461 | src/ReaLTaiizor/Controls/ScrollBar/CyberScrollBar.cs:518-523 — before extracting anything, compare `src/ReaLTaiizor/Controls/Button/CyberButton.cs` and `src/ReaLTaiizor/Controls/CheckBox/CyberCheckBox.cs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 119 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `src/ReaLTaiizor/Controls/ScrollBar/CyberScrollBar.cs:525` calls `FromArgb` and `src/ReaLTaiizor/Controls/Button/CyberButton.cs:431` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (5 lines × 11) src/ReaLTaiizor/Controls/Bubble/ChatBubbleLeft.cs:101— src/ReaLTaiizor/Controls/Bubble/ChatBubbleLeft.cs:101-106 | src/ReaLTaiizor/Controls/Bubble/ChatBubbleRight.cs:112-117 | src/ReaLTaiizor/Controls/Button/ChatButtonLeft.cs:239-243 | src/ReaLTaiizor/Controls/Button/ChatButtonRight.cs:227-231 | src/ReaLTaiizor/Controls/Button/DungeonButtonLeft.cs:241-245 | src/ReaLTaiizor/Controls/Button/DungeonButtonRight.cs:241-245 | src/ReaLTaiizor/Controls/RichTextBox/DungeonRichTextBox.cs:122-126 | src/ReaLTaiizor/Controls/RichTextBoxEdit/RichTextBoxEdit.cs:177-181 | src/ReaLTaiizor/Controls/TextBox/BigTextBox.cs:210-214 | src/ReaLTaiizor/Controls/TextBox/DungeonTextBox.cs:172-176 | src/ReaLTaiizor/Controls/TextBox/SmallTextBox.cs:187-191 — before extracting anything, compare `src/ReaLTaiizor/Controls/Bubble/ChatBubbleLeft.cs` and `src/ReaLTaiizor/Controls/Bubble/ChatBubbleRight.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 65 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `src/ReaLTaiizor/Controls/Bubble/ChatBubbleLeft.cs:111` calls `OnResize` and `src/ReaLTaiizor/Controls/Button/ChatButtonRight.cs:235` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (5 lines × 6) src/ReaLTaiizor/Controls/ControlBox/DungeonControlBox.cs:225— src/ReaLTaiizor/Controls/ControlBox/DungeonControlBox.cs:225-229 | src/ReaLTaiizor/Controls/ControlBox/DungeonControlBox.cs:237-241 | src/ReaLTaiizor/Controls/ControlBox/DungeonControlBox.cs:260-264 | src/ReaLTaiizor/Controls/ControlBox/DungeonControlBox.cs:272-276 | src/ReaLTaiizor/Controls/ControlBox/DungeonControlBox.cs:298-302 | src/ReaLTaiizor/Controls/ControlBox/DungeonControlBox.cs:305-309 — all 6 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/ReaLTaiizor/Controls/ControlBox/DungeonControlBox.cs:225` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (3–5 lines × 4) src/ReaLTaiizor/Controls/ControlBoxEdit/ControlBoxEdit.cs:140— src/ReaLTaiizor/Controls/ControlBoxEdit/ControlBoxEdit.cs:140-144 | src/ReaLTaiizor/Controls/ControlBoxEdit/ControlBoxEdit.cs:153-157 | src/ReaLTaiizor/Controls/ControlBoxEdit/ControlBoxEdit.cs:162-165 | src/ReaLTaiizor/Controls/ControlBoxEdit/ControlBoxEdit.cs:168-170 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `src/ReaLTaiizor/Controls/ControlBoxEdit/ControlBoxEdit.cs:165` calls `DrawString`, `Font`, `SolidBrush` and `src/ReaLTaiizor/Controls/ControlBoxEdit/ControlBoxEdit.cs:144` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (4–5 lines × 4) src/ReaLTaiizor/Forms/Container/DungeonForm.cs:506— src/ReaLTaiizor/Forms/Container/DungeonForm.cs:506-509 | src/ReaLTaiizor/Forms/Container/DungeonForm.cs:511-515 | src/ReaLTaiizor/Forms/Container/ThemeForm.cs:514-517 | src/ReaLTaiizor/Forms/Container/ThemeForm.cs:519-523 — before extracting anything, compare `src/ReaLTaiizor/Forms/Container/DungeonForm.cs` and `src/ReaLTaiizor/Forms/Container/ThemeForm.cs` as WHOLE FILES: this scan already matched 17 separate duplicated blocks between them, totalling at least 286 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (37 lines × 2) src/ReaLTaiizor/Controls/Panel/PoisonPanel.cs:302— src/ReaLTaiizor/Controls/Panel/PoisonPanel.cs:302-338 | src/ReaLTaiizor/Controls/TabPage/PoisonTabPage.cs:299-335 — before extracting anything, compare `src/ReaLTaiizor/Controls/Panel/PoisonPanel.cs` and `src/ReaLTaiizor/Controls/TabPage/PoisonTabPage.cs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 121 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (36 lines × 2) src/ReaLTaiizor/Child/Material/MaterialItemCollection.cs:23— src/ReaLTaiizor/Child/Material/MaterialItemCollection.cs:23-109 | src/ReaLTaiizor/Child/Metro/MetroItemCollection.cs:20-55 — before extracting anything, compare `src/ReaLTaiizor/Child/Material/MaterialItemCollection.cs` and `src/ReaLTaiizor/Child/Metro/MetroItemCollection.cs` as WHOLE FILES: 86% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/ReaLTaiizor/Child/Material/MaterialItemCollection.cs:23` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (12 lines × 16) src/ReaLTaiizor/Controls/Button/Button.cs:118— src/ReaLTaiizor/Controls/Button/Button.cs:118-129 | src/ReaLTaiizor/Controls/Button/ChatButtonLeft.cs:121-132 | src/ReaLTaiizor/Controls/Button/ChatButtonRight.cs:117-128 | src/ReaLTaiizor/Controls/Button/DungeonButtonLeft.cs:119-130 | src/ReaLTaiizor/Controls/Button/DungeonButtonRight.cs:119-130 | src/ReaLTaiizor/Controls/Button/SocialButton.cs:30-41 | src/ReaLTaiizor/Controls/Notify/NotificationBox.cs:93-104 | src/ReaLTaiizor/Forms/Container/HopeForm.cs:36-47 | src/ReaLTaiizor/Forms/Container/ThemeForm.cs:46-57 | src/ReaLTaiizor/Forms/Form/LostForm.cs:41-52 | src/ReaLTaiizor/Util/Air.cs:686-697 | src/ReaLTaiizor/Util/Air.cs:1713-1724 | src/ReaLTaiizor/Util/Moon.cs:679-690 | src/ReaLTaiizor/Util/Moon.cs:1712-1723 | src/ReaLTaiizor/Util/Space.cs:681-692 | src/ReaLTaiizor/Util/Space.cs:1710-1721 — before extracting anything, compare `src/ReaLTaiizor/Controls/Button/Button.cs` and `src/ReaLTaiizor/Controls/Button/ChatButtonLeft.cs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 90 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (16 lines × 4) src/ReaLTaiizor/Controls/Button/MaterialButton.cs:209— src/ReaLTaiizor/Controls/Button/MaterialButton.cs:209-224 | src/ReaLTaiizor/Controls/Button/MaterialFloatingActionButton.cs:179-194 | src/ReaLTaiizor/Controls/Card/MaterialCard.cs:114-130 | src/ReaLTaiizor/Controls/Panel/MaterialExpansionPanel.cs:344-359 — before extracting anything, compare `src/ReaLTaiizor/Controls/Card/MaterialCard.cs` and `src/ReaLTaiizor/Controls/Panel/MaterialExpansionPanel.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 36 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (17 lines × 21) src/ReaLTaiizor/Controls/Button/PoisonButton.cs:64— src/ReaLTaiizor/Controls/Button/PoisonButton.cs:64-80 | src/ReaLTaiizor/Controls/CheckBox/PoisonCheckBox.cs:63-79 | src/ReaLTaiizor/Controls/ComboBox/PoisonComboBox.cs:65-81 | src/ReaLTaiizor/Controls/DateTime/PoisonDateTime.cs:62-78 | src/ReaLTaiizor/Controls/Label/PoisonLabel.cs:64-80 | src/ReaLTaiizor/Controls/LinkLabel/PoisonLinkLabel.cs:68-84 | src/ReaLTaiizor/Controls/ListView/PoisonListView.cs:65-81 | src/ReaLTaiizor/Controls/Panel/PoisonPanel.cs:68-84 | src/ReaLTaiizor/Controls/Progress/PoisonProgressBar.cs:63-79 | src/ReaLTaiizor/Controls/Progress/PoisonProgressSpinner.cs:63-79 | src/ReaLTaiizor/Controls/RadioButton/PoisonRadioButton.cs:64-80 | src/ReaLTaiizor/Controls/ScrollBar/PoisonScrollBar.cs:65-81 | src/ReaLTaiizor/Controls/TabControl/PoisonTabControl.cs:72-88 | src/ReaLTaiizor/Controls/TabPage/PoisonTabPage.cs:64-80 | src/ReaLTaiizor/Controls/TextBox/PoisonTextBox.cs:63-79 | src/ReaLTaiizor/Controls/TextBox/PoisonTextBox.cs:1163-1179 | src/ReaLTaiizor/Controls/Tile/PoisonTile.cs:63-79 | src/ReaLTaiizor/Controls/Toggle/PoisonToggle.cs:64-80 | src/ReaLTaiizor/Controls/TrackBar/PoisonTrackBar.cs:61-77 | src/ReaLTaiizor/Controls/UserControl/PoisonUserControl.cs:59-75 | src/ReaLTaiizor/Forms/Form/PoisonForm.cs:841-857 — before extracting anything, compare `src/ReaLTaiizor/Controls/Button/PoisonButton.cs` and `src/ReaLTaiizor/Controls/CheckBox/PoisonCheckBox.cs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 80 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (17 lines × 22) src/ReaLTaiizor/Controls/Button/PoisonButton.cs:90— src/ReaLTaiizor/Controls/Button/PoisonButton.cs:90-106 | src/ReaLTaiizor/Controls/CheckBox/PoisonCheckBox.cs:89-105 | src/ReaLTaiizor/Controls/ComboBox/PoisonComboBox.cs:91-107 | src/ReaLTaiizor/Controls/DateTime/PoisonDateTime.cs:88-104 | src/ReaLTaiizor/Controls/Extender/PoisonStyleExtender.cs:39-55 | src/ReaLTaiizor/Controls/Label/PoisonLabel.cs:90-106 | src/ReaLTaiizor/Controls/LinkLabel/PoisonLinkLabel.cs:101-117 | src/ReaLTaiizor/Controls/ListView/PoisonListView.cs:91-107 | src/ReaLTaiizor/Controls/Panel/PoisonPanel.cs:94-110 | src/ReaLTaiizor/Controls/Progress/PoisonProgressBar.cs:89-105 | src/ReaLTaiizor/Controls/Progress/PoisonProgressSpinner.cs:89-105 | src/ReaLTaiizor/Controls/RadioButton/PoisonRadioButton.cs:90-106 | src/ReaLTaiizor/Controls/ScrollBar/PoisonScrollBar.cs:91-107 | src/ReaLTaiizor/Controls/TabControl/PoisonTabControl.cs:98-114 | src/ReaLTaiizor/Controls/TabPage/PoisonTabPage.cs:90-106 | src/ReaLTaiizor/Controls/TextBox/PoisonTextBox.cs:89-105 | src/ReaLTaiizor/Controls/TextBox/PoisonTextBox.cs:1189-1205 | src/ReaLTaiizor/Controls/Tile/PoisonTile.cs:89-105 | src/ReaLTaiizor/Controls/Toggle/PoisonToggle.cs:90-106 | src/ReaLTaiizor/Controls/TrackBar/PoisonTrackBar.cs:87-103 | src/ReaLTaiizor/Controls/UserControl/PoisonUserControl.cs:85-101 | src/ReaLTaiizor/Forms/Form/PoisonForm.cs:867-883 — before extracting anything, compare `src/ReaLTaiizor/Controls/Button/PoisonButton.cs` and `src/ReaLTaiizor/Controls/CheckBox/PoisonCheckBox.cs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 80 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (16 lines × 17) src/ReaLTaiizor/Controls/Button/PoisonButton.cs:253— src/ReaLTaiizor/Controls/Button/PoisonButton.cs:253-268 | src/ReaLTaiizor/Controls/CheckBox/PoisonCheckBox.cs:238-253 | src/ReaLTaiizor/Controls/ComboBox/PoisonComboBox.cs:408-425 | src/ReaLTaiizor/Controls/DateTime/PoisonDateTime.cs:301-316 | src/ReaLTaiizor/Controls/Label/PoisonLabel.cs:261-276 | src/ReaLTaiizor/Controls/LinkLabel/PoisonLinkLabel.cs:298-313 | src/ReaLTaiizor/Controls/Panel/PoisonPanel.cs:283-298 | src/ReaLTaiizor/Controls/Progress/PoisonProgressBar.cs:316-331 | src/ReaLTaiizor/Controls/Progress/PoisonProgressSpinner.cs:349-364 | src/ReaLTaiizor/Controls/RadioButton/PoisonRadioButton.cs:209-224 | src/ReaLTaiizor/Controls/ScrollBar/PoisonScrollBar.cs:566-581 | src/ReaLTaiizor/Controls/TabControl/PoisonTabControl.cs:235-250 | src/ReaLTaiizor/Controls/TextBox/PoisonTextBox.cs:653-668 | src/ReaLTaiizor/Controls/Tile/PoisonTile.cs:245-260 | src/ReaLTaiizor/Controls/Toggle/PoisonToggle.cs:236-251 | src/ReaLTaiizor/Controls/TrackBar/PoisonTrackBar.cs:309-324 | src/ReaLTaiizor/Controls/UserControl/PoisonUserControl.cs:163-178 — before extracting anything, compare `src/ReaLTaiizor/Controls/Button/PoisonButton.cs` and `src/ReaLTaiizor/Controls/CheckBox/PoisonCheckBox.cs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 80 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `src/ReaLTaiizor/Controls/ComboBox/PoisonComboBox.cs:429` calls `GetPreferredSize` and `src/ReaLTaiizor/Controls/Button/PoisonButton.cs:272` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (9 lines × 7) src/ReaLTaiizor/Controls/Button/PoisonButton.cs:379— src/ReaLTaiizor/Controls/Button/PoisonButton.cs:379-387 | src/ReaLTaiizor/Controls/CheckBox/PoisonCheckBox.cs:415-423 | src/ReaLTaiizor/Controls/ComboBox/PoisonComboBox.cs:611-619 | src/ReaLTaiizor/Controls/LinkLabel/PoisonLinkLabel.cs:546-554 | src/ReaLTaiizor/Controls/RadioButton/PoisonRadioButton.cs:353-361 | src/ReaLTaiizor/Controls/Tile/PoisonTile.cs:401-409 | src/ReaLTaiizor/Controls/Toggle/PoisonToggle.cs:374-382 — before extracting anything, compare `src/ReaLTaiizor/Controls/Button/PoisonButton.cs` and `src/ReaLTaiizor/Controls/CheckBox/PoisonCheckBox.cs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 80 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (7 lines × 73) src/ReaLTaiizor/Drawing/Poison/PoisonPaint.cs:36— src/ReaLTaiizor/Drawing/Poison/PoisonPaint.cs:36-42 | src/ReaLTaiizor/Drawing/Poison/PoisonPaint.cs:48-54 | src/ReaLTaiizor/Drawing/Poison/PoisonPaint.cs:58-64 | src/ReaLTaiizor/Drawing/Poison/PoisonPaint.cs:68-74 | src/ReaLTaiizor/Drawing/Poison/PoisonPaint.cs:78-84 | src/ReaLTaiizor/Drawing/Poison/PoisonPaint.cs:91-97 | src/ReaLTaiizor/Drawing/Poison/PoisonPaint.cs:101-107 | src/ReaLTaiizor/Drawing/Poison/PoisonPaint.cs:111-117 | src/ReaLTaiizor/Drawing/Poison/PoisonPaint.cs:121-127 | src/ReaLTaiizor/Drawing/Poison/PoisonPaint.cs:134-140 | src/ReaLTaiizor/Drawing/Poison/PoisonPaint.cs:144-150 | src/ReaLTaiizor/Drawing/Poison/PoisonPaint.cs:154-160 | src/ReaLTaiizor/Drawing/Poison/PoisonPaint.cs:164-170 | src/ReaLTaiizor/Drawing/Poison/PoisonPaint.cs:177-183 | src/ReaLTaiizor/Drawing/Poison/PoisonPaint.cs:187-193 | src/ReaLTaiizor/Drawing/Poison/PoisonPaint.cs:197-203 | src/ReaLTaiizor/Drawing/Poison/PoisonPaint.cs:207-213 | src/ReaLTaiizor/Drawing/Poison/PoisonPaint.cs:220-226 | src/ReaLTaiizor/Drawing/Poison/PoisonPaint.cs:230-236 | src/ReaLTaiizor/Drawing/Poison/PoisonPaint.cs:240-246 | src/ReaLTaiizor/Drawing/Poison/PoisonPaint.cs:250-256 | src/ReaLTaiizor/Drawing/Poison/PoisonPaint.cs:264-270 | src/ReaLTaiizor/Drawing/Poison/PoisonPaint.cs:276-282 | src/ReaLTaiizor/Drawing/Poison/PoisonPaint.cs:286-292 | src/ReaLTaiizor/Drawing/Poison/PoisonPaint.cs:296-302 | src/ReaLTaiizor/Drawing/Poison/PoisonPaint.cs:306-312 | src/ReaLTaiizor/Drawing/Poison/PoisonPaint.cs:321-327 | src/ReaLTaiizor/Drawing/Poison/PoisonPaint.cs:331-337 | src/ReaLTaiizor/Drawing/Poison/PoisonPaint.cs:341-347 | src/ReaLTaiizor/Drawing/Poison/PoisonPaint.cs:351-357 | src/ReaLTaiizor/Drawing/Poison/PoisonPaint.cs:364-370 | src/ReaLTaiizor/Drawing/Poison/PoisonPaint.cs:374-380 | src/ReaLTaiizor/Drawing/Poison/PoisonPaint.cs:384-390 | src/ReaLTaiizor/Drawing/Poison/PoisonPaint.cs:394-400 | src/ReaLTaiizor/Drawing/Poison/PoisonPaint.cs:410-416 | src/ReaLTaiizor/Drawing/Poison/PoisonPaint.cs:420-426 | src/ReaLTaiizor/Drawing/Poison/PoisonPaint.cs:430-436 | src/ReaLTaiizor/Drawing/Poison/PoisonPaint.cs:440-446 | src/ReaLTaiizor/Drawing/Poison/PoisonPaint.cs:453-459 | src/ReaLTaiizor/Drawing/Poison/PoisonPaint.cs:463-469 | src/ReaLTaiizor/Drawing/Poison/PoisonPaint.cs:473-479 | src/ReaLTaiizor/Drawing/Poison/PoisonPaint.cs:483-489 | src/ReaLTaiizor/Drawing/Poison/PoisonPaint.cs:499-505 | src/ReaLTaiizor/Drawing/Poison/PoisonPaint.cs:509-515 | src/ReaLTaiizor/Drawing/Poison/PoisonPaint.cs:519-525 | src/ReaLTaiizor/Drawing/Poison/PoisonPaint.cs:529-535 | src/ReaLTaiizor/Drawing/Poison/PoisonPaint.cs:546-552 | src/ReaLTaiizor/Drawing/Poison/PoisonPaint.cs:556-562 | src/ReaLTaiizor/Drawing/Poison/PoisonPaint.cs:566-572 | src/ReaLTaiizor/Drawing/Poison/PoisonPaint.cs:576-582 | src/ReaLTaiizor/Drawing/Poison/PoisonPaint.cs:587-593 | src/ReaLTaiizor/Drawing/Poison/PoisonPaint.cs:599-605 | src/ReaLTaiizor/Drawing/Poison/PoisonPaint.cs:609-615 | src/ReaLTaiizor/Drawing/Poison/PoisonPaint.cs:619-625 | src/ReaLTaiizor/Drawing/Poison/PoisonPaint.cs:629-635 | src/ReaLTaiizor/Drawing/Poison/PoisonPaint.cs:642-648 | src/ReaLTaiizor/Drawing/Poison/PoisonPaint.cs:652-658 | src/ReaLTaiizor/Drawing/Poison/PoisonPaint.cs:662-668 | src/ReaLTaiizor/Drawing/Poison/PoisonPaint.cs:672-678 | src/ReaLTaiizor/Drawing/Poison/PoisonPaint.cs:685-691 | src/ReaLTaiizor/Drawing/Poison/PoisonPaint.cs:695-701 | src/ReaLTaiizor/Drawing/Poison/PoisonPaint.cs:708-714 | src/ReaLTaiizor/Drawing/Poison/PoisonPaint.cs:718-724 | src/ReaLTaiizor/Drawing/Poison/PoisonPaint.cs:728-734 | src/ReaLTaiizor/Drawing/Poison/PoisonPaint.cs:738-744 | src/ReaLTaiizor/Drawing/Poison/PoisonPaint.cs:751-757 | src/ReaLTaiizor/Drawing/Poison/PoisonPaint.cs:761-767 | src/ReaLTaiizor/Drawing/Poison/PoisonPaint.cs:771-777 | src/ReaLTaiizor/Drawing/Poison/PoisonPaint.cs:781-787 | src/ReaLTaiizor/Drawing/Poison/PoisonPaint.cs:794-800 | src/ReaLTaiizor/Drawing/Poison/PoisonPaint.cs:804-810 | src/ReaLTaiizor/Drawing/Poison/PoisonPaint.cs:817-823 | src/ReaLTaiizor/Drawing/Poison/PoisonPaint.cs:827-833 — all 73 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (12 lines × 6) src/ReaLTaiizor/Util/Air.cs:185— src/ReaLTaiizor/Util/Air.cs:185-196 | src/ReaLTaiizor/Util/Air.cs:1558-1569 | src/ReaLTaiizor/Util/Moon.cs:182-193 | src/ReaLTaiizor/Util/Moon.cs:1557-1568 | src/ReaLTaiizor/Util/Space.cs:184-195 | src/ReaLTaiizor/Util/Space.cs:1555-1566 — before extracting anything, compare `src/ReaLTaiizor/Util/Air.cs` and `src/ReaLTaiizor/Util/Moon.cs` as WHOLE FILES: this scan already matched 40 separate duplicated blocks between them, totalling at least 661 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (17 lines × 3) src/ReaLTaiizor/Util/Air.cs:770— src/ReaLTaiizor/Util/Air.cs:770-786 | src/ReaLTaiizor/Util/Moon.cs:763-779 | src/ReaLTaiizor/Util/Space.cs:765-781 — before extracting anything, compare `src/ReaLTaiizor/Util/Air.cs` and `src/ReaLTaiizor/Util/Moon.cs` as WHOLE FILES: this scan already matched 40 separate duplicated blocks between them, totalling at least 661 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (9 lines × 6) src/ReaLTaiizor/Util/Air.cs:905— src/ReaLTaiizor/Util/Air.cs:905-913 | src/ReaLTaiizor/Util/Air.cs:1892-1900 | src/ReaLTaiizor/Util/Moon.cs:898-906 | src/ReaLTaiizor/Util/Moon.cs:1891-1899 | src/ReaLTaiizor/Util/Space.cs:900-908 | src/ReaLTaiizor/Util/Space.cs:1889-1897 — before extracting anything, compare `src/ReaLTaiizor/Util/Air.cs` and `src/ReaLTaiizor/Util/Moon.cs` as WHOLE FILES: this scan already matched 40 separate duplicated blocks between them, totalling at least 661 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (10 lines × 6) src/ReaLTaiizor/Util/Air.cs:1085— src/ReaLTaiizor/Util/Air.cs:1085-1094 | src/ReaLTaiizor/Util/Air.cs:2058-2067 | src/ReaLTaiizor/Util/Moon.cs:1079-1088 | src/ReaLTaiizor/Util/Moon.cs:2059-2068 | src/ReaLTaiizor/Util/Space.cs:1081-1090 | src/ReaLTaiizor/Util/Space.cs:2057-2066 — before extracting anything, compare `src/ReaLTaiizor/Util/Air.cs` and `src/ReaLTaiizor/Util/Moon.cs` as WHOLE FILES: this scan already matched 40 separate duplicated blocks between them, totalling at least 661 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (25 lines × 3) src/ReaLTaiizor/Util/Air.cs:1732— src/ReaLTaiizor/Util/Air.cs:1732-1756 | src/ReaLTaiizor/Util/Moon.cs:1731-1755 | src/ReaLTaiizor/Util/Space.cs:1729-1753 — before extracting anything, compare `src/ReaLTaiizor/Util/Air.cs` and `src/ReaLTaiizor/Util/Moon.cs` as WHOLE FILES: this scan already matched 40 separate duplicated blocks between them, totalling at least 661 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Unfinished stub — throws NotImplementedException src/ReaLTaiizor/Native/User32.cs:97— A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.
Unfinished stub — throws NotImplementedException src/ReaLTaiizor/Native/User32.cs:97— `AnimateWindow` is a shipped member whose whole body throws NotImplementedException — scaffolding that was never completed. Implement it or remove the dead surface.
IC1 · Incompleteness & stubs· Empty method body · ×1
Empty method body — does nothing with its inputs src/ReaLTaiizor/Util/Moon.cs:2592— `ThrowNewException` takes parameters but its body is empty — it accepts inputs and does nothing. Either implement it or remove it.
Sync-over-async (deadlock risk) through `Task.WaitAll` ready/ReaLTaiizor.Portscan/ReaLTaiizor.Portscan/Portscan.cs:391— `Task.WaitAll` blocks this thread until the tasks complete — sync-over-async: it can deadlock under a synchronization context and it parks a thread for as long as the work runs. `await Task.WhenAll(…)` instead.
Swallowed exception (caught, then discarded) src/ReaLTaiizor/Controls/DatePicker/HopeDatePicker.cs:71— `catch` does nothing with the exception it caught — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch. Log it through whatever this codebase already uses to report problems, or let it propagate; if one specific failure genuinely cannot matter, catch exactly that exception type and say why in a comment on the catch.
Minor — 147 finding(s)
P10 · Library API & versioning· Public type used only inside its own library · ×40
Public type used only inside its own library src/ReaLTaiizor/Action/Metro/MetroBadgeActionList.cs:16— `ReaLTaiizor.Action.Metro.MetroBadgeActionList` (src/ReaLTaiizor/Action/Metro/MetroBadgeActionList.cs:16) is public, and the library's own code uses it, but no other project in this repository uses it (read: `ReaLTaiizor_CR(net48)`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such.
Public type used only inside its own library src/ReaLTaiizor/Action/Metro/MetroBadgeActionList.cs:16— `ReaLTaiizor.Action.Metro.MetroBadgeActionList` (src/ReaLTaiizor/Action/Metro/MetroBadgeActionList.cs:16) is public, and the library's own code uses it, but no other project in this repository uses it (read: `ReaLTaiizor_CR(net481)`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such.
Public type used only inside its own library src/ReaLTaiizor/Action/Metro/MetroBadgeActionList.cs:16— `ReaLTaiizor.Action.Metro.MetroBadgeActionList` (src/ReaLTaiizor/Action/Metro/MetroBadgeActionList.cs:16) is public, and the library's own code uses it, but no other project in this repository uses it (read: `ReaLTaiizor_CR(netcoreapp3.1-windows)`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such.
Public type used only inside its own library src/ReaLTaiizor/Action/Metro/MetroBadgeActionList.cs:16— `ReaLTaiizor.Action.Metro.MetroBadgeActionList` (src/ReaLTaiizor/Action/Metro/MetroBadgeActionList.cs:16) is public, and the library's own code uses it, but no other project in this repository uses it (read: `ReaLTaiizor_CR(net6.0-windows)`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such.
Public type used only inside its own library src/ReaLTaiizor/Action/Metro/MetroBadgeActionList.cs:16— `ReaLTaiizor.Action.Metro.MetroBadgeActionList` (src/ReaLTaiizor/Action/Metro/MetroBadgeActionList.cs:16) is public, and the library's own code uses it, but no other project in this repository uses it (read: `ReaLTaiizor_CR(net7.0-windows)`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such.
Public type used only inside its own library src/ReaLTaiizor/Action/Metro/MetroBadgeActionList.cs:16— `ReaLTaiizor.Action.Metro.MetroBadgeActionList` (src/ReaLTaiizor/Action/Metro/MetroBadgeActionList.cs:16) is public, and the library's own code uses it, but no other project in this repository uses it (read: `ReaLTaiizor_CR(net8.0-windows)`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such.
Public type used only inside its own library src/ReaLTaiizor/Action/Metro/MetroBadgeActionList.cs:16— `ReaLTaiizor.Action.Metro.MetroBadgeActionList` (src/ReaLTaiizor/Action/Metro/MetroBadgeActionList.cs:16) is public, and the library's own code uses it, but no other project in this repository uses it (read: `ReaLTaiizor_CR(net9.0-windows)`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such.
Public type used only inside its own library src/ReaLTaiizor/Action/Metro/MetroBadgeActionList.cs:16— `ReaLTaiizor.Action.Metro.MetroBadgeActionList` (src/ReaLTaiizor/Action/Metro/MetroBadgeActionList.cs:16) is public, and the library's own code uses it, but no other project in this repository uses it (read: `ReaLTaiizor_CR(net10.0-windows)`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such.
Public type used only inside its own library src/ReaLTaiizor/Action/Metro/MetroBadgeActionList.cs:16— `ReaLTaiizor.Action.Metro.MetroBadgeActionList` (src/ReaLTaiizor/Action/Metro/MetroBadgeActionList.cs:16) is public, and the library's own code uses it, but no other project in this repository uses it (read: `ReaLTaiizor_CR(net11.0-windows)`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such.
Public type used only inside its own library src/ReaLTaiizor/Action/Metro/MetroButtonActionList.cs:16— `ReaLTaiizor.Action.Metro.MetroButtonActionList` (src/ReaLTaiizor/Action/Metro/MetroButtonActionList.cs:16) is public, and the library's own code uses it, but no other project in this repository uses it (read: `ReaLTaiizor_CR(net48)`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such.
Public type used only inside its own library src/ReaLTaiizor/Action/Metro/MetroButtonActionList.cs:16— `ReaLTaiizor.Action.Metro.MetroButtonActionList` (src/ReaLTaiizor/Action/Metro/MetroButtonActionList.cs:16) is public, and the library's own code uses it, but no other project in this repository uses it (read: `ReaLTaiizor_CR(net481)`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such.
Public type used only inside its own library src/ReaLTaiizor/Action/Metro/MetroButtonActionList.cs:16— `ReaLTaiizor.Action.Metro.MetroButtonActionList` (src/ReaLTaiizor/Action/Metro/MetroButtonActionList.cs:16) is public, and the library's own code uses it, but no other project in this repository uses it (read: `ReaLTaiizor_CR(netcoreapp3.1-windows)`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such.
Public type used only inside its own library src/ReaLTaiizor/Action/Metro/MetroButtonActionList.cs:16— `ReaLTaiizor.Action.Metro.MetroButtonActionList` (src/ReaLTaiizor/Action/Metro/MetroButtonActionList.cs:16) is public, and the library's own code uses it, but no other project in this repository uses it (read: `ReaLTaiizor_CR(net6.0-windows)`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such.
Public type used only inside its own library src/ReaLTaiizor/Action/Metro/MetroButtonActionList.cs:16— `ReaLTaiizor.Action.Metro.MetroButtonActionList` (src/ReaLTaiizor/Action/Metro/MetroButtonActionList.cs:16) is public, and the library's own code uses it, but no other project in this repository uses it (read: `ReaLTaiizor_CR(net7.0-windows)`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such.
Public type used only inside its own library src/ReaLTaiizor/Action/Metro/MetroButtonActionList.cs:16— `ReaLTaiizor.Action.Metro.MetroButtonActionList` (src/ReaLTaiizor/Action/Metro/MetroButtonActionList.cs:16) is public, and the library's own code uses it, but no other project in this repository uses it (read: `ReaLTaiizor_CR(net8.0-windows)`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such.
Public type used only inside its own library src/ReaLTaiizor/Action/Metro/MetroButtonActionList.cs:16— `ReaLTaiizor.Action.Metro.MetroButtonActionList` (src/ReaLTaiizor/Action/Metro/MetroButtonActionList.cs:16) is public, and the library's own code uses it, but no other project in this repository uses it (read: `ReaLTaiizor_CR(net9.0-windows)`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such.
Public type used only inside its own library src/ReaLTaiizor/Action/Metro/MetroButtonActionList.cs:16— `ReaLTaiizor.Action.Metro.MetroButtonActionList` (src/ReaLTaiizor/Action/Metro/MetroButtonActionList.cs:16) is public, and the library's own code uses it, but no other project in this repository uses it (read: `ReaLTaiizor_CR(net10.0-windows)`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such.
Public type used only inside its own library src/ReaLTaiizor/Action/Metro/MetroButtonActionList.cs:16— `ReaLTaiizor.Action.Metro.MetroButtonActionList` (src/ReaLTaiizor/Action/Metro/MetroButtonActionList.cs:16) is public, and the library's own code uses it, but no other project in this repository uses it (read: `ReaLTaiizor_CR(net11.0-windows)`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such.
Public type used only inside its own library src/ReaLTaiizor/Action/Metro/MetroDefaultButtonActionList.cs:16— `ReaLTaiizor.Action.Metro.MetroDefaultButtonActionList` (src/ReaLTaiizor/Action/Metro/MetroDefaultButtonActionList.cs:16) is public, and the library's own code uses it, but no other project in this repository uses it (read: `ReaLTaiizor_CR(net48)`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such.
Public type used only inside its own library src/ReaLTaiizor/Action/Metro/MetroDefaultButtonActionList.cs:16— `ReaLTaiizor.Action.Metro.MetroDefaultButtonActionList` (src/ReaLTaiizor/Action/Metro/MetroDefaultButtonActionList.cs:16) is public, and the library's own code uses it, but no other project in this repository uses it (read: `ReaLTaiizor_CR(net481)`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such.
Public type used only inside its own library src/ReaLTaiizor/Action/Metro/MetroDefaultButtonActionList.cs:16— `ReaLTaiizor.Action.Metro.MetroDefaultButtonActionList` (src/ReaLTaiizor/Action/Metro/MetroDefaultButtonActionList.cs:16) is public, and the library's own code uses it, but no other project in this repository uses it (read: `ReaLTaiizor_CR(netcoreapp3.1-windows)`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such.
Public type used only inside its own library src/ReaLTaiizor/Action/Metro/MetroDefaultButtonActionList.cs:16— `ReaLTaiizor.Action.Metro.MetroDefaultButtonActionList` (src/ReaLTaiizor/Action/Metro/MetroDefaultButtonActionList.cs:16) is public, and the library's own code uses it, but no other project in this repository uses it (read: `ReaLTaiizor_CR(net6.0-windows)`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such.
Public type used only inside its own library src/ReaLTaiizor/Action/Metro/MetroDefaultButtonActionList.cs:16— `ReaLTaiizor.Action.Metro.MetroDefaultButtonActionList` (src/ReaLTaiizor/Action/Metro/MetroDefaultButtonActionList.cs:16) is public, and the library's own code uses it, but no other project in this repository uses it (read: `ReaLTaiizor_CR(net7.0-windows)`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such.
Public type used only inside its own library src/ReaLTaiizor/Action/Metro/MetroDefaultButtonActionList.cs:16— `ReaLTaiizor.Action.Metro.MetroDefaultButtonActionList` (src/ReaLTaiizor/Action/Metro/MetroDefaultButtonActionList.cs:16) is public, and the library's own code uses it, but no other project in this repository uses it (read: `ReaLTaiizor_CR(net8.0-windows)`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such.
Public type used only inside its own library src/ReaLTaiizor/Action/Metro/MetroDefaultButtonActionList.cs:16— `ReaLTaiizor.Action.Metro.MetroDefaultButtonActionList` (src/ReaLTaiizor/Action/Metro/MetroDefaultButtonActionList.cs:16) is public, and the library's own code uses it, but no other project in this repository uses it (read: `ReaLTaiizor_CR(net9.0-windows)`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such.
Duplicated predicate src/ReaLTaiizor/Controls/RichTextBox/HopeRichTextBox.cs:150— `!Controls.Contains(_baseTextBox) && !DesignMode` appears character-identically in 3 files — src/ReaLTaiizor/Controls/RichTextBox/HopeRichTextBox.cs, src/ReaLTaiizor/Controls/TextBox/HopeTextBox.cs, src/ReaLTaiizor/Controls/TextBox/MaterialSingleTextBox.cs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate src/ReaLTaiizor/Controls/TextBox/MaterialMaskedTextBox.cs:981— `!Controls.Contains(baseTextBox) && !DesignMode` appears character-identically in 3 files — src/ReaLTaiizor/Controls/TextBox/MaterialMaskedTextBox.cs, src/ReaLTaiizor/Controls/TextBoxEdit/MaterialMultiLineTextBoxEdit.cs, src/ReaLTaiizor/Controls/TextBoxEdit/MaterialTextBoxEdit.cs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate src/ReaLTaiizor/Util/Air.cs:492— `!IsHandleCreated && ControlMode && value == Color.Transparent` appears character-identically in 3 files — src/ReaLTaiizor/Util/Air.cs, src/ReaLTaiizor/Util/Moon.cs, src/ReaLTaiizor/Util/Space.cs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate src/ReaLTaiizor/Util/Air.cs:1680— `!IsHandleCreated && value == Color.Transparent` appears character-identically in 3 files — src/ReaLTaiizor/Util/Air.cs, src/ReaLTaiizor/Util/Moon.cs, src/ReaLTaiizor/Util/Space.cs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate src/ReaLTaiizor/Util/Air.cs:2578— `!Success && !(Marshal.GetLastWin32Error() == 997)` appears character-identically in 3 files — src/ReaLTaiizor/Util/Air.cs, src/ReaLTaiizor/Util/Moon.cs, src/ReaLTaiizor/Util/Space.cs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate src/ReaLTaiizor/Controls/TextBox/MaterialMaskedTextBox.cs:1164— `!_errorState || (!userTextPresent && !isFocused)` appears character-identically in 2 files — src/ReaLTaiizor/Controls/TextBox/MaterialMaskedTextBox.cs, src/ReaLTaiizor/Controls/TextBoxEdit/MaterialTextBoxEdit.cs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate src/ReaLTaiizor/Controls/ScrollBar/MaterialScrollBar.cs:67— `!isFirstScrollEventHorizontal && type == ScrollEventType.EndScroll` appears character-identically in 2 files — src/ReaLTaiizor/Controls/ScrollBar/MaterialScrollBar.cs, src/ReaLTaiizor/Controls/ScrollBar/PoisonScrollBar.cs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate src/ReaLTaiizor/Controls/TextBox/MaterialMaskedTextBox.cs:1637— `!string.IsNullOrEmpty(SelectedText) && !ReadOnly` appears character-identically in 4 files — src/ReaLTaiizor/Controls/TextBox/MaterialMaskedTextBox.cs, src/ReaLTaiizor/Controls/TextBox/MaterialTextBox.cs, src/ReaLTaiizor/Controls/TextBoxEdit/MaterialMultiLineTextBoxEdit.cs, src/ReaLTaiizor/Controls/TextBoxEdit/MaterialTextBoxEdit.cs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate src/ReaLTaiizor/Forms/Container/DungeonForm.cs:169— `(IsParentForm && ParentForm.WindowState == FormWindowState.Maximized) || ControlMode` appears character-identically in 6 files — src/ReaLTaiizor/Forms/Container/DungeonForm.cs, src/ReaLTaiizor/Forms/Container/FormTheme.cs, src/ReaLTaiizor/Forms/Container/ThemeForm.cs, src/ReaLTaiizor/Util/Air.cs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate src/ReaLTaiizor/Controls/Button/CyberButton.cs:608— `Background_WidthPen != 0 && BackgroundPen == true` appears character-identically in 9 files — src/ReaLTaiizor/Controls/Button/CyberButton.cs, src/ReaLTaiizor/Controls/CheckBox/CyberCheckBox.cs, src/ReaLTaiizor/Controls/GroupBox/CyberGroupBox.cs, src/ReaLTaiizor/Controls/Progress/CyberProgressBar.cs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate src/ReaLTaiizor/Controls/Button/PoisonButton.cs:64— `DesignMode || field != ColorStyle.Default` appears character-identically in 22 files — src/ReaLTaiizor/Controls/Button/PoisonButton.cs, src/ReaLTaiizor/Controls/CheckBox/PoisonCheckBox.cs, src/ReaLTaiizor/Controls/ComboBox/PoisonComboBox.cs, src/ReaLTaiizor/Controls/DateTime/PoisonDateTime.cs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate src/ReaLTaiizor/Controls/Button/PoisonButton.cs:90— `DesignMode || field != ThemeStyle.Default` appears character-identically in 23 files — src/ReaLTaiizor/Controls/Button/PoisonButton.cs, src/ReaLTaiizor/Controls/CheckBox/PoisonCheckBox.cs, src/ReaLTaiizor/Controls/ComboBox/PoisonComboBox.cs, src/ReaLTaiizor/Controls/DateTime/PoisonDateTime.cs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate src/ReaLTaiizor/Controls/Button/PoisonButton.cs:42— `GetStyle(ControlStyles.UserPaint) && CustomPaint != null` appears character-identically in 22 files — src/ReaLTaiizor/Controls/Button/PoisonButton.cs, src/ReaLTaiizor/Controls/CheckBox/PoisonCheckBox.cs, src/ReaLTaiizor/Controls/ComboBox/PoisonComboBox.cs, src/ReaLTaiizor/Controls/DateTime/PoisonDateTime.cs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate src/ReaLTaiizor/Controls/Button/PoisonButton.cs:32— `GetStyle(ControlStyles.UserPaint) && CustomPaintBackground != null` appears character-identically in 22 files — src/ReaLTaiizor/Controls/Button/PoisonButton.cs, src/ReaLTaiizor/Controls/CheckBox/PoisonCheckBox.cs, src/ReaLTaiizor/Controls/ComboBox/PoisonComboBox.cs, src/ReaLTaiizor/Controls/DateTime/PoisonDateTime.cs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate src/ReaLTaiizor/Controls/Button/PoisonButton.cs:52— `GetStyle(ControlStyles.UserPaint) && CustomPaintForeground != null` appears character-identically in 22 files — src/ReaLTaiizor/Controls/Button/PoisonButton.cs, src/ReaLTaiizor/Controls/CheckBox/PoisonCheckBox.cs, src/ReaLTaiizor/Controls/ComboBox/PoisonComboBox.cs, src/ReaLTaiizor/Controls/DateTime/PoisonDateTime.cs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate src/ReaLTaiizor/Controls/Button/MaterialButton.cs:408— `Icon.Width > (int)(ICON_SIZE * ScaleFactor) || Icon.Height > (int)(ICON_SIZE * ScaleFactor)` appears character-identically in 4 files — src/ReaLTaiizor/Controls/Button/MaterialButton.cs, src/ReaLTaiizor/Controls/TextBox/MaterialMaskedTextBox.cs, src/ReaLTaiizor/Controls/TextBox/MaterialTextBox.cs, src/ReaLTaiizor/Controls/TextBoxEdit/MaterialTextBoxEdit.cs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate src/ReaLTaiizor/Forms/Container/DungeonForm.cs:195— `IsParentForm && ParentForm.WindowState == FormWindowState.Maximized` appears character-identically in 6 files — src/ReaLTaiizor/Forms/Container/DungeonForm.cs, src/ReaLTaiizor/Forms/Container/FormTheme.cs, src/ReaLTaiizor/Forms/Container/ThemeForm.cs, src/ReaLTaiizor/Util/Air.cs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate src/ReaLTaiizor/Controls/TextBox/MaterialMaskedTextBox.cs:1241— `LeadingIcon != null && _leadingIconBounds.Contains(e.Location)` appears character-identically in 3 files — src/ReaLTaiizor/Controls/TextBox/MaterialMaskedTextBox.cs, src/ReaLTaiizor/Controls/TextBox/MaterialTextBox.cs, src/ReaLTaiizor/Controls/TextBoxEdit/MaterialTextBoxEdit.cs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate src/ReaLTaiizor/Controls/TextBox/MaterialMaskedTextBox.cs:1219— `LeadingIcon != null && _leadingIconBounds.Contains(e.Location) && LeadingIconClick != null` appears character-identically in 3 files — src/ReaLTaiizor/Controls/TextBox/MaterialMaskedTextBox.cs, src/ReaLTaiizor/Controls/TextBox/MaterialTextBox.cs, src/ReaLTaiizor/Controls/TextBoxEdit/MaterialTextBoxEdit.cs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate src/ReaLTaiizor/Controls/TextBox/MaterialMaskedTextBox.cs:1049— `MouseState == MaterialMouseState.HOVER && (!ReadOnly || (ReadOnly && !AnimateReadOnly))` appears character-identically in 4 files — src/ReaLTaiizor/Controls/TextBox/MaterialMaskedTextBox.cs, src/ReaLTaiizor/Controls/TextBox/MaterialTextBox.cs, src/ReaLTaiizor/Controls/TextBoxEdit/MaterialMultiLineTextBoxEdit.cs, src/ReaLTaiizor/Controls/TextBoxEdit/MaterialTextBoxEdit.cs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate src/ReaLTaiizor/Controls/ListView/CrownListView.cs:194— `MultiSelect && ModifierKeys == Keys.Control` appears character-identically in 2 files — src/ReaLTaiizor/Controls/ListView/CrownListView.cs, src/ReaLTaiizor/Controls/TreeView/CrownTreeView.cs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate src/ReaLTaiizor/Controls/ListView/CrownListView.cs:190— `MultiSelect && ModifierKeys == Keys.Shift` appears character-identically in 2 files — src/ReaLTaiizor/Controls/ListView/CrownListView.cs, src/ReaLTaiizor/Controls/TreeView/CrownTreeView.cs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate src/ReaLTaiizor/Controls/Button/MaterialButton.cs:508— `Parent.Parent == null || (Parent.Parent != null && Parent.Parent.BackColor == Color.Transparent)` appears character-identically in 17 files — src/ReaLTaiizor/Controls/Button/MaterialButton.cs, src/ReaLTaiizor/Controls/Button/MaterialFloatingActionButton.cs, src/ReaLTaiizor/Controls/Card/MaterialCard.cs, src/ReaLTaiizor/Controls/CheckBox/MaterialCheckBox.cs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate src/ReaLTaiizor/Controls/TextBox/MaterialMaskedTextBox.cs:1547— `PrefixSuffix == PrefixSuffixTypes.Prefix && PrefixSuffixText != null && PrefixSuffixText.Length > 0` appears character-identically in 2 files — src/ReaLTaiizor/Controls/TextBox/MaterialMaskedTextBox.cs, src/ReaLTaiizor/Controls/TextBoxEdit/MaterialTextBoxEdit.cs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate src/ReaLTaiizor/Controls/TextBox/MaterialMaskedTextBox.cs:1118— `PrefixSuffix == PrefixSuffixTypes.Prefix && PrefixSuffixText != null && PrefixSuffixText.Length > 0 && (isFocused || userTextPresent || !has…` appears character-identically in 2 files — src/ReaLTaiizor/Controls/TextBox/MaterialMaskedTextBox.cs, src/ReaLTaiizor/Controls/TextBoxEdit/MaterialTextBoxEdit.cs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
redundant comment src/ReaLTaiizor/Controls/Button/PoisonDropDownButton.cs:588— "Spacing between the Text and the Image" repeats the code it sits on: 3 of its 3 words (spacing, text, image) are already in `int element_spacing = 0; // Spacing between the Text and the Image`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment src/ReaLTaiizor/Controls/Button/PoisonDropDownButton.cs:646— "Spacing between the Text and the Image" repeats the code it sits on: 3 of its 3 words (spacing, text, image) are already in `int element_spacing = 0; // Spacing between the Text and the Image`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment src/ReaLTaiizor/Controls/Button/SpaceButton.cs:58— "Set up Color for the Text" repeats the code it sits on: 3 of its 3 words (set, color, text) are already in `B1 = new(GetColor("Text")); // Set up Color for the Text`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment src/ReaLTaiizor/Controls/Close/SpaceClose.cs:84— "Set up Color for the Text" repeats the code it sits on: 3 of its 3 words (set, color, text) are already in `B1 = new(GetColor("Text")); // Set up Color for the Text`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment src/ReaLTaiizor/Controls/GroupBox/GroupBox.cs:109— "Draw the border of the title box" repeats the code it sits on: 4 of its 4 words (draw, border, title, box) are already in `G.DrawPath(new(BorderColorH), RoundRectangle.RoundRect(TitleBox, 4));`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment src/ReaLTaiizor/Controls/Label/SpaceBorderLabel.cs:45— "Set up Color for the Text" repeats the code it sits on: 3 of its 3 words (set, color, text) are already in `B1 = new(GetColor("Text")); // Set up Color for the Text`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment src/ReaLTaiizor/Controls/Label/SpaceLabel.cs:27— "Text Color for Label" repeats the code it sits on: 3 of its 3 words (text, color, label) are already in `SetColor("Text", 254, 254, 254); // Text Color for Label`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment src/ReaLTaiizor/Controls/Label/SpaceLabel.cs:37— "Get the Background Color" repeats the code it sits on: 3 of its 3 words (get, background, color) are already in `C1 = GetColor("Background"); // Get the Background Color`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment src/ReaLTaiizor/Controls/Label/SpaceLabel.cs:38— "Set up Color for the Text" repeats the code it sits on: 3 of its 3 words (set, color, text) are already in `B1 = new(GetColor("Text")); // Set up Color for the Text`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment src/ReaLTaiizor/Controls/Maximize/SpaceMaximize.cs:95— "Set up Color for the Text" repeats the code it sits on: 3 of its 3 words (set, color, text) are already in `B1 = new(GetColor("Text")); // Set up Color for the Text`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment src/ReaLTaiizor/Controls/Minimize/SpaceMinimize.cs:86— "Set up Color for the Text" repeats the code it sits on: 3 of its 3 words (set, color, text) are already in `B1 = new(GetColor("Text")); // Set up Color for the Text`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment src/ReaLTaiizor/Controls/Progress/DungeonProgressBar.cs:227— "Draw value as a string" repeats the code it sits on: 3 of its 3 words (draw, value, string) are already in `string DrawString = Convert.ToString(Convert.ToInt32(Value)) + "%";`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment src/ReaLTaiizor/Controls/Quest/SpaceQuest.cs:84— "Set up Color for the Text" repeats the code it sits on: 3 of its 3 words (set, color, text) are already in `B1 = new(GetColor("Text")); // Set up Color for the Text`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment src/ReaLTaiizor/Controls/RadioButton/DungeonRadioButton.cs:130— "Draw ellipse border" repeats the code it sits on: 3 of its 3 words (draw, ellipse, border) are already in `MyDrawer.DrawEllipse(new(BorderColor), new Rectangle(new Point(0, 0), new Size(14, 14)));`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment src/ReaLTaiizor/Controls/TabPage/TabPage.cs:267— "Draw tab text" repeats the code it sits on: 3 of its 3 words (draw, tab, text) are already in `_Graphics.DrawString(TabPages[TabIndex].Text, new Font(Font.FontFamily, Font.Size, Font.Style), new SolidBrush(ActiveFor …`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment src/ReaLTaiizor/Controls/TrackBar/DungeonTrackBar.cs:277— "Draw pipe border" repeats the code it sits on: 3 of its 3 words (draw, pipe, border) are already in `G.DrawPath(new(BorderColor), PipeBorder); // Draw pipe border`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment src/ReaLTaiizor/Controls/TrackBar/TrackBar.cs:232— "Draw pipe border" repeats the code it sits on: 3 of its 3 words (draw, pipe, border) are already in `G.DrawRectangle(new(Color.FromArgb(124, 131, 137)), PipeBorder); // Draw pipe border`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment src/ReaLTaiizor/Forms/Container/SpaceForm.cs:45— "Get the Background Color" repeats the code it sits on: 3 of its 3 words (get, background, color) are already in `C1 = GetColor("Background"); // Get the Background Color`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment src/ReaLTaiizor/Forms/Container/SpaceForm.cs:46— "Get the Dark Gradient" repeats the code it sits on: 3 of its 3 words (get, dark, gradient) are already in `C2 = GetColor("DarkGradient"); // Get the Dark Gradient`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment src/ReaLTaiizor/Forms/Form/MaterialFlexibleForm.cs:663— "Set the default button..." repeats the code it sits on: 3 of its 3 words (set, default, button) are already in `buttonIndexToFocus = this.defaultButton switch`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment src/ReaLTaiizor/Forms/Form/MaterialFlexibleForm.cs:727— "Set text in clipboard" repeats the code it sits on: 3 of its 3 words (set, text, clipboard) are already in `Clipboard.SetText(textForClipboard);`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment src/ReaLTaiizor/Util/Poison.cs:76— "Initialize the CaseInsensitiveComparer object" repeats the code it sits on: 4 of its 5 words (case, insensitive, comparer, object) are already in `ObjectCompare = new CaseInsensitiveComparer();`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
Commented-out code ready/ReaLTaiizor.MAChanger/ReaLTaiizor.MAChanger/MAChanger.cs:67— A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
Commented-out code ready/ReaLTaiizor.Nerator/ReaLTaiizor.Nerator/CS/Generator.cs:47— A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
Commented-out code ready/ReaLTaiizor.Nerator/ReaLTaiizor.Nerator/CS/Generator.cs:52— 14 consecutive lines of code sit inside a `/* … */` block — a block of code switched off rather than removed, which rots and confuses. Delete it (version control remembers).
Commented-out code ready/ReaLTaiizor.Nerator/ReaLTaiizor.Nerator/CS/Generator.cs:73— 4 consecutive lines of code sit inside a `/* … */` block — a block of code switched off rather than removed, which rots and confuses. Delete it (version control remembers).
Commented-out code ready/ReaLTaiizor.Nerator/ReaLTaiizor.Nerator/CS/Generator.cs:80— 4 consecutive lines of code sit inside a `/* … */` block — a block of code switched off rather than removed, which rots and confuses. Delete it (version control remembers).
Commented-out code ready/ReaLTaiizor.Nerator/ReaLTaiizor.Nerator/CS/Strength.cs:245— A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
Commented-out code ready/ReaLTaiizor.Portscan/ReaLTaiizor.Portscan/Portscan.cs:375— 15 consecutive lines of code sit inside a `/* … */` block — a block of code switched off rather than removed, which rots and confuses. Delete it (version control remembers).
Commented-out code src/ReaLTaiizor/Child/Crown/CrownListItem.cs:54— A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
Commented-out code src/ReaLTaiizor/Child/Poison/PoisonMessageBoxControl.cs:232— A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
Commented-out code src/ReaLTaiizor/Child/Poison/PoisonMessageBoxControl.cs:233— A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
Commented-out code src/ReaLTaiizor/Child/Poison/PoisonMessageBoxControl.cs:234— A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
Commented-out code src/ReaLTaiizor/Child/Poison/PoisonMessageBoxControl.cs:235— A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
Commented-out code src/ReaLTaiizor/Child/Poison/PoisonMessageBoxControl.cs:268— A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
Commented-out code src/ReaLTaiizor/Child/Poison/PoisonMessageBoxControl.cs:269— A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
Commented-out code src/ReaLTaiizor/Child/Poison/PoisonMessageBoxControl.cs:273— A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
Commented-out code src/ReaLTaiizor/Child/Poison/PoisonMessageBoxControl.cs:274— A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
Silent fallback default in catch src/ReaLTaiizor/Extension/Material.cs:24— `HasProperty` swallows `AmbiguousMatchException` into `return true;` — a data error becomes a silent behavior change with no trail. Log the failure or let validation throw.
Silent fallback default in catch src/ReaLTaiizor/Extension/Material.cs:116— `GetIntFromHexColor` swallows every exception into `return 0x00;` — a data error becomes a silent behavior change with no trail. Log the failure or let validation throw.
Silent fallback default in catch src/ReaLTaiizor/Forms/Container/HopeForm.cs:99— `MinimizeBox` swallows every exception into `return true;` — a data error becomes a silent behavior change with no trail. Log the failure or let validation throw.
Silent fallback default in catch src/ReaLTaiizor/Forms/Container/HopeForm.cs:126— `MaximizeBox` swallows every exception into `return true;` — a data error becomes a silent behavior change with no trail. Log the failure or let validation throw.
Silent fallback default in catch src/ReaLTaiizor/Forms/Container/HopeForm.cs:153— `ControlBox` swallows every exception into `return true;` — a data error becomes a silent behavior change with no trail. Log the failure or let validation throw.
Silent fallback default in catch src/ReaLTaiizor/Manager/MetroStyleManager.cs:501— `GetValues` swallows every exception into `return [];` — a data error becomes a silent behavior change with no trail. Log the failure or let validation throw.
Silent fallback default in catch REDACTED:59— `GMAC` swallows every exception into `return null;` — a data error becomes a silent behavior change with no trail. Log the failure or let validation throw.
Silent fallback default in catch REDACTED:77— `RegistryMAC` swallows every exception into `return null;` — a data error becomes a silent behavior change with no trail. Log the failure or let validation throw.
Silent fallback default in catch ready/ReaLTaiizor.Nerator/ReaLTaiizor.Nerator/CS/History.cs:111— `Remove` swallows every exception into `return false;` — a data error becomes a silent behavior change with no trail. Log the failure or let validation throw.
Pass-through layer src/ReaLTaiizor/Controls/RichTextBox/HopeRichTextBox.cs:18— HopeRichTextBox: all 4 public methods forward their arguments unchanged to _baseTextBox and add no behaviour — an extra hop (and usually an extra interface) to trace through. Call _baseTextBox directly, or give the layer a job.
Pass-through layer src/ReaLTaiizor/Controls/TextBox/HopeTextBox.cs:18— HopeTextBox: all 4 public methods forward their arguments unchanged to _baseTextBox and add no behaviour — an extra hop (and usually an extra interface) to trace through. Call _baseTextBox directly, or give the layer a job.
Pass-through layer src/ReaLTaiizor/Controls/TextBox/MaterialSingleTextBox.cs:19— MaterialSingleTextBox: all 4 public methods forward their arguments unchanged to _baseTextBox and add no behaviour — an extra hop (and usually an extra interface) to trace through. Call _baseTextBox directly, or give the layer a job.
Silent fallback default on unknown code ready/ReaLTaiizor.Nerator/ReaLTaiizor.Nerator/CS/Character.cs:18— `GetAlphabeticMode` maps every unrecognised code to `AlphabeticType.BS`, one of the real values, with no log or throw — a malformed or new code silently reads as a known one. Throw on the unknown code, or log it. If that member is the correct answer for any other code, say so in a comment on the member and the row stops firing.
Silent fallback default on unknown code ready/ReaLTaiizor.Nerator/ReaLTaiizor.Nerator/CS/Character.cs:45— `GetSpecialMode` maps every unrecognised code to `SpecialType.NS`, one of the real values, with no log or throw — a malformed or new code silently reads as a known one. Throw on the unknown code, or log it. If that member is the correct answer for any other code, say so in a comment on the member and the row stops firing.
Silent fallback default on unknown code ready/ReaLTaiizor.Nerator/ReaLTaiizor.Nerator/CS/Window.cs:21— `GetWindowMode` maps every unrecognised code to `WindowType.LIGHT`, one of the real values, with no log or throw — a malformed or new code silently reads as a known one. Throw on the unknown code, or log it. If that member is the correct answer for any other code, say so in a comment on the member and the row stops firing.
No ADRs found src/ReaLTaiizor/ReaLTaiizor.csproj:17— No ADRs found. No recognised ADR directory (`docs/adr/`, `docs/decisions/`, `adr/`, `docs/rfcs/`, an `ADR0001/` folder, or their siblings) exists anywhere in this tree. What was searched, so you can tell an empty log from a search that missed one: every directory under the tree (build output, dependencies and VCS metadata excepted), for a document that is either any non-index page inside a recognised ADR directory, whatever its name and however deeply nested (`docs/adr/use-postgres.md`, `docs/adr/2024/0001-x.md`); or a file anywhere whose name is ADR-shaped (`0001-use-postgres.md`, `adr-012-caching.md`); or, when neither turned anything up, a document carrying the decision-record signature (an "Architecture Decision Record" heading, or Status / Context / Decision / Consequences as section headings). A decision log that clears none of these — unnumbered files outside any recognised directory, without those headings — is not seen by this check and this row is then wrong. If that is your case, say so rather than renaming anything; otherwise, consider recording architectural decisions in `docs/adr/`. ADRs are expected here because `src/ReaLTaiizor/ReaLTaiizor.csproj` makes this repository a deployable product (line 17).
D26 · Project Cohesion· Projects may be oversized for their cohesion · ×1
Projects may be oversized for their cohesion src/ReaLTaiizor/ReaLTaiizor.csproj:1— `ReaLTaiizor(net48)` overshoots its size bounds (117096 LoC, 821 public types across 37 namespaces). 1 of 26 project(s) overshoot their size bounds, lowering Project Cohesion to 9.2/10. Size alone is no reason to split a project: where its type references show a separable part, a Split row names it.
No ADRs — No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
M2 · Architecture documentation· No architecture diagram/doc · ×1
No architecture diagram/doc — No C4/Structurizr/PlantUML/Mermaid/Graphviz/D2 diagram, no drawn diagram named for the architecture, no file named `architecture` or `design` in any markup this check reads, and nothing in the README, docs or contributor guides that announces the shape — no `## Architecture` heading, no "architecture overview"/"high-level design" phrasing, no "the architecture is …" introduction, no guided code tour. A shape laid out in prose that never names itself as the architecture is not visible to this check, and neither is one kept outside the repository, so this row reports the absence of a re-findable shape document — not evidence that nobody wrote the shape down.
P3 · Security & performance tooling· Dependabot does not watch github-actions · ×1
Dependabot does not watch github-actions REDACTED:2— `REDACTED` schedules updates, but no `package-ecosystem` entry covers `github-actions`, which this tree depends on — so those dependencies get no update pull requests and no advisory pressure, however complete the dep-scan credit looks. Add the missing entry to the `updates:` list.
No changelog — No CHANGELOG/HISTORY/RELEASES file — what shipped when isn't easy to reconstruct for support or audit. (Versioning/tagging makes releases traceable, but a changelog records the what.)
doc comments repeat the names src/ReaLTaiizor/Controls/Button/MaterialButton.cs:65— 3 of 33 documented parameters and 8 of 530 summaries in `ReaLTaiizor(net48)` only repeat the member or parameter name (e.g. "Gets or sets the Depth" for `Depth`). 46 documentation tag(s) are empty. Delete the restating tags, or add what the name does not say.
Appendix B — Reproduction & audit trail
Every external tool invocation behind a deep-scan dimension — the tool, its captured version, the exact command, how many findings it yielded, and a link to the retained raw output. To reproduce any finding: check out the same commit and run the command shown (repo-relative — never an absolute scratch path). The complete raw scanner output is retained verbatim under artifacts/raw/ (indexed in artifacts/raw/index.json); per-invocation exit codes and wall-clock durations are in sidecar.json — kept out of this table so the rendered report stays byte-identical across runs of the same commit.
trivy: not applicable — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.
semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. semgrep could not parse 1 file(s) — `src/ReaLTaiizor/Animate/Poison/DelayedCall.cs` — so the PII/GDPR sweep did not cover them at all.
disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
Run 01a1e83b-3ea7-7bdc-9bfd-cf58b9990ba0 · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.
Issues: 104 · Warnings: 1034 · Recommendations: 147 · Info: 1 — Appendix A · all findings · full markdown report.
Generated by the Canine Code Analyzer: deterministic code-health analysis. 17-11-2026 @ 06:39 UTC.
Downloadable artifacts
Machine-readable and reproducible from this commit + frozen rubric — drop them straight into a contract appendix, a CRA dossier, or a downstream SCA / VEX tool.