Repository navigation
Validation and defective files
- An Issues panel replaces validation messages in the Logs panel. It lists what loading the
file reported, then what validation found, with Mandatory (DEXPI requirements) and Recommended
(pyDEXPI conventions) issues grouped by rule. Selecting an issue selects and highlights its
objects; double-clicking zooms to them. The full text, the rule's description and its source
are shown beside the list, and the issues can be exported as CSV. - A file is validated as it opens, and the Issues panel opens when the loader left part of the
file out or a mandatory rule is broken. Before, a file pyDEXPI read only in part opened as if
it were whole: the loader's report was discarded. - A file pyDEXPI refuses to load strictly can be opened leniently, from the error message or
with Reopen leniently in the Issues panel; a lenient load lists everything it left out. - A file that is not well-formed XML says so.
- The drawing of a file read in part renders without the objects that were not loaded, instead
of not rendering at all.
Downloads
| System | File |
|---|---|
| Windows (64-bit) | DEXPI-Studio-0.1.1-windows-x64.zip |
| macOS (Apple silicon) | DEXPI-Studio-0.1.1-macos-arm64.zip |
| Linux (64-bit) | DEXPI-Studio-0.1.1-linux-x64.zip |
Unzip and start DEXPI Studio (on Windows DEXPI Studio\DEXPI Studio.exe, on macOS DEXPI Studio.app). The builds are not code-signed yet: on Windows choose More info → Run anyway; on macOS right-click the app and choose Open. Each .sha256 file holds the checksum of its zip (shasum -a 256 -c <file>.sha256). Each zip includes the DEXPI reference P&ID in data/ to try it with.
The macOS build runs on Macs with Apple silicon (M1 or later) only, not on Intel Macs.