Skip to content

InputText in read-only mode doesn't allow InsertChars() in callback, affecting in imgui_memory_editor #8714

@Dimoks

Description

@Dimoks

Version/Branch of Dear ImGui:

afe20dc master

Back-ends:

imgui_impl_glfw.cpp + imgui_impl_opengl2.cpp

Compiler, OS:

MSYS2 UCRT64, gcc 15.1.0, Windows 10

Full config/build information:

No response

Details:

After updating Dear ImGui to a recent version (around commit afe20dc or later), a rendering issue occurs in imgui_memory_editor (v0.58 from ocornut/imgui_club) when used in read-only mode. Specifically, when a byte is selected in the hex area, the InputText widget used to display the byte value renders with an opaque background, which obscures the underlying byte text. This makes the selected byte unreadable until the selection is cleared (e.g., by clicking elsewhere, such as the footer).

The issue does not appear in earlier versions of ImGui. It seems related to changes in the rendering or styling of InputText in read-only mode.

Use imgui_memory_editor (v0.58) from ocornut/imgui_club with the latest ImGui (e.g., commit afe20dc or newer).
Set up a MemoryEditor instance in read-only mode and display some data.
Click on a byte in the hex area to select it.
Observe that the selected byte is obscured by the opaque background of the InputText widget.

Screenshots/Video:

Image

Minimal, Complete and Verifiable Example code:

#include <imgui_memory_editor.h>
...
MemoryEditor mem_edit;
mem_edit.ReadOnly = true;
ImGui::Begin("Example Bug");
mem_edit.DrawContents(raw_data.data(), raw_data.size());
ImGui::End();

Metadata

Metadata

Assignees

No one assigned

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions