If a table uses "Skip Header Row on Page 1" feature,
but the table only takes up 1 page (or 1 column), It will lead to duplication in the table of contents.
Waiting for an official fix for this bug may be too long.
Is there a script to find these tables and then unskip the page 1 header rows?
Initially it may have been correctly needed.
They didn't take up 2 pages (2 columns) later because the layout moved.
But you don't know which ones made the setting
2 Correct answers
Alright - maybe something like this
Before running the script on a large or important document, test it on a smaller sample file to ensure it works as expected. Save a backup of your document as a precaution.
This is just and idea, maybe it does what you want and maybe not, but hopefully it can be refined or used as foundation going forward.
// Loop through all tables in the active document
var tables = app.activeDocument.stories.everyItem().tables.everyItem().getElements();
for (var i = 0; 
// Loop through all tables in the active document
var myTables = app.activeDocument.stories.everyItem().tables.everyItem().getElements();
var T = myTables.length, t;
for ( t = 0; t < T; t++ ) {
var myTable = myTables[t];
if ( myTable.storyOffset.textColumns[0] != myTable.storyOffset.paragraphs[0].insertionPoints[-1].textColumns[0] ) {
myTable.select();
alert( "Do Something! ... What? No idea!!!" )
}
}
(^/)
51
Replies
Yeh I can't figure that out.
By @Eugene Tyson
Figure out what? There is ALWAYS a way to skin a cat š
Please quote message you're replying to - this forum is a mess.
// Place The Cursor Inside A Table Cell:
if ( app.selection[0].parent.constructor.name != "Cell" ) {
alert( "Place The Cursor Inside A Table Cell! ..." )
exit();
} else {
var myTable = app.selection[0].parent.parent;
if ( myTable.storyOffset.parentTextFrames[0] != myTable.storyOffset.paragraphs[0].insertionPoints[-1].parentTextFrames[0] ) {
if ( myTable.storyOffset.parentTextFrames[0].parentPage === myTable.storyOffset.paragraphs[0].insertionPoints[-1].parentTextFrames[0].parentPage ) alert( "1a/ Table on 2 text frames and 1 page" )
else alert( "1b/ Table on " + Number( (myTable.storyOffset.paragraphs[0].insertionPoints[-1].parentTextFrames[0].parentPage.documentOffset - myTable.storyOffset.parentTextFrames[0].parentPage.documentOffset) + 1) + " pages" )
} else if ( myTable.storyOffset.textColumns[0] != myTable.storyOffset.paragraphs[0].insertionPoints[-1].textColumns[0] && myTable.storyOffset.parentTextFrames[0].parentPage === myTable.storyOffset.paragraphs[0].insertionPoints[-1].parentTextFrames[0].parentPage ) alert( "2/ Table on 2 columns and 1 page" )
else alert( "3/ Table on 1 column on 1 page" )
}
(^/)
No problems found except that it doesn't work when it contains overflow text
No other problems were found.
Only 1 column or 1 page. But there is an overflow
== correspondsćmyTable.skipFirstHeader = false;
or
!= correspondsćmyTable.skipFirstHeader = true;
All failing.
----------------------Below is the code for the test--------------------
// Loop through all tables in the active document
var myTables = app.activeDocument.stories.everyItem().tables.everyItem().getElements();
var T = myTables.length, t;
for ( t = 0; t < T; t++ ) {
var myTable = myTables[t];
if ( myTable.storyOffset.textColumns[0]== myTable.storyOffset.paragraphs[0].insertionPoints[-1].textColumns[0] ) {
//myTable.select();
myTable.skipFirstHeader = false;
//alert( "Do Something! ... What? No idea!!!" )
}
}
Otherwise, the catalog (contents) you extracted, will have duplicate items.
This is a big bug.
By @dublove
No, it's not, it's just your specific layout / design.
Because, I'm pretty sure there is / are much easier way(s) to solve your "problems" - and you're "trying too hard" to accomplish everything at once.
By @Robert at ID-Tasker
I also think you're way better off. Well hope you can share.
I've been waiting for you 10,000 years.
It is usually used for printing.
Interactive output is only used for proofreading. It can be disregarded.
AdChoices