MS Office: Can't change row height of a Table

You really cannot change the row height in table. Whenever you insert a Table it comes with certain style. It sets the Table's font size as well. As a result if you want to set the Table row height less than it can accommodate the font then it will not let you to do that. So to be able to change the table row height

1. Select the Table
2. Go to Home Tab
3. Change the font size to lower size
4. Now try to change to Table row height

Blogger: AdSense not appearing in blog front page.

Google Forum answered:

I think I have solved my problem, I had changed the url address settings from http://fishfootspa.net to http://www.fishfootspa.net . When I changed these back to without the www , the adsense appears on the home page which is great news.  The bad news is the adsense now doesn't show on my main keyword post http://fishfootspa.net/fish-foot-spa/ .

It's an improvement though for sure and now I'm getting somewhere.

Adam

google adsense to display information, takes time to arrange, about 2-3 hours later, you can F5 to see the show

I waited days and it still doesn't show on the home page. After adding them they were immediately active on the sub pages.

danoreef

Facebook: Create a page - Web address is not available. Please try another one.

Problem:
I was trying to create a facebook page. In the web address field whatever I put it says: Web address is not available. Please try another one. 

Solution:
Just create the page WITHOUT entering the adress, and once page created you can put a special name via page settings

MAC Computer: Cannot print image file or large document file

In order to solve the printing issue in MAC. It is recommended to save the file as post script file, then open with Adobe Distiller and print.

1. Select File > Print… from the menu bar.
2. Prepare the document for print, e.g. enter a specific page range.
3. Click on the PDF button (towards the bottom left of the Print dialogue box) and select Save as
PostScript…from the drop down menu. A Save dialogue box will appear.
4. Give the file a meaningful name.
5. Select Desktop as the save location from the drop down menu.
6. Click the Save button. The file will be saved on your Desktop.
7. Go to Applications > Adobe Acrobat 9 Pro and click on the Acrobat Distiller application (brown square
icon) to launch it.
8. Locate the file on your Desktop that you saved in step 6.
9. Drag this file onto the Distiller icon in the Dock. Distiller will start processing the file.
10. In the Acrobat Distiller window that appears a progress bar will indicate when the conversion is
complete. The completed file will also appear in the list below the progress bar.
11. Select your newly created PDF from the list and double click to open it or open it from within the
Preview application.
12. Select File > Print… from the menu bar and print the file to your preferred printer

MAC Word 2011: How to Print Background Colors and Images of Current Document

Word 2011: How to Print Background Colors and Images of Current Document

Posted by Rob Rogers in Apple Mac

If you’ve prepared a fancy Word document that contains background images and/or colors, you will need to make a change to the Options setting for these to show up when printed.

1. Open up the desired Word document.

2. Go to the Menu, click Word and select Preferences.

3. In the Output and Sharing section, select Print.

4. Go to the Options for current document only section.

5. Check the Print background colors and images checkbox.

6. Click the OK button.

Livecycle Designer: Creating repeating and multipage subforms

Creating repeating and multipage subforms

You can place a subform anywhere on a page; however, when a large amount of data is merged with the form, the subform may expand beyond the bottom edge of the rendered page. To deal with this issue, you can either select the Allow Page Breaks Within Content option to cause the server to break the subform in the middle or deselect this option to force the entire subform to the top of the next rendered page. Forcing a subform to the next page ensures that any nested subforms are displayed together on the same page. If you do not select the Allow Page Breaks Within Content option, you will probably want to create an overflow leader and overflow trailer subform. (See About overflow leaders and trailers.)

When data is merged, the server positions the content of a subform within the confines of content areas only. In cases where a large amount of data needs to be merged with any of the objects in a subform, a subform may span multiple form pages. When a form page is filled, the server automatically renders another identical page and continues to place the subform on the new page unless you explicitly direct the flow to a different content area or master page. When more than one content area or master page exists in the same form, you can specify whether a subform will be placed in a particular content area or positioned according to the specified master page.

To create a repeating subform

1. In the Hierarchy palette, select the parent subform of the subform you want to repeat. (See About subforms).
2. In the Object palette, click the Subform tab, and in the Content list, select Flowed.
3. Select the subform to repeat.
4. In the Object palette, click the Subform tab and, in the Content list, select either Positioned or Flowed.
5. Click the Binding tab and select Repeat Subform For Each Data Item.
6. To specify the minimum number of repetitions, select Min Count and type a number in the associated box. If this option is set to 0 and no data is provided for the objects in the subform at data-merge time, the subform is not placed when the form is rendered.
7. To specify the maximum number of subform repetitions, select Max and type a number in the associated box. If you do not specify a value in the Max box, the number of subform repetitions will be unlimited.
8. To specify a set number of subform repetitions, regardless of the quantity of data, select Initial Count and type a number in the associated box. If you select this option and either no data is available or fewer data entries exist than the specified Initial Count value, empty instances of the subform are still placed on the form.
   Note: The value in the Initial Count box must be between the Min Count and Max values. If the Min Count value is not specified or is 0, the Initial Count value defaults to 0.

