Thanks, this has been fixed in the beta version and should be fixed when Cameron releases to production version.MajkiiTelini wrote:I see some issue with closure length recognition:
Thanks,
John
US Global Champ
John
US Global Champ
I think the NaN hours is bug that he was working on.sketch wrote:Bug? When I'm in the same time zone as the closure, it'd be better if the message either reassured me that I'm in the same time zone or simply didn't say anything, rather than "warning" me that "Warning, the times for the closure you are adding is NaN hours ahead."
Thanks,
John
US Global Champ
John
US Global Champ
He has this bug on his list of things to fixSteveSnail wrote:Hi
Don't know if this is something you can look at or fix, but after having installed WME Closure Helper, it seems to be having an effect on UR-MP Tracking.
As soon as you select a segment, WME Closure Helper seems to remove the scroll bar from UR-MP Tracking preventing you from scrolling up and down. Only comes back when you reload the WME and then only until you click on a segment again
Without WME Closure Helper enabled
With WME Closure Helper enabled
Thanks,
John
US Global Champ
John
US Global Champ
That is currently out of the scope of this script. This script is designed for live closures not advanced closures. Advance Closures does do that for you though.YanisKyr wrote:I installed this script a few weeks ago but haven't got the chance to use it until today, I have to say it saves a lot clicks so thank you for that!
There's one suggestion I'd like to make about the presets. Would it be possible to define the start date/time as well?
Thanks,
John
US Global Champ
John
US Global Champ
FYI, the latest WME appears to have broken this script.
Thanks,
John
US Global Champ
John
US Global Champ
Pull request submitted that hopefully fixes the script.
Thanks,
John
US Global Champ
John
US Global Champ
I have temporarily revived this script until fourLoop is able to make it back.
https://github.com/jm6087/wme-closure-h ... er.user.js
New feature added in Version 2021.05.22.01
Added a box to enter a custom minutes for the clicksaver button. Enter numbers only. Should accept both positive and negative. i.e. 30 or -30
Settings appear to take a few minutes to update, so when you enter the custom time, wait a few minutes to see if the clicksaver updates.
https://github.com/jm6087/wme-closure-h ... er.user.js
New feature added in Version 2021.05.22.01
Added a box to enter a custom minutes for the clicksaver button. Enter numbers only. Should accept both positive and negative. i.e. 30 or -30
Settings appear to take a few minutes to update, so when you enter the custom time, wait a few minutes to see if the clicksaver updates.
Thanks,
John
US Global Champ
John
US Global Champ
The first issue has always been the case. I am not sure if I can figure that issue out or not.KuniaKid wrote:Brilliant! Thanks!
I've noticed that if you select a preset and go "oops! I picked the wrong preset", cancel the closure, the preset buttons do not appear. Other than that it works great!
UPDATE: I added a preset with an ampersand (&) in the name and that one is not showing up in the list. Not sure if the name is causing this.
I am not seeing the same thing on the second issue. What exactly did you enter? I even tested with a space. A & B
Thanks,
John
US Global Champ
John
US Global Champ
With help from Bruce, we were able to resolve this issue. Will probably push update tomorrow.KuniaKid wrote:Brilliant! Thanks!
I've noticed that if you select a preset and go "oops! I picked the wrong preset", cancel the closure, the preset buttons do not appear. Other than that it works great!
Thanks,
John
US Global Champ
John
US Global Champ
2021.05.23.00 fixes this issue - Thanks BruceKuniaKid wrote:Brilliant! Thanks!
I've noticed that if you select a preset and go "oops! I picked the wrong preset", cancel the closure, the preset buttons do not appear. Other than that it works great!
Thanks,
John
US Global Champ
John
US Global Champ
Re: [Script] WME Closure Helper