fre, 05.09.2003 kl. 22.02 skrev Thomas J. Moore:
> For a very long time now, enabling DGA causes mouse/keyboard events to be
> ignored. There have been a few threads on this issue in the past, and it
> seems nobody is willing to actually fix this problem (even though some have
> submitted patches
hatky wrote:
My first patch, so a deep check is welcome
Change log:
- Remove W->A call from WineHelpA/W
- This patch is dedicated to dimi that guided me
I'm afraid the patch is wrong.
the current implentation of WinHelp, which sends data from any app to
the program winhelp, requires that
Thanks, that fixed the problem.
I see that you added the dependancy to re-generate testlist.c. :)
> You can remove the testlist.c files and they will be regenerated
> correctly. Or simply do a make clean.
=
Sylvain Petreolle (spetreolle_at_users_dot_sourceforge_dot_net)
ICQ #170597259
Say
I was noticing something similar for myself, but I can't explain why the
difference is occurring other than to say that it must be a newbie error
on my part. But I downloaded the latest cvs earlier this afternoon.
Ran
./configure
./make depend && make
./make install
and now when I try to run wine
Juan Lang <[EMAIL PROTECTED]> writes:
> Interesting. The behavior of the program that called
> it (ipconfig.exe) was different, it crashed in a
> different location. But since the FormatMessage fix
> got rid of the crash altogether, I'm not particularly
> concerned.
Well I am, the behavior shou
Sylvain Petreolle <[EMAIL PROTECTED]> writes:
> After updating to the latest CVS via cvs update (the only patch involved was the
> header dependancies fix), wine doesnt compile.I tried to rerun './configure' but
> there is no change.What I get is : (make depend runs fine.)[EMAIL PROTECTED] tests
After updating to the latest CVS via cvs update (the only patch involved was the header dependancies fix), wine doesnt compile.
I tried to rerun './configure' but there is no change.
What I get is : (make depend runs fine.)
[EMAIL PROTECTED] tests]$ LANG=en_US make
gcc -c -I. -I. -I../../../inclu
On 22 Aug 2003, Jeremy Newman wrote:
[...]
> - No tags. Just the content. ie, everything that
> would be between the tags.
I have a Perl script that does that part. Should be easy to extend to
also extract the title...
Here goes as a starting point. Maybe I'll work a bit more on it
tomorrow but
The new list had an immediate response after it showed up on WineHQ -
somebody submitted her testresults of Total Commander run under Wine.
Maybe we should keep it that way? If people submit their stories there,
so much the better - bugzilla will be kept more free from loose ends.
No risk of mix
> etc.). For data files (such as this update.ini), there was another
> command to search automatically in multiple directories called
> append.
> I'm not aware of an equivalent for Unix.
... and it made users, developers and publishers upset because it
almost never worked. :)
=
Sylvain Petreol
IMHO this has no reason to work because you add this, or the myprog.exe
is bad designed.
note : since 'C:\myprogdir' is in %PATH%, there's no need to write it
in the command line.
> fine the update.ini. If you were to do:
>
> C:\> set path=%path%;C:\myprogdir
> C:\> cd somedir
> C:\somedir> C:\m
It looks like comctl32.dll is seting up some hooks to forward messages
to requested window because even if you use --dll comctl32=n the owner
is set up to "GetAncestor( cs->hwndParent, GA_ROOT )" Same thing
happends under Windows so it seems that everything is OK with
windows/win.c
I tried to figu
--- Vincent Béron <[EMAIL PROTECTED]> wrote:
> Le ven 05/09/2003 à 15:34, Dustin Navea a écrit :
> > Well, I can tell you that the reason it didnt work in windows when
> running
> > from another directory is because the directory that update.ini (or the
> exe
> > file) is in probably wasnt in your
> make sure you use --with-nptl when you configure Wine.
see
> > Wine runs fine in my machine. Now I try to complie windows project
> in Linux via WineLib.
> You shouldn't be running as root.
hehe :)
> > I have made the following things,
> > copy all the .c, .h, .rc files from programs/winemine
--- Lionel Ulmer <[EMAIL PROTECTED]> wrote:
> whereas 'in the golden days' anyone using Linux was a developper).
Correction: anyone using Linux either was a developer, or proficient enough
with computers to want to become one.. ;)
=
Dustin Navea
Minor Contributor, http://www.winehq.com
B
For a very long time now, enabling DGA causes mouse/keyboard events to be
ignored. There have been a few threads on this issue in the past, and it
seems nobody is willing to actually fix this problem (even though some have
submitted patches to fix it, nothing has ever made it into CVS). Why is
t
When using --with-wine=/usr/local/wine, "/usr/local/wine" or whatever
you substitute for it becomes $WINE_ROOT to the configure script.
Configure expects there are going to be certain things in the directory
tree at $WINE_ROOT. The directories include:
$WINE_ROOT/include
$WINE_ROOT/include/wi
Le ven 05/09/2003 à 15:34, Dustin Navea a écrit :
> Well, I can tell you that the reason it didnt work in windows when running
> from another directory is because the directory that update.ini (or the exe
> file) is in probably wasnt in your path.. But either way, fixing the program
> to get the ex
--- Fabian Cenedese <[EMAIL PROTECTED]> wrote:
>
> >> I just updated to the actual cvs version and tried to run my program.
> It's
> >> a simple Win32 command line tool which reads a text file from the same
> >> directory called Update.ini.
> >
> >Are you running the tool in the same way? If you a
[EMAIL PROTECTED] wrote:
> Ok, one last line:
>
>strcpy(((char*)lpwh) + sizeof(WINHELP), lpHelpFile);
I'm also not sure about the context here and it seems a little strange
but what you would want to do here is probably:
strcpyW((LPWSTR)((char*)lpwh + sizeof(WINHELP)), lpHelpFile);
> > Oh well, I am sure a lot of people will disagree (heck, there are even some
> > people who find Linux on the Desktop a good idea :-) ).
>
> Man, you're looking for a fight, aren't you? :)
Well, it's more a 'good old days' feelings than a real theory. Ie the
biggest problem I see with 'Linux o
Juan Lang <[EMAIL PROTECTED]> writes:
> ChangeLog: fixes RtlImageNtHeader when hModule is
> NULL.
>
> One line patch (two tokens!), should be easy enough to
> verify correctness.
Well, it may be correct, but it's useless, there's already an
exception handler that deals with that.
--
Alexandre J
hatky wrote:
Ok, one last line:
strcpy(((char*)lpwh) + sizeof(WINHELP),
lpHelpFile);
I do not realy get what it means (but I know it
shouldn't be this way becouse I get a warning:
passing arg 1 of `strcpy' from incompatible pointer
type
lpHelpFile is a LPCWSTR unicode variable and
lpw
On Fri, 5 Sep 2003, Anjan Sarkar wrote:
> Hello,
> I am using wine for my personal interest and need your help regarding the following
> problem I have faced.
> I have following configuration,
>
> a) Red Had Linux 9.0
make sure you use --with-nptl when you configure Wine.
> b) Wine (wine-200
On Fri, 5 Sep 2003, hatky wrote:
> Ok, one last line:
>
> strcpy(((char*)lpwh) + sizeof(WINHELP),
> lpHelpFile);
I don't have time now to look at the code, but
this is rather strange, I think you want this:
strcpyW((LPWSTR)(((char*)lpwh) + sizeof(WINHELP), lpHelpFile);
--
Dimi
hatky <[EMAIL PROTECTED]> writes:
> getting the trace of a certain component is not that easy
> because there is no place listing them
If you can find that component in the source tree (often
easier than in the man page, which simply lists all the
channels), then at the top of the .c file you wil
Lionel Ulmer wrote:
On Thu, Sep 04, 2003 at 02:23:34PM -0700, hatky wrote:
Some games are failing at detecting a 3D card or
sometimes the screen dept, have a look at bug :
http://bugs.winehq.org/show_bug.cgi?id=1696
getting into another bugzila/testing prenzy,
What about rather a coding /
Hello,
I am using wine for my personal interest and need your help regarding the following
problem I have faced.
I have following configuration,
a) Red Had Linux 9.0
b) Wine (wine-20030813.tar.gz) is extracted in /ww/wine-20030813
c) It creates a directory /c for windows
and /root/.wine
d) All t
> passing arg 1 of `strcpy' from incompatible pointer
> type
Sorry I ment trying strcpyW gets
../../windows/winhelp.c:167: warning: passing arg 1 of
`strcpyW' from incompatible pointer type
and strcpy gets
../../windows/winhelp.c:167: warning: passing arg 2 of
`strcpy' from incompatible pointer
Ok, one last line:
strcpy(((char*)lpwh) + sizeof(WINHELP),
lpHelpFile);
I do not realy get what it means (but I know it
shouldn't be this way becouse I get a warning:
passing arg 1 of `strcpy' from incompatible pointer
type
lpHelpFile is a LPCWSTR unicode variable and
lpwh is of t
On 5 Sep 2003, Mike Hearn wrote:
> This patch will add some warnings, and yeah, the commenting out of lots
> of code is ugly, but don't worry, it's all temporary until I've finished
> bringing the code across from the old global config struct. At that
> point it'll all be deleted in favour of the
"Rolf Kalbermatter" <[EMAIL PROTECTED]> writes:
> However I seem to get some problems compiling shobjidl.idl with with widl.
>
> I tried ./tools/widl/widl -I ./include ./include/shobjidl.idl and get an error.
You should use widl -h to only generate the header. Or easier do 'make
idl' in the inclu
On Fri, 5 Sep 2003, hatky wrote:
> So should I make it uCommand as in msdn or leave it
> wcommand?
I'd change both to uCommand as per msdn.
> > WCHAR clsName[] = { 'M', 'S', '_', 'W', 'I',
> > 'N', 'H', 'E', 'L', 'P', 0 };
> > hDest = FindWindowW(clsName, NULL);
Don't forget Robert's ad
> OK, I have to warn you I haven't looked at the code,
> so I'll just go by what I see in this email.
That's what I was expecting so I checked it carfully
and copied what seems to mater + I know that if/when I
will submit the patch it will be checked more...
> > why did they call them wcommand in
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
> Behalf Of Dimitrie O. Paun
> Sent: 05 September 2003 17:40
> To: [EMAIL PROTECTED]
> Cc: [EMAIL PROTECTED]
> Subject: Re: Get rid of W->A calls
>
> > why did they call them wcommand in WinHelpA and
> > command in Win
I'm trying to get a new shell object into Wine and seeing that most of the
object definition stuff has recently been moved to IDL files I wondered if
I could define the object in shobjidl.idl.
However I seem to get some problems compiling shobjidl.idl with with widl.
I tried ./tools/widl/widl -I
On 5 Sep 2003, Jon Brandenburg wrote:
> If you could give me a bit of direction on an area of the project that
> needs some attention and perhaps a little bit of hand holding to begin
> with I'd like to help out.
Well, a good way to start is to browse the WineHQ (http://www.winehq.org)
website to
On Fri, 5 Sep 2003, hatky wrote:
> Ok, lets take another one, winhelp.c WinHelpW->A
OK, I have to warn you I haven't looked at the code,
so I'll just go by what I see in this email.
> I take whatever is in WinHelpA and move it into
> WinHelpW with the fallowing changes:
>
> -BOOL WINAPI WinHelp
On Fri, 5 Sep 2003, Ivan Leo Murray-Smith wrote:
> Hi list,
> A guy that lives in my town found me via the linux counter, and we would like to
> translate the wine web site to italian, I was thinking of something like
> microsoft, with a drop menu of languages, where one can choose the destination
> Because I'm a lousy teacher :) Also, it is more
> productive
> to start with simpler examples, so you also do part
> of the
> learning from experience.
grr.
Ok, lets take another one, winhelp.c WinHelpW->A
I take whatever is in WinHelpA and move it into
WinHelpW with the fallowing changes:
Hi, I'm interested in doing some development/help for wine and was
wondering in what way I could help out? I have a college level
understanding of C/C++/Java, have done some professional programming in
(ack, VB), am currently in the process of learning C#, but would really
like to do some developm
On Fri, 5 Sep 2003, hatky wrote:
> I am getting the felling this will repeat, why not
> just teach me?
Because I'm a lousy teacher :) Also, it is more productive
to start with simpler examples, so you also do part of the
learning from experience.
--
Dimi.
> You've picked a wrong one to do -- this one is a bit
> trickier, because of the callback, and because we
> store information internally as ASCII. Do another
> one
> instead, leave this one for now.
I am getting the felling this will repeat, why not
just teach me?
Hatky.
___
On Fri, 5 Sep 2003, hatky wrote:
> > Let us know if you need any help.
>
> Just to be sure I got it right, I moved the
> DirectDrawEnumerateExA stuff into
> DirectDrawEnumerateExW since there is nothing ascii or
> unicode specific in it I think it's ok on it's own now
> in DirectDrawEnumerateExA
Hi list,
A guy that lives in my town found me via the linux counter, and we would like to
translate the wine web site to italian, I was thinking of something like
microsoft, with a drop menu of languages, where one can choose the destination
language.
This guy is also a really good web designer, an
> Let us know if you need any help.
Just to be sure I got it right, I moved the
DirectDrawEnumerateExA stuff into
DirectDrawEnumerateExW since there is nothing ascii or
unicode specific in it I think it's ok on it's own now
in DirectDrawEnumerateExA I have these variables:
LPDDENUMCALLBACKEXA lp
On Fri, 5 Sep 2003, Tom wrote:
> Junk, humm one mans junk is anothers treasure!
Indeed. Now, I agree the thing can be update a bit
more often, but it's not that out-of-date. The
reason it wasn't updated as of late is that not
much happened in the area. I've made a real
effort of keeping the thing
On Fri, 5 Sep 2003, hatky wrote:
> What sould I do?
> 1. copy the entire DirectDrawEnumerateExA into it
> 2. create a 3rd function DirectDrawEnumerateEx that
> both of them will call
> 3. somthing else (you tell me)
It's not always the same answer. Most of the time, you do
3. xxxA converts its
Le ven 05/09/2003 à 09:41, hatky a écrit :
> Janitorial reporting ;-)
>
> In the Get rid of W->A calls task,
> Say I try
> dlls/ddraw/main.c: ddraw: DirectDrawEnumerateExW:
> illegal call to DirectDrawEnumerateExA
>
> The misbheaving function is :
>
> HRESULT WINAPI DirectDrawEnumerateExW(
> L
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
> Behalf Of Fabian Cenedese
> Sent: 05 September 2003 13:39
> To: [EMAIL PROTECTED]
> Subject: RE: Current Working Dir?
>
> Well, I don't know if ever ran this program on wine before, but it's a
> simple command line t
Janitorial reporting ;-)
In the Get rid of W->A calls task,
Say I try
dlls/ddraw/main.c: ddraw: DirectDrawEnumerateExW:
illegal call to DirectDrawEnumerateExA
The misbheaving function is :
HRESULT WINAPI DirectDrawEnumerateExW(
LPDDENUMCALLBACKEXW lpCallback, LPVOID lpContext,
DWORD dwFlags)
{
>> I tried another app which needs dlls and again I had the error that the
>> file was not found, this time from wine. But the dll sure was in the
>> fake c:\windows\system32. Just as a wild guess I made a copy of
>> this dll and changed the case to all upper case as was the name
>> wine told me.
hatky wrote:
About coding it's even harder since I do not know a
lot about linux and in programming for linux for a
first, the list of tasks is updated very slowly and
usually not very clear to outsiders, the Janitorial
list that is suppose to be the easiest is not very
clear about what to do and
>> I just updated to the actual cvs version and tried to run my program. It's
>> a simple Win32 command line tool which reads a text file from the same
>> directory called Update.ini.
>
>Are you running the tool in the same way? If you are now running it with,
>for example, "wine ../../../tool" th
Le ven 05/09/2003 à 08:19, Fabian Cenedese a écrit :
> Hi
>
> I just sent an email about a file that isn't found -> Current Working Dir.
> I don't know if my next problem is related to it, just mentioning it.
>
> I tried another app which needs dlls and again I had the error that the
> file was n
Hi
I just sent an email about a file that isn't found -> Current Working Dir.
I don't know if my next problem is related to it, just mentioning it.
I tried another app which needs dlls and again I had the error that the
file was not found, this time from wine. But the dll sure was in the
fake c:\
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
> Behalf Of Fabian Cenedese
> Sent: 05 September 2003 12:36
> To: [EMAIL PROTECTED]
> Subject: Current Working Dir?
>
>
> Hi
>
> I just updated to the actual cvs version and tried to run my program. It's
> a simple Win
On September 5, 2003 07:41 am, Lionel Ulmer wrote:
> Oh well, I am sure a lot of people will disagree (heck, there are even some
> people who find Linux on the Desktop a good idea :-) ).
Man, you're looking for a fight, aren't you? :)
--
Dimi.
> What about rather a coding / debugging frenzy ?
I considered them both but they are very hard to do
for me for a known reason, Documentation.
I read them all + a lot of the mailing lists but
still
do not know where to start with all of this even in
the debugging, getting the trace of a certain
On Fri, Sep 05, 2003 at 11:56:09AM +0200, Jakob Eriksson wrote:
> >Considering the lots of time people seem to spend on fixing Bugzilla bugs
> >(instead of fixing their 'own' bugs), I think learning how to code and to
> >fix bugs yourself would be time better spend :-)
>
> Is this meant to be ironi
Hi
I just updated to the actual cvs version and tried to run my program. It's
a simple Win32 command line tool which reads a text file from the same
directory called Update.ini.
When I run it with winedbg it opens the app console window and brings
me an app error dialog that it can't find the sec
Installshield for dx8.1 sdk with win98 set in config is giving this
error:
err:dc:DCE_FreeWindowDCE[0x10023] GetDC() without ReleaseDC!
A trace is attached.
trace.bz2
Description: Binary data
62 matches
Mail list logo