To specify a subform to span multiple pages

Subforms can be placed anywhere in a form design. However, when a large amount of data is merged, the subform may expand beyond the bottom edge of the rendered page.

To deal with this issue, you can either enable a page break in the middle of the subform or force the entire subform to be rendered starting at the top of the next rendered page. Forcing a subform to the next page ensures that any nested subforms are displayed together on the same page.

When data is merged, the content of a subform is placed within the confines of content areas only. In cases where a relatively large amount of data needs to be merged with any of the objects in a subform, a subform may span multiple form pages.

When a form page is filled, an additional identical page is rendered automatically. The subform continues to be placed on the new page unless you explicitly direct the flow to a different content area or master page. When more than one content area or master page exists in the same form, you can specify whether a subform will be placed in a particular content area or positioned according to the specified master page.

To enable a subform to span multiple pages

 In the Object palette, click the Subform tab and select Allow Page Breaks Within Content.

When this option is deselected, the objects in the subform are kept together on the same page.

About overflow leaders and trailers

Because the length of a form that has a flexible layout varies depending on the amount of data merged with the form, forms that have a flexible layout are often longer than one page. Using overflow leader and overflow trailer subforms is an effective way to start and finish subforms that repeat over multiple pages. You can use any subform that is configured to position content as an overflow leader or trailer. For example, in the Purchase Order sample form, the detail subform is configured to position content and repeat for every data item. When the form is merged with data, if the first page has insufficient space to display all occurrences of the detail subform, a new page is added and the data continues to flow into the next content area.

When data flows this way across multiple pages, you may want to carry forward onto each new page certain text such as "Continued from previous page" or specific formatting elements such as a column header row that includes the descriptive labels for each column of data. Using column header rows on each subsequent page makes the resulting form much easier for users to follow. To do this, you can create an overflow leader subform that will act as the column header row for each additional page. In the Purchase Order sample form, for example, the detailHeader subform is selected as the overflow leader. As a result, a copy of the detailHeader subform is rendered at the top of every new page before the first occurrence of the detail subform.

Similarly, you may want to include information following the last occurrence of the repeating subform, at the bottom of all pages except the last page. For example, you may want to include text such as "Continued on next page" at the bottom of these intervening pages. To do this, you can create an overflow trailer subform for the repeating subform in the same way that you created an overflow leader subform.

When a subform overflows to the new page, the server performs these operations:

• Places the overflow trailer on the current page
• Places the overflow leader on the next page
• Flows the expanding subform and the remainder of its repeating objects onto the new page

An overflow leader is a special type of positioned subform that appears at the top of the next page whenever a page overflow occurs.

Overflow leaders are similar to the heading row in a standard table. The heading row appears at the top of the table and contains a descriptive label for each of the columns in the table. You can format the table so that when it expands beyond one page, the heading row is repeated at the top of the new page. This makes the information in the table easier to understand as the reader moves from page to page.

An overflow leader subform behaves in a similar way. When you specify that a specific subform will be the overflow leader for a subform that repeats, the overflow leader subform will appear once before the repeating subform at the top of the current page and each subsequent page thereafter.

The repeating subform is added as many times as necessary when merged with data. When there is no more room on the first page, a new page is added and the data continues to flow into the next page until all the data is consumed. The overflow leader subform will appear once at the top of each page.

You can see an example of how an overflow leader subform is used in the sample form design whose layout adjusts to accommodate data that is included with Designer ES2. The sample, Purchase Order.xdp, is in the Samples folder where Designer ES2 is installed on your system. In that example, the subform named detailHeader acts as the overflow leader for the repeating subform named detail.

Bookend leaders are subforms that appear before a repeating subform. If you define a subform sibling just above a repeating subform and then specify it as an overflow leader, you have defined it as a bookend leader and as an overflow leader.

An overflow trailer appears at the bottom of the next page whenever a page overflow occurs. Use an overflow trailer to include information that appears only once, after all the data is positioned.

