3 ms·
Apps could draw directly to DC, but it flickered a lot, and everyone quickly ended up with CreateCompatible{Bitmap,DC} and blitting into BeginPaint’s DC after d
by wruza 6y ago
Apps could draw directly to DC, but it flickered a lot, and everyone quickly ended up with CreateCompatible{Bitmap,DC} and blitting into BeginPaint’s DC after drawing. After all, at win95 you had 4 to 8 megabytes or RAM - you definitely had the space. Not sure when it happened, but I can remember fighting with flicker circa 97. Also, rectangular controls were what you had in standard winapi, which was based on HWNDs, which were rectangular-only. I don’t think that unroundness was really forced by hardware constraints (transparency - yes), it was just a default simplest flavor of time. (And not that I like round/flat/text-only controls. What we called “flat” back then is pretty 3d-bordered in modern terms, and what we called “round”, today is border-radius:3px)
- acdha 6y ago4-8MB wasn’t all that much if you were running more than one app at >640x480x256. It was certainly possible but fancy visual effects were going to exclude a lot of low-end hardware, which is what a LOT of mainstream users bought since hardware cost a good but more back then and the value proposition was less established. I agree that roundness wasn’t prohibitive in general. The rectangular nature of the APIs encouraged it but you certainly saw it in applications. What I was thinking about most was complex usage where there was overlap outside of the active context (e.g. dragging a window with the expectation of a lower layer showing around the curve, rather than either not having that or being able to assume a solid fill color) or interfering with hardware accelerated painting or later video decoding which only worked in rectangular regions.