Blogged by Björn Meyer on July 01, 2009 and tagged with Service Pack.
Today, the following service packs were released:
- Service Pack 1 for TX Text Control .NET Server 15.0
- Service Pack 1 for TX Text Control .NET 15.0
- Service Pack 1 for TX Text Control ActiveX Server 15.0
- Service Pack 1 for TX Text Control ActiveX 15.0
Please take a look at the updated known issues list at:
http://www.textcontrol.com/support/issues/
You can download the service pack at:
http://www.textcontrol.com/downloads/sps/
As ever, our support team is waiting to answer your questions. Full contact details at:
http://www.textcontrol.com/support/
Blogged by Björn Meyer on June 17, 2009 and tagged with Section 508.
Section 508, part of the Rehabilitation Act, was adjusted by the U.S. Congress to require that all Federal agencies make their electronic and information technology accessible to users with disabilities. It was enacted to remove barriers in information technology.
We always make sure that all products and versions of TX Text Control are Section 508 compliant. Thus implies that the Windows built-in accessibility features are supported and well tested in combination with TX Text Control. The following accessibility tools has been tested:
- Magnifier
- Narroter
- On-Screen Keyboard
- High Contrast
- Magnifier
- Sticky Keys
Currently, we are working on the official templates for all products. You can find more detailed information on how TX Text Control .NET is compliant by reviewing our Section 508 Voluntary Product Accessibility Template (VPAT):

TX Text Control .NET Section 508 compliance
Helpful link:
US Government - http://www.section508.gov/
Blogged by Björn Meyer on June 15, 2009 and tagged with Page Rendering Engine, Release.
A very popular new feature of TX Text Control .NET 15.0 is the Page Rendering Engine. It allows you to export metafiles or images from each separate page of TX Text Control. The content of the page is exactly the same content (rendering) like in an exported PDF or printed document.
Technically, the Page object of the PageCollection got a new method called GetImage with the following implementations:
public System.Drawing.Imaging.Metafile GetImage(PageContent contents)
public System.Drawing.Imaging.Bitmap GetImage(int zoomFactor, PageContent contents)

The first implementation returns a Metafile that can be easily processed by using standard .NET classes. You could convert it to other image formats, print the metafile directly in a PrintDocument or scale it freely to your required size to display it in an image control. The right-hand diagram shows these possibilities.
The second implementation creates a Bitmap that can be saved as an image out-of-the-box without creating an image explicitely. You can specify the zoom factor in the GetImage method that should be used to create the high quality image of the specific page.
In both implementations, you need to specify the page content that should be exported. The following values are allowed:
- All: The image contains all parts.
- Background: The image contains the background of the page.
- HeadersAndFooters: The image contains the header and the footer of the page.
- MainText: The image contains the page's text contents.
The following code creates TIFF images from each page of the current document and stores them in an ArrayList.
ArrayList inputImages = new ArrayList();
foreach (Page page in textControl1.GetPages())
{
MemoryStream image = new MemoryStream();
Bitmap mf = page.GetImage(100, TXTextControl.Page.PageContent.All);
mf.Save(image, ImageFormat.Tiff);
inputImages.Add(image);
}There are many different applications for this new feature and I am very interested in your solutions. Feel free to send me your ideas or questions you might have. What did you realize with the Page Rendering Engine?
Blogged by Björn Meyer on June 11, 2009 and tagged with Sections, Headers and Footers.
In TX Text Control 14.0, we introduced formatting sections that allows you to split a document into separate sections to enable different page sizes, margins or headers and footers.
TX Text Control 15.0 additionally implements page columns that can be adjusted separately for each inserted section.
When you are not used to word processing, sections might not be self-explanatory. For instance, sections enables you to create documents with mixed page orientation, so that parts are inserted as portrait and other parts as landscape. It is possible to add different headers and footers to specific sections or you can include page numbering only for the main part of a document and omit it in an appendix.
Accessing the sections
All sections are listed in the SectionCollection class that can be accessed using the Sections property.
By inserting a new section using the Add method, a section break character is inserted at the current input position. TX Text Control lets you insert a new section that starts at a new page or at a new line. The page size and different headers and footers can only be changed when inserting a new page.
All settings of the previous section are inherited when creating a new document section. In other words, if you inserted a specific header to the previous section, this header will be displayed in the new section as well. To avoid that, you can set the ConnectedToPrevious property of the HeaderFooter object to false. In this case, the new section is getting it's own header.
To modify the headers and footers of a specific section, you need to manipulate the HeadersAndFooters property of the specific section. In previous versions of TX Text Control, the headers and footers were accessed through the HeadersAndFooters property of the main control which is no longer recommended. It is still possible, but if you have more than 1 section, most of the other collections in the HeaderFooter object are NULL. Example:
You need to change the text of each header in every section. Therefore, you need to iterate through all sections and their headers and footers:
foreach (Section sec in textControl1.Sections)
{
foreach (HeaderFooter hed in sec.HeadersAndFooters)
{
hed.Selection.Text = "New Text";
}
}Sections is a layer wrapped over the text and its pages. The text, images, tables and all other elements can be accessed using the normal collections of the main TX Text Control. Only the content in the different headers and footes must be accessed through the specific section.
The section dialog box
TX Text Control is shipped with a dialog box that can be used to manipulate the section settings. The first screenshot shows the section format dialog that comes with TX Text Control. It allows you to change the page format for the complete document or the current section.

The following screenshot shows the second tab of the same dialog box. On this tab page, it is possible to specify whether headers and footers are added to the current section, if they should be connected to the previous one and to adjust the different settings for headers and footers.

In the combo boxes, you have three possibilities for headers and footers when applying the changes to the complete document:
- None: No header or footer is inserted
- All sections equal: All sections are getting the same header or footer
- All sections different: Each section is getting it's own header or footer
When applying the settings to the current section, you will have the following possibilities:
- None: No header or footer is inserted
- Same as previous section: The new header or footer is connected to the previous one
- This section different: The new header or footer is not connected to the previous one
With sections, TX Text Control provides you a powerful tool to create professional documents. Feel free to post questions you might have about sections.
Blogged by Björn Meyer on June 04, 2009 and tagged with Sample, TIFF, Page Rendering Engine.
TX Text Control .NET 15.0 introduced the page rendering engine that allows you to export a metafile or a bitmap of each separate page. This enables you to create thumbnails of the pages or to export images to view them in a browser.
We just published a sample that shows how to create a multipage TIFF image from a document in TX Text Control.
Read the full article in our source code library
As ever, feel free to post comments on this sample, if you have any questions or suggestions.
Archive