Bookend trailers are subforms that appear just below a repeating subform. If you define a subform just below a repeating subform and then specify it as an overflow trailer, you have defined it as a bookend trailer and as an overflow trailer.

To create and assign overflow leaders and trailers

An overflow leader or overflow trailer is a positioned subform that can be assigned to any repeating subform. Typically, you create the subform that will become overflow leader or trailer first. Then you assign them to a repeating subform and give them overflow properties.

If the overflow leader is also treated as a bookend leader, it is placed in the Hierarchy palette just above the subform. Also, if the overflow trailer is also treated as a bookend trailer, it is placed in the Hierarchy palette just below the subform.

To create an overflow leader or overflow trailer subform

1. Create a form design with all the necessary subforms.
2. On your form design, locate the subform that you want to use as an overflow leader or an overflow trailer, select the subform, and do these tasks:
   • Look at the Subform tab in the Object palette. Ensure that the Content list displays Positioned. In the Object palette, click the Subform tab and make sure that Positioned is selected in the Content list.
   • Look at the Binding Tab in the Object palette. In the Object palette, click Binding tab and select Repeat Subform For Each Data Item to have the leaders and trailers appear for more than one overflow. Bookend leader and trailers are not counted against this number.

To apply an overflow leader or overflow trailer to a subform

1. Select the subform or subforms that you want to repeat.
2. In the Object palette, click the Binding tab and select Repeat Subform For Each Data Item to set the subform to repeat.
3. In the Object palette, click the Pagination tab and, in the Overflow box, specify either a content area or page where the form should place the overflow subforms."]
4. If you want to specify an overflow leader, in the Overflow Leader list, select the subform that you want to use as the overflow leader subform for the current repeating subform. Alternatively, select New from the Overflow Leader list to create and assign a new overflow leader subform.
5. If you want to specify an overflow trailer, in the Overflow Trailer list, select the subform that you want to use as the overflow trailer subform for the current repeating subform. Alternatively, select New from the Overflow Trailer list to create and assign a new overflow trailer subform.
   Note: You do not need to have both an overflow leader and an overflow trailer. Whether you have one, both, or none is determined entirely by the requirements of your form.

Livecycle Designer: To create a table that grows using the Button object

Masud' solution To create a table that grows using the Button object 

1. Insert a Table with one row and three column for practice purposes.
2. Now Select Table-->Select Row1--> in the Object palette-->Select Binding tab-->and check "Repeat Row for Each Data Item"
3. Add a button
• In the click Event-->Type the following javascript code:
• this.resolveNode('Table1._Row1').addInstance(1);
4. Delete button
• In the click Event-->Type the following javascript code:
• try
    {
      var rowNum = this.parent.parent.index;
      this.parent.parent.instanceManager.removeInstance(rowNum);
    }
  catch(err)
    {
     app.alert("The minimum number of rows is 1");  
    }

To create a table that grows using the Button object  

You can create a table that adds a row when a user clicks an Add Row button. You can also include a Delete Row button. You must create the table, add the buttons, and then set the properties that will make the table grow.

A. Buttons that add a row or delete a row B. When the user clicks the Add Row button twice, LiveCycle Designer ES adds two rows.

To create a table that grows using the Button object

1. Select Table > Insert Table.
2. In the Insert Table dialog box, select Create Table Using Assistant and click OK.
3. In the Body Layout panel of the Table Assistant, select Body Rows Vary Depending On Data.
   This creates a table that adds or removes rows, depending on the data sent to it.
4. Enter the number of columns and click Next.
5. (Optional) Select Has Header Row and click Next.
6. (Optional) Select Has Footer Row and click Next.
7. (Optional) Select Has Body Rows And No Sections and click Next.
8. (Optional) Select Alternate Row Colors and click Finish.
9. Save the form as an Adobe Dynamic XML Form (*.pdf).
   Now, you must add the buttons that will be used to add and delete rows.

To add the buttons

1. Select the first cell of the body row and, in the Object palette, click the Cell tab and select Subform from the Type list.
   This cell needs to be a subform so that it can contain two buttons.
   You can also drag the Subform object from the Object Library palette into a cell in the table.
2. In the Object Library palette, click the Standard category and drag the Button object into a cell in the body row. For example, place it in the first cell of the body row.
3. In the Object palette, click the Field tab and type Add Row in the Caption box.
4. Repeat steps 2 and 3 to create a Delete Row button.
5. Select the Add Row button and, in the Script Editor, select Click from the Show list.
6. In the Script Editor, select JavaScript from the Language list.
7. Type the following script:

   Table.Row1.instanceManager.addInstance(1);
   
   

   To modify the script for your own form, you must understand how the script relates to the hierarchy. For example, in the hierarchy for the current form, both buttons are inside the same subform; therefore, you do not need to specify any objects beyond the Table level.
   
