"Jacek Caban" <[EMAIL PROTECTED]> wrote:
> @@ -310,15 +335,24 @@ static void intern_atoms(void)
> names = HeapAlloc( GetProcessHeap(), 0, count * sizeof(*names) );
> atoms = HeapAlloc( GetProcessHeap(), 0, count * sizeof(*atoms) );
>
> -for (format = ClipFormats, i = 0; format; for
It appears that Mike has been doing a lot of work on this.
http://www.winehq.org/hypermail/wine-devel/2004/09/0221.html
So you probably first want to coordinate with him.
Yes. I'm aware that I'm holding people up right now due to my
non-connectedness. I'm actually living in a bed&breakfast with no
Saturday, September 11, 2004 8:34 AM Duane Clark
>
> By the way, I really do like the look mentioned here:
> http://www.winehq.org/hypermail/wine-devel/2004/09/0220.html
> It is much improved over the current look. Hopefully that will become
> part of winecfg.
>
Per suggestion of Robert Shearman,
Joris Huizer wrote:
Fine by me ;) where do I start then.. I can't find much on the winehq
site about that (I found a http://sourceforge.net/projects/winecfg/ but
it seems the last update was over a year ago..)
What's there to do, how to... etc - kind find much documentation except
for the fact i
On Fri, Sep 10, 2004 at 08:19:09PM +0200, Joris Huizer wrote:
> site about that (I found a http://sourceforge.net/projects/winecfg/ but
> it seems the last update was over a year ago..)
> What's there to do, how to... etc - kind find much documentation except
> for the fact it's mentioned as a To
Duane Clark wrote:
Mike Hearn wrote:
If you're just generally looking for things to do, W->A cleanup isn't
the only task. You could help extend the test suite :)
Or another possibility... since there is no longer a ~/.wine/config file
installed, we really, really need some serious work on winecf
ction?
(rather than just trusting I am sort-of sure my hacks are working??)
as a side note, changing the W->A calls for mciSendStringW only makes
sense when the MCI drivers (at least the 32 bit ones) are ported to
unicode interface (which another magnitude of effort than just the
mciSendStringW function).
A+
Mike Hearn wrote:
If you're just generally looking for things to do, W->A cleanup isn't
the only task. You could help extend the test suite :)
Or another possibility... since there is no longer a ~/.wine/config file
installed, we really, really need some serious work on winecfg. That
should be
So -- is there a unit testing or so or do all people just make a bunch
of extra files to make the function calls and make what they need compile?
If I change, say , dlls/winmm/mci.c: winmm: mciSendStringW , how will I
be able to verify the change didn't change the behavior of the function?
(rath
James Hawkins wrote:
However, I don't know how to make simple tests.. as I'd really need to
test wether the code I write works, and works properly :p
The best way to test the functionality of a certain api function
against windows is to read the msdn docs on that function. There are
certain easy
ot into windows) so how should I do this (testing without windows
> environment)? How are tests supposed to run?
>
> I hope you can give some clues on that; I found there are many W->A
> calls in dlls/winmm/winmm.c (according to the janitorial page) so I
> might start there (hoping not all of them are so tricky ;) )
>
> Thanks for suggestions on this,
>
> Joris
>
>
--
James Hawkins
run?
I hope you can give some clues on that; I found there are many W->A
calls in dlls/winmm/winmm.c (according to the janitorial page) so I
might start there (hoping not all of them are so tricky ;) )
Thanks for suggestions on this,
Joris
Hey Joris, I would be glad to write a howto for your and possibly
others. I will get started on that soon.
On 25 Aug 2004 11:43:57 -0400, Vincent Béron
<[EMAIL PROTECTED]> wrote:
> Le mer 25/08/2004 à 11:27, Joris Huizer a écrit :
> [snip]
> > Hi James,
> >
> > Yeah I would like that, thanks for
Le mer 25/08/2004 à 11:27, Joris Huizer a écrit :
[snip]
> Hi James,
>
> Yeah I would like that, thanks for suggesting :)
> I'll try and do a search on unicode functions and stuff but -- well, you
> have seen more of wine specific details ...
>
> Also, I think it'd be smart to put something like
James Hawkins wrote:
Hey Joris,
I started developing wine in exactly the same way you are
starting: working on the janitorial projects. My current project is
converting the crypt cross calls, and it is almost finished, but im
waiting for my CryptSetProviderExA patch to be committed before I se
Hey Joris,
I started developing wine in exactly the same way you are
starting: working on the janitorial projects. My current project is
converting the crypt cross calls, and it is almost finished, but im
waiting for my CryptSetProviderExA patch to be committed before I send
the rest of my cr
Joris Huizer wrote:
Hello,
I'm thinking of trying to do some helpfull work on wine;
Cool!
I have the following problem,
- I don't know where to start (I have never done stuff in wine or
another open source project) ; but I hope you have patience to guide me
into that (but I'm a informatica studen
t yet have much of that
overview..)
About a month ago, I saw a thread, including an interesting patch, about
the W->A calls; Could someone find that link? Are there
tutorials/manuals/guides/... about Unicode funcitons you recommend ?
Now, on to the work: if you can hand me that thread, how do I
K i will use A->W calls. What documentation are you referring to?
I'd like to read up on the subject.
James Hawkins
On Wed, 30 Jun 2004 07:00:58 -0700 (PDT), Steven Edwards
<[EMAIL PROTECTED]> wrote:
>
> Hi James,
>
> --- James Hawkins <[EMAIL PROTECTED]> wrote:
> > If I'm totally off the ma
Hi James,
--- James Hawkins <[EMAIL PROTECTED]> wrote:
> If I'm totally off the mark, let me know, and if there are other
> jobs I
> could be doing, let me know as well because I would like to
> contribute,
> but I'm not exactly sure what to do yet. Thankyou for your time.
Welcome! I dont think
am new to the process, I have chosen menial tasks to take on.
> >This way I can learn more about Wine while contributing.
> >
> > I am currently working on the janitorial task of getting rid of W->A
> >calls and I have a few questions about how I should implement these
> &g
have chosen menial tasks to take on.
This way I can learn more about Wine while contributing.
I am currently working on the janitorial task of getting rid of W->A
calls and I have a few questions about how I should implement these
changes.
Initially CryptAcquireContextW converts all of
I recently decided to help with the development of Wine, and seeing as
how I am new to the process, I have chosen menial tasks to take on.
This way I can learn more about Wine while contributing.
I am currently working on the janitorial task of getting rid of W->A
calls and I have a
.
Em Sáb 10 Jan 2004 04:51, Marcelo Duarte escreveu:
> Updated with the lastest cvs.
>
> Changelog:
> Marcelo Duarte <[EMAIL PROTECTED]>
> -Janitorial: Get rid of W->A calls for shlexec
> -Implementation of FindExecutableW
--
Marcelo Duarte
Marcelo Duarte <[EMAIL PROTECTED]> writes:
> Hi,
>
> Changelog:
> Marcelo Duarte <[EMAIL PROTECTED]>
> -Janitorial: Get rid of W->A calls for shlexec
> -Implementation of FindExecutableW
>
> Coments:
> After you aplying my patch 1/2 and made corrections
Not 100% about the part changing METAHEADERDISK.filename type. Can apps
access it directly and barf if they find WCHAR instead of CHAR? And is
the length set to 0x100 for binary compatibility?
Changelog:
Get rid of W->A calls for metafiles.
Vincent
Index: dlls/gdi/mfdrv/ini
On Fri, 12 Sep 2003, hatky wrote:
> Do you mean the conver of lpHelpFile in WinHelpA
> before it calls WinHelpW?
It means that somehow you picked another tricky
example to work on :) WinHelp is a very special
API in that it does some fucky/ugly stuff to
pass data between apps.
I'd do another on
> ASCII, I'd suggest
> keeping the encoding of strings inside the message
> as ASCII.
Do you mean the conver of lpHelpFile in WinHelpA
before it calls WinHelpW?
p.s. sorry I didn't find time for this doing the week
Hatky.
__
Do you Yahoo!?
Yahoo! SiteBuilder - F
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
[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);
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, 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
> 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 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 wcomma
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
> 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:
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
> 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, 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 :
>
> HRES
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 dwFl
46 matches
Mail list logo
