On Fri, 31 Mar 2000, Ove Kaaven wrote:
On Fri, 31 Mar 2000, Joshua Thielen wrote:
After checking out the memory leak, I think I've narrowed it down to this code
snippet:
---in main.c---
hMemDC = CreateCompatibleDC( hdc );
SelectObject (hMemDC, p_board-hMinesBMP);
BitBlt( hdc,
Hallo,
with win31 style, the Get[Save|Open]Filename widget for a long
directory path writes the whole sting in the field allocated for
Directories. The Text often extends into the area with the "Open" and
"Cancel" buttoms and doesn't get erased when the directory is changes.
What function is
Hello everybody,
I'm sorry, the patch I just sent should be applied to Peter's patch, not
necessarily the CVS, because I can't actually get to the CVS. His patch
reduces the number of Create and DestroyDC's (thanks, Peter :) so the
memory leak is reduced by 80% or so, but not eliminated . Also,
gerard patel wrote:
Maybe it would be a good thing to add some test for too big values in
dump_bytes if the ultimate reason for the crash can't be fixed.
Did this patch never get in? I'm still in windows : ( so I can't check.
Joshua
--- server/trace.c.old Thu Mar 9 16:24:53 2000
+++
In message "Re: fw:winemine patch", you write:
snip
my machine (PII 350). BTW, it's best if you send your patches to
[EMAIL PROTECTED] because that way people (like you and me) who can't
get at the CVS can still apply them.
Yes well, I don't like my mailbox filling up with patch submissions
I have the debugger starting in its own xterm (or rxvt,...)
there are (at least) two issues that need to be fixed:
A] the command line for starting the debugger is read from the registry (something
like "xterm -T WineDebugger -e winedbg pid hEvent)
(read
On Sat, 1 Apr 2000, Eric Pouech wrote:
I have the debugger starting in its own xterm (or rxvt,...)
there are (at least) two issues that need to be fixed:
Any chance this can work on a console and not require an xterm? I'm
kind of GUI challenged and tend to get tangled up trying to debug
