Felix RiestraandClaude Sonnet 5
e767507850
The previous commit's Apple Event handler only ever catches an open sent to an already-running process. A cold double-click (app not running yet) still failed: every registration point tried inside the real binary — before app::run(), on the Subscription's first poll, even the literal first statement of main() — reliably caught a warm open but never the original cold-launch event. A raw AEInstallEventHandler in a separate, minimal, non-AppKit process (no winit/iced, just a manual CFRunLoopRunInMode pump) still missed it too, ruling out "the real binary's heavy dependency graph loading before main() wins the race" as the explanation. What does reliably catch a cold launch, verified against real Finder-equivalent opens: a from-scratch NSApplication with its own delegate implementing application:openURLs: — in a process where we own setDelegate: from the start, with no contention over the single delegate slot winit already claims. That has to be a separate process from the real GUI binary (only one -[NSApplication run] call can own a process), so src/bin/ocs_launcher.rs is now the .app's actual CFBundleExecutable: a small, dependency-light binary (no iced, wgpu, or cadkernel) whose only job is to catch the open and relay it. Relaying by replacing this process's image (exec, same PID) or by spawning a child and exiting turned out to both be dead ends: Launch Services tracks "the running instance of this bundle" by the Application Serial Number it handed out to whichever process it actually launched — this launcher, not whatever it execs into or spawns. Once the launcher's own ASN stopped pointing at a live, listening process, every later open Finder tried to deliver silently went nowhere (measured with lsappinfo against a real second "Open With", not assumed). So the launcher now stays running for the app's session — invisible, via NSApplicationActivationPolicyAccessory, since it owns no window — and relays every open (cold or warm) over the same channel a second CLI invocation already uses: io::single_instance. That relay only worked once single_instance's rendezvous key stopped being computed from the running executable's own path. That was fine when one binary always did the job, but the launcher and the real binary are different executables and independently computed different ports, so they could never find each other. Anchor the key on the enclosing .app bundle instead, shared by both. packaging/build_macos_signed.sh and .github/workflows/release.yml now build ocs_launcher and place it at Contents/MacOS/OpenCADStudio (the CFBundleExecutable Info.plist already names), with the real GUI binary renamed to Contents/MacOS/OpenCADStudio-App alongside it. Co-Authored-By: Claude Sonnet 5 <[email protected]>
English · Български · Português (Brasil) · Čeština · Nederlands · Français · Suomi · Deutsch · Ελληνικά · Magyar · Italiano · 日本語 · 한국어 · Polski · Русский · 简体中文 · Español · 繁體中文 · Türkçe · हिन्दी · العربية
Open CAD Studio
Open-source 2D drafting and 3D modeling for desktop and web, built with Rust.
Launch the web app · Download the desktop app · Join the discussion
Overview
Open CAD Studio is a cross-platform application for technical drawing, layout work, and solid modeling. It reads and writes DWG and DXF drawings natively, with a shared editing core across the desktop and browser versions.
The project is under active development. Keep backups of important production drawings and report reproducible problems through GitHub Issues.
Highlights
- Native drawing workflow — open, edit, recover, and save DWG and DXF files without a conversion service.
- Precise 2D drafting — lines, polylines, curves, splines, hatches, object snaps, tracking, layers, blocks, and external references.
- Documentation tools — text, dimensions, leaders, tolerances, tables, model space, paper space, viewports, and plot styles.
- Kernel-backed 3D modeling — solid primitives, extrusion, revolution, sweep, loft, Boolean operations, and ACIS entity tessellation.
- GPU rendering — accelerated 2D and 3D viewports through
wgpu, with orthographic and perspective cameras. - Extensible workflows — native plugins, command scripts, headless conversion, and a line-based JSON automation API.
File workflows
| Format or workflow | Support |
|---|---|
| DWG | Read and write; versioned save targets from R14 through 2018 |
| DXF | Read and write; versioned save targets from R14 through 2018 |
| BAK / SV$ | Open drawing backups and autosave files |
| OBJ | Import polygon meshes |
| LandXML | Import CgPoint survey points |
| STL | Export 3D mesh data |
| STEP AP203 | Export 3D mesh data |
| Plot layouts and selected geometry on desktop | |
| CSV | Extract entity property data |
| CTB / STB | Load and edit plot style tables |
Desktop or web
Use the web app for immediate access with no installation. Drawings are selected through the browser and saved as local downloads.
Use the desktop application for native file associations, file-manager thumbnails, system printing, PDF output, external plugins, command scripts, and headless automation. Release builds are available for Windows, Linux, and Apple Silicon macOS.
Install
Download all current packages from the latest release.
Windows
Choose one of these signed x86-64 packages:
OpenCADStudio-*-windows-x86_64-installer.msi— recommended installer with Start Menu shortcuts, DWG/DXF file associations, and drawing thumbnails.OpenCADStudio-*-windows-x86_64-portable.exe— standalone application; no installation required.
Linux
Download the x86-64 AppImage, make it executable, and run it:
chmod +x OpenCADStudio-*-linux-x86_64.AppImage
./OpenCADStudio-*-linux-x86_64.AppImage
macOS
The published macOS package supports Apple Silicon:
- Download
OpenCADStudio-*-macos-arm64.dmg. - Open the image and drag
OpenCADStudio.appinto Applications. - If Gatekeeper blocks the first launch, approve the app from System Settings → Privacy & Security.
The application is ad-hoc signed but is not currently notarized by Apple.
Languages
Open CAD Studio can follow the system language or use any of these 21 interface languages:
Arabic · Brazilian Portuguese · Bulgarian · Czech · Dutch · English · Finnish · French · German · Greek · Hindi · Hungarian · Italian · Japanese · Korean · Polish · Russian · Simplified Chinese · Spanish · Traditional Chinese · Turkish
Change the language from the application settings. The browser version also uses the browser's preferred locale when System is selected.
Build from source
Desktop
Requirements:
- Git
- Current stable Rust toolchain
- Platform graphics and font development libraries
On Ubuntu or Debian, install the native dependencies with:
sudo apt update
sudo apt install libgl1-mesa-dev libx11-dev libxcursor-dev libxi-dev \
libxrandr-dev libxkbcommon-dev libwayland-dev libfontconfig1-dev \
libfreetype6-dev
Then build and run:
git clone https://github.com/HakanSeven12/OpenCADStudio.git
cd OpenCADStudio
cargo build --release --bin OpenCADStudio
The resulting binary is written to target/release/OpenCADStudio (OpenCADStudio.exe on Windows).
Web
Install the WebAssembly target and build tools once:
rustup target add wasm32-unknown-unknown
cargo install trunk wasm-bindgen-cli
Start the development server:
trunk serve
Automation
The desktop binary supports one-shot conversion, a persistent headless server, and a client-neutral MCP endpoint for AI applications:
OpenCADStudio --export input.dwg output.dxf
OpenCADStudio --serve
OpenCADStudio --serve --port 4242
OpenCADStudio --mcp
The automation server exchanges one JSON object per line over standard input/output or a local TCP socket. The self-contained MCP endpoint exposes the live desktop editor through the same tools to every compatible client. To connect a client, configure it to launch OpenCADStudio --mcp. See the MCP control guide.
Plugins
Desktop plugins run in separate processes and communicate with the host through the versioned plugin API. The browser build does not load native plugins.
Project documentation
Contributing
Bug reports, focused pull requests, translations, documentation improvements, and plugin contributions are welcome.
- Search existing issues before opening a new report.
- Use Discussions for questions and ideas.
- Report vulnerabilities privately by following the security policy.
Application translations live in locales/*/opencadstudio.ftl; source labels map through
src/locale_catalog.rs. After editing translations, run python3 scripts/export-locales.py
to refresh web and desktop packaging labels. Validate with python3 scripts/test_site.py
and cargo test --lib i18n::tests.
Project growth
Stars
Release downloads
Support the project
If Open CAD Studio helps your work, support continued development through GitHub Sponsors or Patreon.
License
Open CAD Studio is distributed under the GNU General Public License v3.0.