Am 18.11.2011 00:41, schrieb cgutman(a)svn.reactos.org:
> Author: cgutman
> Date: Thu Nov 17 23:41:18 2011
> New Revision: 54415
>
> URL: http://svn.reactos.org/svn/reactos?rev=54415&view=rev
> Log:
> [I8042PRT]
> - Implement support for hot plugging PS/2 mice if one was present at boot (same requirement as Windows)
> - Fixes bug 1395
>
>
Exellent!
--
Johannes Anderwald
Hi all,
As some of you know, I have started university about a month ago. Due to
the amount of time I have to spend on university tasks these days, I can
no longer fulfil all my project obligations. Therefore, I'm looking for
new maintainers in the following areas:
* RosBE-Unix
* My Web tools (especially Testman and the rest of the regression
testing system, but also GetBuilds/People Map/Subsystem integration)
* Release Engineering (unless Ziliang can fully takeover my position)
Provided that I find time, I'll introduce the new maintainers into these
tasks as good as possible.
I try to stay available for infrastructure and foundation tasks, but my
time for these will definitely be limited as well.
Best regards,
Colin
Debug log from testing cmake soundchip in KSStudio.
http://www.reactos.org/paste/index.php/9568/
Btw i'm getting crash in cmuda.sys on two different PCs (though i didn't
notiv=ce if chips are the same)
To get your attention, Johannes ;)
Am 16.11.2011 22:17, schrieb tfaber(a)svn.reactos.org:
> Author: tfaber
> Date: Wed Nov 16 21:17:38 2011
> New Revision: 54401
>
> URL: http://svn.reactos.org/svn/reactos?rev=54401&view=rev
> Log:
> [ATL] - Fix buffer overflow in CComDynamicUnkArray::Add. Found by Coverity (CID 2474)
> [NDK] - Remove meaningless const attribute from pointer rvalues to make Coverity's life easier
> -#define SharedUserData ((KUSER_SHARED_DATA *CONST)USER_SHARED_DATA)
> +#define SharedUserData ((KUSER_SHARED_DATA *)USER_SHARED_DATA)
It is like this (with the const) in wdm.h
#define SharedUserData ((KUSER_SHARED_DATA * const) KI_USER_SHARED_DATA)
maybe its supposed to express that "SharedUserData" is a constant and
not a variable... although that doesn't make much sense
>The Total Commander comboboxes for the left and right drive list
>are Unicode. However, Total Commander calls
>SendMessage(handle,CB_ADDSTRING,0,(LPARAM)ansitext);
>to add items as ANSI text. This seems to work, but it's adding some
>extra text at the end.
If I understand correctly, Total Commander is calling SendMessage, which in
this case is translated to SendMessageW (as the comboboxes are Unicode).
So TC is calling SendMessageW to append an ANSI string to a Combobox.
Let's give a look to SendMessageW implementation thanks to Doxygen:
http://doxygen.reactos.org/da/d64/winuser_8h_a18e5b961d742150a18d3039b5dd88…
02161 Result = NtUserMessageCall( Wnd,
02162 KMMsg.message,
02163 KMMsg.wParam,
02164 KMMsg.lParam,
02165 (ULONG_PTR)&Result,
02166 FNID_SENDMESSAGE,
02167 FALSE);
Line 2167 FALSE is the BOOL ANSI param of NtUserMessageCall.
But in this case the BOOL ANSI should be TRUE as the string is really ANSI.
So since this moment we are treating TC call ( SendMessageW(handle,CB_ADDSTRING,0,(LPARAM)ansitext); )
in the same way as we would be treating SendMessageW(handle,CB_ADDSTRING,0,(LPARAM)unicodetext);
This seems a bug for me.
Feel free to correct me, but seems that SendMessageW is able to set both kind
of strings ANSI and UNICODE in Windows, while we are forcing to our
SendMessageW implementation to treat them as UNICODE always.
Am I wrong?
This could be a big potential issue as this could affect to all the SendmessageW calls.
This is all just a guess, so please feed me with your knowledge.
Thanks a lot!
Hi all,
Looking at
https://verein.ing-diba.de/sonstiges/33378/reactos-deutschland-ev, we
have scored the 810th place in the tough competition and just won 1000
EUR for the foundation! :-)
Even if we lost our position in the top of the list, comparable German
Open-Source foundations like KDE e.V. or Free Software Foundation Europe
are both out of the game.
I'd like to use this opportunity to thank every voter for the great
support towards the project! Over 8000 votes in four weeks really shows
that we still have a huge fan base.
Best regards,
Colin
I'm getting questions, if it's "just formatting and no code changes",
why author names are removed for good and not readded in the new file?
WBR,
Aleksey Bragin.
On 07.11.2011 3:01, ion(a)svn.reactos.org wrote:
> Author: ion
> Date: Sun Nov 6 23:01:04 2011
> New Revision: 54323
>
> URL: http://svn.reactos.org/svn/reactos?rev=54323&view=rev
> Log:
> [KERNEL32]: Move the "curdir.c" APIs into path.c as well, as they are Path APIs. No code changes (just formatting and moving to DPRINTs).
> Removed: trunk/reactos/dll/win32/kernel32/client/file/curdir.c
> URL: http://svn.reactos.org/svn/reactos/trunk/reactos/dll/win32/kernel32/client/…
> ==============================================================================
> --- trunk/reactos/dll/win32/kernel32/client/file/curdir.c [iso-8859-1] (original)
> +++ trunk/reactos/dll/win32/kernel32/client/file/curdir.c (removed)
> @@ -1,388 +1,0 @@
> -/* $Id$
> - *
> - * COPYRIGHT: See COPYING in the top level directory
> - * PROJECT: ReactOS system libraries
> - * FILE: lib/kernel32/file/curdir.c
> - * PURPOSE: Current directory functions
> - * PROGRAMMER: Eric Kohl
> - * Filip Navara
> - * Steven Edwards
> - * Thomas Weidenmueller
> - * Gunnar Andre' Dalsnes
> - * UPDATE HISTORY:
> - * Created 30/09/98
> - */
>
Hi!
What I have run across in regards of ReactOS send message subsystem,
ros is not packing before co_MsqSendMessage and unpacking after
co_IntCallWindowProc! Instead packing before co_IntCallWindowProc with
send message. Does that not raise any questions?
co_IntSendMessageWithCallBack seems to do it almost right, but
IntCallWndProc/Ret should be called when calling the client via
co_IntCallWindowProc and should pack before the call to MsqWakeQueue
and then unpack after the call to co_IntCallWindowProc. Confused?
Basing this on IntCallLowLevelEvent and co_IntCallLowLevelHook when
the lParam is used to save information that could get lost in a stack
switch or release.
Setting up the pattern; Pack before co_MsqSendMessage or related
friends and Unpack after calling co_IntCallWindowProc to client. Have
co_MsqDispatchOneSentMessage call something other than
co_IntSendMessage so the Packed data can be handled correctly when
calling to the client via co_IntCallWindowProc.
I'm sure Michael Martin has brought this up to me on many occasions.
Let's see where this goes!
Thanks,
James