3.301 was stuck in the Apple notarization pipeline 
Should be online now.
I think the floating webview is really quite powerful now and will enable many amazing things. I'm using it as a Netflix player while I'm working full screen in Xcode 
.
Re-recording them did not work. However, it did help me discover what is probably the issue, which is that the shortcut is being inadvertently recorded as a Chinese character:
The chinese characters are normal, the component used for displaying the shortcut doesn't like some of the special keyboard glyphs
However the issue is super weird, I tried to reproduce it on all of my keyboards (MBP 2018 internal, wired fulll size Apple Keyboard, bluetooth full size Magic Keyboard, and small bluetooth Magic Keyboard) and it seems to work fine on all of them. Could you maybe copy & paste the json for the problematic shortcuts here? (They should show different key codes)
Brightness down:
[
{
"BTTTriggerType" : 0,
"BTTTriggerClass" : "BTTTriggerTypeKeyboardShortcut",
"BTTPredefinedActionType" : 29,
"BTTPredefinedActionName" : "Brightness Down",
"BTTAdditionalConfiguration" : "8388608",
"BTTEnabled2" : 1,
"BTTKeyboardShortcutKeyboardType" : 1806,
"BTTRepeatDelay" : 0,
"BTTUUID" : "CF96CA91-49C2-4A68-B735-029620F57693",
"BTTTriggerOnDown" : 1,
"BTTNotesInsteadOfDescription" : 0,
"BTTLayoutIndependentChar" : "เขณ",
"BTTEnabled" : 1,
"BTTModifierMode" : 0,
"BTTShortcutKeyCode" : 145,
"BTTShortcutModifierKeys" : 8388608,
"BTTOrder" : 4,
"BTTDisplayOrder" : 0,
"BTTAutoAdaptToKeyboardLayout" : 0,
"BTTAdditionalActions" : [
{
"BTTTriggerType" : -1,
"BTTTriggerClass" : "BTTTriggerTypeKeyboardShortcut",
"BTTPredefinedActionType" : 121,
"BTTPredefinedActionName" : "Brightness Down (External Display)",
"BTTEnabled2" : 1,
"BTTKeyboardShortcutKeyboardType" : 0,
"BTTRepeatDelay" : 0,
"BTTUUID" : "763F424B-453C-4B68-A122-08896FD31F82",
"BTTTriggerOnDown" : 1,
"BTTNotesInsteadOfDescription" : 0,
"BTTEnabled" : 1,
"BTTModifierMode" : 0,
"BTTShortcutKeyCode" : -1,
"BTTShortcutModifierKeys" : -1,
"BTTOrder" : 0,
"BTTDisplayOrder" : 0,
"BTTAutoAdaptToKeyboardLayout" : 0
}
]
}
]
Brightness up:
[
{
"BTTTriggerType" : 0,
"BTTTriggerClass" : "BTTTriggerTypeKeyboardShortcut",
"BTTPredefinedActionType" : 28,
"BTTPredefinedActionName" : "Brightness Up",
"BTTAdditionalConfiguration" : "8388608",
"BTTEnabled2" : 1,
"BTTKeyboardShortcutKeyboardType" : 0,
"BTTRepeatDelay" : 0,
"BTTUUID" : "F53314B1-3E14-4C6C-A5C2-0C36D0C28E28",
"BTTTriggerOnDown" : 1,
"BTTNotesInsteadOfDescription" : 0,
"BTTLayoutIndependentChar" : "",
"BTTEnabled" : 1,
"BTTModifierMode" : 0,
"BTTShortcutKeyCode" : 144,
"BTTShortcutModifierKeys" : 8388608,
"BTTOrder" : 5,
"BTTDisplayOrder" : 0,
"BTTAutoAdaptToKeyboardLayout" : 0,
"BTTAdditionalActions" : [
{
"BTTTriggerType" : -1,
"BTTTriggerClass" : "BTTTriggerTypeKeyboardShortcut",
"BTTPredefinedActionType" : 120,
"BTTPredefinedActionName" : "Brightness Up (External Display)",
"BTTEnabled2" : 1,
"BTTKeyboardShortcutKeyboardType" : 0,
"BTTRepeatDelay" : 0,
"BTTUUID" : "89649BDD-0A8E-4310-A6EC-BF568C9E7A81",
"BTTTriggerOnDown" : 1,
"BTTNotesInsteadOfDescription" : 0,
"BTTEnabled" : 1,
"BTTModifierMode" : 0,
"BTTShortcutKeyCode" : -1,
"BTTShortcutModifierKeys" : -1,
"BTTOrder" : 0,
"BTTDisplayOrder" : 0,
"BTTAutoAdaptToKeyboardLayout" : 0
}
]
}
]
The first one was re-recorded, the second one was not.
Looking all good 
Does it also only happen for the brightness down key for you?
The brightness down key was re-recorded. I re-recorded brightness up after posting that, and it fixed the issue. However, since it's affecting all existing users, let me go grab the affected JSON from my backup.
EDIT - Here's the pre-rerecording brightness down JSON:
[
{
"BTTTriggerType" : 0,
"BTTTriggerClass" : "BTTTriggerTypeKeyboardShortcut",
"BTTPredefinedActionType" : 29,
"BTTPredefinedActionName" : "Brightness Down",
"BTTAdditionalConfiguration" : "8388608",
"BTTEnabled2" : 1,
"BTTKeyboardShortcutKeyboardType" : 0,
"BTTRepeatDelay" : 0,
"BTTUUID" : "CF96CA91-49C2-4A68-B735-029620F57693",
"BTTTriggerOnDown" : 1,
"BTTNotesInsteadOfDescription" : 0,
"BTTLayoutIndependentChar" : "",
"BTTEnabled" : 1,
"BTTModifierMode" : 0,
"BTTShortcutKeyCode" : 145,
"BTTShortcutModifierKeys" : 8388608,
"BTTOrder" : 4,
"BTTDisplayOrder" : 0,
"BTTAutoAdaptToKeyboardLayout" : 0,
"BTTAdditionalActions" : [
{
"BTTTriggerType" : -1,
"BTTTriggerClass" : "BTTTriggerTypeKeyboardShortcut",
"BTTPredefinedActionType" : 121,
"BTTPredefinedActionName" : "Brightness Down (External Display)",
"BTTEnabled2" : 1,
"BTTKeyboardShortcutKeyboardType" : 0,
"BTTRepeatDelay" : 0,
"BTTUUID" : "763F424B-453C-4B68-A122-08896FD31F82",
"BTTTriggerOnDown" : 1,
"BTTNotesInsteadOfDescription" : 0,
"BTTEnabled" : 1,
"BTTModifierMode" : 0,
"BTTShortcutKeyCode" : -1,
"BTTShortcutModifierKeys" : -1,
"BTTOrder" : 0,
"BTTDisplayOrder" : 0,
"BTTAutoAdaptToKeyboardLayout" : 0
}
]
}
]
Pair this with the brightness up JSON from my previous post and the issue occurs.
Dang it still seems to work here when pasting the jsons. Might be some internal database structure thingy which is not exported to JSON.
Can you still reproduce it on your machine? If so it would be really great if you could go to Help => Export Diagnostic Debug Information and send the result to andreas@folivora.ai
Sent!
Thank you! Unfortunately I'm still unable to reproduce it here ;-(
Is this the keyboard you use? https://www.apple.com/shop/product/MLA22LL/A/magic-keyboard-us-english
I agree. Very powerful and has replaced a few other apps I created just for exactly what you are doing and other uses. It's important the process closes for a few Webviews in particular. Mainly for my office phone system interface, its a "live view" into the PBX and can use a lot of data if left running in background (just an example why I the close process is so important).
Yep, that's the exact keyboard. How else can I help you debug this issue? It would be awful to require everyone to install a new version of GC to fix this issue.
Just to be sure, this issue is still happening On 3.301 alpha?
I'll probably try to get one of these keyboards tomorrow, I think it's the only model I don't own 
(and I spilled coffee on my old one yesterday, so time to get a new one anyways)
Yes, the issue still happens on 3.301! The issue still happens on my secondary MacBook, where I haven't made any changes.
Was the debug info you sent from the machine where it still happened?
Yes
Damn, I'm a bit out of ideas
Do you possibly remember whether this started after a BTT update or after the update to macOS 10.15.3?
Tough to say, but I'm pretty certain it was after one of the BTT alpha updates. Later this afternoon I'll have some time to try out previous BTT versions to figure out where the change occurred!
1 Like
@Andreas_Hegenberg After testing, the last working version is 3.280. The issue occurs with 3.281 and higher. Installing 3.280 fixes the issue.
Thanks for looking into that. I feared it was that version (I enabled automatic memory management for the remaining code in BTT that was still doing manual one, and possibly some hard to trace memory management issue is causing the behavior... the stupid thing is that I can't reproduce it yet, but I'll try with the new keyboard tomorrow
@yuuiko 3.303 should have added the requested calendar widget features!
1 Like
Like the idea of the date range, great solution... BUT, you broke my calendar event widget. LOL
v. 3.303
BUG:
Todays Event does not show when setting the start range 0 days - end x# days. Looks like no matter what I do, I cant get todays event to show anymore