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

🐞 Suggestion window fails to draw

Open
#351 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
swift
Domain
desktop-dev

Research direction

Start by reproducing the failure with the example's mock completions, allowing the suggestion panel to appear and disappear repeatedly. Inspect the suggestion window and viewmodel handling around the reported canBecomeKeyWindow warning. Done means the suggestions window continues to render after repeated use, and completions are not inserted when the view fails to render.

Written by the indexing model from the issue text.

Description

bug
Description

Everytime after using the editor with the suggestion feature for a short period of time (5-15 appereances of the panel), the panel window just doesnt appear anymore, but pressing "TAB" or "ENTER" still inserts suggestions at the cursor.

In the XCode console I get:

Warning: -[NSWindow makeKeyWindow] called on <NSWindow: 0x401330240> windowNumber=151f8 which returned NO from -[NSWindow canBecomeKeyWindow].

This happens for the latest version still, with the new "Suggestion Window Fixes" PR merged.

To Reproduce
  1. Use the example with the mock completions for a longer period of time
  2. Let the panel appear and disappear 10-20x
Expected Behavior

The suggestions window should always render, and IF something fails to render, the viewmodel should refrain from inserting completions.

Version Information

CodeEditSourceEditor: latest main branch
macOS: 15.5 (24F74)
Xcode: 16.4 (16F6)

Additional Context

No response

Screenshots

No response

Dominant language
Swift
Stars
720
Forks
162
PR merge metrics
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

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 CodeEditApp/CodeEditSourceEditor

All issues in CodeEditApp/CodeEditSourceEditor

Similar issues

More Swift issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.