@Vexir you can change keyboard shortcut from
BTT > Keyboard Shortcuts > 
SWM Popup Window > Change it from right panel
No SWM doesnt update automatically. SWM keeps dynamic settings on updates but not guaranteed. But you have to re configure static settings(Prefs.js in preset folder) on uptades. Its minor issue since there is not too much settings and i release 3-4 updates in a year
I added drag feature to next release. I'm planning to share soon but not too soon 
Got it. How do I check the version to see if I need an update?
Having an issue here. Odd things are happening to my external mouse, regardless of which mouse I'm using. At first the left and right clicks were switched, then after I restarted my machine, scroll down minimizes windows and scroll up toggles between maximizing them and unmaximizing. There is no configuration I've ever set up to make this happen. Then I looked at Recently Used and found that SWM is doing it??
Edit: Ignore. Found the issue - it's actually hilarious.
@Vexir glad to fixed that. you can check current version of swm from topic tags
Ah I meant how do I check the version of SWM that I have downloaded?
@Vexir definitely its not user friendly. but you can check from Pref.js file
Open SWM > press P to open preset folder
I will add a dialog to show swm version with V key that should be easier
Hi @yw4z , I’m not sure if this is an SWM bug or a BTT bug (cc: @Andreas_Hegenberg) , but I’m not able to activate the full screen overlay with a hotkey. Nothing happens other than the active window losing focus. I have tried other shortcuts as well with less odd keys, like Shift+Cmd+T. Same result.
@yw4z bump!
@Vexir hi did you check troubleshoot section on first post. inspect element section important to identifying what causing issue if you dont have any notification from BTT
Same issue…
@yw4z Very nice work by the way!
Just spend over an hour trying to figure out why FSO doesn’t show up. Turns out it does; in a 2x2 pixels in the middle of the screen:
Looking at the action:
I suppose this is an error? But I’m not sure what value is supposed to go there as the overlay’s size should be dynamic…
@Julien no thats not an error, window launches with 2x2px and should resize itself to screen size
can you set window size to 100x100px and right click then inspect in context menu so i can see error
check first post for detailed troubleshooting
not sure its a new limitation by OS or a BTT issue. im still using ventura
Thanks for reaching back.
I just spend another 2h trying to find the issue without success. I got to the web inspector like you proposed, but there are now errors, just an object logged from FSO.html.
In FSO.html, I can tell that within the BTTInitialize function, the VJ object gets the proper screen resolution.
I tried messing around a bit with COM.js but you minified the code so it was pretty hard to understand.
Perhaps you could tell me a bit more in depth on where to look and even PM me the non-minified versions of the files?
thanks for help on finding issue. that means there is a problem with
callBTT('resize_webview',VJ)
@Andreas_Hegenberg can you check resize_webview function still working? or should i stringify object now while using parameter? i have tried stringfy but didnt accepted value
you can check FSO.html(line 352) for testing
It seems like the script "crashes" on Tahoe, but I'm not yet sure why. The first error I got was that Q() is undefined in FSO.html. Where does that function come from?
BTTWillHideWindow=i=>Q();
BTTWillCloseWindow=i=>Q();
I think I found the issue, I'll upload a new build later today or tomorrow!
Im still on ventura and it doesnt throw error for it. maybe i forget to replace with b()
you can replace it with b() it triggers closeFloatingWebView
b=(d,a,c)=>{
if(!d||c)trigger_named({closeFloatingWebView:1});
if(d=='p')trigger_action({json:{BTTPredefinedActionType:a}});
if(d=='n')trigger_named({trigger_name:a});
}
also i dont have use resize_webview if there should be an option on launching webview content to setting its size automatically with screen with cursor
Great! btw nice to see this script still works nicely on BTT after all years
Should be resolved in 6.195 alpha!
I confirm the issue is resolved in 6.195, on macOS Sequoia!
Thanks @Andreas_Hegenberg and @yw4z for teaming up to resolve the issue!