On Thursday 25 May 2006 20:51, Saulius Krasuckas wrote:
> BTW, now the issue is seen on my box too. Heh, it reminds my of my own
> bugreport [*]. Could this be related, Troy?
>
>
> [*] http://bugs.winehq.org/show_bug.cgi?id=5248
No, your problem is definitely different.
--
Troy Rollo - [EMAIL
On Thursday 25 May 2006 19:47, Huw Davies wrote:
> Nice catch! This should fix it.
Indeed it does.
--
Troy Rollo - [EMAIL PROTECTED]
* On Thu, 25 May 2006, Saulius Krasuckas wrote:
> I'am running wine from a local src tree, so I had to compile this way:
>
> $ tools/winegcc/winegcc -Btools/winebuild/ -B/usr/bin/ -g sysfont.c -Ldlls
> -Llibs -Iinclude -mwindows
Sorry, -B/usr/bin is a leftover from my experiments and isn't neede
On Thu, May 25, 2006 at 04:49:04PM +1000, Troy Rollo wrote:
> The attached sample program demonstrates a bug in font handling that can lead
> to corrupted fonts. Compile with "winegcc -g sysfont.c -lgdi32 -lcomdlg32".
> Run the resulting a.out, and you will see the letter "C" in the top left
> c
* On Thu, 25 May 2006, Troy Rollo wrote:
> The attached sample program demonstrates a bug in font handling that can
> lead to corrupted fonts. Compile with "winegcc -g sysfont.c -lgdi32
> -lcomdlg32".
I'am running wine from a local src tree, so I had to compile this way:
$ tools/winegcc/winegcc
The attached sample program demonstrates a bug in font handling that can lead
to corrupted fonts. Compile with "winegcc -g sysfont.c -lgdi32 -lcomdlg32".
Run the resulting a.out, and you will see the letter "C" in the top left
corner of the window, rendered in the system font. Click anywhere in
