Hi,
thanks for the further explanations!
I see your points, but I think the current handling is justified:
TablePress has a documention for its “own” features at https://tablepress.org/documentation/
This does indeed not really cover the “Custom Commands” field, as that can be used for adding/changing advanced functionality from the DataTables JS library only. Thus, it requires a little bit of coding, with commands that you have found in the actual DataTables Documentation at https://www.datatables.net/ (to which there is a link right below the text field). It would simply not be justified to copy all of that over to the TablePress Documentation, as it simply is a different product that’s just used as one part of TablePress.
Showing/Hiding columns: This is actually a fairly widely used feature. It for example allows people to draft data in their table, without already having to show it to the site visitors. Also, many users import tables e.g. from Excel, where those tables might have information in them that they don’t want to show. In that case, they could of course delete it, but then they are for example using the “Import” feature with the “Replace existing table” option. They would then have to delete that data everytime again, from which they are saved with the Hide feature.
Another use cases would be to add more “internal” data to a record in a table, like an internal rating or whatever. Some people also put special filter terms (for the Row Filter Extension from https://tablepress.org/extensions/row-filter/ ) into hidden columns.
So, trust me, there are valid use cases for this, and people are using the feature ??
Do those explanations make sense?
And thanks for offering help, I really appreciate it! Don’t forget that TablePress is open source, and everything is on Github at https://github.com/TobiasBg/TablePress , waiting for your improvements ??
Regards,
Tobias