Etterna 0.74.4
Loading...
Searching...
No Matches
Public Member Functions | Public Attributes | List of all members
metaHandInfo Struct Reference

#include <MetaHandInfo.h>

Collaboration diagram for metaHandInfo:
Collaboration graph
[legend]

Public Member Functions

 metaHandInfo (Calc &calc)
 
void full_reset ()
 
void operator() (const metaHandInfo &last, const col_type &ct)
 

Public Attributes

col_type _ct = col_init
 col
 
col_type _last_ct = col_init
 
base_type _bt = base_type_init
 type of cross column hit
 
base_type _last_bt = base_type_init
 
base_type last_last_bt = base_type_init
 needed for the BIGGEST BRAIN PLAYS
 
meta_type _mt = meta_type_init
 
meta_type _last_mt = meta_type_init
 
int offhand_taps = 0
 number of offhand taps before this row
 
int offhand_ohjumps = 0
 
Calc_calc
 

Detailed Description

potentially outdated comment below this should contain most everything needed for the generic pattern mods, extremely specific sequencing will take place in separate areas like with rm_sequencing, and widerange scalers should track their own interval queues metanoteinfo is generated per row, from current noteinfo and the previous metanoteinfo object, each metanoteinfo stores some basic information from the last object, allowing us to look back 3-4 rows into the past without having to explicitly store more than 2 mni objects, and we can recycle the pointers as we generate the info metanoteinfo is generated per hand, not per note or column. it contains the relevant information for determining what the column configuation of each hand is for any row, and it contains timestamp arrays for each column, so it is unnecessary to generate information per note, even though in some ways it might be more convenient or clearer

Member Function Documentation

◆ full_reset()

void metaHandInfo::full_reset ( )
inline

we need to reset everything between hands or the trailing values from the end of one will carry over into the start of the other, not a huge practical deal but it could theoretically be abused and it's good practice to reset anyway


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