[Script] UrComments

Any idea what I am doing wrong?

Maybe it is related to the following error message, which I get only when using the beta?

I am going to guess that you are not in the US?

I just posted another version, where i changed the way i build the URL background data URL. I used to have a big if else statement that was missing beta’s IL and world server. it is now one line that should now work on all servers production and beta.

version 1.5.3

You are correct - I am using the IL server.
1.5.3 solved the issue - thanks!

However, I noticed that 1.5.3 doesn’t let me use the IsraeliHebrew comments file, nor my own Custom comment files.

What should we change in the comments file for them to work?

Today, I am getting an error message that my custom comments file (which worked fine yesterday) cannot be loaded. Has something changed?

Yes
Dont know what exactly but I copied my custom txt
Then reinstalled the file and pasted in my custom txt and it all worked fine again…

Sent from my XT1080 using Tapatalk

Here are the changes that need to be incorporated into the custom comment scripts to make then work again. Looks like it’s a new array for storing URLs, probably for instructions/help

Thank you

Sent from my XT1080 using Tapatalk

Concerning the language files, there also seem to be problems with FF not updating them. If you want the latest version, uninstall and reinstall. Or copy the code from the new version into your current version.

Don’t forget to save any personalized parts first and insert them back again.

Thanks,

for the custom comments there was a request that the url for the instructions could be customizable. Also the support url in the comment ‘App Bug’ was no longer valid.

for the main script I made the changed it to use the new url array, changed the way the background data url is built and changed the ‘App Bug’ url, and made the instruction url open in a new tab.

If anyone is having problems with the diff that crazycaveman posted make sure you don’t copy the + symbols at the beginning of each line. The next easiest way would be to reinstall the custom comments file and then paste in your comments.

all of the language files have been updated.

Love the script, thanks.

Have one slight problem: when I am working my way through using UR-MP-tracking to find and add the ‘4 day reminder’, URComments adds the reminder fine, but it shows the pre-auto-send view of the UR as if the comment had not already been sent.

It would be much better if it showed a view that made it clear that the message had already been sent. It would also be nice to have a shortcut to close so I don’t have to use the mouse to hit the ‘close x’ button each time. (I hate to use the mouse to press buttons!)

URO+ has the option to replace the “Next” with the original “Done” button.
Still a click, but easier than finding the “x”

1.Third option from the bottom of URC settings (Auto send reminders) will automatically send reminder and notification will be shown on top of the window.
2. Also in settings there is “All comments - double click link (auto send)” which allows to fill, auto send and close the UR if double clicked on specified area.

Are you aware of those options?

I use, but sometimes it doesn’t send or I don’t see or hit the send button anyway and end up sending the reminder twice because it doesn’t look like it got sent.
I was wishing that the UR window would get updated so that it was clear that the text had been sent.

use all the time when appropriate.

Thanks for trying to help. :slight_smile:

you should see the pill counts update immediately after sending a comment and when sending a comment it should appear in the conversation area of the UR?

the auto reminders will only be sent to UR where the initial comment is from you, where the comment count is 1, where the days past the initial comment are equal or greater than the number of days in your settings, and if the UR is on screen.

this is not how i would recommend sending reminders. i would set URO+ to backfill UR, set URC to auto send reminders, and then zoom all the way out and URC finish. After URC is done sending reminders i would click on rescan in UR-MP.

also i am not understanding what you mean by “pre-auto-send view of the UR” does this mean UR-MP is not showing that the UR was updated or that the waze does not show the comment or URC’s pills and filters are not showing the update?

The amber bar(s) showing auto-reminders show briefly, but the UR window does not change from what one sees when any message is auto added but not yet sent.
The pill count does not change until I close the UR window. Sometimes I must do a Shift-alt-R to get the count to update.
…

yes

the comment shows as if it has just been added to the box but not yet sent.

yes.

The short of it is that you are using two scripts that were not designed to work together the way you are attempting to use them.

i will quote / update what i said a few messages ago…

After sending reminders this way there is no reason to use UR-MP for sending reminders. as for the view not updating, the message is sent in the background when the UR is on screen, if you open the UR before the message is sent waze will not reload the UR data. There is no way i am going to attempt to try to update UR-MP’s data / list. If you insist on doing things the way you described, disable the auto send reminder and all your problems will be solved!

Close days - Is that the number of days after the report was initially submitted? Or days after your last reply? Example:

Report date: Jan 7, 2015

Reminder days: 4
Close days: 7

A reminder will be given on Jan 11. Will the close date be Jan 14 or 18?

both the reminder and the close days are based off the date of the last comment from an editor.

Rick,

I figured out how to reproduce this error. If you actually disable URO+, your async script calls enter a RACE condition sometimes, especially if you are in an area with high UR density (500+) and/or if you have a lot of scrolls or movements in close succession.

Somehow, the URO+ backfill setting seems to keep this from happening at some point. Probably due to the fact that some event is fired after the URs are backfilled.