I've found this in control/edit.c
HWND hwndParent; /* Handle of parent for sending EN_* messages.
Even if parent will change, EN_* messages
should be sent to the first parent. */
Is this
Hello,
I've reviewed the documentation on the web site as will as some of the
documents in the distribution but I cannot seem to find this
information.
Is there a document that describes the format of the .spec files used in
the dll directories?
Thanks,
Gil
signature.asc
Description:
--- Gil Hauer [EMAIL PROTECTED] wrote:
Hello,
I've reviewed the documentation on the web site as
will as some of the
documents in the distribution but I cannot seem to
find this
information.
Is there a document that describes the format of the
.spec files used in
the dll
Hi Jon
I upgraded my autoconf, which solved my first problem. Now,
everything runs fine until I get to the make install step, when
I get this error:
make[2]: Leaving directory `/home/stevenlu/wine/dlls/x11drv'
mydll.dll.so \
rm -f /usr/local/lib/libntdll.dll.so
make[1]: mydll.dll.so: Command
Dimitrie O. Paun a écrit :
On September 18, 2002 04:10 am, Eric POUECH wrote:
IMO, most of the documentation (even the internals description,
status of DLL) should be made in the DocBook form
I don't think this is right. Documenetation that is meant for
the user should go into .sgml,
Hi,
first of all let me say that I am impressed by the progress that wine
made in the last months and I also see that working things don't get
broken for long anymore. Congrats!
I have one problem with a game and I think the problem might be easy
to solve if you point me to the right piece of
On September 18, 2002 01:51 pm, Alexandre Julliard wrote:
-- rename installation-und-konfiguration.german
We have already a README.fr, we should be consistent.
But installation-und-konfiguration.german is not really a translation
of the README. I think it should rather be integrated
On September 19, 2002 01:28 pm, Eric Pouech wrote:
we mostly agree:
Yeap.
- my point was to remove (mainly) the README and stuff like that from
the module dir
I don't have a problem with that, but if it's general info for developers
working on that DLL, where do you put it?
- I know quite
Hi,
I am having some difficulty into understanding some parts of
wine source because of my lack of win32 knowledge.
I am looking for undertanding into win32 types like
WCHAR, LPWSTR, LPCWSTR and so on.
I tryed to search msdn for this but I did not find any good
doc about it.
So, can someone
--- Raul Dias [EMAIL PROTECTED] wrote:
Hi,
I am having some difficulty into understanding some
parts of
wine source because of my lack of win32 knowledge.
I am looking for undertanding into win32 types like
WCHAR, LPWSTR, LPCWSTR and so on.
I tryed to search msdn for this but I did
I have a windows app that calls LoadLibrary on all the DLLs
in a certain directory. It doesn't actually call any
functions in the DLL; simply loading it causes the desired
effects to take place. I'd like to replace one of those
DLLs with a WineLib version that calls some Linux functions.
I've
Is this perhaps related to bug 640?
On Thu, 2002-09-19 at 09:54, Martin Cracauer wrote:
Hi,
first of all let me say that I am impressed by the progress that wine
made in the last months and I also see that working things don't get
broken for long anymore. Congrats!
I have one problem
- Forwarded message from Takashi Iwai [EMAIL PROTECTED] -
From: Takashi Iwai [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Subject: [Alsa-devel] update of known bugs list
Date: Thu, 19 Sep 2002 17:46:58 +0200
Hi Patrick,
the following is the update of known bugs list on the web.
could you
Le jeu 19/09/2002 à 17:25, Arthur L. Jones a écrit :
[...]
notes: it seems like, if this ever worked correctly, that
OLE_GetFormatA could be implemented by just copying
the ascii buffer and sending it along to OLE_GetFormatW?
That's the easiest way of implementing both
14 matches
Mail list logo
