Hi all, great thread, lots of good info. One question: on the old site I used the two mmmturkeybacon scripts to calculate both pending earnings as well as "approved (pending payment)" earnings. Is there any equivalent right now? HITdb isn't really a solution for me since I work on different computers at different times. I found it really useful to be able to refresh those two controls anytime and get a snapshot of what I had coming in.
Unless the Worker site has changed anything else that might've broken it, my monkey patch script fixes Hit Finder Beta as well as any other script that breaks when hit_requirements turns up undefined as a result of Worker changing it to project_requirements: https://greasyfork.org/en/scripts/36308-monkey-patch-the-worker-data-changes Any simple script-breaking variable name changes will be added the same monkey patch.
Hi, New to this forum but turking since August 2012. This forum was mentioned frequently in Discord where I ended up after mturkforum. I've been using Mturk Suite for almost a year, but don't like the look of HitFinder. I miss the colors which seemed much easier to read. I downloaded Hit Scraper but can't get it to work. Someone at Discord mentioned Forker, but I can't get that to work either. Does Forker only work in Chrome? I have HitFinder up in Chrome because I like the logged hits feature and thought I would run something else in Firefox. Any suggestions?
How feasible would it be for a script to place the HIT search bar on all the various worker pages (similar to the way the Queue Header Link script places a link to your queue there all the time)?
I feel like an ass, but has there been a replacement for return & accept? https://greasyfork.org/en/scripts/5053-hit-return-accept
What WWW scripts do people miss that they want to see work on the WORKER site? Consider this a hypothetical and not an intention to have said scripts made. Some of the scripts that I had up on greasyfork are in the process of being redone. One of the scripts unique to WORKER is to make the titles (and requester names) fit instead of being cut off. https://greasyfork.org/en/scripts/36951-maketitlesfit
I got it to look like this by loading the page maximized at 100% zoom in 1080p, then sizing down the window: React says: YOU MUST CONSTRUCT ADDITIONAL PYLONS MUTATIONOBSERVERS
Zooming does cause issues, but at 100% or smaller, it should be fine. However, if you do zoom, just refresh and it may or may not be okay depending on the zoom level.
No, I didn't have to zoom to break it. I just opened the window with a large viewport and then shrunk the window space.
Right. Refreshing after fixing fixes it. It's React changing (or in this case, not changing) the height of the row. That's why I said "You require more MutationObservers." (Worker needing MutationObsevers is basically a meme right now, regardless of whether or not you actually need them specifically for this.)
Here, adding this (basically your code without jQuery, but in an event listener listening for resize events) fixes the issue: PHP: window.addEventListener("resize", e => { let allTitles = document.querySelectorAll("span.project-name-column.text-truncate, span.requester-column.text-truncate"); for(let title of allTitles) { if(title.parentElement.clientHeight < title.clientHeight) { title.parentElement.style.height = `${title.clientHeight}px`; } }}); You might want to convert it to the jQuery equivalent to keep it stylistically equivalent. Since I'm not a professional web developer who needs to polyfill IE6 compatibility, I have the luxury of being able to avoid jQuery wherever possible.
If I add that to the script (or separate script), do you want me to credit you with a comment where the code is? If so, how should I do the crediting? Credit: Totally Not , @ TurkerHub
You can if you want, but it's no big deal. It's basically just your short script inside of an event listener.
