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

Verify: the input pane does not scroll the first time after a structure save from the Builder

Open
#332 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
30/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
linux
Domain
desktop-dev

Research direction

Start by reproducing the sequence in the report: open an example calculation in the Organizer, open the Builder, save with Ctrl+S, save in the calculation editor, then open Verify and try to scroll the input pane. The issue suggests a mouse grab, window disabler or busy cursor left over from the structure update, and names VerifyReportDialog as the same code in both cases, so compare the state before the first and second Verify. Done means the first Verify after a Builder save scrolls, and the second and later dialogs keep working. Commit 5ff5db9e is mentioned as related, so check it for context.

Written by the indexing model from the issue text.

Description

Found 2026-10-15 on Linux (9.1.0 plus wip branches), reproduced with an example calculation (NWChem, MOPAC and the benzene example all show it).

Does not scroll (scroll bar shown, wheel and bar do nothing):

  1. Select an example calculation in the Organizer and open the Builder.
  2. Ctrl+S in the Builder.
  3. In the calculation editor, Save.
  4. Verify. The input pane cannot be scrolled.

The same happens with Final Edit between steps 3 and 4.

Scrolls:

  • the same sequence, but Verify once, close it, Final Edit, Verify again: the second Verify dialog scrolls;
  • Verify after a Save made in the editor alone (no Builder save before it).

So the first modal dialog that CalcEd opens after the Builder's save cannot be scrolled, and later ones can. A likely cause is something left over from the structure update, such as a mouse grab, a window disabler or a busy cursor that is never released, rather than VerifyReportDialog itself, which is the same code in both cases. Not yet investigated.

Related: MOPAC Verify marking fixed in 5ff5db9e (comment lines, whole geometry, second OLDGEO job).

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.