Skip to main content

So I got crashed out by blinkinglights. Hard. Major flicker fail, only using my phone in dim red mode and going to stick the eink back on the laptop for safety so I can work for a few days at least. Or maybe forever; I shouldn't have to take that kind of risk.

Cause? The official flutter documentation website. It hit a render glitch with one of the inline sample displays and the whole page started doing a rapid black/white jitter; bad enough I had to block my vision to move well enough to find a key to shut it off.

The fact we can't (apparently; if you know a way, I want to hear it!) filter at the window manager or display level to Never Do That is a technological abomination.

Mina reshared this.

d.rift :fire_blue:
d.rift :fire_blue:  
•
@thegibson Seriously. What do I have to code or who do I have to pay to be able to safely use a screen instead of being one piece of bad code away from curled up on the floor. Because putting that power in the hands of every JavaScript developer on the planet doesn't please me.
@The Gibson
d.rift :fire_blue:
d.rift :fire_blue:  
•
@thegibson Some of us really can get punched through the internet. :/
@The Gibson
‏:neocat_floof_happy: ‎lexi
‏:neocat_floof_happy: ‎lexi  
•
wait, is there seriously no software out there that can detect flickering and automatically hide it?? that should be only a couple of lines of code if you have a screen capture library, how is that not a thing already
d.rift :fire_blue:
d.rift :fire_blue:  
•
@lexi ikr?! If I knew where in the pipeline to insert it I'd be on that like lightning. Pretty sure it'd be closer to 100 lines all told, but, still trivial effort relative to the risk flicker poses to segments of the population. People shouldn't be at the mercy of render glitches.
@‏:neocat_floof_happy: ‎lexi
silverwizard
silverwizard  
@d.rift :fire_blue: @The Gibson I gotta admit, I just assumed that there was a way to update the refresh differential or something. I assumed that would exist. Though, of course, it's possible/likely it's hard. But wtf.
@d.rift :fire_blue: @The Gibson
d.rift :fire_blue:
d.rift :fire_blue:  
•
@silverwizard @thegibson just disallowing fast refresh would cause a lot of artifacts, but there would be ways to do proper detection in real-time and only freeze sections of the screen that were actually trying to do something dangerous. Just have to get in the right point in the render pipeline... It is a stunning oversight though, given this is a long known safety issue.
@The Gibson @silverwizard
silverwizard
silverwizard  
@d.rift :fire_blue: @The Gibson Yeah, that makes sense. I assume it's a differential per region, but I dunno.
@d.rift :fire_blue: @The Gibson
⇧