Don’t be sorry, thanks for being in the conversation 
It’s a great function for user feedback! Thanks for sharing it!
Edit: Plus, now I know how we got discussing that effect from the original discussion on vibrancy 
I played with it a while ago, I got sidetracked and never took the time to figure out why the blacks of the text were also turning transparent.
https://www.dropbox.com/s/b7fi5xzfoy831gl/TestBlurWindow.xojo_binary_project?dl=0
However, this is glass using DWM, not the newer Acrylic which will need a little more tinkering
https://docs.microsoft.com/en-us/windows/uwp/design/style/acrylic
[quote=488043:@]I played with it a while ago, I got sidetracked and never took the time to figure out why the blacks of the text were also turning transparent.
https://www.dropbox.com/s/b7fi5xzfoy831gl/TestBlurWindow.xojo_binary_project?dl=0
However, this is glass using DWM, not the newer Acrylic which will need a little more tinkering
https://docs.microsoft.com/en-us/windows/uwp/design/style/acrylic[/quote]
Thank you Julian, the TestBlurWindow is what I needed.
Except, I only want a portion of the window to have vibrancy (for example the left part of the window). Is that also doable?
A bit hijacking this thread, but hopefully adding some information to it as well:
Has someone developed a good solution for full vibrancy support on macOS with Xojo?
Technically Vibrancy on macOS is a combination of two things:
a NSViusalEffectView that must be embedded into the view hierarchy of the window. No problem with simple declares, although Xojo discourages us from mingling with the hierarchy of Xojo-created views. A VisualEffectView adds a specified translucency effect, making the view background more or less milky or dark and in most cases mixing it with background colors and a blur effect.
Vibrancy itself which is the blending of foreground elements with this translucency so that text and similar elements will still look sharp and readable no matter how wildly the background might be coloured. This, for reasons unknown to me, is a class property of a NSView, which usually would mean youd have to subclass the Xojo subclass of the respective control (i.e. a TextView) which does not look attractive to me one could easily mess up the internal event/method handling. I would rather have a property or event to use but dont see it easily implementable without Xojos support.
Or did someone have a much brighter idea how to implement Vibrancy?