Hi Michael,
--- Michael Lin <[EMAIL PROTECTED]> wrote:
> If your target platform is windows, don't define the WINE_UNIX_PATHS
> flag when you compile and it will all behave
> the same as before. It's only when you define WINE_UNIX_PATHS flag that
> GetOpenFileNameW() will be mapped
> to UnixFSGe
Hi Steve,
Steven Edwards wrote:
--- Michael Lin <[EMAIL PROTECTED]> wrote:
--- dlls/commdlg/comdlg32.spec
+@ stdcall UnixFSGetOpenFileNameA(ptr)
+@ stdcall UnixFSGetOpenFileN
Is there anyway for us to have these functions inlined or something rather than exported all the
time is there? The reason
On Thu, 2005-05-12 at 16:49 +0200, Francois Gouget wrote:
> This patch adds the framework for translating Wine's documentation and
> adds a translation of the FAQ to French as a demonstration.
No compressed patches, please.
Also, the patch is big, and some things are cleaner than others.
Let's b
Hi Michael,
I really like the idea of trying to tie the apps in better for users of Winelib
applications but I
have a few problems. (I should have spoken up when the first of the Unixfs
stuff was going in to
shell32 because I feel it should have been a shellext outsite of shell32 but
now I am o
Alexandre Julliard wrote:
Error 21 in LoadModule16 means that the file exists but is 32-bit,
which seems to be the appropriate error in that case.
I dunno about LoadModule16() (no means to test it since it's a Win16
function...) but for LoadLibrary16() (which is just a one-line wrapper
around the
--- Francois Gouget <[EMAIL PROTECTED]> wrote:
> Furthermore a lot of '32bit applications' actually use 16bit code either
> directly or indirectly (although that may be getting less common these
> days). What this means is that if you remove 16bit support it's quite
> likely a lot of 32bit appl
Jonathan Wilson wrote:
Its highly likely that GCC and WINE are already infringing on some
software patent somewhere (since its well nigh impossible not to in the
current "patent everything you can" climate inside a number of big
companies)
What makes this particular borland patent any different
"Alexandre Julliard" <[EMAIL PROTECTED]> wrote:
> > Current window activation code in Wine is not entirely correct. I believe
> > that
> > might be a part of WM rewrite Alexandre is finishing which at the moment.
>
> Not really, I'm not aware of any problem with the window activation
> code, and
Its highly likely that GCC and WINE are already infringing on some software
patent somewhere (since its well nigh impossible not to in the current
"patent everything you can" climate inside a number of big companies)
What makes this particular borland patent any different?
On Wed, 11 May 2005, Marcus Meissner wrote:
[...]
16bit support is deeply integrated into the WINE core and not easy to extract.
Furthermore a lot of '32bit applications' actually use 16bit code either
directly or indirectly (although that may be getting less common these
days). What this means i
On Thu, 12 May 2005, Mike Hearn wrote:
On Wed, 11 May 2005 21:11:40 -0500, Dustin Navea wrote:
I was wondering if there was a better way to post them? Ill keep that
in mind from now on.
Well, I'm a bit dubious as to the value of posting bugs here anyway, we
have wine-bugs for that. If it really do
* On Thu, 12 May 2005, Hans Leidekker wrote:
> * On Thursday 12 May 2005 00:14, Kevin Koltzau wrote:
> > The ole32_test.exe file is linked to missing export NTDLL.DLL:atoi.
>
> This patch fixes it.
...
> Changelog:
> Don't import from ntdll.
Can someone explain me, please, where would atoi() f
> "Alexandre" == Alexandre Julliard <[EMAIL PROTECTED]> writes:
Alexandre> Do 'rm dlls/*.def' and it should work again.
Thanks, that worked
--
Uwe Bonnes[EMAIL PROTECTED]
Institut fuer Kernphysik Schlossgartenstrasse 9 64289 Darmstadt
- Tel. 06151 162516 --
juan melgarejo wrote:
Is there any document or how-to showing:
how to run a backtrace using the wine debugger
how set debug parameters for wine tracing of program execution
how to submit bugs to bugzilla (how to report, content)
How to Know proper settings for bugs
(when a bug should be
Uwe Bonnes <[EMAIL PROTECTED]> writes:
> I updated yesterday and today. Compiling with todays CVS gives:
> ../../../tools/winegcc/winegcc -B../../../tools/winebuild -mconsole
> joystick.o keyboard.o mouse.o testlist.o -o dinput_test.exe.so
> -L../../../libs/port -lwine_port -L../../../dlls -L../.
gslink wrote:
Borland probably doesn't even
realize that Wine exists although some of the people in Borland are
probably very familiar with it. I think you will find this to be true
of all big software companies such as IBM and Microsoft.
IRC borland had a delphi for linux named kylix which
juan melgarejo wrote:
Is there any document or how-to showing:
how to run a backtrace using the wine debugger
how set debug parameters for wine tracing of program execution
how to submit bugs to bugzilla (how to report, content)
How to Know proper settings for bugs
(when a bug should be
Hallo,
I updated yesterday and today. Compiling with todays CVS gives:
../../../tools/winegcc/winegcc -B../../../tools/winebuild -mconsole
joystick.o keyboard.o mouse.o testlist.o -o dinput_test.exe.so
-L../../../libs/port -lwine_port -L../../../dlls -L../../../dlls/dinput
-L../../../dlls/ole32 -
Hi,
I want to merge some Robert Dickenson's version of winfile (derived from the
old winefile code in 2002) in the next time into winefile. At the same time I
want to keep the code it in sync between the ReactOS code base and Wine.
What do you think about splitting the source file into several
David Lee Lambert wrote:
Would Wine be able to proceed if we got the following statement from them?
"Borland hereby grants a worldwide, royalty-free, non-exclusive license to
use the methods described in U.S. patent 5,628,016 to the current Wine
developers when they use the current LGPL source-code
On Thu, May 12, 2005 at 08:04:57AM -0400, gslink wrote:
> The easiest way to resolve this business with Borland is to contact
> Borland. They may also have an interest in Wine. If they have no
> objection to what Wine wants to do then there is no one else to
> complain. They might even help
Use the native Linux Reader 7 from the Adobe web site. Running Reader 7
under Wine isn't worth the trouble. Acrobat Professional is a different
matter. The latest Acrobat Professional that will work on Wine is 5.
Both 6 and 7 require dlls that must be supplied from Windows. Seven has
copy pr
gslink wrote:
The easiest way to resolve this business with Borland is to contact
Borland. They may also have an interest in Wine. If they have no
objection to what Wine wants to do then there is no one else to
complain. They might even help Wine. Borland probably doesn't even
realize that
Hello,
Andreas Mohr wrote:
On Thu, May 12, 2005 at 02:58:11PM +0100, Mike Hearn wrote:
On Wed, 11 May 2005 21:11:40 -0500, Dustin Navea wrote:
I was wondering if there was a better way to post them? Ill keep that
in mind from now on.
Well, I'm a bit dubious as to the value of posting bugs here an
Andreas Mohr wrote:
Many people don't subscribe to wine-bugs.
exactly
If we have a few select bugs posted here (ones that are very interesting/
important/critical/whatever), then this can only be a good thing.
(as long as it does remain a moderate number of mails!)
hehe, I was hoping someone would
Please do not reply to this email with this same subject line unless you
are notifying myself that you would like to have an interview. If you
need to discuss this more with me, use a subject of "Discuss - Now
Recruiting"
Attention all users of wine! Have you ever run into a situation where
Hi,
On Thu, May 12, 2005 at 02:58:11PM +0100, Mike Hearn wrote:
> On Wed, 11 May 2005 21:11:40 -0500, Dustin Navea wrote:
> > I was wondering if there was a better way to post them? Ill keep that
> > in mind from now on.
>
> Well, I'm a bit dubious as to the value of posting bugs here anyway, w
Mike Hearn wrote:
Well, I'm a bit dubious as to the value of posting bugs here anyway, we
have wine-bugs for that. If it really does motivate people to work on them
though then I guess it'd be OK.
It seems to not necessarily _motivate_ someone to work on a bug, but it
does seem to get them fixed f
On Wed, 11 May 2005 21:11:40 -0500, Dustin Navea wrote:
> I was wondering if there was a better way to post them? Ill keep that
> in mind from now on.
Well, I'm a bit dubious as to the value of posting bugs here anyway, we
have wine-bugs for that. If it really does motivate people to work on the
On Thu, 12 May 2005 02:59:38 -0500, you wrote:
> Hey,
>
> This is a patch for the WM_LBUTTONUP msg problem, but I've taken the
> advice of Dmitry and now all messages are dispatched.
>
> Changelog
> * Make sure all msg's are dispatched while tracking a WM_LBUTTONDOWN msg.
Patches like this have
The whole business of software patents is very likely to explode at any
time. There are several software patents on cds and dvds which are so
vague that it is impossible to tell exactly what is going on. The
licenses to use these patents allow the company issuing the patent to
control cd cont
Dimi Paun <[EMAIL PROTECTED]> writes:
> I've taken a stab (prototype level) at the LOCAL_Alloc() function
> (patch included below). Would such an approach be acceptable?
Yes, that should be OK.
--
Alexandre Julliard
[EMAIL PROTECTED]
"Dmitry Timoshkov" <[EMAIL PROTECTED]> writes:
> Why WM_LBUTTONUP should be different from other kinds of messages?
> I.e. why all messages could not be passed to DispatchMessage? What
> if just move DispatchMessageW call right right after PeekMessageW?
Actually the whole function looks very susp
Hi,
On Thu, May 12, 2005 at 10:45:06AM +0200, Peter wrote:
> Hello,
> I try to install the Adobes Acrobatreader 7.0.
Your rather normal request for help sounds to me like you're doing this
in order to get Acrobat Reader 7 installed, not in order to further Wine
development.
This is rather questio
Juan Lang <[EMAIL PROTECTED]> writes:
> +switch (sig)
> +{
> +/* Cases that fall through to signal(2) */
> +case SIGABRT:
> +case SIGFPE:
> +case SIGILL:
> +case SIGSEGV:
> +ret = signal(sig, func);
> +break;
You can't do that, this will cause major tro
"Ge van Geldorp" <[EMAIL PROTECTED]> writes:
> I'm wondering what happened to the reworked widl patch at
> http://www.winehq.org/hypermail/wine-patches/2005/04/0371.html? It hasn't
> been applied yet, does that mean there's no interest on the Wine side and I
> can drop it from my TODO list?
There
"Dmitry Timoshkov" <[EMAIL PROTECTED]> writes:
> Current window activation code in Wine is not entirely correct. I believe that
> might be a part of WM rewrite Alexandre is finishing which at the moment.
Not really, I'm not aware of any problem with the window activation
code, and I'm certainly n
Hello,
I try to install the Adobes Acrobatreader 7.0.
Now this didn't work it gave me a quite odd message that an unexpected
error occured with a long number.
I tried to run wine with the debug Variable +all.
I never done this before so can anybody help me?
Is the ntdll missing something or is it
I'm wondering what happened to the reworked widl patch at
http://www.winehq.org/hypermail/wine-patches/2005/04/0371.html? It hasn't
been applied yet, does that mean there's no interest on the Wine side and I
can drop it from my TODO list?
Best regards, Ge van Geldorp.
"Vitaliy Margolen" <[EMAIL PROTECTED]> wrote:
> >> According to native messages sent to app we should redraw window
> >> inside SetActiveWindow.
> > If you have a test app then it should be converted into a Wine message
> > test, there is no other way to prove that your patch is correct.
> I have
"James Hawkins" <[EMAIL PROTECTED]> wrote:
> You were right about having the NM_CLICK msg sent in
> LISTVIEW_LButtonUp, and the problem was that a WM_LBUTTONUP msg was
> never sent. This fixes the problem where you had to double click an
> item in the drives list to select it.
>
> Changelog
> *
"Vitaliy Margolen" <[EMAIL PROTECTED]> wrote:
> > Then each owned window will receive 2 WM_SHOWWINDOW messages. Are you sure
> > that Windows does it that way? I'd advise to write a message test to verify
> > it.
> That's exactly what happens. Window receives two WM_SHOWWINDOW messages. One
> wit
42 matches
Mail list logo
