OpenTM v0.0.3

Fixed

• The Communications Processor tab did not appear when selecting a DECR target on a fresh launch. It only showed up after deselecting the target and selecting it again, because the tab's visibility was decided from the session's record before that record had been filled in. (#3)
• Changing Reset Mode had no effect on a connected target. The new mode was saved but never handed to the live session, so a reset booted whichever mode had been set previously and appeared to alternate between the two. Edits made in Target Properties, including MAC, timeouts and File Server Dir, were dropped the same way and now also reach the session. (#4)

Added

• Load and Run Executable accepts EBOOT.BIN, in both the file dialog filter and the placeholder text. Thanks to @ZephyrCodesStuff. (#2)
• An issue template and a reporting guide, covering which details make a report diagnosable, where to find the wire log, and how to filter a packet capture so it does not carry your whole network.

OpenTM v0.0.2

Fixed

• Editing a target's port or type after it had been connected once had no effect, the session server kept the old address and refused to move it, so the app kept dialling the original port (Connection refused). Reopening a target now reconnects it at its new address. #1
• After a failed target.open, the app connected anyway using whatever address the server still held under that handle, rather than the one just configured.

Changed

• A connect requested while target.open is still in flight now waits for it instead of being treated as a failure.
• The connecting log line names the address actually being dialled, instead of the previous target or nothing.

OpenTM v0.0.1

fix screenshot crop