On Tue, Aug 31, 2010 at 9:45 AM, Austin English wrote:
> On Mon, Aug 30, 2010 at 4:06 PM, Dan Kegel wrote:
> > I suppose we'll hear what the goals for 1.4 are at Wineconf, but
> > here's my little wish list:
> >
> > Bug 6971, the mouse problem affecting many FPS-style games (Alexandre
> > thinks
On Mon, Aug 30, 2010 at 4:06 PM, Dan Kegel wrote:
> I suppose we'll hear what the goals for 1.4 are at Wineconf, but
> here's my little wish list:
>
> Bug 6971, the mouse problem affecting many FPS-style games (Alexandre
> thinks it would take a month of his time?)
> Solving Wine's problems with P
Are there any Chinese speakers on the list?
Any interest in starting a Chinese translation of wiki.winehq.org?
I bring this up because a Chinese user/developer is asking for help
getting started with submitting translations to Wine. I think he would find
Chinese versions of
http://wiki.winehq.org
On 08/30/2010 05:44 PM, Octavian Voicu wrote:
1. You set color.ui to always and you're using less or another pager
that doesn't support color. You don't need to use a pager in git diff.
Normally, if you set color.ui to auto (or true), then color escape
sequences are only enabled when output is a
On Mon, Aug 30, 2010 at 9:25 PM, David Adam wrote:
> Does not work for me :crying: I voluntary added trailing space to my file.
> Nothing appears in red. I obtain in white and black
> testcooperativelevels_normal();ESC[m
> ESC[32m+ESC[mESC[32m testcooperativelevels_normal_other_ddraw();ESC
I suppose we'll hear what the goals for 1.4 are at Wineconf, but
here's my little wish list:
Bug 6971, the mouse problem affecting many FPS-style games (Alexandre
thinks it would take a month of his time?)
Solving Wine's problems with Pulseaudio (bug #10495)
Mono integration similar to the current
> Yeah, I'm not really sure how this is supposed to work. load_mono()
> ensures that mono is loaded, so mono_handle should be set if it
> succeeds. Unless someone calls CorExitProcess in another thread and
> unloads it before we can grab the critical section again.
>
> Maybe load_mono should return
> Hi Vincent,
>
> + EnterCriticalSection(&mono_lib_cs);
> + if (!mono_handle)
> + {
> + ERR("CorExitProcess called on another thread?\n");
> + return -1;
> you don't release mono_lib_cs here.
Doh, thanks.
> Similarly, in patch 3,
> STDAPI ClrCreateManag
Hi Vincent,
+EnterCriticalSection(&mono_lib_cs);
+if (!mono_handle)
+{
+ERR("CorExitProcess called on another thread?\n");
+return -1;
you don't release mono_lib_cs here.
Similarly, in patch 3,
STDAPI ClrCreateManagedInstance(LPCWSTR pTypeName, REF
On Aug 29, 2010, at 8:49 PM, Jeff Cook wrote:
> To clarify, it's not about having secret DIB engine code, it's about
> saying "I guess we just won't find time to provide useful feedback
> until some company sponsors it...", as I saw several times during the
> old threads.
What Jeremy neglected to
On Sun, Aug 29, 2010 at 2:18 PM, Jeff Cook wrote:
> I hate to stir the pot, especially as an unknown in the community, but
> I've spent the last few hours reading WINE's history regarding DIB
> engines and it is pretty distressing.
>
> I have seen expressions of frustration from many regarding the
Dmitry Timoshkov writes:
> This patch fixes the problem reported in the bug 12001.
>
> This version of the patch uses an internal message to fetch window state
> from a foreign thread. Another aproach could be to store the window state in
> the server, but that would require to introduce another
Eric Pouech writes:
> +if (tcgetattr(fd, &term) < 0) fprintf(stderr, "Couldn't get
> termios\n");
> +console_input->termios = term;
> +term.c_lflag &= ~(ECHO | ECHONL | ICANON | IEXTEN);
> +term.c_iflag &= ~(BRKINT | ICRNL | INPCK | ISTRIP | IXON);
Errors need to
Michael Stefaniuc wrote:
>
>Now that "that waive with $$$" isn't very likely as the cost/benefit
>ratio isn't very good. More likely is that Codeweavers will start
>working on a Quartz driver and that work will make the DIB engine
>"cheaper" to implement. Again, this is my *personal* opinion.
>
I
On Mon, Aug 30, 2010 at 2:11 PM, GOUJON Alexandre wrote:
> Can someone add this here
> http://wiki.winehq.org/GitWine#head-b20b05157175835751686365f9818ae978ceca23
Added this to the wiki. Can't find a way to create links to sections
within the page though; the ids of the sections are regenerated
On Mon, Aug 30, 2010 at 2:11 PM, GOUJON Alexandre wrote:
> Hey, that's pretty cool.
>
> Can someone add this here
> http://wiki.winehq.org/GitWine#head-b20b05157175835751686365f9818ae978ceca23
> ?
>
> Thanks for the tip Octavian !
Well, that's what I love about git the most -- the pretty colored
Add support for the qAttached packet. Main benefit is that gdb now will
ask if it should detach from the debuggee if it was attached to a
debuggee instead of asking whether the debuggee should be killed. (It
still will ask whether the debuggee should be killed if it launched the
debuggee itself).
On 08/30/2010 12:34 AM, Octavian Voicu wrote:
Try running:
git config --global color.ui auto
This will activate colorful output for all git commands (in particular
for `git diff' too).
Then, when you run `git diff' from a terminal you will see whitespace
errors (eg. trailing whitespace) highli
GOUJON Alexandre writes:
> On 08/30/2010 11:21 AM, Alexandre Julliard wrote:
>> Now you are overdoing it. I said to remove broken() for minor spelling
>> differences, not for everything. For instance confusing 936 and 950
>> codepages for Chinese is broken, it's not just a spelling difference
> S
Jeff Cook wrote:
> On Sun, Aug 29, 2010 at 7:12 PM, Jeremy White wrote:
>>> This could also help. If I recall correctly, Jeremy White mentioned
>>> at Wineconf 2008 that this was a major reason they haven't invested
>>> serious energy into one themselves: they had a hard time finding an
>>> appl
On 08/30/2010 11:21 AM, Alexandre Julliard wrote:
Now you are overdoing it. I said to remove broken() for minor spelling
differences, not for everything. For instance confusing 936 and 950
codepages for Chinese is broken, it's not just a spelling difference
Sorry, I'm trying to do my best but
N
Alexandre Goujon writes:
> I removed all broken() and ran the tests on all WineTestBot machines
> (https://testbot.winehq.org/JobDetails.pl?Key=4829)
> Then, I cleaned up tests accordingly : removed superflous broken() and
> extending ok().
> (https://testbot.winehq.org/JobDetails.pl?Key=4831)
22 matches
Mail list logo