Flutterby™! : before the screen is finished rendering

Next unread comment / Catchup all unread comments User Account Info | Logout | XML/Pilot/etc versions | Long version (with comments) | Weblog archives | Site Map | | Browse Topics

before the screen is finished rendering

2018-10-29 17:30:58.558236+01 by Dan Lyke 3 comments

Here’s how to avoid problems with straight-ticket voting in Texas:

But according to the Texas secretary of state’s office, the voting machines are not at fault. Rather, the problems reported are the result of “voters hitting a button or using the selection wheel before the screen is finished rendering,” which de-selects the pre-filled candidate selection.

"before the screen is finished rendering". What the fuck century are we living in that a screen of a couple of candidate choices is taking longer to render than a display refresh?

[ related topics: Graphics ]

comments in ascending chronological order (reverse):

#Comment Re: before the screen is finished rendering made: 2018-10-30 07:27:58.012006+01 by: spc476

Perhaps because the app is written in a bloated environment?

#Comment Re: before the screen is finished rendering made: 2018-10-30 18:09:15.75539+01 by: Dan Lyke

As someone currently fighting with drag and drop on Cocoa, on a 2018 MacBook Pro that has how many thousands? Millions? more cycles per second than the machines I learned to program on: Oh hell yes on bloated environments. Ugh.

Others have suggested that the whole thing looks like a WinCE device...

I remember when we thought that Emacs was bloated.

Sigh.

#Comment Re: before the screen is finished rendering made: 2018-11-01 02:18:51.409685+01 by: DaveP

Hey, making emacs feel svelte and responsive is quite a trick!