CCSTUDIO-THEIA: Loss of focus when compiling and chating with CODEX in the same time

Part Number: CCSTUDIO-THEIA
Other Parts Discussed in Thread: TMS320F280049C

HI guys,

 

A small but annoying behavior - see below a polished bug report that i asked CODEX to generate.

I do not know if this is intended or a funtionality bug - but it's annoying.

Title

Build completion unexpectedly steals keyboard focus from Codex Chat and redirects typing into the source editor

Environment

  • Code Composer Studio: CCS 21.x (C:\ti\ccs2100)
  • Operating system: Windows
  • Target project: TMS320F280049C C2000 project
  • Active source file: C2000-MPPT02.c
  • Build configuration: CPU1_RAM
  • Codex Chat open inside CCS

Description

While a project build was running, I was typing a message in the Codex Chat input field.

When the build completed, CCS unexpectedly moved keyboard focus away from the chat input and into the source editor. The editor navigated to C2000-MPPT02.c near the main() function.

Because I was still typing, the remaining text was inserted directly into the C source file instead of the chat window.

Steps to reproduce

  1. Open a C source file in the CCS editor.
  2. Open Codex Chat.
  3. Start building the active CCS project.
  4. While the build is running, place the cursor in the Codex Chat input and begin typing.
  5. Allow the build to finish while continuing to type.
  6. Observe whether focus moves from Codex Chat to the source editor.

Expected behavior

Build completion should not change keyboard focus when the user is actively typing in Codex Chat.

The chat input should retain focus unless the user explicitly selects another view or editor.

Actual behavior

At build completion:

  • Keyboard focus moved from Codex Chat to the source editor.
  • CCS navigated to the main() function.
  • Continued keyboard input was inserted into the source file.
  • The source file was unintentionally modified.

Impact

Severity: Minor UI issue, but with potential data-integrity consequences.

The behavior can silently corrupt source code because the user may not immediately notice that keyboard focus changed. In embedded or safety-related projects, accidental source modification is especially undesirable.

Frequency

Observed once so far. Reproducibility has not yet been confirmed.

Suggested behavior

  • Never steal keyboard focus from an actively edited chat input when a build completes.
  • Navigation to a source location should not automatically focus the editor.
  • If build completion must reveal a source location, the currently focused input control should retain keyboard focus.

Workaround

After build completion, verify that Codex Chat still has focus before continuing to type. If text enters the source editor, immediately undo the unintended edit and confirm that the file was not saved with the accidental text.

 

Thank you.

 

  • While a project build was running, I was typing a message in the Codex Chat input field.

    When the build completed, CCS unexpectedly moved keyboard focus away from the chat input and into the source editor. The editor navigated to C2000-MPPT02.c near the main() function.

    Because I was still typing, the remaining text was inserted directly into the C source file instead of the chat window.

    I somewhat see this but the behavior is a bit different. As I am typing the the Codex Chat input field while it builds, i have the focus shift to the Problems or Output view. This is not exactly unexpected since these views are often bought to focus to inform users of the build status. I don't have it switch to the editor however.

    In any case, the IDE behavior of switching focus is likely expected. I'll need to check with engineering to see if there is a way to suppress this behavior.