http://bugs.winehq.org/show_bug.cgi?id=421
--- Comment #380 from max@veneto.com 2010-08-30 10:53:21 CDT --- (In reply to comment #379)
I tried it with SolidWorks, with hope that it would solve some performance issues with toolbar refresh and left panel display, but unfortunately it doesn't change anything. I didn't notice any improvement in general responsiveness during 3D modelling.
But there is at least one positive effect : geometric constraints in solidworks sketches are shown with little blue-background icons. With dibengine on, they are displayed correctly, but without, they are completely garbled.
And a negative point : icons in CSG (left panel) are partially black. It doesn't seems to be directly related to transparency, as the black area is not exactly the transparent area of the icons, but maybe it is related to an offset problem with alpha channel ?
The toolbar refresh slowness (which has also to some extent Autocad) depends (I guess) of app's mixing of DIB and DDB ops. Not solvable by current state of the engine, it should handle DDB directly too without having to convert to an forth, so co-operate with wineX11.drv internals which, because of being an "external" part of wine (and, mostly, because I don't want to rebase it on each change in winex11 !) it can't do now.
About the transparency, I've noticed that one too, but I have no time right now to investigate it in depth. It should be something trivial, indeed.... Maybe on next months, but I'm not motivated anymore to do hard development on DIB engine now. AutoCad works and that was my urgent problem. I lost the hope to see the engine into mainstream some time ago....
About the constraints, I'm happy to hear that :-) I've seen that the engine, in some graphic parts, pass more tests than wine GDI itself :-) I also have an app that behaves (graphically) better with the engine than without, but usually it's the opposite, the engine has still some missing points.
Ciao
Max
-
wine-bugs＠winehq.org