From 7b373744d2d69c362a371533650c13fdb9f5cf82 Mon Sep 17 00:00:00 2001 From: Konstantin Aladyshev Date: Fri, 23 Sep 2022 17:47:15 +0300 Subject: Add info that RouteConfig can bypass VFR checks Signed-off-by: Konstantin Aladyshev --- .../Lesson_Configuration_Language_5/README.md | 13 ++++++++++++- 1 file changed, 12 insertions(+), 1 deletion(-) diff --git a/Lessons_uncategorized/Lesson_Configuration_Language_5/README.md b/Lessons_uncategorized/Lesson_Configuration_Language_5/README.md index 4e8943f..6165772 100644 --- a/Lessons_uncategorized/Lesson_Configuration_Language_5/README.md +++ b/Lessons_uncategorized/Lesson_Configuration_Language_5/README.md @@ -215,7 +215,18 @@ Variable NV+BS 'EF2ACC91-7B50-4AB9-AB67-2B04F8BC135E:CheckboxValue' DataSize = 0 ``` -If you want to, you can issue route requests to our `HIIFormDataElements.efi` form storage, just remember two things: +If you want to, you can issue route requests to our `HIIFormDataElements.efi` form storage, just remember these things: - like with the `extract` case it is not mandatory for the OFFSET/WIDTH to be on element boundaries, - don't forget to pay attention to the byte order in the `VALUE=` string and to the order of bytes in the actual form elemet. The order is reversed. So you will need to pass string element data backbards (i.e `VALUE=`). +- changing element via `RouteConfig()` call can bypass some VFR limitations. For example even if numeric element has `minimum` and `maximum` attributes set like this: +``` +numeric + ... + minimum = 0, + maximum = 10, + ... +endnumric +``` +it would still possible to set a value outside of these limits. + -- cgit v1.2.3-18-g5258