The alternate font color issue seems to have been resolved. Will continue to test.
I seem to have miscommunicated, I was looking for "Show All Events X days away" instead of "Show All Events for the next x days" (this is in order to create a widget that only displays tomorrow)
Sorry for the hassle! 
I also have some other requests with calendar widgets;
Is it possible to set the action for the calendar widget's "today event" to open up the current day instead of displaying the event, or remove it completely?
(also some weird spacing going on there)
In addition, an "All Day and Normal Events only" option (essentially no reminders) for the Calendar widgets would be useful.
You could change this to a bunch of checkboxes instead:
Show All Day Events
Show Calendar Events
Show Reminders
Finally, any news about the due dates for reminders not working?
Thanks so much! I'm revamping AQT's calendar widgets to kick out iCalBuddy but in order to get a neat / intuitive UI i'm needing a few things from BTT, appreciate you're listening!
The new Show all Events for x days is very nice! I can see the need for a "Include/show Today's Events" check box or something, so those, @yuuiko, who do not want to see todays events and only future days have that option.
@Andreas_Hegenberg the latest alphas have some issues with my brightness up/down keyboard shortcuts. Using those keys now causes a context menu to show up for some reason:
Which shortcuts are this? (In the default Goldenchaos preset?)
How do you trigger these on a Macbook keyboard? 
Is maybe secure input active? (BTT will show that when clicking the menubar icon). FN based shortcuts can be problematic because they stop working while secure input is on.
Ah, my apologies. I'm using an external magic keyboard 
I have it set up so that the brightness keys change the brightnesses of all monitors at once! BTT recognizes the built-in brightness keys as fn shortcuts even though I'm not actually pressing fn, and it's been that way for as long as I can remember.
I see! I'll check when I'm at my desk later!
I'd think an "only show events for this day" option would be good too but your suggestion would work in my context.
I can't seem to reproduce the shortcut issue. Can you check whether this still happens in 3.289?
Quick status update:
- The floating HTML / Webview has become MUCH more powerful with the latest alphas. I will soon release new documentation and various examples for it.
- Various performance improvements
- Fixed spacing in calendar widget
- Long press named triggers must now be selected from a dropdown
- Named triggers are now visible in the predefined action selector popover
- When exporting presets you can specify a min required BTT version
- Java Script based Apple Script widgets should reimport correctly
- Finally completed the switch from old memory management to auto reference counting. This might lead to a few crashes during the alpha phase, but should make BTT much more stable in the long run.
- Apple Scripts should not freeze BTT anymore.
- BTT window switcher can now be controlled by keyboard
- Apps that belong to hidden presets will now also be hidden
@yuuiko I'll add the calendar stuff tomorrow.
Here is also an improved example for slider buttons:
GestureSliderP3.bttcompressedpresetbundle (29.0 KB)
2 Likes
@Andreas_Hegenberg Just tried 3.289, the Brightness Up, and Brightness (small step) Up/Down work correctly, but Brightness Down still causes the popup that @GoldenChaos showed.
Edit: After toggling the shortcut disabled/enabled BTT seems to be behaving normally and now I can't reproduce the context menu.
Weird, is this with Goldenchaos 3.202?
In general the popup means that BTT thinks the brightness up and down are the same shortcuts. Could you try whether just re-recording the shortcut works?
Now working on AQT again.
Noticed some issues for the next event widget when set to reminders mode:
When the "no events" note is displayed, the Icon is not displayed
Tapping the widget should execute assigned actions, but instead it opens the BTT calendar input.
These issues seem to be occurring if there are no reminders events to display.
v. 3298
Noticed Floating WebView bugs:
1. No longer terminating window when pressing X on Bezel to close or touchbar button to close (Audio still plays (My Test/Tell) in background if a URL with audio). Same issue you fixed a few builds ago.
2. Strange behavior where one or more Floating Webview Touch Bar icons disappear when making changes to one of the "new" Z-index setting. They only reappear when de-select and re-selecting the Enabled/Visable check on that item in configuration.
2a. Had the button configuration line in BTT Config even disappear from BTT window, but re-appears after I re-opened BTT Config.
1 - are you sure caching is disabled for the webview? Otherwise it will stay active in background.
// edit: ah I can reproduce it with external URLs. Apparently conflicts with the new support for going fullscreen. I'll add a workaround!
2 - what do you mean by floating webview touchbar button and „button activation line“?
The z-index setting is quite advanced and not documented yet. It directly sets the raw NSWindowLevel of a window - which can lead to all kind of unexpected behavior.
This was the post from the other thread, its happening again, but now even the touchbar button used to close a webview doesn't stop the background processing. And ye, "Do not keep content active..." is checked.
- Floating Touch Bar button = The actuall button on the Touch Bar used to activate the webview. When I said the Configuration Line in BTT config, im speaking of the actual row in the BTT config window disappeared from the BTT configuration (like it was erased, leaving a blank row), and onlycame back into view after restarting BTT. Only happened twice so far while editing the Webview options.
BUG:
When using the "close" red window button on the webview bezel, it closes the window, but content and audio (if audio) is still running in background. Same for using the touchbar button to close webview. Example site: https://tunein.com/cnn
I expected the red close button to CLOSE that process/connection and it does not.
Ah I see (I mostly use the webviews with keyboard shortcuts thus didn't realize what you meant by Floating Touch Bar button :-))
I'll have a look. The close button issue should be fixed now.
Close button on Bezel, and using the touchbar button to close should also terminate process. As of 3.300, both methods do not close process.
Ahh sorry it should already be 3.301 - I'll check why it hasn't uploaded yet.