Micro and macro structures connected through attachment points can be saved in CML format but cannot be opened
- Dominant language
- C++
- Stars
- 406
- Forks
- 134
- Avg merge
- 2d 11h
- Merged PRs (30d)
- 24
Description
**Summary**
Micro and macro structures connected through attachment points can be saved in CML format but cannot be opened
**Steps to Reproduce**
1. Open Ketcher.
2. Draw a benzene ring
3. Add an attachment point to the benzene ring via right click menu
4. Switch to Macro mode and connect attachment point to a macro structure
5. Switch to Micro mode
6. Save structure in CML format
7. Open saved file
If it is not possible to draw the structure, then you can open the prepared file (you just need to open it in macro mode and then switch to micro mode):
[ketcher (53).zip](https://github.com/user-attachments/files/15620336/ketcher.53.zip)
**Expected behavior**
Micro and macro structures connected through attachment points can be saved in CML format and can be opened
**Actual behavior**
Micro and macro structures connected through attachment points can be saved in CML format but cannot be opened

**Saved file:** [ketcher (4).zip](https://github.com/user-attachments/files/16099298/ketcher.4.zip)
**Desktop (please complete the following information):**
- OS: Windows 11
- Browser Chrome
- Version 124.0.6367.79 (Official Build) (64-bit)
**Ketcher version**
[Version 2.23.0-rc.1]
**Indigo version**
[Version 1.22.0-rc.1]
**Refers to feature:** https://github.com/epam/ketcher/issues/4530
**Found when testing:** https://github.com/epam/Indigo/issues/1990
Contributor guide
No contributing guide indexed for this repository
Research direction
Reproduce the failure in Ketcher using the attached structure or the listed micro/macro attachment-point steps, with the reported Ketcher and Indigo versions. Trace the CML save and open paths, then verify that the saved structure can be reopened while preserving the micro and macro structures connected through attachment points.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100