8. Select the Delete Row button and, in the Script Editor, select Click from the Show list.
9. In the Script Editor, select JavaScript from the Language list.
10. Type the following script:

    Table.Row1.instanceManager.removeInstance(1);
    
    

    To reuse these buttons in another form, you can add them to the Custom category (or your own category) of the Object Library palette. Note that you may have to edit the script for the button if you use it in a different form.
11. View the form in the Preview PDF tab.
    For example, this is what you would see if you modified the Part table from the Purchase Order template.
    

Adobe Acrobat: How to merge files into one PDF

How to merge files into one PDF:

1. Within Acrobat XI, select File > Create > Combine Files into a Single PDF.
2. Click Add Files and select the files you want to add.
3. Click, drag, and drop to reorder the files and pages. Double-click on a file to expand and rearrange individual pages. Press the Delete key to remove unwanted content.
4. When finished arranging the files, click Combine Files.
5. Select File > Save As > PDF.
6. Name your PDF file and click Save.

LiveCycle: Text Field grow to accommodate Text

Once you’re in edit mode you follow the steps: The key to making the text fields grow to accommodate text is to:

1. Make them multiline (Object palette > Field tab > Allow multiline property). 
2. Make them expandable in height (see “Making a Field Expandable” here). 
3. Put these Text Fields in a flowed subform *Note: you can highlight all your objects and use the contextual menu (right click) to ‘Wrap in a subform’

• Select the subform whose Object palette > Subform tab > Content property: is set to “Flowed”
• That allows page breaks within its content (via the “Object palette > Subform tab > Allow Page Breaks within Content property”). . 

4. Allow their contents to break across pages (Object palette > Field tab > Allow Page Breaks within Content property). 

5. Just don’t for get to save it as a Dynamic PDF

Have you ever lived through the frustration of previewing a form on which you’ve written a simple little script to affect the presence of an object when a button is clicked and pulling your hair out because you keep clicking on the button and nothing happens (object doesn’t disappear, there’s no error message, etc.)? Or maybe you’ve been in a situation where you’ve added script to a button in order to insert a new instance of a repeatable subform and while clicking on the button doesn’t produce one, the submitted XML data file contains entries for each new instance that was added?

Even if you haven’t, it may happen someday so here’s the remedy for the case of the “Common (Static PDF) Flue”…

In Designer, there are two different locations containing settings which affect the type of temporary PDF file created when you click on the Preview tab:

1. Under the “File Options” section within the “Document Handling” panel of the “Tools | Options” dialog, you can set the Default File Type for New Forms. This type is used on new forms which you preview prior to saving (because Designer doesn’t know which format you’ll use at the time of preview). This is set to a static PDF format by default.
2. Even if you’ve specified a dynamic PDF format for the Default File Type for New Forms, this setting may be overridden by the Preview Type and XDP Preview Formatproperties in the “File | Form Properties” dialog in the “Defaults” panel once you’ve saved your form. The Preview Type property, set to “Interactive” by default, determines whether the form will be previewed as an interactive (dynamic) form or as a print (static) form. This property supersedes the PDF format. The XDP Preview Format property usually picks-up the Default File Type for New Forms setting and determines what PDF format will be used to preview your form should it be saved as an XDP. (Note that if you’ve saved your form as a PDF file, then the XDP Preview Format setting is ignored).

Now that we’ve covered the different properties which affect the PDF preview format, here’s how to kick that flue I was talking about earlier (so that you actually do preview in a dynamic PDF format and stop pulling your hair out):

1. If you haven’t saved your form, make sure the Preview Type is set to “Interactive” and that the Default File Type for New Forms is set to a dynamic PDF format. You may also want to set the XDP Preview Format to a dynamic PDF format while you’re at it.
2. If you’ve saved your form as a dynamic PDF, make sure the Preview Type is set to “Interactive”.
3. If you’ve saved your form as a static PDF, none of these settings will help you. You must first save your form as a dynamic PDF.
4. If you’ve saved your form as an XDP, make sure the Preview Type is set to “Interactive” and the XDP Preview Format is set to a dynamic PDF format.
5. If you’re tired of running into these problems and want to avoid them in the future, just set your Default File Type for New Forms to a dynamic PDF format.

I hope this tip improves your form design health. It did wonders for me!

PDF Form: Ranking, Sorting Formula in PDF Form

