FriFlo

Title says it all ... I will have a huge number of tables, once this project of mine is finished. But I cannot find how to tell the tables to not open. Actually, I guess I could just loadbang a "wclose" message and that would save me from having to close them manually. However, isn't there an option or attribute, so they won't open at all? I need your help ... cannot find anything like that.

Title says it  all ... I will have a huge number of tables, once this project of mine is finished. But I cannot find how to tell the tables to not open. Actually, I guess I could just loadbang a "wclose" message and that would save me from having to close them manually. However, isn't there an option or attribute, so they won't open at all? I need your help ... cannot find anything like that.


how-do-i-prevent-the-table-graphical-window-to-open-at-the-start-of-max

I'm not at a computer where I can test it, but I think you just need to save your patch with them all closed.

Thanks Christopher, but unfortunately, saving the patch with them closed is not the reason. All of them get opened on launch of Max, wether they were opened or closed the last time I saved. The patch is a sub patcher within a bigger project - maybe that has to do with it?

My temporary solution for now is to send a 'wclose'-message to all of those tables with a loadbang. But the template is going to grow! Now, for testing there are only 32 tables there (16 for each midi port). It is going to expand to probably 64 Ports! That is why I want to avoid any unnecessary patching, as it makes everything even more complicated. It would be great, if someone could come up with a reason, why this might happen ...

Thanks Christopher, but unfortunately, saving the patch with them closed is not the reason. All of them get opened on launch of Max, wether they were opened or closed the last time I saved. The patch is a sub patcher within a bigger project - maybe that has to do with it?
My temporary solution for now is to send a 'wclose'-message to all of those tables with a loadbang. But the template is going to grow! Now, for testing there are only 32 tables there (16 for each midi port). It is going to expand to probably 64 Ports! That is why I want to avoid any unnecessary patching, as it makes everything even more complicated. It would be great, if someone could come up with a reason, why this might happen ...


If, by "sub patcher" you mean a named file that you're using as an abstraction within your main patch, you'll need to open 

 patch, close the table window(s), and save it.

If, by "sub patcher" you mean a named file that you're using as an abstraction within your main patch, you'll need to open that patch, close the table window(s), and save it.


I meant an object 'p [name]' and ... Yes, I did open (doubleclick) it and saved. The main patcher, however is part of a max-project, so that might have to do with it still opening the table Windows on launch. I send them the wclose for now, until I found a solution to fix it.

I meant an object  'p [name]' and ... Yes, I did open (doubleclick) it and saved. The main patcher, however is part of a max-project, so that might have to do with it still opening the table Windows on launch. I send them the wclose for now, until I found a solution to fix it.


I actually found that if you change the name of the table the problem dissappears. Maybe in some version of the table in another patch I left it open, anyway that worked.

I am also having this problem and saving the patch with them closed doesn't seem to work. 

Changing their name does work, but then you lose an saved data in the table. 

I am also having this problem and saving the patch with them closed doesn't seem to work. 
Changing their name does work, but then you lose an saved data in the table. 


How do I prevent the table graphical window to open at the start of Max?