Jump to content

ThomasLewis

Members
  • Posts

    298
  • Joined

  • Days Won

    11

Posts posted by ThomasLewis

  1. EDIT: I think I misunderstood at first, this should work:

     

    FusionPro.Composition.chunksBreakStacks = true;
    
    var amount = parseInt(Field("Unit"));
    FusionPro.Composition.repeatRecordCount = amount;
    var rrn = FusionPro.Composition.repeatRecordNumber;
    
    if (rrn == 1)
       FusionPro.Composition.StartNewStack();
    
    FindTextFrame("Content").content = '<color name="' + Field("Group") + '">' + rrn + " of " + amount;
    

     

    The CSV should look like this:

     

    Group,Unit
    Red,20
    Green,15
    Blue,32
    

  2. It's strictly for preview purposes. I want to be able to add some information on specific templates that users of lower variations would see. The users I have on FP Designer don't know the product very well but still want to be able to preview templates for a certain client. I guess you could think of this like a watermark on the preview screen.
  3. Is there a way to check in the rule validator which variation of FusionPro the template is open on? Basically whether it's open on Designer, Desktop, or Producer.

     

    I know you can see if the composition is inBatch and you can grab the longversion number, but neither of those work to check against all variations of the product.

  4. The part of the script that needs to be altered is the part inside the quotes, not the name of the variable.

     

    var field_id_name = "Phone Number";

    Should be changed to:

    var field_id_name = "Phone1";

     

    Or as you have the variable name changed already:

    var Phone1 = "Phone1";

  5. Interesting. Not sure there is a benefit to calling out unused body pages, vs. calling out individual graphics, vs. calling out single pages of a PDF. After all, you still need the graphics.

     

    After looking at what I wrote, I can see my definition wasn't very clear. The example I posted above isn't using unused body pages in the FusionPro template. The original document is basically left alone.

     

    This method uses a multipage PDF resource (an Illustrator CC 2015 document called screen.pdf in the zip file) where each page has a white box with a varying level of transparency applied. This allows you to only have to create a single resource that can be reused wherever you need screens. You simply grab the percentage of transparency the user selects and call that page of the resource PDF into the overlapping graphic frame. You can see how this works in the onRecordStart rule of the fusionfile.pdf document in the zip file.

  6. Sorry if the workflow where you see random borders and fills when composing locally seems cumbersome, but it's the best we could think of to allow users to see the frame positioning working locally, while still keeping the ability to compose production output limited to users with the higher level licenses.

     

    The problem with those borders is it screws up the ability to see copyfitting properly or anything at all in frames smaller than 12pt. If there were one thing I could change about FusionPro out of everything it would be the removal of those 6pt preview borders.

     

    Evan, check the attached PDF. I made some adjustments to your code and moved it into onRecordStart. One major part was changing the values for y to hundredths of points. Also, I expanded the text frames larger than 12pt to accommodate the 6pt border so when you turn on preview you can actually see content.

    2015_supTest.pdf

  7. Thanks Thomas but...

     

    I get over 10,000 pdf's weekly and I have a data field called "PD_GRAPHIC" that pulls them in so how can I revise what you wrote to use that field to count the pages?

     

    Thanks

    Kal

     

    I have no idea what you mean by "pulls them in". Does it create a 10,000 record input file you use in FusionPro? Where do you want the page numbers displayed?

     

    Sample files showing your input and expected output would be helpful.

  8. Here's an updated version that should work with any ascii positions. Simply find the ascii number where the 0 is.

     

    For many Adobe Pro fonts the tabular oldstyle 0 is at 63043 and proportional oldstyle 0 is at 63280.

     

    //numerical ascii position without the 
    var ascii = 63043;
    
    var n = "1234 S. Street, Suite 567";
    
    return n.replace(/([0-9])/g, function(str, n) {return "" + (parseInt(n) + ascii) + ";";}).replace(/\s/g, " ");

×
×
  • Create New...