- Original Message -
From: "José Manuel Ferrer Ortiz" <[EMAIL PROTECTED]>
>
> > Do you plan to translate other programs and dlls
> > that still they lack?
>
> Probably, if I have enough spare time (I'll have two
> exams in September).
I think about evaluating the use of all the necessary
s and dlls that still they lack?
- Original Message -
From: "José Manuel Ferrer Ortiz" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Friday, August 15, 2003 3:40 PM
Subject: Spanish translation of winemine
> Hi, I've translated the winemine program into S
hen I try to port a small application sample provided by winelib user's guild> > enter winemine directory, type:> > $winemaker -lower-uppercase .> $./configure -with-wine=/usr/local/wine> $make> > It shows error when I run the second command ./configure> > I get the error:>
> Better, why not help make Linux as nice as MacOS, then you wouldn't need
> to go to all this hassle in the first place.
In that case, why not just install Windows, it would prevent us all the
hassle to develop Wine :-)
Lionel
--
Lionel Ulmer - http://www.bbrox.org/
On mercredi, juil 16, 2003, at 14:42 Europe/Paris, Mike Hearn wrote:
PS : I would like to know if the color of winemine are the colors
which
are supposed to be, thanks.
Why don't you just install Linux/PPC, I think that would make this
stuff
a lot easier for you.
I don't have more
> Gee, flamebaiting already?
*sigh* No, debugging tips. It's alright at the moment, because Pierre
knows that Wine builds, and that WineMine runs. Wine doesn't ship if it
doesn't build, and WineMine is so basic it hardly ever breaks. What
happens when it gets more complex - how
On Wed, 16 Jul 2003, Mike Hearn wrote:
: > PS : I would like to know if the color of winemine are the colors which
: > are supposed to be, thanks.
:
: Why don't you just install Linux/PPC, I think that would make this stuff
: a lot easier for you.
Gee, flamebaiting already?
Linu
> PS : I would like to know if the color of winemine are the colors which
> are supposed to be, thanks.
Why don't you just install Linux/PPC, I think that would make this stuff
a lot easier for you.
Better, why not help make Linux as nice as MacOS, then you wouldn't need
t
On mercredi, juil 16, 2003, at 00:42 Europe/Paris, Vincent Béron wrote:
Le mar 15/07/2003 à 18:33, Pierre d'Herbemont a écrit :
Hey!
I have some good news. I am able to play with WineMine on Mac OS X :)
See the screenshot here:
http://stegefin.free.fr/WineMine.jpg
Good work Pierre!
T
Le mar 15/07/2003 à 18:33, Pierre d'Herbemont a écrit :
> Hey!
>
> I have some good news. I am able to play with WineMine on Mac OS X :)
> See the screenshot here:
> http://stegefin.free.fr/WineMine.jpg
Good work Pierre!
>
> But comctl32 is not working and probably so
Hey!
I have some good news. I am able to play with WineMine on Mac OS X :)
See the screenshot here:
http://stegefin.free.fr/WineMine.jpg
But comctl32 is not working and probably some others dlls, so I still
have some work, but this is a good step.
Cheers,
Pierre
PS : I would like to know if
color in winemine
> specifically to make it annoying ;). Actually, at the
> time I didn't want it to have a boring old gray
> background, so I chose green in order to make it would
> look like grass (a mine field). But I guess it's
> pretty annoying. Do you have a color pr
;d like to work on wine more,
but I've been really busy with school lately.
Hopefully, I'll have more time when I graduate.
Anyway, I chose that green color in winemine
specifically to make it annoying ;). Actually, at the
time I didn't want it to have a boring old gray
background, so
Hi,
I seem to have a bit of trouble building the winemine
sample.
When it gets to the wrc stage it just says:
make: *** [rsrc.res] Error 1
Any ideas?
Andriy Palamarchuk <[EMAIL PROTECTED]> writes:
> Alexandre,
> do we really want to install winemine Wine
> application by default?
Sure, why not?
--
Alexandre Julliard
[EMAIL PROTECTED]
--- Alexandre Julliard <[EMAIL PROTECTED]> wrote:
> Andriy Palamarchuk <[EMAIL PROTECTED]> writes:
>
> > Alexandre,
> > do we really want to install winemine Wine
> > application by default?
>
> Sure, why not?
No problem. T
Alexandre,
do we really want to install winemine Wine
application by default?
Andriy
__
Do You Yahoo!?
Yahoo! Health - your guide to health and wellness
http://health.yahoo.com
>> what about putting a "static into the function declaration? Of course
>> you can rename it also.
I tried declaring AboutDlgProc as static, but it is needed by shell.c's
AboutDlgProc16. I could just rename it, but is there a better way?
Joshua
***
* Joshua Thielen
WineMine is not retaining settings because the registry key used in
LoadBoard() is not the same as the one used in SaveBoard().
Also fixed a typo in the position saving code.
--- main.c Wed Apr 5 20:37:56 2000
+++ main.c Sun Apr 9 09:43:15 2000
@@ -295,9 +295,9 @@
size = sizeof
ried it both ways to no avail.
> As of 'not completely', what do you mean by that ? How do you measure
> the leak, anyway ? If you use top, look for the RSS and SIZE fields for Winemine
> and the X server.
> For me, Winemine memory has never any trend and hardly changes whil
was changed very
recently.
I think that with your version of Wine, your patch has the same effect as mine.
Or maybe try to add a ->pixmap at the end.
As of 'not completely', what do you mean by that ? How do you measure
the leak, anyway ? If you use top, look for the RSS and SIZE fields fo
Hello,
I was able to try your patcht his morning, but I got a compiler error that
bmp->physBitmap is undeclared. I tried replacing this with bmp->DDBitmap->physBitmap,
but it did not fix the memory leak (at least not completely). I was in a rush
so I wasn't able to investigate it. Looking at the
At 05:49 PM 3/31/00 -0500, you wrote:
Could you try this patch against graphics/x11drv/init.c ?
It seems to fix the leakage for me.
--- init.c.orig Sun Apr 2 16:56:14 2000
+++ init.c Sun Apr 2 19:27:05 2000
@@ -241,7 +241,8 @@
{
BITMAPOBJ *bmp = (BITMAPOBJ *) GDI_GetObjPt
> Also, I was
> wondering whether I should just rename the AboutDlgProc function in
> shell32_main.c to something like SHELL32_AboutDlgProc, or if it is
> somehow being exported by mistake. I believe that this is the function
> that is conflicting with AboutDlgProc in winemine, b
At 05:49 PM 3/31/00 -0500, you wrote:
>Peter Hunnisett wrote:
>
>> Well if the leak appears to be comming from the CreateCompatilbeDC,
>> my changes will have reduced the impact since we were doing some
>> pretty massive creation/deletion for DrawMine. I didn't even look
>> for a leak, though.
>
>
ot eliminated . Also, I was
wondering whether I should just rename the AboutDlgProc function in
shell32_main.c to something like SHELL32_AboutDlgProc, or if it is
somehow being exported by mistake. I believe that this is the function
that is conflicting with AboutDlgProc in winemine, but I didn&#
ect the original bitmap back into
>the memory DC before calling DeleteDC on it. But I don't know if it
>actually makes a difference in practice.
It can make a difference. I'm not sure about this particular example but
one of my programs had a leak where I wasn't deselecting a
for example, this code may be valid only in windows 9x,
invalid in windows 3.1:
hDC = Create[Compatible]DC();
SelectObject( hDC, (anyobject) );
DeleteDC( hDC );
in windows 3.1,
original handle of selected object should be restored:
hDC = Create[Compatible]DC();
hObj = SelectObject(
Peter Hunnisett wrote:
> Well if the leak appears to be comming from the CreateCompatilbeDC,
> my changes will have reduced the impact since we were doing some
> pretty massive creation/deletion for DrawMine. I didn't even look
> for a leak, though.
What changes? Sorry if I'm missing something,
t,
or are they all.
What about the fact that SelectObject can return the old handle? Could that
be your leak - handle to a resource?
In message "Re: Fwd: Memory leak in WineMine",
"Joshua Thielen" <[EMAIL PROTECTED]> writes:
>After checking out the memory leak, I think
> Yes, but it may be unrelated to the memory leak:
> The first SelectObject() has a return value: it returns the previously
> selected bitmap. You are supposed to select the original bitmap back into
> the memory DC before calling DeleteDC on it. But I don't know if it
> actually makes a differenc
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,
> (col - 1) * MINE_WIDTH + p_bo
bugs in these
functions. Actually, I did notice that origDC never gets unlocked in
CreateCompatibleDC, is this a bug? Unlocking this does not stop the memory
leak in winemine, however.
Joshua Thielen
_
NetZero - Defenders of the Free World
Click here for
Dave Pickles wrote:
> Playing WineMine in 'expert' mode for 15 minutes (I'm no expert ;-)) the
> machine becomes very sluggish. 'top' reports that the winemine process has
> grown from 4Mb to 36Mb, and the X process from 22Mb to 64Mb.
>
> This is on t
Playing WineMine in 'expert' mode for 15 minutes (I'm no expert ;-)) the
machine becomes very sluggish. 'top' reports that the winemine process has
grown from 4Mb to 36Mb, and the X process from 22Mb to 64Mb.
This is on today's CVS, btw.
Dave Pickles
data, but
> bitmaps files are not, well at least IMHO :). Is winemine something
> you would considere including in wine and should I fix this stuff and send a
> patch?
The main reason is for diff/patch to work, so that you can always
upgrade to the next release by applying the diff. And ye
readable data, but
> bitmaps files are not, well at least IMHO :). Is winemine something
> you would considere including in wine and should I fix this stuff and send a
> patch?
Hallo,
it might be that people on machines with different byte order will try
to compile your winelib-winmine. T
Hi again,
Sorry about that last message, it was supposed to read, Hello Alexandre,
but I messed up on my school's dang VMS mail editor.
Greetings,
Joshua Thielen
[EMAIL PROTECTED]; home
[EMAIL PROTECTED]; school
MHO :). Is winemine something
you would considere including in wine and should I fix this stuff and send a
patch?
Joshua Thielen <[EMAIL PROTECTED]> writes:
> The registry entries are stored in HKEY_LOCAL_MACHINE\SOFTWARE\The Wine
> team\WineMine is "The Wine team" the official place for wine registry
> entries?
Personally I prefer simply "Wine" rather than "the
Just a few comments on along with my winemine addition:
The registry entries are stored in HKEY_LOCAL_MACHINE\SOFTWARE\The Wine
team\WineMine is "The Wine team" the official place for wine registry
entries?
The resource languages (or actually language) are done like this:
41 matches
Mail list logo
