As PDF in Foxit Reader. But yeah ^^
Von Samsung Mobile gesendet
<div>-------- Ursprüngliche Nachricht --------</div><div>Von: Hermès BÉLUSCA - MAÏTO <hermes.belusca(a)sfr.fr> </div><div>Datum:24.09.2014 20:13 (GMT+01:00) </div><div>An: 'ReactOS Development List' <ros-dev(a)reactos.org> </div><div>Cc: </div><div>Betreff: Re: [ros-dev] Video of our ReactOS presentation online </div><div>
</div>Also, were you actually running your powerpoint presentation *in* ROS ?! :D
De : Ros-dev [mailto:ros-dev-bounces@reactos.org] De la part de Hermès BÉLUSCA - MAÏTO
Envoyé : mercredi 24 septembre 2014 19:37
À : 'ReactOS Development List'
Objet : Re: [ros-dev] Video of our ReactOS presentation online
Wow !! 43 minuten of video ^^
H.
De : Ros-dev [mailto:ros-dev-bounces@reactos.org] De la part de Colin Finck
Envoyé : mardi 23 septembre 2014 22:17
À : ros-dev(a)reactos.org
Objet : [ros-dev] Video of our ReactOS presentation online
Hi all,
As the question usually arises: The video of Daniel's and my ReactOS presentation at Kieler Linux Tage is online: http://youtu.be/oQsKzW_Rx3k
Do whatever you want with it ;)
This is probably the first ever ReactOS presentation held using ReactOS itself! And it worked like a charm!
We also met an author of German news site heise.de there, who wants to publish an article about the current state ReactOS soon.
Cheers,
Colin
Hello,
Let me invite you to the monthly status meeting taking place 25th of
September, 19:00 UTC. If there are any proposals regarding moving the
meeting date/time - please send them today.
IRC service will only be started shortly before the meeting. Your
participation passwords and server address will be emailed to you
shortly before the meeting starts, and they are going to be different
once again as they are not stored in any database. Hopefully it's not
much of inconvenience.
If someone still is not getting passwords sent before a meeting - please
email Pierre before the meeting started to get one.
Please send agenda proposals to me before the meeting, so that we can
start with a proposed agenda.
Proposed agenda points so far:
- Agile missing in Jira (looks like an incompatible version)
- new on-demand builders (Clang, VC, x64, arm, branch, patch)
- testbot on a win 2003 machine
Let me know if any of those is already resolved. Thanks!
Regards,
Aleksey Bragin
Am 17.09.2014 11:54, schrieb jgardou(a)svn.reactos.org:
> Author: jgardou
> Date: Wed Sep 17 09:54:14 2014
> New Revision: 64176
>
> URL: http://svn.reactos.org/svn/reactos?rev=64176&view=rev
> Log:
> [GDI32]
> - Fix up values got from win32k in GetOutlineTextMetrics and do not fail if the provided buffersize is only sizeof(OUTLINETEXTMETRICW).
> CORE-8507 #resolve
>
> Modified:
> trunk/reactos/win32ss/gdi/gdi32/objects/font.c
>
> Modified: trunk/reactos/win32ss/gdi/gdi32/objects/font.c
> URL: http://svn.reactos.org/svn/reactos/trunk/reactos/win32ss/gdi/gdi32/objects/…
> ==============================================================================
> --- trunk/reactos/win32ss/gdi/gdi32/objects/font.c [iso-8859-1] (original)
> +++ trunk/reactos/win32ss/gdi/gdi32/objects/font.c [iso-8859-1] Wed Sep 17 09:54:14 2014
> @@ -9,8 +9,19 @@
>
> #include <precomp.h>
>
> +#include <math.h>
> +
> #define NDEBUG
> #include <debug.h>
> +
> +/* Rounds a floating point number to integer. The world-to-viewport
> + * transformation process is done in floating point internally. This function
> + * is then used to round these coordinates to integer values.
> + */
> +static __inline INT GDI_ROUND(FLOAT val)
> +{
> + return (int)floor(val + 0.5);
> +}
roundf() is the appropriate function here. The older MS crt headers
don't have the *round*() functions, but VS 2013 headers seem to have
them (according MSDN).
I propose adding them inside some #ifdef, instead of reimplementing them
in different places.
For the other functions: strange coding style. Is this taken from wine?
Hi,
I'd like to propose some topics for the next meeting:
- Agile missing in Jira (looks like an incompatible version)
- new on-demand builders (Clang, VC, x64, arm, branch, patch)
- testbot on a win 2003 machine
Timo
Awesome stuff!
Am 11.09.2014 22:55, schrieb jgardou(a)svn.reactos.org:
> Author: jgardou
> Date: Thu Sep 11 20:55:42 2014
> New Revision: 64121
>
> URL: http://svn.reactos.org/svn/reactos?rev=64121&view=rev
> Log:
> [KDGDB]
> - introduce KDGDB, a KDCOM-like DLL, wrapping the KD protocol and the GDB remote protocol together.
> It is not fully functional, but for now it permits source-level debugging in some modules. More will be added as I feel the need and find the time to work a bit more on it. (That is, unless an angel comes and resume the work)
> To use it, set GDB and _WINKD_ to TRUE in your CMakeCache.txt. Using separate debug symbols is also a good idea.
>
>
while(1); is not really a good solution. It should be something that is
visible in GDB.
But I fear that a KeBugCheck() won't work here, since it will rely on a
working KD connection.
Maybe a KD_ASSERT() macro, that calls KdAssert() on failure or
something, resets the GDB connection somehow, issues a debug print and
then halts.
Am 12.09.2014 22:23, schrieb jgardou(a)svn.reactos.org:
> Author: jgardou
> Date: Fri Sep 12 20:23:08 2014
> New Revision: 64127
>
> URL: http://svn.reactos.org/svn/reactos?rev=64127&view=rev
> Log:
> [KDGDB]
> - Add a callback mechanism permitting to "simulate" KD send <-> receive loop without having to actually communicate to GDB
> - Use that to update the program counter when cont'ing a breakpoint
> Now cont'ing an assertion failure is possible, since we actually get beyond the int 3 instruction
>
> Modified:
> trunk/reactos/drivers/base/kdgdb/gdb_input.c
> trunk/reactos/drivers/base/kdgdb/kdgdb.h
> trunk/reactos/drivers/base/kdgdb/kdpacket.c
>
> +)
> +{
> + DBGKD_MANIPULATE_STATE64* State = (DBGKD_MANIPULATE_STATE64*)MessageHeader->Buffer;
> +
> + /* We just confirm that all went well */
> + if ((PacketType != PACKET_TYPE_KD_STATE_MANIPULATE)
> + || (State->ApiNumber != DbgKdSetContextApi)
> + || (State->ReturnStatus != STATUS_SUCCESS))
> + {
> + /* Should we bugcheck ? */
> + while (1);
> + }
> +}
> +
> +static
> +KDSTATUS
> +SetContext(
> + _Out_ DBGKD_MANIPULATE_STATE64* State,
> + _Out_ PSTRING MessageData,
> + _Out_ PULONG MessageLength,
> + _Inout_ PKD_CONTEXT KdContext,
> + _In_opt_ KDP_MANIPULATESTATE_HANDLER ManipulateStateHandler
> +)
> +{
> + State->ApiNumber = DbgKdSetContextApi;
> + State->Processor = CurrentStateChange.Processor;
> + State->ReturnStatus = STATUS_SUCCESS;
> + State->ProcessorLevel = CurrentStateChange.ProcessorLevel;
> + MessageData->Length = sizeof(CurrentContext);
> +
> + if (MessageData->MaximumLength < sizeof(CurrentContext))
> + {
> + while (1);
> + }
> +
>
