[Script] WME Presets v1.1 -- 2021-04-11

[jm6087]

@G_W1Z

This is a great idea and script - thank you!

Would you consider adding the ability to handle WME Color Highlights? At times I like to switch back and forth between looking at segments with or without speed limits added. TB lets you show segments with speed limits added, but not invert that.

From original post:

@iainhouse

Currently, I cover:

• WME “native” Layers
• WME Colour Highlights
• WME Toolbox Highlights tab

[G_W1Z]

Doh, I didn’t connect the dots that WMECH stood for Color Highlights. I’m getting used to this script :).

[abc1357]

THANK YOU very much. I can now select the drop down menus now.

I’d like to request if it’s possible to “link” the presets so that 1 click will set all 3. Thanks.

[iainhouse]

@abc1357

I’d like to request if it’s possible to “link” the presets so that 1 click will set all 3.

I’ve had that request already from one of my Beta testers.

It wasn’t something I initially wanted to do. Each preset reduces clicks/actions from half a dozen to one. It doesn’t seem to me to be too much trouble to then need 3/4 clicks to load 3/4 presets. However, since it was originally asked of me I’ve been thinking about it.

What I’m thinking is that you could “link” presets in the different sections by giving them the same name; then using CTRL+CLICK on one of them to apply all with the same name. Without actually having tried to write any code, I think that would be relatively easy to implement.

If you have any alternative ideas for how to load multiple presets with only one click/action, then I would like to hear it. But please don’t come up with anything that requires adding extra menu items or even a menu hierarchy. I’m concerned that, once I start adding requested scripts, the menu might get quite big; and multi-level menus is just more new UI than I can bear to face.

[abc1357]

Having it “link” using the same name sounds good.

I just found an issue with the WME Layers section. I have several scripts that add check boxes to the layers menu to enable/disable. The WME layers section does not manage them. Thanks.

[iainhouse]

@abc1357

I just found an issue with the WME Layers section. I have several scripts that add check boxes to the layers menu to enable/disable. The WME layers section does not manage them. Thanks.

From the first post:

Within the menu is a section for WME Layers, plus a section for every other script it handles. If you don’t have that script installed, the section won’t be shown. Please note that WME Layers presets only include “standard” WME Layers. Where a script (like Magic) adds a layer to the Layers menu, it will not be picked up by this script.

One of the reasons I decided to start on this script was the discovery that the WME Layers Manager is exposed in the data model. It makes it easy to read the native layer settings as a single data structure, store it, and apply the settings.

I’m aware that there are scripts that add layer checkboxes to the menu; some of them add a LOT of checkboxes. I decided not to try and handle all of them, as it would likely make that function a great deal more complicated. If I later have a request to handle one of the scripts that adds a whole batch of layers, I might consider it as a separate set type; but I don’t currently intend to pick up any “added” layers.

[juliansean]

Thanks so much for the time and effort you’ve put into this script. My laptop is past it’s “best if used by date” so I’m having to keep a lot of scripts off. Having the ability to quickly turn on layers that I need for a specific edit is terrific!

Respectfully,

Sean

[AquaZR1]

Installed and set up yesterday. Logged in this morning and it was showing red and my presets are gone. What would cause them not to save? Running on Chrome.

[iainhouse]

@AquaZR1

Installed and set up yesterday. Logged in this morning and it was showing red and my presets are gone. What would cause them not to save? Running on Chrome.

I don’t know of anything that would stop the settings saving. In common with most WME scripts, this script picks up the window.unload event to save the settings. It’s possible that if the browser crashed, or a shutdown forcibly closed it, that could prevent the save function running.

Other, possibilities are creating settings in Beta which aren’t linked to Production (and vice versa) or using different browsers or computers. If you use an in-private tab, local storage changes are dumped on browser close.

[ojlaw]

It looks like a recent WME update finally broke this script. Does anyone know how to fix this issue? Like a simple code change since the script isn’t being maintained(RIP). After hovering on the preset button the dropdown is to the left of the button too far and it’s not possible to move the mouse to the dropdown without it disappearing.
Thanks.