Userscripts.org

Please take a look at this link: Here the script makes it impossible to click the "enlarge" ("vergrößern") link for the main picture, since the outline area marking the "next page" image overlaps with it and links to the next page. I worked around that by adding that site to the exclusion list (which is OK for me), but after each update I have to add this exclusion again. A fix would be fine - marking the site in the script by @exclude until you find time for a real solution would be OK (for me) as well.

TIA,
Izzy.

Thank you for your fast response! I was aware of the fact there may be no easy way to create a "general fix" (which is why I suggested to temporarily @exclude this domain - but due to the "stable state" and "not to many updates", I can do so from the GM script manager). Will not be easy to automatically detect possible causes to this kind of trouble.

But maybe I though can make some suggestions:
1) would be to move the configured variables out of the script, so they won't be overwritten on updates. Since all affected settings here are scalars, this can be achieved easily - just have a look at this guide.
2) is to add a new setting for a minimal size for an image to be considered. I see no good reason to consider 1x1px images here: First, they are far to small to be seen if not enlarged (sure, if you add a border you will notice) - and when they're enlarged, they do not contain any "information" you can tell. Second, they are usually placeholders ("spacers") only, and thus are not even intended to carry any information. I'd even go so far to count all images having less than 5px wither width or height in this category - but setting it to "2" for sure is on the safe side.

Oi. For 1), please look here. I could not resist, so I already fulfilled my own request. Guess you will like it (much more user friendly). Only changed things above the "code section". After installing it (and reloading the page), just check your GM user scripts menu for an entry to invoke the configuration screen.

Take over the code if you like it

As for 2), shouldn't check_min_edge have prevented this with its default of 20px?

Crend King wrote: usually things go on the opposite way, i.e. they get popular after you make it easier to use. I may make some change later.

However, concerning the second issue there's a little (temporary) drawback: GM_config doesn't allow you to store a zero (0) as integer. I'm the author of the GM_config extender, and also work on the basic GM_config script together with its main authors Joe and Sizzle - so I sent a fix to Joe already who "owns" the script here at USO, so he hopefully publishes it soon.

check_min_edge is the variable you want. However, currently it only check the target geometry, not the source.

Crend: On your last update, you increased the version number in the change log (1.3.3) - but not in the MetaData (still 1.3.2). Since I don't think this was done on purpose, I thought I drop you a note

You're welcome!
Btw: If you need any help with the UI, feel free to contact me. Remember I'm the author of the GM_config Extender - so if you miss something, I can probably help. Moreover, Joe already fixed the issue with the zero mentioned above and published an update of GM_config, so everything is ready
And if you want to include my GM_ScriptUpdater, just let me now and I adapt the code on pastebin (including a hook into the GUI to adjust the update check interval plus to "check for updates now")...

Crend, I just updated the snippet at PasteBin to match the latest release. All you had to do to integrate the UI is to replace the "preference section" with the code from there (and, of course, include the two @require statements). So it's a matter of 2-5min at maximum.

To give you some idea (and make you hungry, hopefully):

Of course, tootips are displayed when hovering an option...