You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the feature you'd like to request.
Currently, the table is static and you can't remove/add data. This does make sense since there isn't a lot of information to display yet. However, in the future other information like RSD, Mean, Median, and more will be needed. A good approach to this problem would be to allow users to modify the table by adding/removing certain data. The only exception to this obviously should be the segment name column since that is how you identify segments. If this feature is implemented, you should also restrict users from adding too many columns too (like maybe no more than 5-7).
Give reasoning on why this feature is needed.
Allows easier expansion of the program
Allows customization of the program for the user (for the table)
Another feature worthy of advertisement
Additional context
Keep in mind that whatever configuration the user left the table, should be saved when the user closes the splits. My suggestion on the default configuration of the table would be to have Personal Best and Possible Timesave shown. I also would suggest showing a giant + on the side of the table to show the user that they can add columns (and once they have reached the limit the plus sign will disappear). You can reuse the trash can for deleting columns too. If you have additional questions ask over discord.
The text was updated successfully, but these errors were encountered:
Describe the feature you'd like to request.
Currently, the table is static and you can't remove/add data. This does make sense since there isn't a lot of information to display yet. However, in the future other information like RSD, Mean, Median, and more will be needed. A good approach to this problem would be to allow users to modify the table by adding/removing certain data. The only exception to this obviously should be the segment name column since that is how you identify segments. If this feature is implemented, you should also restrict users from adding too many columns too (like maybe no more than 5-7).
Give reasoning on why this feature is needed.
Additional context
Keep in mind that whatever configuration the user left the table, should be saved when the user closes the splits. My suggestion on the default configuration of the table would be to have Personal Best and Possible Timesave shown. I also would suggest showing a giant + on the side of the table to show the user that they can add columns (and once they have reached the limit the plus sign will disappear). You can reuse the trash can for deleting columns too. If you have additional questions ask over discord.
The text was updated successfully, but these errors were encountered: