Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Basis Set Tool: periodic table cut off on the right; elements 110-118 still have placeholder names

Open
#337 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
40/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
c
Domain
desktop

Research direction

Start with the Basis Set Tool window layout for the periodic table cut-off, then trace the placeholder symbols through data/client/config/AtomicElements, Isotopes.txt, AtomicOxidationStates and the data/client/cursors/Uun-*.xpm files. Check every code path and basis-set file that reads the symbol before renaming, since the issue warns that some may key on it. Done means the full table fits at the default window size, elements 110-118 show Ds through Og, and no reader breaks.

Written by the indexing model from the issue text.

Description

Found 2026-10-15 (Linux, wip/test-912 build):

  • The Basis Set Tool's periodic table is cut off at the right: the last column (He, Ne, Ar, Kr...) is half hidden at the window's default size.
  • Elements 110-118 still show the IUPAC placeholder symbols (Uun, Uuu, Uub, Uut, Uuq, Uup, Uuh, Uus, Uuo) instead of Ds, Rg, Cn, Nh, Fl, Mc, Lv, Ts, Og. The names come from data/client/config/AtomicElements and are also used in Isotopes.txt, AtomicOxidationStates and the Builder cursors (data/client/cursors/Uun-*.xpm). Renaming needs every reader checked, including basis-set files that may key on the symbol.
Dominant language
C
Stars
10
Forks
8
Avg merge
21m
Merged PRs (30d)
1

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from FriendsofECCE/ECCE

All issues in FriendsofECCE/ECCE

Similar issues

More C issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.