Hacktoberfest 2026:維護者為十月標記出來的 issue,仍然開放、適合新手。 瀏覽 Hacktoberfest issue

Builder: metal–π bonds cannot be made to ring carbons (Metal order still needs nubs)

未關閉
#325 6 則留言 0 個 reaction 已指派 0 人 在 GitHub 檢視

還沒有人認領這個 Issue。

評估

難度
4/5
預估耗時
3-5 天
新手友好度
40/100
Issue 類型
缺陷
描述清晰度
描述清楚
活躍度
活躍
技術堆疊
cpp
領域
desktop

研究方向

Start in Fragment::bondAtoms and BondEditCmd, where Builder bonds currently go between two nubs, then check how addBond is reached in Bond mode with the Metal order. The change lets a Metal bond join two picked atoms directly without consuming nubs or hydrogens, while the align prompt for two molecules keeps working. Done when Fe(PPh3)3 plus benzene gets six Metal bonds to ring carbons with no change in atom count, and ferrocene can be built from two Cp⁻ rings. The typo fix ("unambigously") is part of the same change.

由索引模型根據 Issue 內容生成。

描述

Seen: ECCE 9.1.0. A tetrahedral Fe with three PPh3, then a benzene from the Structure Library. Inserting benzene: "Cannot unambigously connect fragments. Please select the sites that should be bonded." Bond mode with the Metal (metal–π) order, Fe to a ring carbon: "No bond sites are available to create this bond."

Cause: every bond the Builder makes goes between two nubs (Fragment::bondAtoms, BondEditCmd), including the Metal order (0.5). Ring carbons of benzene, Cp⁻ or an alkene have no nub (all valences used), so a metal–π bond to them cannot be made. Elsewhere the Builder already treats Metal bonds as not counting toward valence (shape and hydrogen placement ignore them), so requiring nubs here is inconsistent.

Fix: a Metal bond neither needs nor consumes nubs: in Bond mode with the Metal order, the two picked atoms are bonded directly (addBond), and nubs and hydrogens of both atoms stay as they are. With two molecules, the align question keeps working as now. Test: Fe(PPh3)3 + benzene, six Metal bonds to the ring carbons, no change in atom count; ferrocene from two Cp⁻.

Also: "unambigously" in the first message → "unambiguously".

主要語言
C
星號
10
分支
8
平均合併
21 分鐘
30 天內合併 PR
1

環境準備

這個專案沒有提供開發容器、Dockerfile 或貢獻指南,環境需要你自己搭建:先看它的 README,通用步驟見我們的新手貢獻指南。

從這裡開始

  1. 先讀完整個 Issue,再讀專案的貢獻指南。
  2. 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
  3. Fork 儲存庫,在一個分支上完成修改。
  4. 送出 Pull Request,並在描述裡引用這個 Issue 編號。

FriendsofECCE/ECCE 的其他 Issue

查看 FriendsofECCE/ECCE 的全部 Issue

相似的 Issue

更多 C Issue

把新 issue 寄到你的電子郵件信箱

精選適合新手參與的 GitHub issue 摘要。