Dear Tpk
Very very thank you so much!!!!!!!! for your helping skills
Thanks
kathik
Dear Tpk
Very very thank you so much!!!!!!!! for your helping skills
Thanks
kathik
Dear Pickory
How to done two colors control the script. one help friend.
Plz send your coding
Thanks
Karthik s
I've done a good amount of testing on Windows and Mac, and here's a report of where the progress bar bug bites. (The bug is that the progress bar doesn't progress; well, it doesn't appear altogether. Also this bug isn't really limited to the progress bar: in every case of a modeless window [a "palette" window], nothing refreshes while the script is being run, as per the table below.)
Interestingly, it makes a difference whether the script is run from the Scripts panel or via a script menu action. And of course, because the ScriptUI engine changed between CS6 and CC, that makes a big difference as well (at least on Windows).
1. Mac OS (Yosemite)
InDesign CS6 | InDesign 2015 | |||
---|---|---|---|---|
Redraw On | Redraw Off | Redraw On | Redraw Off | |
1. Run from panel | ✓ | X | ✓ | X |
2. Run from menu | X | X | X | X |
2. Windows 7
InDesign CS6 | InDesign 2015 | |||
---|---|---|---|---|
Redraw On | Redraw Off | Redraw On | Redraw Off | |
1. Run from panel | ✓ | ✓ | ✓ | X |
2. Run from menu | ✓ | ✓ | X | X |
Summary:
1. In InDesign CS6 on Windows, the progress bar always works!
2. In every other case, the progress bar will only work if the script is run from the scripts panel with redraw on.
There has been at least one other post about this issue here on the forum, but I've tried to systematically test each possibility. Post here if you've noticed different results!
I don't have Windows 10 to test on, but I presume it's the same. Ditto El Capitan.
If anyone knows of a workaround, please share it here!
Ariel
Karthiks,
its an experimental plugin, this thread promoted me to nearly finish it. just a bit of fun. Tpk's, script is better.
Best.
P.
Hi Ariel,
I used a workaround inspired by Marc Autret's work which consisted in creating a new window instance for every step while closing the underlaying one. That worked well a few versions ago (CS6 or CC). But I recently tried to reuse this trick for a project in a CC14/15 environment and that doesn't work anymore.
Perhaps Marc or Peter will share some thoughts here.
I don't know what to think of ScriptUI those days and should I say of UIs in general as there are inconsistencies and trouble whatever the ecosystem you try to work with…
Loic
By paragraph style I believe not be possible to reach the textFrame
What about findGrep() ?
Loic
Hi Loic,
Thanks for chipping in.
I used a workaround inspired by Marc Autret's work which consisted in creating a new window instance for every step while closing the underlaying one. That worked well a few versions ago (CS6 or CC). But I recently tried to reuse this trick for a project in a CC14/15 environment and that doesn't work anymore.
I guess it was CC, or maybe CS6 on the Mac. Sounds a bit crazy, but if it worked, why not! I wonder why it doesn't work any more.
ScriptUI is still good for basic stuff, and it's much less hassle than anything else I'm aware of.
Ariel
Dear Pickory
Okay, i understand Pickory
Thanks
Karthik
Hi, there.
I have a number of text-frames threaded to each other. tfLK[0] (the first in an array of textframes) has (visually) 29 lines, but "$.writeln(tfLK[0].lines.length)" returns 33, and indeed, when I target "tfLK[0].lines.items(32)" I get the 4th line on the second frame. Like-wise, when I target "tfLK[1].lines.items(32)" (the second frame of the thread), I get the 4th line of the third frame.
What is going on?
Can I fix this?
Any help would be appreciated.
Hi, there.
I need to find out the leading of certain text in points. When I try doing that, I get "AUTO"
How can I change "AUTO" to the leading in points?
Any help would be appreciated.
ScriptUI is still good for basic stuff
Yeah for sure but all those inconsistencies, really ? Plus the lack of support. Was told ScriptUI is no longer developed nor considered at Adobe.
If Adobe doesn't want to support ScriptUI any longer, why not but what is the alternative ??? The problem is also that as far as I am concerned I have no idea of who at Adobe is in charge of those technologies. That would be nice to have a point with them about this.
Loic
leading | Leading Unit | r/w | The leading applied to the text. Can return: Unit or Leading enumerator. |
This function returns the leading value whether the leading is automatic or fixed:
function leading (p) { if (p.leading == Leading.AUTO) { return (app.selection[0].pointSize * p.autoLeading) / 100; } else { return p.leading; } }
Peter
I am using a InDesign CC 2014 on a Mac, running 10.10.5. For scripting, I am using ESTK CC version 4.0.0.1 (which according to my CC app, is the latest version).
In my Mac OS X console, I find the following error message, repeated 9 times every two seconds:
2/11/16 7:19:59.662 PM ExtendScript Toolkit[20480]: assertion failed: 14F1605: libxpc.dylib + 33745 [D765980C-9448-3637-AE66-360C7DC2DCEB]: 0x13
Is there anything I can do to stop these messages (I mean, besides quitting the application )?
This does not happen every time I use ESTK, but I've seen it on several occasions in the past.
Thanks.
Hi Karthik,
Here is revised script which used 2 color for differentiating positive and negative tracking.
theTextR = app.selection[0].parentStory.textStyleRanges; try { app.activeDocument.colors.item("PositiveOvertracked").name; } catch (myError){ app.activeDocument.colors.add ({name:"PositiveOvertracked",space:ColorSpace.CMYK,colorValue:[100,15,100,0]}); } try { app.activeDocument.colors.item("NegativeOvertracked").name; } catch (myError){ app.activeDocument.colors.add ({name:"NegativeOvertracked",space:ColorSpace.CMYK,colorValue:[15,100,100,0]}); } var i=0; while (i<theTextR.length) { if (theTextR[i].tracking >= 15) { theTextR[i].fillColor = "PositiveOvertracked"; i++; } else if (theTextR[i].tracking <= -15) { theTextR[i].fillColor = "NegativeOvertracked"; i++; } else { i++; } } alert("The tracking value more than +15 and -15 is highlighted in PositiveOvertracked and NegativeOvertracked color respectively.");
PS: Pickory, I don't have knowledge in plugin development. But eager to see how yours work
Regards,
Karthi
I hope it is because of text-frames threaded. If you draw 2 text frames without threaded and try the same coding what you wrote. It gave correct answer.
Karthi
Just select any text frame and run the script...
Dear Tpk
Thank thank thank so match Tpk. your script working good. I like so match
I need your help continued.
karthik
Glad to help you, karthik