HELP! Keystrokes Not Appearing in Editable Hover-Over! Feeding to DAW

General JUCE discussion
1

I’m admittedly a newbie. If it wasn’t for a couple friends and a lot of Googling how to translate my logic into JUCE-accepted C++ a LOT, I’d be nowhere, but I’m about as smart as they come. So, conceiving the logic is simple and that’s gotten me through building a pretty complex immersive plugin that I needed for work. My cousin wants me to release it and some colleagues were asking me to send it to them, so I decided to go back and give it a better GUI. Everything was moving fine until I decided to make the hover-over value displays editable. I’ve been stuck ever since.

No matter what I do, the keystrokes go to the DAW and trigger editor window tools, instead of appearing in the hover-over value display that’s in its editable mode. For some reason I can get g, h, l, backspace, delete, and a few other keys to appear, but that’s all.

I saw the long history of this being an issue, but the most recent one I saw was about 8yrs ago. So, I was hoping that means the solution is now common knowledge and nobody, but me, gets stuck with this issue anymore. I can edit value in my Waves plugins, so clearly a solution does exist for plugins created in JUCE. However, I’ve tried everything that makes sense. I’ve even tried things that only vaguely make sense, but nothing has worked.

PLEASE, can someone tell me how to solve this issue.

Projucer 8.0.9
C++20
Windows 11 Pro
VST3
Microsoft Vusial Studio 2022
Steinberg Nuendo is the primary testing DAW due to the Dolby Atmos/immersive features.
Alternate testing DAWs: WaveLab, Reaper, Resolve, Reason, MixBus Pro, Fruity Loops, Luna, Resolve

2

Whoever I saw say “model window” in one of the past posts about this issue, I owe them.
I also fee like I owe gratitude to @RiphRaph. While working on a way to augment your solution to suit my code, I saw a way to switch some of the existing code in my ValueOverlay class at the top of my PluginEditor.h and with a few really small changes to my code and a handful of additional lines– I can now enter text into my edit field and just about everything still functions as it should.
My click-away to cancel function doesn’t work and the text becomes too small when it becomes editable now, plus I still have to set my guidelines for what values & characters can be accepted, and make it cancel if the value doesn’t meet those conditions… but that should be easy after the nightmare I went through to find a solution.

I would post the relevant sections of my code, but its 5am. I have to walk my son to the bus stop in 3 hours, it would take me a bit to trim the code down to the relevant sections, and I’m sure someone else here could write it a 1000x better anyway. Good night