This kind of begs the question: how many more places in Wine should the
volatile keyword be used? I find it hard to believe that this is the only
spot in a large very low-level project like Wine.
You're comment is absolutely right. The thing is, those bugs are especially
hard to find out
IMHO, performing code review of the whole tree for missing volatile
keywords
would be a waste of time compared to do it on a case by case basis.
Simply
keep in mind that those bugs may happen - especially with "aggressive"
compilers such as gcc 2.96. If a bug didn't happen with the
If the network is not lying to me again,
[EMAIL PROTECTED] wrote on Thu, Dec 21, 2000 at 01:37:39PM -0800:
Francois Jacques [EMAIL PROTECTED] writes:
+static HRESULT
+INVOKE_InvokeStdCallFunction(IUnknown* pIUnk,
+ FUNCDESC* pFuncDesc
Folks,
While adding asynchronous recording, I needed the following hack to make
things work with the application I'm working on. If someone could give
me a quick explanation, that would be great.
Thanks in advance,
Francois
--
Francois Jacques, Software Designer
Macadamian Technologies Inc
adding new functions to x11drv, please make sure to add a
corresponding stub in ttydrv.
I thought that ttydrv went away, but now I see (grep -r ttydrv) that it's now in
dlls/ttydrv.
Fair enough, I'll make the changes!
Francois
--
Francois Jacques, Software Designer
Macadamian Technologies Inc.
Arg !
Alexandre, please forget that patch ! I'll repost it soon with yet
another update...
Sorry guys for the inconvenience.
Francois
Francois Jacques wrote:
Description :
If typelib path cannot be found with neither primary language ID or
secondary language ID, use system ID (0
is that for non-standard pointed types, td[3] is always 0
(duh!). I observed that the type is stored at td[2]/8 and not td[3]/8.
This would cause TLB_GetTdesc to return the wrong type when processing
non-standard types.
The problem has been observed against Microsoft's stdole2.tlb.
Francois Jacques
Hi Huw,
Nope I didn't see it.
Thanks a lot for the tip!
F.
Huw D M Davies wrote:
On Mon, Jul 31, 2000 at 10:15:14AM -0400, Francois Jacques wrote:
huw,
Thanks for this update... After a while, I thought that my WindowRgn
patch wouldn't make it into the tree. I have an updated
huw,
Thanks for this update... After a while, I thought that my WindowRgn
patch wouldn't make it into the tree. I have an updated version which
had this fix along with other XShape--WindowRgns issues. Look for an
update later this week...
Francois
Huw D M Davies wrote:
Huw D M
Hi Martin,
A few ideas thrown in...
1. you can choose if you want to generate new or edit existing
wine.conf file.
Generating new wine.conf would have default value? The generated wine.conf
should have comments in it...
2. choose a location of your wine.conf file
hmmm... that depends
Juergen Schmied wrote:
What I would suggest is a merge between your new implementation and Rein
Klases' original code. The code could go like this...
I removed this code because when starting hh.exe it finds something what
is not a typelib and crashes. We would need a more safe way
Rein Klazes wrote:
On Thu, 6 Jul 2000 20:31:13 +0200, you wrote:
Sounds good let's impement like this. Should I go for if?
If I understand correctly, Francois Jacques has been assigned to fix
this and others issues with regard to ole automation.
True. But if Juergen feels like
OLE book is in MSDN!)
Francois Jacques
Macadamian Technologies Inc.
Hello world!
Here's a implementation for Set/GetWindowRgn. Notice that it modifies
configure.in and make_X11wrappers, so a few additional steps are needed
to apply the patch. Here is the procedure
cd your_wine_sandbox_here
patch -p0 WindowRgn.diff
autoconf configure.in configure ; chmod u+x
(same as previous, but with the patch attached!)
Hello world!
Here's a implementation for Set/GetWindowRgn. Notice that it modifies
configure.in and make_X11wrappers, so a few additional steps are needed
to apply the patch. Here is the procedure
cd your_wine_sandbox_here
patch -p0
15 matches
Mail list logo