Readables not able to scroll with mouse - mousing over inventory spaces causes text to scroll

[DaveA2021]

Readables not able to scroll with mouse - mousing over inventory spaces causes text to scroll

[DaveA2021]

Thanks for your response! I have not changed the set up as far as I know (unless I did something by accident) but here is the book in question:-

I also noticed that if I add paragraphs to another readable I have, I also cannot scroll.

Edit: Just confirming - I can use the scroll in the COGITO_3_Lobby scene after your update but still can't scroll in my scene - readables seem to be set up the same.

[DaveA2021]

Ok I feel silly now :D I moved the player node to the top of the hierarchy in my scene and the scrolling now works!

Thank you for the help :D

[Phazorknight]

Don't feel silly! I've run into this problem more times than I can count.
Glad you were able to solve it!

[Phazorknight]

Hey, so I was not able to reproduces this bug fully.

I've added a few more paragraphs to the first demo readable (note_welcome) and I can scroll with the mouse and the scrollbar as expected.

2024-07-09.08-55-11_compressed.mp4

Have you by chance changed the ReadableComponent setup? If so, could you show your node setup?

The behavior with the readable scrolling when the player highlights inventory slot is caused by the follow_focus_center script. This script basically "auto-scrolls" the ScrollContainer relative to whatever Control node is in focus, even if those nodes are the Inventory slots. It's not really a major issue.

If you want the player to be unable to have the Inventory and a Readable open at the same time, make sure to turn Ignore Open GUI off in the InteractionComponent section of your ReadableComponent.

As a side note: I've noticed that you couldn't scroll the readables with a game pad. I've just pushed a small update that fixes this, enabling the player to scroll readables with the right thumbstick.

[Phazorknight]

Hm... would you mind sharing the node setup of your scene?

For anything UI related, node order inside the hierarchy matters, so I suspect that somehow another node might be "on top" of your readable, blocking the input.

As a quick test, you could try putting your readable object into one of the demo scenes as well and see if that changes the behavior.