I asked Copilot to help me with this request, it seems to have done a fairly good job.
I understand there are other breakpoint feature requests but this one is really more of a review mode so that a user can confirm that the morph needs no further transformations. Maybe an option in the 'Call another module/project' action that forces the called project to open?
Context
In EasyMorph Desktop, I’ve built a modular workflow where one project calls another, passing parameters to the called project. This design supports reusability and scalability across a larger series of morphs.
Challenge
When debugging or validating logic in the called project, I’ve found that breakpoints placed inside it are ignored during execution. The calling project runs the called project to completion without pausing, likely because breakpoints are only respected in the calling context.
Current Workaround
To force a pause and open the called project, I intentionally trigger an error—e.g., by omitting the worksheet name in a passed Excel file path. This causes the calling project to fail and prompts the user with an option to open the called project. While functional, this approach is not user-friendly and relies on artificial error injection, which I’d prefer to avoid.
Request
Could EasyMorph Desktop support a breakpoint or “review mode” in called projects that allows:
- Pausing execution inside the called project when a breakpoint is present
- Optionally opening the called project for inspection or modification without requiring an error
- A debug flag or parameter that signals the called project to open in interactive mode
Why It Matters
Combining both projects into one is a temporary workaround, but it undermines modularity and maintainability—especially as the workflow scales. A native way to inspect or pause inside called projects would greatly improve debugging, validation, and user experience for complex morph chains.