i think one thing i did not anticipate in my initial design was that most VE tables have more than one interval on map, rpm, or both.. for example they'll go 20,30,40,50,80,100 or something
so i think i will write in support for arbitrary column definitions and drop my current method of base/n_values/interval
will make it take a bit longer for users to define a simple fixed interval table, but the presets will be perfect this way, and i'm seeing a lot less fixed interval tables than i expected.
problem is this adds complexity, as intervals don't involve any actual lookup, but now i'll have to write a super speedy way to figure out cell borders. i'd like to keep it fast, since right now it's working well with auto-refreshing, so any changes to layout or analysis engine can update almost instantly.. my analysis algorithm is cell iterated rather than data point iterated (it finds the appropriate data point groupings for each cell, not the appropriate cell for each data point), the increased complexity of arbitrary cell border definitions during analysis should only be affected per number of table cells. i think it'll be alright.
Bookmarks