Jeremy Wright

Which build did you try? [Build 155](https://github.com/jmwright/CQ-editor/actions/runs/2169082713) is from 6 days ago and should have the latest sketch changes in it.

@jpoles1 > is there any way to "release" a version that is aligned with the current CadQuery version (and documentation)? https://github.com/CadQuery/CQ-editor/issues/274

@dumblob This doesn't address your core concern, but here are a few issues relevant to 2D sketching in CadQuery. [Sketchlets](https://github.com/CadQuery/cadquery/issues/52) [Parametric Sketching](https://github.com/CadQuery/cadquery/issues/42) [DXF Import](https://github.com/CadQuery/cadquery/issues/17)

@greyltc Is there an example that shows how it was wrong?

I tried a few things with this change and I think the fix makes sense. It seems odd that this bug would have gone undiscovered for so long, so that...

@jpoles1 I think it would be fine if you want to create an updated cheat sheet. I created that CQ cheat sheet several years ago and have never really updated...

Then can we do like I have with cq-cli and do a 0.2.1-beta.1 release?

I have the schedule set to build weekly right now, but I can do nightly if that will help. I'm not sure if GitHub changed something or not, but I...

@r4dr3fr4d There is no way to currently do this. The code assumes a standard `XY` workplane when importing. [Reference](https://github.com/CadQuery/cadquery/blob/3f6da6d8b528d1556382e691b92b70a8e6c5d1b6/cadquery/occ_impl/importers/__init__.py#L67)

Steps to reproduce: 1. Click the Debug button or press Ctrl+F5 2. Click the close button on the CQ-editor window