Evil wrote:
Dreamweaver's "Add Site" (and other) dialog are completely broken when
using the built-in comctl32.
OK, there is a patch that is in CrossOver that has not yet been
committed to WineHQ for some reason, that fixes this problem.
This was known way before I ever started using WINE
Vitaliy Margolen wrote:
...So having an option to use native comctl32 is not such a bad idea.
I couldn't agree more. I can't imagine that DreamWeaver's the only
program that's broken (or will be broken, as new features are added and
problems are worked out) when using the built-in impl
Duane Clark wrote:
Well the patch does improve the cursor. I can now see it. Although it
is only grey. It there any reason why the best cursor selection method
always checks for bits == 1. What about color cursors?
I don't really understand how the patch fixed things, but...
Riven uses a b
Kevin DeKorte wrote:
On Thursday 18 August 2005 03:24 am, Dripple wrote:
Hi,
I tested the patch submitted in
http://bugs.winehq.org/show_bug.cgi?id=3165 Bugzilla page with Notes.
Seems to fix the issue.
Regards.
Dripple.
Well the patch does improve the cursor. I can now see it. Although it
Paul Vriens wrote:
> the subject says it all. If yes, I will start adding some for the ones
IMHO that's a good idea.
--
By By ...
... Detlef
Felix Nawothnig wrote:
> > While rewriting the conformance-tests for winspool.drv, how should we
> > handle this bugs / features ?
> a) ...
> b) ...
> c) ...
> Disclaimer: These are my personal guidelines, so treat them as such. :-)
Thanks for your hints. I will change some Tests to trace, when
On Sun, 14 Aug 2005 17:53:33 +0400
Phil Krylov <[EMAIL PROTECTED]> wrote:
> this patch needs to be applied after the "Re: RICHED20: Implement
> EM_SETRECT, EM_SETRECTNP and WM_SETREDRAW messages (fixed)" patch.
>
> ChangeLog:
>
> Avoid flicker in RichEdit using proper update region invalidation
On Thursday 18 August 2005 03:24 am, Dripple wrote:
> Hi,
>
> I tested the patch submitted in
> http://bugs.winehq.org/show_bug.cgi?id=3165 Bugzilla page with Notes.
> Seems to fix the issue.
>
> Regards.
>
> Dripple.
Well the patch does improve the cursor. I can now see it. Although it is only
g
I suspect this may not be in Wine at all. There is currently a problem
that shows up both in and out of Wine with the cursor vanishing
permanently until reboot on some games that block or change the cursor.
This appears to be a problem in FC but I have not had time to track it
down.
Thursday, August 18, 2005, 12:10:39 AM, Mike McCormack wrote:
> Evil wrote:
>> I'm no longer able to run programs that require the native comctl32 and
>> commctrl DLLs, since updating to today's CVS. Could it be related to
>> these theme patches?
> You shouldn't need to use the native comctl32
Hi,
I tested the patch submitted in
http://bugs.winehq.org/show_bug.cgi?id=3165 Bugzilla page with Notes.
Seems to fix the issue.
Regards.
Dripple.
Andreas Mohr wrote:
Just to verify: are you sure that you're
*either* running both commctrl.dll and comctl32.dll as native
*or* both commctrl.dll and comctl32.dll as builtin?
Otherwise it *will* fail, with a thunk error similar (or equal?) to above.
Yes, using both native is when I get the
Mike McCormack wrote:
You shouldn't need to use the native comctl32 any longer. Please
update your dll overrides to "comctl32" = "builtin".
Wine's comctl32 implementation is almost complete. If there's bugs
with the builtin comctl32 then please help us by reporting them rather
than sweepin
Detlef Riekenberg wrote:
I wrote a Commandline-Program for testing the Printing-API and found
many misterious behaviour.
While rewriting the conformance-tests for winspool.drv, how should we
handle this bugs / features ?
There are several types of undocumented behaviour:
a) The documentation
14 matches
Mail list logo
