Sorry to sound like a stuck record but the Wine website still lists "write a DIB engine" as a requirement, and every time someone does, the patches dissapear down a hole because they're "not right". Someone document what "would be right", or take "write a DIB engine" off the list. I'd love to have a go at documenting it myself, but I don't have the time to reverse engineer it from a few years' worth of rejected solutions.
The latest attempt of Massimo Del Fedel satisfied all requirements set previously for the long standing bug 421 and his optional engine seems to work fine by all Wine quality standards. He seems to be extraordinary stubborn and insusceptible to mobbing. Usually it is extremely frustrating for developers when the goal post is constantly moved. When is the right time that project members should fork when their chief maintainer does not respond anymore or pursues an adverse commercial agenda?"
Because you're above average. Just like everybody else.
...programmer building up its resume.
I always knew programmers weren't human.
I know for some reason
What? You might want to read up on NewYorkCountryLawyer's contributions.
A penny saved is a penny to squander. -- Ambrose Bierce