开云体育

Drew Derbyshire wrote:
> Fish wrote:
>
> > Windows has always provided full backward compatibility
> > in all versions of their operating system, allowing programs
> > written for/on older versions of Windows to continue to run
> > perfectly fine on future/newer versions of their operating
> > system.
>
> This is incorrect.? They dropped 16-bit support years ago.

Fine.

Windows has always provided full backward compatibility in all versions of their operating system for the same machine (hardware) architecture, allowing programs written for/on older versions of Windows of the same machine (hardware) architecture to continue to run perfectly fine on future/newer versions of their operating system of the same machine (hardware) architecture.

Better?

My point is, they provide a set of operating system APIs that well written programs are supposed to use in order to do certain Windows type things (like painting a window or drawing a widget, etc), but NOW, when your program *uses* those provided functions that you're supposed to use to perform those typical Windows things, they no longer work correctly.

THAT is a first for Microsoft and Windows. They've never done that before.

My software behaved perfectly fine on all versions of Windows from Windows 7 up to Windows 10. But NOW, suddenly and unexpectedly, starting with Windows 11, to both my and my customers' consternation, that's no longer true. NOW, starting with Windows 11, my well written program that painted its windows and displayed its dialogs just fine on previous versions of Windows, fucks up and paints incorrectly, even though I'm following THEIR RULES for how windows and widgets and supposed to be painted.

THAT *sucks*, and *REALLY* pisses me off!? >8-<

--
"Fish" (David B. Trout)
Software Development Laboratories

mail: fish@...