643041_en-US

liliconcom

Re: Set Visibility of Data Tables

Another case of lost text, I see.  I'll try to remember what I put.

 

I like to use private tables to avoid table names popping in and out of the Window List or to keep people from meddling with certain data tables.  When troubleshooting a table I normally have private, I wanted to set it to private again.  I found <

 

I'd like to have simple messages to set data tables' visibility.  At a minimum, fix the <

 

This is just an ease of use improvement.

Re: Set Visibility of Data Tables

Set Private does work -- it just doesn't get rid of the window or get rid of the entry from the HomeWindow's Table list, but it does make the table private and prevent it from appearing in the standard method of getting currently open data tables.

 

You could pair the Set Private command with a Show Window command, something like this?

 

Names Default To Here( 1 );
dt = Open( "$SAMPLE_DATA/Big Class.jmp" );
Show( Get Data Table List() );
Wait( 1 );

dt << Show Window( 0 ) << Set Private; // make table private and not visible
Show( Get Data Table List() );

It appears as invisible in the Home Window list -- but it is private and double-clicking on it will bring it into view but it will still be private.

 

Re: Set Visibility of Data Tables

I just saw your comment, @ErraticAttack.  I see I was mistaken, somewhat.  <

Re: Set Visibility of Data Tables

A an alternative:

All commands which create a data table (open, subset, summary, concatenate, ...) have an option (..., Private ) to hide the table when it's generated.

That's not exactly what is requested here (i.e. making a table private AFTER it's generated) - but for 99% of the cases it's even better

 

What is actually missing is an invisible/private option for MFI: 
Private option for Import Multiple Files 
but is seems it will come soon:

Private tables with Multiple File Import function 

Set Visibility of Data Tables

What inspired this wish list request?

 

 

What is the improvement you would like to see? 

 

 

 

 

 

 

<<VISIBILITY></VISIBILITY>

 

 

 

Why is this idea important? 

 

 

Automation and ScriptingRe: Set Visibility of Data Tables

@mmarchandTSI , I think you are right and I have the same issue... the scripting index says <

and it's weird that the private you get when create a private table would be different that what you get from << set private

Re: Set Visibility of Data Tables

the issue got "fixed": documentation was adjusted to the actual behavior.

 

JMP17:

 

JMP18:

 

and the user who wants to set a data table private and hide it (like it was advertised in JMP17)?
... he can use:

dt << Set Private( 1 );
dt << showWindow(0)

and afterwards, maybe:

dt << Set Private( 0 );
dt << showWindow(1)

Re: Set Visibility of Data Tables

ah, no ...

Names Default to Here(1);
dt = Open( "$SAMPLE_DATA/Big Class.jmp", Private  );

dt << Set Private( 0 );
dt << showWindow(1)

-> dt stays private, right?

Re: Set Visibility of Data Tables

I agree with you @hogi .

 

My list of weird things about private tables includes <self reference for a table script - JMP User Community

 

Also, I see a table that starts normal and is set private with  <