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 16:30:58.558236+00 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 06:27:58.012006+00 by: spc476

Perhaps because the app is written in a bloated environment?

#Comment Re: before the screen is finished rendering made: 2018-10-30 17:09:15.75539+00 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.


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

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

Add your own comment:

(If anyone ever actually uses Webmention/indie-action to post here, please email me)

Format with:

(You should probably use "Text" mode: URLs will be mostly recognized and linked, _underscore quoted_ text is looked up in a glossary, _underscore quoted_ (http://xyz.pdq) becomes a link, without the link in the parenthesis it becomes a <cite> tag. All <cite>ed text will point to the Flutterby knowledge base. Two enters (ie: a blank line) gets you a new paragraph, special treatment for paragraphs that are manually indented or start with "#" (as in "#include" or "#!/usr/bin/perl"), "/* " or ">" (as in a quoted message) or look like lists, or within a paragraph you can use a number of HTML tags:

p, img, br, hr, a, sub, sup, tt, i, b, h1, h2, h3, h4, h5, h6, cite, em, strong, code, samp, kbd, pre, blockquote, address, ol, dl, ul, dt, dd, li, dir, menu, table, tr, td, th

Comment policy

We will not edit your comments. However, we may delete your comments, or cause them to be hidden behind another link, if we feel they detract from the conversation. Commercial plugs are fine, if they are relevant to the conversation, and if you don't try to pretend to be a consumer. Annoying endorsements will be deleted if you're lucky, if you're not a whole bunch of people smarter and more articulate than you will ridicule you, and we will leave such ridicule in place.

Flutterby™ is a trademark claimed by

Dan Lyke
for the web publications at www.flutterby.com and www.flutterby.net.