I have been looking at this and my advice is start simple and establish
the basic framework ie. display a frame with a title. Then add
functions and text items or buttons types one by one. Add complexity to
the functions after the basic form is accepted.
On 09/06/11 17:00, Patrick Gauthier wrot
>
> It would be understandeable to me if its written in the bug that the
> fix of this bug will consume a lot of resources and its
> impossible to fix this, but just to ignore it is not "the proper way
> to behave".
Most wine developers are just people sorting out problems that either
affect them
On 10/11/2010 04:40 AM, André Hentschel wrote:
Hi "lats",
you should please provide your real name in your mail, otherwise your patch has
bad chances to get in.
Normally you can configure git, so that it reports your name in the "From:"
field.
Sorry about that but I have b
When does this unpredictability occur? The tests have always run ok for me.
On 11/10/09 19:29, Ričardas Barkauskas wrote:
Removes trailing spaces to have it clean for next patch
I will be interested to see how you go with this one as the word has
been that formatting only patches are not accepted.
On 16/08/09 09:33, José Francisco Facundo Pérez wrote:
When sending to wine-patches, please don't cc: wine-devel but set the
Reply-To to wine-devel@winehq.org
On 25/07/09 12:46, Daniel Santos wrote:
I finished the actual code about 3 weeks ago,
but it's been a lot of work for me to split it out into
smaller pieces, especially being new to git.
The intention is that is that you build and test smaller chunks, hence
the term "commit often". It cert
On 19/06/09 20:44, Paul Vriens wrote:
Another one used quite often in the tests is something like wine_dbgstr_w.
This one seems to be very useful.
Robert Shearman wrote:
lats wrote:
+const SCRIPT_PROPERTIES Default_Script_0 = {0, 0, 0, 0, 0, 0, 0, 0,
+0, 0, 0, 0, 0, 0, 0};
This can be "static const" instead of just "const".
Ok, can fix.
+/* Set up a sensible d
I have been trying to track a problem in gdiobj.c where I had a handle
of 0x107e. In GDI_GetObjPtr the handle & 2 is said to indicate a GDI
Heap handle. From everything else I have read, that bit is supposed to
indicate a Moveable handle. Is there something special about GDI
handles that I sho
In the last week WINEDBG has stopped outputting the file/path and
linenumber of entries in the backtrace. Does anyone know what happened?
Jeff
11 matches
Mail list logo
