Changes to the tutorials to reflect changes in the code generated by the new version of the commsdsl2comms.

Author: arobenko

tutorials/tutorial13/README.md

@@ -96,16 +96,16 @@ One other extra thing which is worth paying attention to is how the `switch` bas
 (see [include/tutorial13/dispatch/DispatchMessage.h](include/tutorial13/dispatch/DispatchMessage.h)) 
 is implemented.
 ```cpp
-template<typename TProtOptions, typename TMsg, typename THandler>
+template<typename TProtOptions, typename TId, typename TMsg, typename THandler>
 auto dispatchMessage(
-    tutorial13::MsgId id,
+    TId id,
     std::size_t idx,
     TMsg& msg,
     THandler& handler) -> decltype(handler.handle(msg))
 {
     using InterfaceType = typename std::decay<decltype(msg)>::type;
-    switch(id) {
-    case tutorial13::MsgId_M1:
+    switch(static_cast<std::intmax_t>(id)) {
+    case 1 /* 0x1 */:
     {
         switch (idx) {
         case 0U:
@@ -120,7 +120,7 @@ auto dispatchMessage(
         ...
         break;
     }
-    case tutorial13::MsgId_M2:
+    case 2 /* 0x2 */:
     {
         switch (idx) {
         case 0U:

tutorials/tutorial14/include/tutorial14/frame/checksum/PlusOneSum.h

@@ -1,5 +1,8 @@
 #pragma once
 
+#include <cstdint>
+#include <type_traits>
+
 namespace tutorial14
 {
 

tutorials/tutorial19/README.md

@@ -325,7 +325,7 @@ template <typename TMsgBase, typename TOpt = tutorial19::options::DefaultOptions
 class Msg3 : public
     comms::MessageBase<
         TMsgBase,
-        comms::option::def::StaticNumIdImpl<tutorial19::MsgId_M3>,
+        comms::option::def::StaticNumIdImpl<3 /* 0x3 */>,
         comms::option::def::FieldsImpl<typename Msg3Fields<TOpt>::All>,
         comms::option::def::MsgType<Msg3<TMsgBase, TOpt> >,
         comms::option::def::HasName,

tutorials/tutorial20/README.md

@@ -102,20 +102,6 @@ As the result, for all the messages that follow, the `Version` member field
 the `read()` operation is forwarded to the `<payload>` layer, which in turn invokes `read()` operation of 
 the message object. 
 
-----
-
-**SIDE NOTE**: If [CommsChampion Tools](https://github.com/commschamp/cc_tools_qt/wiki/How-to-Use-CommsChampion-Tools)
-are intended to be used for the protocol visualization and/or debugging, it is better to hide the `Version` field 
-inside the transport framing from being displayed altogether (because it's not really there). In such case it is
-recommended to slightly update the definition of the `<value>` layer above into the following:
-```xml
-<value name="Version" interfaceFieldName="Version" pseudo="true">
-    <ref field="Version" displayHidden="true" />
-</value>
-```
-
----
-
 Note that in this tutorial the client is also compiled to have the default version **5** (the default state of all the 
 fields in all the messages is valid for version **5**). In order to emulate version **4** client the 
 field of the pseudo `Version` `<value>` layer is modified when `Connect` message is sent:

tutorials/tutorial23/README.md

@@ -109,7 +109,7 @@ using ServerProtocolOptions =
 Without using options from the `t23_ext::options` the compilation will fail because
 `t23_ext::ns1::field::S1` [field](include/t23_ext/ns1/field/S1.h) attempts to
 access the options referencing `typename TOpt::t23_ext::ns1::field::S1`, which
-does not existing in the options provided by the `tutorial23`.
+does not exist in the options provided by the `tutorial23`.
 
 ```cpp
 template <typename TOpt = t23_ext::options::DefaultOptions, typename... TExtraOpts>

tutorials/tutorial24/README.md

@@ -64,7 +64,7 @@ template <typename TMsgBase, typename TOpt = tutorial24::options::DefaultOptions
 class Msg1 : public
     comms::MessageBase<
         TMsgBase,
-        comms::option::def::StaticNumIdImpl<tutorial24::MsgId_M1>,
+        comms::option::def::StaticNumIdImpl<1 /* 0x1 */>,
         comms::option::def::FieldsImpl<typename Msg1Fields<TOpt>::All>,
         comms::option::def::MsgType<Msg1<TMsgBase, TOpt> >,
         comms::option::def::HasName,

tutorials/tutorial6/README.md

@@ -173,7 +173,7 @@ using Frame = tutorial6::frame::Frame<Message>;
 ```
 
 The much better approach would be to reuse `AllMessages` inner type defined by the
-[comms::frame::ProtocolLayerBase](https://commschamp.github.io/comms_doc/classcomms_1_1protocol_1_1ProtocolLayerBase.html)
+[comms::frame::FrameLayerBase](https://commschamp.github.io/comms_doc/classcomms_1_1protocol_1_1ProtocolLayerBase.html)
 class which serves as a base type of any framing **layer**. The better code would be:
 ```cpp
 using AllMessages = Frame::AllMessages;