GUI blocked, no editing possible

[ccossou]

Hi, In the editor, if I select some text, the only key that then work are "Delete" or "Backspace" . If I start to write something it doesn't work. I assume this is not how this is supposed to work, but maybe I'm wrong. But this is how it works on any other editors I've ever used.

[edit] Just an edit, I experienced a similar issue just a bit after, no selection was done, and I still couldn't type any text in the window, no info was visible in the log section on the GUI. Only solution was to close the GUI.

After lauching, I could overwrite selected text, so I changed the issue title to reflect that.

I've started the GUI in command line to try and get some error message I can feed here.

When this happens, I can save the file proving that the UI is not completely frozen, and I can type in other windows than AsciidocFX. [/edit]

On the same note, the middle click copy/paste of Linux doesn't work.

I'm on Ubuntu 22.04.3 LTS, Using the latest .deb file of AsciidocFX 1.8.7.

[ccossou]

I've made a video to showcase the issue. https://github.com/asciidocfx/AsciidocFX/assets/3242621/642a3f62-445c-4e62-8865-7ebd8ea9f4b4

Note that when I switch to the file that doesn't work, I type but nothing happen except the cursor blinking.

The bug dissapear after I press on "Delete" after selecting the text "background". But before that "delete" press, No typing works, wether a text is selected or not, on that panel. The unsaved text meanline, correctly works.

In the terminal, no usefull error message appear. The only kind of message I can see are of this type:

1958678 [] INFO  c.k.e.AsciidocAsciidoctorjConverter - Converted Asciidoc to HTML5

Hope it helps,

[rahmanusta]

Hi, how frequent do you face with the problem? Does it happen only in one file or in some other files as well? Does it fix when you close and reopen the file?

[ccossou]

I experience the issue 3 times today, and my day is not over yet. I would say approx. once per day. It happens with any file as far as I can tell. I haven't tried to close/reopen the file, as I just noticed as I filled this issue that I still could type for another file. I wonder if this could be due to something being activated without me noticing. I know that in Inkscape for instance, when you start to type the code for an utf8 character, typing is interrupted and you type the utf8 code instead. But I couldn't notice anything of that sort in that situation.

[ccossou]

Just had the issue again, without typing any weird shortcuts. And closing/reopening the file solved the issue.

[rahmanusta]

I noticed the key events on development and build behaves differently, and it causes some issues. You can disable custom shortcut handler, and it should work as expected.

[ccossou]

Thanks, I just did. Difficult to report on the absence of random events, but I'll try to update this issue in a few days/weeks if I ever encounter the issue again.

[rahmanusta]

I've just published the new version. I hope it resolves the issue https://github.com/asciidocfx/AsciidocFX/releases/tag/v1.8.8 Btw. If it repeates again, pressing Esc should resolve the key handler back to normal.

[ccossou]

I experienced the issue again with 1.8.8, but using "Esc" solved the issue and I could type again.

[rahmanusta]

Please test with https://github.com/asciidocfx/AsciidocFX/releases/tag/v1.8.9 . I hope it resolves the key event issues

[ccossou]

Thanks, I have installed it. Before that, I experienced again the issue when I tried to do "Ctrl+F", but so far so good with the version 1.8.9. I'll keep you up to date in the coming weeks.

[ccossou]

I have not experienced the issue again since I updated to 1.8.9. This is always hard to be definitive about the absence of something, but so far so good.

You might decide to close this issue and I'll reopen it if I experience the issue again (or open a new one if reopening is not possible).

Thanks for your time and efforts on this.

Best.