network profile
| bio | website | |
|---|---|---|
| location | London, United Kingdom | |
| age | 31 | |
| visits | member for | 8 months |
| seen | Feb 6 at 22:26 | |
| stats | profile views | 1 |
Software engineer, 5+ years
|
Sep 23 |
awarded | Good Answer |
|
Sep 9 |
comment |
Why are progress bars horizontal? @BrendanBerg We're getting off-topic here, but Bresenham's algorithm is fast at calculating the pixels that make up the line segment. It has nothing to do with actually writing those pixels. |
|
Sep 9 |
comment |
Why are progress bars horizontal? @BrendanBerg read this, it can mean either waiting minutes for your calculation to finish or seconds: en.wikipedia.org/wiki/Row-major_order. Video memory is row_major so if you try to write to it in column_major style you'll see a degradation in performance. |
|
Sep 9 |
comment |
Why are progress bars horizontal? @AndroidHustle The line of thought for who? Ancient programmers who had 64k RAM to work with, and thus had to squeeze more functionality out of less CPU instructions as their executable's size was limited? |
|
Sep 9 |
comment |
Why are progress bars horizontal? @BrendanBerg How is it untrue? On a 32-bit CPU for example, you could write 4 pixels in one instruction (in 256 colour mode) if you blit horizontally. If you go vertically each pixel has to be dealt with separately. Of course, on new machines with GPUs this is no longer an issue, however my post talked about the legacy reasons. |
|
Sep 7 |
awarded | Nice Answer |
|
Sep 7 |
awarded | Teacher |
|
Sep 7 |
answered | Why are progress bars horizontal? |
