Well, here is the DIB engine that a couple of people at TransGaming (mostly David Hammerton, I think) did some work on a while ago, I finally got around to review it and make sure it compiles against the current ReWind (though perhaps it needs a few tweaks to compile against Wine). It's not all that complete by any means, but we wanted to get it out there, so feel free to comment on it (or even apply it to Wine if it's good enough).

Primary attribution should go to Jonathan Meunier, a co-op student who worked with us earlier this year. David Hammerton, Peter Hunniset, and I all assisted with it to one degree or another.

If there is any general interest in pursuing DIB Engine work, we would of course appreciate it if developers are willing to license their contributions to ReWind.

Ove seems to have forgotten to include the documentation, which includes some nice background on DIB issues in general, and should go into the documentation directory.

• Drawing of lines
• Partial drawing of ellipses
• Drawing of polygons (several of the implementations, such as Polygon, Polyline, etc)
• Filling of polygons (including patterns)
• Pattern blitting
• ROP2 and ROP3 engines

After removing such entries from system.reg:

| [Software\\Microsoft\\Windows\\CurrentVersion\\RenameFiles\\ProgramFilesRen] 976188522
| @="D:\\"
| "!$!$!$!$.pfr"="Program Files,1"
| "PROGRA~1"="!$!$!$!$.pfr"

it stops.

I noticed recently that Wine was able to do anti-aliasing for font sizes >16 although my Gnome 2 looked nice with anti-aliasing of <16. I started to look why Wine apps were only anti-aliased for >16, and I came across this:

--- dlls/x11drv/xrender.c.orig 2002-09-29 12:56:27.000000000 +0200
+++ dlls/x11drv/xrender.c 2002-09-29 12:56:56.000000000 +0200
@@ -322,7 +322,7 @@
assert(entry->nrealized == 0);


- if(antialias && abs(plfsz->lf.lfHeight * plfsz->xform.eM22) > 16) {
+ if(antialias && abs(plfsz->lf.lfHeight * plfsz->xform.eM22) > 8) {


pf.depth = 8;
pf.direct.alphaMask = 0xff;


When I changed this, my Notes was much nicer to work with. I presume there is a reason why anti-aliasing was off, but I would reconsider that decision. You can look for yourself on these 2 screenshots:

• http://dag.wieers.com/Screenshot-2.png
• http://dag.wieers.com/Screenshot-3.png

Especially look at the widgets.

Implementations of these and much more can be found in this patch submission, which was apparently never applied: http://www.winehq.com/hypermail/wine-patches/2002/06/0103.html

You can probably try to extract what you need from that patch if you want more rpcrt4 stuff.

OK, howsabout I slowly merge these in by hand, feeding them to you in chunks, kind of like Dimitrie's recent storm of ListView patches, and doing a little testing of my own along the way?

Auditing the server stuff may be a problem for me since I really don't grok that aspect of the system yet; but I can defer that for last and maybe by then I'll have an idea of what The Right Thing To Do is.

Hi folks,

Here's a quick status update on the listview.

Currently, the listview goes through a major cleanup. It is required -- the file is huge (over 10000 lines when I started, now it's 9200 with more features!), and has accumulated a lot of cruft over the last few years. This is very normal for such a complex control as listview, and we need to prep the code to add more features.

At the same time, I go over the code, review it for correctness, fix bugs, and implement the missing functionality. While it may look I do mostly code reorganizations, this is not the case: a lot of corner bugs have been fixed, functionality has been enhanced, code has been cleaned up, and simplified. Due to the cleaner code base, we are in a better position to fix problem, and add features.

The downside of all this is that (1) old bugs, and missing functionality is exposed, (2) new bugs are introduced. On top of it all, two major efforts were happening simultaneously: Guy's ICON mode work, and mine. Guy did a wonderful job at fixing some of the issues in ICON mode, unfortunately my changes interacted with his in a nasty way.

So we have some problems. I am aware of some of them, and I'm working to fix them. But it will take some time, as I trying to fix a problem, I see some cleanup that needs doing _before_ I work on the bug itself.

Currently, I am aware of the following problems:

• selection (clicking on items sometimes does not select them)
• drawing (focus, background, etc.)
• calculating item rectangles

If you are experience problems with the listview, I'd like to hear from you. If you want to help, some test cases will help quite a bit.