you don't need to care about this, the scripts I posted do automatically set the correct ones.
Possibly test 4.140 I fixed something related to scripts
The only important thing is, that your shortcut returns the path to the image file
you don't need to care about this, the scripts I posted do automatically set the correct ones.
Possibly test 4.140 I fixed something related to scripts
The only important thing is, that your shortcut returns the path to the image file
Amazing !
It works now with 4.140 ![]()
Are Image [Fill, Stretch,...], Image position [Center, Top left, ...],... Planned for floating menus ?
[I don't currently need them, just necessary customization options to have when working with images]
Yes, they are already implemented and could be triggered via script, but I haven't exposed them in the UI yet. Will do that soon.
Great !
Planned for menus ?
Did you find anything about this issue? [Now it takes 5sec to activate trackpad click, gestures are working fine now]
V4.140
Scrolling can not be disabled right now, what would be the use case for this?
Unfortunately I don't know what could cause your gesture issue, there haven't been any changes to that for quite a while.
Is this only happening when you closed the macbook lid, or also when you put the mac to sleep via the Apple menubar icon?
For turning off scrolling, it's not very useful.
But Reseting scroll position, it's very useful, When I hover over a menu, I scroll down. It auto resets to the top, I don't have to scroll Up each time, since the most useful part of the menu is at the top.
When I open the lid, sleep doesn't do this, or at least I didn't notice ![]()
I've been trying just now.
As soon I opened the Macbook's lid, I did a 3-finger click (Pause/Play for me), and a few other gestures, clicks, ...
It took around 15sec for the trackpad to be usable, and It executed all the gestures I did before all at once (sensed a lot Haptic feedback)
Update:
I disabled these 2 automations, apparently, now it works normally!
Ok, I'll add a way to reset the scroll. Disabling the scroll should be easy, but I need to think about whether it's worth adding to the UI ![]()
Oh that makes a lot of sense, I think the bluetooth actions currently block the main thread, which causes the whole BTT to freeze until a timeout or until the bluetooth devices have connected.
I'll change that so it works in the background!
Amazing!
Honestly, I don't think disabling scroll is useful! but resetting is.
looking forward to the next update!
Maybe a better solution for you would be to hide items while the menu is not hovered.
This would then automatically lead to a scroll position reset and also save some memory.
Tested it, doesn't reset the scroll.
[Tested in the Notch test Menu]
Sometimes, I get that too.
I usually quit the app and reopen ![]()
Or just close it and reopen it.
[Sometimes it works when I change the menu and get back to where I was]
But it's rare!
I think that there is small bug in Floating Menu logic. When user will activate "close After Button Press" then submenu button set as "Back Button Item" stops working as menu hides instead of going back from submenu. In my opinion "Back Button Item" should be excluded from "close After Button Press" option.
You are right, will be fixed in the next alpha later today.
Two bugs:
Default behavior of BTT for all triggers is to always save when you switch to a different trigger. Always asking would kill the experience
If necessary users can undo.
Could you copy the menu that shows the wrong colors and paste it here? (or send to andreas@folivora.ai)
Does it show the correct colors after restarting BTT?
BTT restart solves the problem with exchanged colors. Do you need copy of menu then?
Going back to default save and experience - so maybe the experience should be improved and be more consistent by automatic save after every change as user still can "undo" changes?
For most things that's the case. But for things like text areas and some other form types, I can't save after every entered letter or changed value (similar for the system color picker). That's basically the reason for the save button - usually you can just ignore it.
If it works after restart I don't need a copy. If you can reproduce the issue, please let me know!
Good grief, this looks amazing!!
Thank you for this — going to do some serious tinkering next week.