On Wed, Sep 11, 2002 at 10:27:50PM +0200, Patrik Stridvall wrote:
I noticed this when adapting WINE code for ReactOS
[...]
- * DialogBoxIndirectParam (USER.240)
- * DialogBoxIndirectParam16 (USER32.)
+ * DialogBoxIndirectParam16 (USER.240)
+ *
On Thu, Sep 12, 2002 at 08:38:09PM +1000, Michael Beach wrote:
Recently I've been using WINE to run a Win32 exe which needs to load certain
DLLs which are located in the same directory as the exe. I was most perplexed
when I found that this worked initially, but when I moved the exe and DLLs
On Wed, Sep 11, 2002 at 10:27:50PM +0200, Patrik Stridvall wrote:
I noticed this when adapting WINE code for ReactOS
[...]
- * DialogBoxIndirectParam (USER.240)
- * DialogBoxIndirectParam16 (USER32.)
+ * DialogBoxIndirectParam16 (USER.240)
On Thursday 12 September 2002 20:55, Andreas Mohr wrote:
On Thu, Sep 12, 2002 at 08:38:09PM +1000, Michael Beach wrote:
Recently I've been using WINE to run a Win32 exe which needs to load
certain DLLs which are located in the same directory as the exe. I was
most perplexed when I found
I think there is issue with _T(x). I have this line in my Windows app
that I'm compiling with WineLib (I'm using -fshort-wchar):
const TCHAR *Name() const { return _T(my_name); };
The compiler gives me an error of:
cannot convert `const __wchar_t *' to `const
TCHAR *' in return
It similarly
When should I use wstr and when ptr for wide strings
in the spec files functions specification?
Looking at existing files I see that LPCWSTR type is
usually mapped to wstr, but LPWSTR is sometimes mapped
to ptr, sometimes to wstr.
Andriy
Boston, MA, USA
As an employee of an oil company, let
Andriy Palamarchuk wrote:
Unicode is supported relatively well in Wine. Please
report if you have any issues with it.
Andriy
Except where special manipulations are required (reordering, ligation,
diacritics etc.). How are we on Kerning, BTW?
Shachar
On Friday 13 September 2002 00:44, David Fraser wrote:
Michael Beach wrote:
static BOOL DIR_TryModulePath( LPCWSTR name, DOS_FULL_NAME *full_name,
BOOL win32 ) {
-/* FIXME: for now, GetModuleFileNameW can't return more */
-/* than OFS_MAXPATHNAME. This may change with Win32. */
-
When should I use wstr and when ptr for wide strings
in the spec files functions specification?
Looking at existing files I see that LPCWSTR type is
usually mapped to wstr,
It should almost always map to wstr.
but LPWSTR is sometimes mapped
to ptr, sometimes to wstr.
As the general
--- [EMAIL PROTECTED] wrote:
I think there is issue with _T(x). I have this line
in my Windows app
that I'm compiling with WineLib (I'm using
-fshort-wchar):
const TCHAR *Name() const { return _T(my_name); };
The compiler gives me an error of:
cannot convert `const __wchar_t *' to
At 10:04 PM 11/9/02 +0200, Lionel Ulmer wrote:
Well, Linux already runs on the Xbox, and the Xbox uses Direct3D. I
suppose
that there will be some hackers interested in writing Linux games to
run on
the Xbox, so it might be a good idea to join efforts, or to find some
other
On Thu, 12 Sep 2002 [EMAIL PROTECTED] wrote:
I think there is issue with _T(x). I have this line in my Windows app
that I'm compiling with WineLib (I'm using -fshort-wchar):
const TCHAR *Name() const { return _T(my_name); };
The compiler gives me an error of:
cannot convert `const
Jon [EMAIL PROTECTED] writes:
Does anyone object to my moving SHLWAPI_1 2 into url.c and moving out the
definitions from ordinal.h in there as well?
I want to tidy this up because at some point in the not too distant future the
ordinal code will get a lot bigger. So it makes sense to me
shlwapi.exp(.edata+0x34):fake: undefined reference to `AssocCreate@12'
C:\mingw\bin\dllwrap.exe: C:\mingw\bin\gcc exited with status 1
make: *** [shlwapi.dll] Error 1
The def should contain AssocCreate@24 I do not know what is needed in the *.spec though
Thanks
Steven
Thanks, that worked! Do you think you could update the Unicode section
in the WineLib user's guide (section 2.2)? It doesn't even mention
WINE_UNICODE_NATIVE (not like the rest of the guide is that current,
but every little bit helps for new developers).
-Steve
On Thu, 12 Sep 2002 [EMAIL
I also have the .lib and .pdb files for the DLLs, if that helps.
I'm writing a WineLib DLL that makes calls in my own Windows DLLs
(not Wine's DLLs). I have the header files for those DLLs, and the
Windows binaries for them. How do I link to them? Do I need to wrap
them in spec files?
I was under the impression that MAX_PATH is a Windows limitation rather than
one of the UNIX that WINE is running on. Since Windows doesn't promise to
permit any more than MAX_PATH, we gain nothing by allowing for more in WINE,
hence the use of MAX_PATH to size the buffers.
Dunno about
On Friday 13 September 2002 09:13, David Laight wrote:
I was under the impression that MAX_PATH is a Windows limitation rather
than one of the UNIX that WINE is running on. Since Windows doesn't
promise to permit any more than MAX_PATH, we gain nothing by allowing for
more in WINE, hence
18 matches
Mail list logo
