Ahaha I guess the normal mouse is a bit too beige but for now it'll do . I've got some other things to do and they took ages to shape and shade right!
Edit: You can easily tune the beige-ness of the normal mouse through adjusting the saturation in preview. Turning it all the way down looked pretty good to me
@GoldenChaos the webview (and all other actions) settings will soon be integrated into the side-bar and they'll also get a popout for the editor part. Will however not be available in the first public release.
@Caliguvara the notes column has already been added, it will be available with the next alpha later today
Will the Notes column be optional? (Select via right click on column headers, like in Finder or iTunes.) If not, please consider making it so.
I agree, this would be tremendously useful. I'd even go further and separate the named triggers from the "Others" tab (or dropdown in the new UI) into a separate category, and then wherever there is a selection box for an action, present all named triggers in the same list as the pre-defined ones, under a new heading "Named Triggers". Then named triggers would simply be handled like any other action. This would also solve the strange problem that in the Touch Bar section, you cannot assign a default action to a long press unless you first create a custom (named) trigger that does nothing else than trigger the default action.
(I also never understood why named triggers are called that and not "custom actions" β they don't define trigger conditions but actions, and what distinguishes them from pre-defined/shipped actions is not that they're named, but that they're custom... ;-))
In any case, this would probably be a significant piece of restructuring of BTT's UI logic, but I think the new UI would be the ideal opportunity to implement it. And to be honest, the current logic seems more like something tacked onto the existing BTT structure rather than a proper integration.
I'd absolutely love it if that could be implemented, and I think it would also make this feature much more accessible to new or less technically inclined users.
I'm not current on the various iterations of the new UI, but speaking just from that mockup: in principle, that seems good to me β simply two ways of pressing a Touch Bar button. In column view, it would be another column after the default actions.
Two things though:
The named trigger selection should really be a list (at least as an option; @Andreas_Hegenberg already agreed on that much here ).
As I said, I really don't see why the long press should be limited to custom/named triggers/actions (). That should be exactly the same UI as for the short press/tap, with all predefined actions available and named triggers as just one option among them (ideally all integrated into the same list so that you wouldn't have to open any submenus for the selection of named triggers). Chained actions should be available as well.
(By the way, making the UI identical for predefined and named triggers also would make it much easier to define complex chained actions in the named triggers section and then use them like any predefined action, at any place in the app, wherever an action can be selected. Tidier too.)
There will definitely be a (optional) list selection for named triggers. Other functionality related to them might come in the future when breaking compatibility with the old UI is not a big issue anymore, but is very low priority right now.
Sorry for not many updates the last few days. I'm currently fixing many little bugs & crashes and am adding German translation (and looking for a good company to translate to other languages, probably it'll be https://www.oneskyapp.com/ because that allows BTT users to improve translations if the paid translators didn't get something right). New alpha should be available sometime tomorrow.
@Shnub
Yes, that was what I did in the original mockup, but @Andreas_Hegenberg said that this would require a significant change to the data model and is hard to implement. (very understandable) This is why you can see a β+ Soonβ faded button below it as I adapted the design to accomodate the current limitations!
Uhhh finally finished the localizability "project" to make the new UI adapt correctly to different sized strings and translated more than 13000 strings to German. Already ordered translations for Japanese, Chinese, French and Spanish that should be delivered in a few days. If that works well I'll order more languages - feel free to post requests in this thread: Request other translations here
jup for now it was just important to migrate the old settings to the new format. Making it look nice and adding features like search will come over time!
@yuuiko just added (kind of) your triangles and "speech bubble" actions
The indicator triangle is really helpful (although it was hell to hack a table view to do this, your exact design would require even more hacks, so that's it for now).
Just been using the new UI for some legit AquaTouch trigger formatting and i've gotta say it's working... okay.
I've been using the column view and it seems to be somewhat easier to navigate when compared to the old UI, but present everywhere are lots of small tiny little bugs that build to be a bit annoying... Here's a quick list of some gripes:
Moving the mouse up to hit save in order to see changes in the columns got very tiring... the Auto-save would be great!
Unable to rename triggers within the cell. More mouse motion to rename
Lots of times changes didn't save and I had to re-do whatever I did to convince BTT to save it as if it was stubborn
Some stability issues with the image drop area, sometimes the icon will go behind the drop image then it'll get lost and I'd need to redo that change
The 'rounded corners on left/right only' never saved if it was set by itself, i always needed to restate the round px to save
Lots of things are stuck with the default values inserted, or are empty.
The config panel doesn't visualise 'multiple values' that well if more than one trigger is selected. I think apple does a grey italic value
I always had to squint, scroll up and down and pause to find the right setting in the last column. Making this more concise with less popups would be great, e.g:
Edit: You could probably go one step further like:
Instead of:
This would also reduce clicks, mouse movement and reading for the right option.
such bugs are definitely expected as I have been the only one really using it so far. They will be fixed very quickly as soon as I finally do a first real release (waiting for my Chinese and Japanese translations, should arrive very soon)
About the save: do you know you can just hit cmd+s?
For renaming buttons you also shouldn't need to move the mouse - double clicking or hitting enter will focus the name field in the side-bar (unless there is a bug with that). In-cell stuff however won't be possible, everything will go through the side-bar.
Huge bug that makes it really annoying to edit anything inside a widget group: the "show inside any Touch Bar group" setting unsets itself if you don't check it every time when editing a widget.
I don't totally understand why the "Save" functionality exists? I like it just auto-saving as I edit, which it seems to still do anyway. I think the extra "Save" bit is very confusing and unnecessary.