It will still take a bit (sorry for moving this a lot, but every time I wanted to finally tackle the floating menu, something got in the way). New (I think now realistic) ETA: end of February.
Lately I have fixed and added many little things that were on my TODO list for v4.0 (which I'll release maybe sometime this weekend). So after that is out I'll focus completely on finishing the floating menus.
I've not been following the forums for a while. Could someone explain to me briefly what the fixed floating menus is? I kinda thought that the webview thing could already do menus, but maybe I've misunderstood?
Right now I have one floating menu implemented using Keyboard Maestro; when I hit a hotkey, I get this little menu appear, which lets me choose one of four screenshot options:
(the first three trigger BTT named triggers via ActionScript, and the last fires a hotkey to trigger Snagit)
Is it that sort of functionality that Andreas is working on bringing to BTT? It'd be great to have this inside BTT rather than using Keyboard Maestro for it (it's literally the only thing I'm using that software for right now! )
@TheBloke I agree with Andreas. For the menu you showed you don't even need "Custom Context Menu (New)". If you are familiar with KM then you know the conflict palettes. You can do something similar with BTT. If you assign the same tigger to several macros, BTT will also show a simple conflict menu.
Totally agree with that. The difference between BTT and KMM is that the BTT menu disappears when you activate a point, unlike KMM which can keep it fixed. That's why "fixed" is crucial for me. I'm envisioning something like the StreamDeckEmulator, an individual starter menu that can be customized for each app, and it can stay fixed. Back in the day, Adobe Configurator 2.0 had similar setups, and I was all over it. Unfortunately, it got discontinued. I know I can do it with KMM, and I've already built some panels. But as @TheBloke pointed out, KMM is not my go-to because I prefer BTT. So, it would be wicked helpful to have a deadline for when we can expect this feature.
Thanks all! Yes, I do keep forgetting about the standard conflict system - had I remembered that a few months ago I'd probably never have bought Keyboard Maestro It works OK, but with the one disadvantage that you can't (that I can see) specify another name for the entries in the conflict list, so eg when one of the entries is sending a hotkey, the conflict list just shows Send ^⌘C or whatever. It's not a deal breaker for my simple example but it's not ideal for a proper menu.
But that hopefully won't matter, because yes, Custom Context Menu (NEW) is precisely what I wanted!
That's so cute! I do have a technical problem with it (it's not showing up over full screen windows) but I've raise that in the proper place.
Thanks again for the info and help. The planned new update sounds really sophisticated and awesome and I'll watch for the updates with interest! Thanks again for all the info and help.
I suggest using the "Show Custom Context Menu (NEW)" option instead of the "conflict menu" to avoid having to use the same shortcut repeatedly. This way, you can also add different items to the menu.
You can create groups or direct links to an internal WIKI, or anything else you can think of. I am using a named trigger that can be activated through a menu bar item, mouse click, keyboard shortcut, or any other method you prefer.
When tackling more complex tasks, things can quickly spiral out of control. And if something goes wrong, the troubleshooting process can be a total nightmare. That's why I stick to using the program's default shortcuts and trigger them this way. Plus, it's way easier on the eyes.
But of course, that's just my opinion. The beauty of it is that everyone can customize it to their own liking.
Patience is a virtue, as they say. We first talked about this feature in the middle of last year. Then there were several deadlines (until Christmas and until the end of February) that passed without anything happening.
Multiple users have expressed that this function is of high priority for their future workflows and therefore is important to them. The point here is that these users also have customers and have to make business decisions to work as profitably and efficiently as possible. Orders are accepted or rejected based on these criteria. At least that's the case for me.
If BTT wants to play in the big leagues, it has to stick to its self-imposed deadlines. Otherwise, it's just a nice little niche product without much ambitions. It would be really good to get a deadline that is then kept so that planning can be based on it. If it turns out now that the feature isn't coming after all, that's not great, but it's better than waiting in vain, as we can then reorient ourselves and build the desired functionality elsewhere.
You are influencing the productivity and work processes of your customers with your product. We rely on your tool and your commitments. This responsibility is both a curse and a blessing for you, and you should be aware of that.
Just the 2cents of a guy who is slowly losing patience because he had to reject a potentially very profitable order due to the uncertainty of when a promised feature will be introduced.
You don't have to respond to that post because I'm going to have a beer now ... or two.