Hi all !
In the forums some spokesperson of an Indian company offering services
related to FOSS wants to add us to their online shop, see
http://www.reactos.org/forum/viewtopic.php?f=13
<http://www.reactos.org/forum/viewtopic.php?f=13&t=13780> &t=13780 for more
information. What do you think about this? How should we react? Should we
make clearer our line of conduct about such kind of things?
Cheers,
Hermès.
On 2014-11-23 10:49, pschweitzer(a)svn.reactos.org wrote:
> + ASSERT(NT_SUCCESS(RtlUpcaseUnicodeString(&IntFileName, FileName, TRUE)));
You need NT_VERIFY here or this will break debug builds.
Heheh, who could it be... ^^
It was always a event to watch you two arguing. ^^
Am 23.11.2014 21:57 schrieb Alex Ionescu <ionucu(a)videotron.ca>:
>
> I'm just going to chime in here and confirm that Timo does indeed own a master's diploma on surviving pissing contests, taught by the greatest master there ever was.
>
> Best regards,
> Alex Ionescu
>
> On Sat, Nov 22, 2014 at 11:47 AM, Timo Kreuzer <timo.kreuzer(a)web.de> wrote:
>>
>> Am 22.11.2014 11:39, schrieb Love Nystrom:
>>>
>>>
>>> On 2014-11-21 04.00, Timo Kreuzer wrote:
>>>>
>>>> Am 20.11.2014 14:18, schrieb Love Nystrom:
>>>>>
>>>>>
>>>>> Well... Actually not exactly the same.. ;)
>>>>> "if (f != FALSE)" requires an explicit comparison with a second operand,
>>>>
>>>> No, it does not. It requries the compiler to generate code that executes the following statement, when f is not 0.
>>>
>>>
>>> I suspect we look at it from two different viewpoints here..
>>> Yours is "C centric" and mine is "object code centric".
>>> You talk about what the compiler is required to do,
>>> and I talk about what comes out at the end of compilation.
>>
>> And what comes out at the end of the compilation is what the compiler creates. And the compiler is following the rules of the C standard and the rules of logic.
>> You claimed '"if (f != FALSE)" requires an explicit comparison with a second operand,' and that is factually wrong. No matter whether you are looking at it from the compiler perspective or from the perspective of an expressionist painter living in a yellow tree house on the bottom of Lake Tanganyika.
>>
>>>
>>> And.. dear friend.. don't turn this into a pissing contest.
>>
>> Don't even get me started. I battled the grand master and I survived.
>>
>>
>>> Let's check the egos in with the coat check girl at the entrance.
>>> May I ask how old you are?
>>
>> Are we talking about age or maturity?
>>
>> We better end this discussion, it's not leading anywhere. And you don't want me to turn into the Grinch and steal your Christmas.
>>
>> Thanks,
>> Timo
>>
>>
>> _______________________________________________
>> Ros-dev mailing list
>> Ros-dev(a)reactos.org
>> http://www.reactos.org/mailman/listinfo/ros-dev
>>
>
I don't know how many times I need to send the same link here but let's say that this is the last time:
this is a post about wpf but in the middle there is a paragraph about how win32k in windows processes mouse messages:
http://blogs.msdn.com/b/dwayneneed/archive/2008/09/08/transparent-windows-i…
And here is the important part:
Which HWND is the mouse over?
The operating system must respond very quickly to mouse movement. Windows uses a dedicated Raw Input Thread (RIT), running in the kernel, to handle the signals from the mouse hardware. The RIT quickly scans over the HWND hierarchy to see which window the mouse is over. Because the system must be responsive, no application code is invoked. For normal windows, the RIT checks the mouse position against the window's rectangle (or region, if one is set). But for layered windows, the RIT looks in the bitmap that specifies the content for the window and checks the effective transparency at that location (which can be affected by the constant opacity setting, the color key setting, or the per-pixel alpha channel). If the pixel is 100% transparent, the RIT skips the window and keeps looking. Once a window has been located, the mouse move flag is set on the thread that owns the window. This will cause the thread to receive a WM_MOUSEMOVE message the next time it calls GetMessage() and there are no other higher-priority messages.
Now let me explain why a flag is needed. The window manager needs to coalesce mouse move messages. If the mouse moves over a window and the system registers 10 positions over it, if the window doesn't process messages fast enough the unprocessed positions are dropped and only the last is kept. Even if another message gets between these mouse move messages get lost.
That's why the last mouse position is not stored in a message queue but in a field in the thread info. That's how the window manager worked the last 20 years in windows.
I'm sick and tired to see readable and correct code to be rewritten by shitty code, that is not readable and has obvious bugs without any reason why the previous implementation was wrong. I just give up. Do whatever you like with this shitty project of yours. I don't care anymore.
On 2014-11-15 13:34, dquintana(a)svn.reactos.org wrote:
> [SHELL32]
> * Commit the folder location fixes. They are mostly untested due to being unable to boot to desktop, but looking at the contents of the HDD after syssetup runs seems that the shortcuts are all created in their rightful place. If anyone is able to boot, feel free to test.
>
> Modified:
> branches/shell-experiments/dll/win32/shell32/wine/shellpath.c
So which is it; to Wine or not to Wine? If we need to fork this then
let's put it in another file? Or at least #ifdef __REACTOS__?
On 2014-09-29 19.00, ros-dev-request(a)reactos.org wrote:
> w0000t
> natively? via an emulator???
> what the....
> \o/
@ Javier
I just stumbled by and saw it..
Выглядит безумно, но я установил и запустил ReactOS через обертку
Qemu - Limbo ARM 7 на своем Samsung Galaxy S III mini.
It looks crazy, but I installed and started the ReactOS through wrapper
Qemu - Limbo ARM 7 on your Samsung Galaxy S III mini.
//
It might be interesting to try wedging an ARM build into the S3 though.
I was mulling over the possibility to squeeze it into an Maple Native..
Love
I saw an article on heise online (German-language website)
http://www.heise.de/newsticker/
on
ReactOS liest NTFS
http://www.heise.de/newsticker/meldung/ReactOS-liest-NTFS-2442615.html
Date is 05.11.2014, meaning just yesterday.
I subsequently looked on reactos.org and couldn't find any reference to this article.
So far, this is only for reading NTFS on ReactOS; writing ability stil has to be worked on.
This is the first article I've seen on this subject: looks like progress.
Some ReactOS developers must be familiar with this?
Tom