Page 30 of 54
Re: UrComments
Posted: Wed Dec 31, 2014 12:36 pm
by rickzabel
sorry i missed your first message,
how are you attempting to get it to work in Brazilian? are you using the custom comments file?
if you edited my main script and have an error the script will not load, try reinstalling the script with out editing and see if it loads.
Re: UrComments
Posted: Wed Dec 31, 2014 1:57 pm
by rickzabel
walbing wrote:oh yes in Spanish!
if you are willing to translate the list into Spanish contact me directly and i will explain how.
Re: UrComments
Posted: Wed Dec 31, 2014 2:56 pm
by rickzabel
Murilo-Carvalho wrote:I am not sure if there is any incompatibility, but I am also running the AutoUR script....
I will try to disable it and let you know.
I sometimes use auto ur side by side with UR Comments. since the WME update Auto Ur has not been working, supermedic is working on a fix.
I think your problem was my fault I uploaded a version with a missing comma. Try to force a update or reinstall at greasyfork.
Re: UrComments
Posted: Wed Dec 31, 2014 3:11 pm
by rickzabel
Murilo-Carvalho wrote:
Is there any specific step I should do?
lots of very specific steps, step one message me on gmail @ rickzabel
Re: UrComments
Posted: Wed Dec 31, 2014 4:01 pm
by rickzabel
walbing wrote:Oh sorry for write in spanish
no download link yet we are working on it today.
Re: UrComments
Posted: Thu Jan 01, 2015 3:07 am
by rickzabel
PesachZ wrote:How about making the language selectable, or automatic based on the wme language? Just a thought, instead of maintaining different scripts
the main purpose in having separate language files is so that the creator can update their file whenever they need. If i included each language all of the changes would have to go trough me which sounds like more of a pain for everyone.
Re: UrComments
Posted: Thu Jan 01, 2015 3:20 am
by rickzabel
PesachZ wrote:At least to translate the displayed text in the main script (like settings, tool tips,...)
i was thinking about this also, we did not know if the script would work correctly in other areas. so i did go as far with converting it. once we have a bit of testing done i think we should set up a way to convert the text.
Re: UrComments
Posted: Thu Jan 01, 2015 5:28 pm
by rickzabel
bz2012 wrote:Feature request:
I often 'scan' an area by scrolling and handling URs as I come upon them.
It is nice to zoom in and see the UR area in detail, but after I handle the UR, I want to be back at the same zoom setting and see the same area that I saw before I opened the UR.
I changed the way the script zooms out to work this way. I should be posting a new version in a day or so.
Thanks again for a very useful extension.
thanks i am glad people are finding the script useful!
Re: UrComments
Posted: Sun Jan 04, 2015 8:26 am
by rickzabel
dmcrandall wrote:It's very useful. How would one go about editing the custom list? Does it need to be opened in a word processor, or some other program, or is it a text file to edit?
I don't want to mess something up.
Install and edit this file directly if you wish to use your own comments.
https://greasyfork.org/en/scripts/6236- ... stom-list/
then choose custom under settings
bz2012 wrote:I edited mine by opening the javascript module in tamper monkey, selected the contents, copied them, pasted them into Notepad++ and saved as a text file with .js on the name (to let Notepad know it was in js format), then I went through and made the changes I wanted, and did a copy/paste onto the opened script in tamper monkey and did a save. When I reloaded the WME window, the changes showed up.
I am sure I could have just made the changes directly in tamper monkey, or operated on a saved copy of the .js file with any text editor, but I wanted to have an editor I was familiar with to do my editing.
Hope that helps.
as long as this was in the custom file you will be ok. if you did this to the main script it will be overwritten the next time i update, or you will not get updates.
Re: UrComments
Posted: Mon Jan 05, 2015 11:03 am
by rickzabel
shawndoc wrote:One suggestion: On the stock response to Turn Not Allowed reports, add something along the lines of "And why?" I find more often then not the turn the person is complaining about can be determined with some accuracy, but why the person thought the turn is not allowed is not.
i will relay your suggestion, thanks!