Give your script a way to sign-out / revoke access / de-authorize. URC-E doesn't need API v4 credentials to see the standard data on Google. It only needs the v4 credentials during creation / conversion of a custom comment list. During standard work, URC-E accesses all the data it needs via "shared with public" (anyone with link can VIEW) access.samighaffari wrote:I write a script with google speardsheet .
But when your script is on use your session and make an error with my script .
what can we do for this problem ?
https://s.waze.tools/scrp.pnghttps://s.waze.tools/am.pnghttps://s.waze.tools/betc.pnghttps://s.waze.tools/beta.pnghttps://s.waze.tools/mapr.pnghttps://storage.googleapis.com/wazeopedia-files/7/74/Waze_signature_200k_plain.pnghttps://s.waze.tools/c5s.png
• AM: Eastern Oklahoma, DFW, Southern Florida
• Wiki: WME | Editing Manual | Best Practices | FAQ | Places
• T-Mobile | iPhone 14 Pro | iOS Latest | Waze Latest Beta
• AM: Eastern Oklahoma, DFW, Southern Florida
• Wiki: WME | Editing Manual | Best Practices | FAQ | Places
• T-Mobile | iPhone 14 Pro | iOS Latest | Waze Latest Beta
2019.07.23.01 is out!!
Code: Select all
2019.07.23.01: NEW: WazeWrap settings storage ability.
CHANGE: Compatibility with latest WME release.
CHANGE: Cleanup of mutation processing.
BUGFIX: Per comment list settings toggles.
https://s.waze.tools/scrp.pnghttps://s.waze.tools/am.pnghttps://s.waze.tools/betc.pnghttps://s.waze.tools/beta.pnghttps://s.waze.tools/mapr.pnghttps://storage.googleapis.com/wazeopedia-files/7/74/Waze_signature_200k_plain.pnghttps://s.waze.tools/c5s.png
• AM: Eastern Oklahoma, DFW, Southern Florida
• Wiki: WME | Editing Manual | Best Practices | FAQ | Places
• T-Mobile | iPhone 14 Pro | iOS Latest | Waze Latest Beta
• AM: Eastern Oklahoma, DFW, Southern Florida
• Wiki: WME | Editing Manual | Best Practices | FAQ | Places
• T-Mobile | iPhone 14 Pro | iOS Latest | Waze Latest Beta
I'll get to everyone's posts and PMs as soon as I can. Wanted to get this release sent out first.
P.S. Before thinking something is wrong with any script, disable all other scripts first. With scripts sharing resources / libraries (particularly WazeWrap), if a script causes the library to crash (error), other scripts can be affected by it. One in particular causing issues with URC-E (and likely other scripts) is PL Jumper. I am sure things will get updated by the script authors, but please be mindful of basic troubleshooting steps.
Thank you all for your support and help!
P.S. Before thinking something is wrong with any script, disable all other scripts first. With scripts sharing resources / libraries (particularly WazeWrap), if a script causes the library to crash (error), other scripts can be affected by it. One in particular causing issues with URC-E (and likely other scripts) is PL Jumper. I am sure things will get updated by the script authors, but please be mindful of basic troubleshooting steps.
Thank you all for your support and help!
https://s.waze.tools/scrp.pnghttps://s.waze.tools/am.pnghttps://s.waze.tools/betc.pnghttps://s.waze.tools/beta.pnghttps://s.waze.tools/mapr.pnghttps://storage.googleapis.com/wazeopedia-files/7/74/Waze_signature_200k_plain.pnghttps://s.waze.tools/c5s.png
• AM: Eastern Oklahoma, DFW, Southern Florida
• Wiki: WME | Editing Manual | Best Practices | FAQ | Places
• T-Mobile | iPhone 14 Pro | iOS Latest | Waze Latest Beta
• AM: Eastern Oklahoma, DFW, Southern Florida
• Wiki: WME | Editing Manual | Best Practices | FAQ | Places
• T-Mobile | iPhone 14 Pro | iOS Latest | Waze Latest Beta
To further this statement, Twister and I have been in discussions in the past about combining our efforts so as to not "step on each others toes" so-to-say. We, as a developer community, don't want to take anything away from another developer or script, and definitely don't want to waste the time of developing the same feature set separately.Twister-UK wrote:
After almost 7 years of continuous development, a little bit of feature creep away from the original intention of the script is to be expected And back when I started releasing stuff on the Chrome Web Store, there was a fairly low limit on the number of things you could publish using the cheapest developer account option, so merging new ideas into one or another of my existing scripts rather than creating standalone scripts was the only sensible option if I wanted to continue supporting Chrome users.
These days, with the Chrome version of Tampermonkey working just as well as the Firefox version (something that was far from true, hence the need to release webstore versions as well as just the bare code versions on userscripts/greasyfork), and with the growing levels of control freakery exhibited by Google over what they expect from stuff in the webstore, I've decided to abandon that entirely and only do greasyfork releases from now on. As this means I'm now no longer constrained in how many scripts I release, it gives me the freedom and the potential to start thinking about taking a scalpel (or perhaps sledgehammer) to the URO code and breaking it down into seperate scripts focussed more one one specific aspect.
So your wishes may well be granted, just please don't ask me when, unless you want me to give the one word answer sure to strike fear and dismay into the heart of any seasoned Wazer... soon
As the development community has continued to grow, the OG's have worked hard to create a good collaborative environment to assist each other. I am glad for this as it made it super easy to "jump in" when I started developing.
I'm with Twister on this, things will continue to change and grow, as to when.. well.. soon. LOL.
https://s.waze.tools/scrp.pnghttps://s.waze.tools/am.pnghttps://s.waze.tools/betc.pnghttps://s.waze.tools/beta.pnghttps://s.waze.tools/mapr.pnghttps://storage.googleapis.com/wazeopedia-files/7/74/Waze_signature_200k_plain.pnghttps://s.waze.tools/c5s.png
• AM: Eastern Oklahoma, DFW, Southern Florida
• Wiki: WME | Editing Manual | Best Practices | FAQ | Places
• T-Mobile | iPhone 14 Pro | iOS Latest | Waze Latest Beta
• AM: Eastern Oklahoma, DFW, Southern Florida
• Wiki: WME | Editing Manual | Best Practices | FAQ | Places
• T-Mobile | iPhone 14 Pro | iOS Latest | Waze Latest Beta
And just like that, more bugs squashed. That SHOULD be all of them.
2019.07.24.01
2019.07.24.01
Code: Select all
2019.07.24.01: BUGFIX: Further refinement of unstacking and selection.
CHANGE: Future deprecation of properties for countries and states.
https://s.waze.tools/scrp.pnghttps://s.waze.tools/am.pnghttps://s.waze.tools/betc.pnghttps://s.waze.tools/beta.pnghttps://s.waze.tools/mapr.pnghttps://storage.googleapis.com/wazeopedia-files/7/74/Waze_signature_200k_plain.pnghttps://s.waze.tools/c5s.png
• AM: Eastern Oklahoma, DFW, Southern Florida
• Wiki: WME | Editing Manual | Best Practices | FAQ | Places
• T-Mobile | iPhone 14 Pro | iOS Latest | Waze Latest Beta
• AM: Eastern Oklahoma, DFW, Southern Florida
• Wiki: WME | Editing Manual | Best Practices | FAQ | Places
• T-Mobile | iPhone 14 Pro | iOS Latest | Waze Latest Beta
I have replied to a PM from GabiruX_. I believe they are going to work on the pt-BR translations. Please get with them and if they would like assistance, I will be happy to give you edit access to the translations and comment list.edu_scott wrote:Can pt-BR be added, please?
I want to test the script
Thank you!
https://s.waze.tools/scrp.pnghttps://s.waze.tools/am.pnghttps://s.waze.tools/betc.pnghttps://s.waze.tools/beta.pnghttps://s.waze.tools/mapr.pnghttps://storage.googleapis.com/wazeopedia-files/7/74/Waze_signature_200k_plain.pnghttps://s.waze.tools/c5s.png
• AM: Eastern Oklahoma, DFW, Southern Florida
• Wiki: WME | Editing Manual | Best Practices | FAQ | Places
• T-Mobile | iPhone 14 Pro | iOS Latest | Waze Latest Beta
• AM: Eastern Oklahoma, DFW, Southern Florida
• Wiki: WME | Editing Manual | Best Practices | FAQ | Places
• T-Mobile | iPhone 14 Pro | iOS Latest | Waze Latest Beta
Replied to your PM. Sorry it took so long to get back to you!GabiruX_ wrote:Yes, we can help on. I already have translation to this old script.edu_scott wrote:Can pt-BR be added, please?
I want to test the script
Thank you for offering to help!
https://s.waze.tools/scrp.pnghttps://s.waze.tools/am.pnghttps://s.waze.tools/betc.pnghttps://s.waze.tools/beta.pnghttps://s.waze.tools/mapr.pnghttps://storage.googleapis.com/wazeopedia-files/7/74/Waze_signature_200k_plain.pnghttps://s.waze.tools/c5s.png
• AM: Eastern Oklahoma, DFW, Southern Florida
• Wiki: WME | Editing Manual | Best Practices | FAQ | Places
• T-Mobile | iPhone 14 Pro | iOS Latest | Waze Latest Beta
• AM: Eastern Oklahoma, DFW, Southern Florida
• Wiki: WME | Editing Manual | Best Practices | FAQ | Places
• T-Mobile | iPhone 14 Pro | iOS Latest | Waze Latest Beta
I'll send you a PM as well. I received a PM from aamazotr about Spanish - Ecuador. I can add that as a separate Comment List for sure. Would you be assisting in maintaining this list as well? Or just Spanish - Colombia?mincho77 wrote:Hi guys, I'm back on it, how can I get access to correct some bugs on Spanish Colombia texts and add some more on excel file, Im the owner of the old translation? and how can I ask to add a dictionary for Spanish Ecuador ?
Also, does Spanish - Colombia and Spanish - Ecuador both use the "Espanol - Latin America" WME language setting?
Thank you for offering your assistance!
https://s.waze.tools/scrp.pnghttps://s.waze.tools/am.pnghttps://s.waze.tools/betc.pnghttps://s.waze.tools/beta.pnghttps://s.waze.tools/mapr.pnghttps://storage.googleapis.com/wazeopedia-files/7/74/Waze_signature_200k_plain.pnghttps://s.waze.tools/c5s.png
• AM: Eastern Oklahoma, DFW, Southern Florida
• Wiki: WME | Editing Manual | Best Practices | FAQ | Places
• T-Mobile | iPhone 14 Pro | iOS Latest | Waze Latest Beta
• AM: Eastern Oklahoma, DFW, Southern Florida
• Wiki: WME | Editing Manual | Best Practices | FAQ | Places
• T-Mobile | iPhone 14 Pro | iOS Latest | Waze Latest Beta
Great idea! If you think about it, could you add it as a feedback on the GitHub page for URC-E?dfortney wrote:dbsooner, thank you for the script - it is having a positive impact on the community and Wazers everywhere!
Now, for the inevitable Feature Request: I find myself scrolling down to turn off UR filtering in the settings tab — I’d love to see that more prominent. I keep a bunch of filters active but in certain editing situations I want to quickly “see it all”
https://s.waze.tools/scrp.pnghttps://s.waze.tools/am.pnghttps://s.waze.tools/betc.pnghttps://s.waze.tools/beta.pnghttps://s.waze.tools/mapr.pnghttps://storage.googleapis.com/wazeopedia-files/7/74/Waze_signature_200k_plain.pnghttps://s.waze.tools/c5s.png
• AM: Eastern Oklahoma, DFW, Southern Florida
• Wiki: WME | Editing Manual | Best Practices | FAQ | Places
• T-Mobile | iPhone 14 Pro | iOS Latest | Waze Latest Beta
• AM: Eastern Oklahoma, DFW, Southern Florida
• Wiki: WME | Editing Manual | Best Practices | FAQ | Places
• T-Mobile | iPhone 14 Pro | iOS Latest | Waze Latest Beta
1. We do have a casual time of day, but it is in reference to when the drive happened (report was made). I can add the option to add a salutation based on time of day. It will be a variable that can be added to the responses. Similar to all the others.vince1612 wrote:So when URC-E came out I asked to make 3 lists and since then I'm a bit ashamed to admit that I didn't take much time to dive into them much. I'm very late to the party
Partially because I've been much more used to the french script "WME UR responses types" by seb-d59 until now and kept using it for a long time, but it's only in french and is not really adapted for a multi-lingual community. So I am now (finally) making it my goal to complete URC-E lists this week and switch to this script with our community. I just have 2-3 questions/feature requests which I couldn't figure out by a quick-reading of this thread or the master sheet.Thanks and looking forward to get things running with URC-E.
2. That's a little more in depth. As a starting point, I would suggest grouping your responses together in "groups" based on common UR types, or issues. Maybe in the future, I can add tagging to responses to allow the list to be filtered based on the tags collated to the UR type. But that would be a future thing.
3. Auto switching is setup "per list". There is a tab in the URC-E Master Control sheet that lets us specify a given lists area. The area can be an entire state (if the country support it) or country. If auto-switching is enabled for a user, and they click a UR in a state/country that has a list associated with it, the list is automatically changed to the one specified for that state/country. Then switched back if they open a UR outside that area.
If you have a list that you would like to have setup as a default for a given state or country, let me know.
https://s.waze.tools/scrp.pnghttps://s.waze.tools/am.pnghttps://s.waze.tools/betc.pnghttps://s.waze.tools/beta.pnghttps://s.waze.tools/mapr.pnghttps://storage.googleapis.com/wazeopedia-files/7/74/Waze_signature_200k_plain.pnghttps://s.waze.tools/c5s.png
• AM: Eastern Oklahoma, DFW, Southern Florida
• Wiki: WME | Editing Manual | Best Practices | FAQ | Places
• T-Mobile | iPhone 14 Pro | iOS Latest | Waze Latest Beta
• AM: Eastern Oklahoma, DFW, Southern Florida
• Wiki: WME | Editing Manual | Best Practices | FAQ | Places
• T-Mobile | iPhone 14 Pro | iOS Latest | Waze Latest Beta
Re: [Script] URComments-Enhanced (URC-E)