dBsooner wrote: Thank you, Justin! Good stuff! Is the update content capable of being HTML encode?
Just want to pass in a UL with LIs. Basically take what I’m already doing and pass it to WazeWrap instead of my own alertbox. Gracias!
I am not sure if this is WazeWrap or not but it didn't start happening until the new update window was added.
I have seen various scripts "stuck" in my address bar, BED, Outreach Tracker and some others. Also it appears to never finish loading. I have had the page show it is still loading for over 30 minutes.
I haven't seen that problem (regarding page never finishing loading) with the new update dialog, editor loads fine whether an update log is shown or not. However, regarding the update log, if there are several scripts that update and produce a scroll bar, I am unable to scroll the list with the mouse (in Chrome and Firefox, have to click and drag the bar). Would it be possible to make the list scrollable with the mouse wheel?
crazycaveman wrote: I haven't seen that problem (regarding page never finishing loading) with the new update dialog, editor loads fine whether an update log is shown or not. However, regarding the update log, if there are several scripts that update and produce a scroll bar, I am unable to scroll the list with the mouse (in Chrome and Firefox, have to click and drag the bar). Would it be possible to make the list scrollable with the mouse wheel?
I noticed the scroll wheel was not working when I was developing it but I don't see a reason for it to not work. I tried forcing it and still no-go. Not sure what is going on to be honest.
I see this behavior in other webpages. One of which is my companies MNS / RMM portal. If I click to see a systems profile (popup of a ton of info about a computer / server) it opens in a overlaying div. wheel doesn’t work to scroll. Have to use scroll bar. Also, page down / page up doesn’t work either, unless I click somewhere in the actual div first. I think this is a problem with Chrome and handling DIV layer scrolling.
Added an Events class. This class is designed to add extra, simple error handling when hooking WME events. All scripts that hook any of the WME events should add in their own error handling, but many do not, to prevent WME updates from breaking multiple scripts - even if there is only an error in one.
If one script breaks after hooking one of the events and the error that is thrown is not caught, the rest of the event handling queue is not executed so other scripts can/will be affected. Changing to use the WW events will prevent other scripts from being affected if there is an issue. Additional error handling should be done in the script, but switching to these events is a quick and easy way to protect your script, and others, in case of an error.
Implement virtually the same as when hooking native events.
It is possible to pass an error handling method to the WazeWrap.Events.register() method as well if you want to try and recover from any error that occurs.
If no error handling method is passed then the error will be logged to the console, including the method name that threw the error.
Note that when using the WazeWrap.Events.register for these you must pass a null value as the 2nd parameter - this is to keep the usage in line with all of the other register calls, despite the native registrations only taking two parameters.
Last edited by JustinS83 on Wed Mar 06, 2019 6:43 pm, edited 1 time in total.
Found an interesting z-index issue tonight. I can't seem to get the z-index high enough to be on-top of the UR Panel, but going to 10000 instead of 1000 gets above the turn restriction arrows. I found this by going directly to a UR in the URL (while I left my disabled turns enabled).
EDIT: Yep and I see a bug with URC-E too. LOL.
dBsooner wrote: Found an interesting z-index issue tonight. I can't seem to get the z-index high enough to be on-top of the UR Panel, but going to 10000 instead of 1000 gets above the turn restriction arrows. I found this by going directly to a UR in the URL (while I left my disabled turns enabled).
I wasn't going to mess with the zindex to get on top of that stuff but people won't stop pointing it out. So. FINE.
Lol! Hey. You don’t gotta fix it. I only mentioned it so others might not. Hehehe. Thanks for fixin it!