TASEmulators / TASEmulators/BizHawk
Dump Status Report is somehow the Log Window?
Open
Nobody has claimed this yet.
App: EmuHawk
Repro: Affects 2.6.1
Repro: Affects 2.8
Tool: Log Window
- Dominant language
- C#
- Stars
- 2.8k
- Forks
- 468
- PR merge metrics
- No merged PRs in 30d
Description
When you open the Dump Status Report, the console stops receiving C# console calls (when in debug mode), and in all modes the Dump Status Report starts receiving those messages? I guess it's a repurposed copy of the log window but something isn't working right and the signals are crossed
edit: also affects Linux --yoshi
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the Dump Status Report behavior with C# console calls in debug and non-debug modes, including on Linux. Trace how messages are routed between the console and log window; done means each window receives only its intended messages in all tested modes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- desktop
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100