Trevor Gentry

Alright, got it! Again, sorry about that. I had no idea. I'll get that done tonight.

I created the report. I don't have knowledge on how to go about fixing it. I can only further report that the bug is still present. People with further knowledge can test more in depth and share their results. That's the point. But it doesn't mean the report itself needs to be passed around like a game of tag. Those who have more information to share will share it either way without introducing that unnecessary complication. If the report goes inactive it is not my fault alone, nor should the reporter be expected to be held responsible for keeping the information up to date. It is a community effort. I brought attention to it, others confirmed its existence, etc. You can't actually expect me to have spent more than ten years doing... something here with this when the developers behind the code haven't even gotten to it during that amount of time. That's absurd.

If it works differently here somehow and being the reporter grants me some sort of tools I haven't been using then by all means hand it to someone who's better equipped. But if I'm supposed to be occasionally updating the OP with the information in the comments and it is on me to keep it up to date then I wasn't aware that responsibility was mine, I apologize, and I'll get right on that after work today.

I'm right here. I've been following along the entire time. There just isn't any additional information I can add beyond repeating that it's still not working correctly.