Create a text field:

• Edit-->Select the text field-->Properties-->Format tab->Number
• Edit-->Select the text field-->Properties-->Calculate tab-->Click radio button: Custom calculation script-->Edit: 

    var n1=this.getField("Number2Row1").value;

    var n2=this.getField("Number2Row2").value;

    var n3=this.getField("Number2Row3").value;

    

    var arr = [n1, n2,n3];

    var sorted = arr.slice().sort(function(a,b){return b-a})

    var ranks = arr.slice().map(function(v){ return sorted.indexOf(v)+1 });

    event.value=ranks[0];

Here: n1, n2 and n3 will get the value from all the text fields will be included in the ranking.

Example of Javascript code for Ranking Array Elements:

Problem:

I need an algorithm to rank elements of an array in Javascript.

Example : I have an array as follows:

[79, 5, 18, 5, 32, 1, 16, 1, 82, 13]

I need to rank the entries by value. So 82 should receive rank 1, 79 rank 2 etc. If two entries have the same value they receive the same rank and the rank for a lower value is raised.

So for this array, the new ranking array would be:

[2, 7, 4, 7, 3, 9, 5, 9, 1, 6] 

How can I do this ?

Solution:

var arr = [79, 5, 18, 5, 32, 1, 16, 1, 82, 13];
var sorted = arr.slice().sort(function(a,b){return b-a})
var ranks = arr.slice().map(function(v){ return sorted.indexOf(v)+1 });

Result :

[2, 7, 4, 7, 3, 9, 5, 9, 1, 6]

If you want to be compatible with old browsers, you may have to define a shim for indexOf and for map (note that if you want to do this very fast for very big arrays, you'd better use for loops and use an object as map instead of indexOf).

Livecycle Designer: Changing the background colors of fields, fillable areas, and subforms

Dynamically setting image field href

I'm trying to dynamically set an image field on my LiveCycle PDF form. On my form onReady function I have some Javascript code that is executing. For some reason, if I explicity set my image field to a string value, everything works. However, if I try to dynamically set it using a value from a text input, it doesn't work.

Any ideas? I've used app.alert to make sure that the value in the textfield is correct.

//Try to set image field to a string value. [WORKS]
swatch1.image.value.image.href = "http://localhost/qs/images/waterswatch.png";
 
//Alert Value of text field (Result: http://localhost/qs/images/waterswatch.png )
app.alert(swatch1.imgPath.rawValue)
 
 //Try to set image field dynamically. [DOESNT WORK]
 
 
swatch1.image.value.image.href = swatch1.imgPath.rawValue;
 
 
 

Changing the background colors of fields, fillable areas, and subforms

This example demonstrates how to change the background color of subforms, fields, and fillable areas on a form in response to form filler interaction at run time.

In this example, clicking a button changes the background color of an associated object.

Note: To manipulate the background color of objects at run time, you must save your form as an Acrobat Dynamic XML Form file.

To see this scripting example and others, visit the LiveCycle ES2 Developer Center at www.adobe.com/devnet/livecycle.

Scripting the subform and text field background colors

You set the subform and the text field background colors by using the fillColor method. For example, the following line is the script for the subform:

    Subform1.fillColor = "17,136,255";

The following lines make up the script for the background color of the text fields:

    Subform1.Name.fillColor = "102,179,255";
    Subform1.Address.fillColor = "102,179,255";
    Subform1.City.fillColor = "102,179,255";
    Subform1.State.fillColor = "102,179,255";
    Subform1.ZipCode.fillColor = "102,179,255";
    Subform1.Country.fillColor = "102,179,255";

Scripting the fillable area background color

When setting the background color or the fillable area for each text field, your scripts must access properties that require a reference syntax expression that includes the number sign (#). Because JavaScript does not interpret the number sign (#) properly in reference syntax expressions, the script uses the resolveNode method to resolve the expression.

    xfa.resolveNode("Subform1.Name.ui.#textEdit.border.fill.color").value = "153,204,255";
    xfa.resolveNode("Subform1.Address.ui.#textEdit.border.fill.color").value = "153,204,255";
    xfa.resolveNode("Subform1.City.ui.#textEdit.border.fill.color").value = "153,204,255";
    xfa.resolveNode("Subform1.State.ui.#textEdit.border.fill.color").value = "153,204,255";
    xfa.resolveNode("Subform1.ZipCode.ui.#textEdit.border.fill.color").value = "153,204,255";
    xfa.resolveNode("Subform1.Country.ui.#textEdit.border.fill.color").value = "153,204,255";