Custom FlexGrid editor: first typed char is at wrong position

Posted by: wknauf on 16 July 2026, 4:58 am EST

  • Posted 16 July 2026, 4:58 am EST - Updated 16 July 2026, 5:03 am EST

    We use a custom WPF TextBox as C1FlexGrid editor. This textbox provides built in OS spellchecking.

    When you select the C1FlexGrid cell and start typing, the first chars might have the wrong order in the textbox.

    This is a rather old problem that happens only in an internally used application and thus never had a high priority. But I found this in the readme for .796: “[FlexGrid] Fixed an issue where the first time you pressed a keyboard key in the grid editor, the value would not be set in the editor. (Jira:C1WIN-34246)”. As this does not change the problem, I took the time to create a reproducer:

    Start attached sample:

    FlexGridEditor.zip

    Select any cell in column 1 (but don’t double click it, just select it). Then quickly type the digits “1234”. The editor will probably contain the text “2134”:



    Another sample: If your input starts with an uppercase letter (“Shift” + “a”), the textbox will just contain the lower case “a”.

    Do you have any idea for a workaround? Or is this something that can be improved?

    My sample contains a lot of “OnKeyDown” overrides/eventhandlers and traces some output. Here you also see that the event order is “broken”.

    Best regards

    Wolfgang

  • Posted 17 July 2026, 2:49 am EST

    Hi Wolfgang,

    Thank you for providing the sample project.

    We were able to observe the mentioned behavior. We are getting in touch with our development team for further investigation. Rest assured, we will update you as soon as we have more information from them.

    Regarding issue C1WIN-34246 that you mentioned, it is a different issue in which the first key press was not being passed to the underlying editor when using a custom UserControl as the editor, even after implementing IEmbeddedEditor.

    [Internal Tracking ID: C1WIN-35492]

    Best Regards,

    Kartik

  • Posted 30 July 2026, 12:42 am EST

    HI Wolfgang,

    The development team has confirmed this as a bug.

    Here is the Bug Tracking ID : C1WIN-35494

    Best Regards,

    Vivek Singh

Need extra support?

Upgrade your support plan and get personal unlimited phone support with our customer engagement team

Learn More

Forum Channels