Quote:
Originally Posted by scylla
If OOP has mulitple actions, then there will also be multiple spots where IP gets to act. So for example, if OOP either bets or checks then IP's actions would need to be displayed separately for each scenario by OOP. And each data point will have been measured for a different range and frequency for OOP. This means that this data for IP is essentially not suitable for being displayed in a table/graph. We can decide to ignore this, and plot it anyhow for later releases, but right at this moment it has been left out for this reason.
a filter would be useful and make it easier to display. A drop down box that shows all the potential actions Player 1 can take, and then the table will display Player 2's actions depending on which of Player 1's actions is selected.
This seems like exactly the kind of stuff that the database functionality would be used for and could be a huge selling point.
To add to it, a search function would be useful because the "sort" function you mentioned has limited usefulness once you are using 50+ flops. So it would be in high demand i reckon!
Thanks