https://bugs.documentfoundation.org/show_bug.cgi?id=141881

--- Comment #11 from BDF <[email protected]> ---
(In reply to Dieter from comment #10)
> Is it possible for you, to add a short screencast? Perhaps this would make
> it easier for us to see the problem. Thank you.

Now this is weird AF: Yesterday I had the problem again. Today it works fine -
for now.
The thing is I did not change anything at all. Like literally ZERO! No updates
for LO or Windows. I did not even restart the PC . Heck, I did not even bother
to close the writer file I'm currently working on! So I have literally not a
single clue where this would come from.

Since the problem persisted for I have no idea how long and this is the first
time that it did not show the bug, I wager that it will be gone after the next
restart (but let's see).

UPDATE: Ahh, there you go. I fixe-broke it: I closed the file and reopened it
and now I have the problem again.

If I come across the problem again I will try to film it with my phone. A
simple screencast will probably not do the trick because you would only see
that the file is not changing at all.

On that note: Is there any debug option in LO that shows me what buttons I
press?
The question is: Does LO not 'get' the button press or does it not act on
button press. I imagine such a debug tool to be a separate window with a
keyboard layout (like
https://commons.wikimedia.org/wiki/File:ANSI_US_QWERTY_(Windows).svg ) that
would highlight/darken the keys when pressed down.
The thing I also though about was if my keyboard would maybe not pick up
Ctrl+Shift+O + Ctrl+scroll for some reason. I wouldn't think so because it
works in other programs without any problem, but it's multiple keys at once -
so maybe?
But maybe not: The 'writing mode' does not have the issue. I can zoom in and
out using Ctrl+touchpad up/down; touchpad pinch to zoom; Ctrl+mousewheel
up/down

"Very, very strange" is all I can say right now.

I'll add a video as soon as possible!

-- 
You are receiving this mail because:
You are the assignee for the bug.

Reply via email to