reflection/member_ranges

• C

  View on GitHub

  #include <member_ranges.h>
  #include <stdio.h>
   
  typedef struct {
      double value;
  } CpuUtilization;
   
  int main(int argc, char *argv[]) {
      ecs_world_t *ecs = ecs_init_w_args(argc, argv);
   
      ECS_COMPONENT(ecs, CpuUtilization);
   
      // Register reflection data warning and error ranges. This adds metadata to
      // a type which can be used by tools (like the explorer) to visualize data.
      ecs_struct(ecs, {
          .entity = ecs_id(CpuUtilization),
          .members = {{
              .name = "value", 
              .type = ecs_id(ecs_f64_t),
              .range =         {0, 100}, // Specifics values that the member can assume
              .warning_range = {0, 60},  // Values outside this range are considered a warning
              .error_range =   {0, 80}   // Values outside this range are considered an error
          }}
      });
   
      ecs_entity_t m1 = ecs_entity(ecs, { .name = "MachineA" });
      ecs_set(ecs, m1, CpuUtilization, {50});
   
      ecs_entity_t m2 = ecs_entity(ecs, { .name = "MachineB" });
      ecs_set(ecs, m2, CpuUtilization, {75});
   
      ecs_entity_t m3 = ecs_entity(ecs, { .name = "MachineC" });
      ecs_set(ecs, m3, CpuUtilization, {90});
   
      // Uncomment this line and open 
      //   https://www.flecs.dev/explorer?show=query&query=CpuUtilization 
      // to see how ranges affect visualization:
      // return ecs_app_run(ecs, &(ecs_app_desc_t){ .enable_rest = true });
      return ecs_fini(ecs);
  }

• C++

  View on GitHub

  #include <member_ranges.h>
  #include <iostream>
   
  struct CpuUtilization {
      double value;
  };
   
  int main() {
      flecs::world ecs;
   
      ecs.component<CpuUtilization>()
          .member<double>("value")
              .range(0.0, 100.0)        // Specifics values that the member can assume
              .warning_range(0.0, 60.0) // Values outside this range are considered a warning
              .error_range(0.0, 80.0);  // Values outside this range are considered an error
   
      ecs.entity("MachineA").set<CpuUtilization>({ 50.0 });
      ecs.entity("MachineB").set<CpuUtilization>({ 75.0 });
      ecs.entity("MachineC").set<CpuUtilization>({ 90.0 });
   
      // Uncomment this line and open 
      //   https://www.flecs.dev/explorer?show=query&query=CpuUtilization 
      // to see how ranges affect visualization:
      // ecs.app().enable_rest().run();
  }