rcbench
Servo and ESC test bench: panel, IOmcu and shared C
Loading...
Searching...
No Matches
kst_file_load_t Struct Reference

What loading a file into a servo does. More...

#include <kst_file.h>

Data Fields

kst_file_verdict_t verdict
kst_file_kind_t kind
kst_type_t file_type
kst_type_t servo_type
uint8_t named
uint8_t fields
kst_field_set_t editable
kst_field_set_t skipped
kst_rules_t rules
kst_field_id_t hard_field
unsigned hard_line
kst_image_t target

Detailed Description

What loading a file into a servo does.

Field Documentation

◆ editable

kst_field_set_t kst_file_load_t::editable

the editable fields in which the file differs from the servo: what the load changes

◆ fields

uint8_t kst_file_load_t::fields

named fields of the field table: 27

◆ file_type

kst_type_t kst_file_load_t::file_type

the type the file states

◆ hard_field

kst_field_id_t kst_file_load_t::hard_field

KST_FILE_LOAD_HARD_LIMIT: the first field of the file whose value the broken hard rules need, by line; else and when no single field is at fault KST_F_COUNT

◆ hard_line

unsigned kst_file_load_t::hard_line

the line of hard_field in an edited file; 0 for a verified file and without a field

◆ kind

kst_file_kind_t kst_file_load_t::kind

the file's kind, for the display

◆ named

uint8_t kst_file_load_t::named

fields the file gives a value for: fields for a verified file, the lines read for an edited one

◆ rules

kst_rules_t kst_file_load_t::rules

every rule the load breaks, hard and soft, as kst_limits_edit() gives them. KST_FILE_LOAD_OK leaves soft rules only: the caller asks for their confirmation. 0 for a type mismatch

◆ servo_type

kst_type_t kst_file_load_t::servo_type

the type of the servo's image

◆ skipped

kst_field_set_t kst_file_load_t::skipped

fields of the other access classes in which the file differs from the servo after the load: they keep the servo's value

◆ target

kst_image_t kst_file_load_t::target

KST_FILE_LOAD_OK: the servo's image with the fields of editable set by kst_field_edit(), so register 01 follows a changed Max. Duty. Any other verdict: the servo's image


The documentation for this struct was generated from the following file: