Table Improvement Tips

I would appreciate an option in the table properties that allows to deactivate the question "Save table?" after changing any values and leaving the ensemble without saving it.
Never want to be asked because if i wanted to save the table data i could do that out of the table context menu or otherwise would save an instance of the ensemble.
Another cool effect would be to have the option to use tables just for visualization matters.
Closing an ensemble with loads of tables not saving it can really be distressing.

Another one in table properties could be:
If using more than one instance usually saving table data as "xxx" updates all instances to "xxx" but loading table data "yyy" does not load "yyy" to the other instances. I think this is unreasonable.
Instances should always behave as one table whether i save data or load...

Oh, yes, another one is:
Audio tables could behave just as samplers (or sometimes even more interesting) if i were able to load more than one sample into it.
Unfortunately i can record to more rows (y>1) but if i load a sample all selected properties are cancelled.
I think set xy-settings should stay as they are - the user being able to define where any audio data is loaded (x in between any existing data, y -> new row). Reaktor would get interesting Wave-Editor options.

Last but not least: A new table module "midi table" which can load, record, save midi data with two ins (Gate, Pitch) and two outs (dito). Voices (Gate/Pitch rows) like instrument or valuable in properties...
I know a table sequencer can be realized very well but it would be cool to have it as a module (i can`t think of another way to implement midi files because of Gate & Pitch being in one data).

BTW: I´m not moaning about the usability of the table modules. Infact they are a huge improvement to 2.3!!!

Greetings
[...soundvision...]