How to adjust pacman column widths

Even when I run pacman in a fullscreen xterm, many package names are cut off in the "Retrieving packages" step...
The individual lines look like the following:
kdemod-kdemultimedi... 263.3K 956.0K/s 00:00:00 [#############################################################################################################################################################################] 100%
Now, I don't see the need for so many #'s to be shown in each line that you can't even read the whole package name, let alone the package version, for many packages...
Is there a way to tweak pacman's column widths to something more sensible?
Thanks...

Any hints?
Even for 80-chars-terminal-width I'd much prefer this:
kdemod-kdemultimedia-common-4.3.90-1 3.1M 1783.4K/s 00:00:01 [######----] 61%
over the current output:
kdemod-kdemultimedi... 3.1M 1783.4K/s 00:00:01 [#############--------] 61%
I mean, the progress bar is just a bonus - it doesn't provide any additional information... It should never prevent any important info from being shown...

Similar Messages

How to set displayed column width for a search help

I have created an elementary search help for a custom field with a value table behind it.
The search help functions correctly, but when displayed the column widths are all 10 characters. The user has to adjust the column to view the descriptive text.
Can anyone tell me how to set default column widths for the help?

Please open you Elementary search help and see the Column width behind the Fields of your ...there increase the width of the fields
"Activate it and refresh
reward points if it is usefull .....
Girish

How to change the column width in Smartforms..?

Hi All..
I need to change the column width in a smartform.
The requirement has been mentioned as follows...
Adjust the column width of the following columns:
MATERIAL: 14 char
DESCRIPTION: 20 char
How to perform this..??
Where can i find the column width of various columns of a smartform..???
Please Help me...
Regards
Pavan

In the SMART Forms, you would have created a Table object and specified the line width and divided that into no. of columns that you want, you have to mandatorily specify the width of each column so that total of column width will be equal to that of the line width.
When you double click on the Table object, you can TABLE tab on the right side. If you can't see the line / columns details, click on the DETAILS button.
Regards,
Ravi
Note - Please mark all the helpful answers

SAPScript: how tu adjust heigh and width of standard text (logo)?

Hi!
how to adjust heigh and width of standard text (logo)?
I do not want to edit the logo, because it is used elsewhere, so I need to adjust heigh and width when using it in a form.
For now stadard text comes over the window. Here is how I use it:
INCLUDE ZHEX-LOGO OBJECT TEXT ID ST
Will reward,
Mindaugas

Hi Mindaugas,
While uploading using RSTXLDMC. You have to maintain your size of the logo.
Go through below mentioned document.
Upload TIFF files to SAPscript texts
Description
The report RSTXLDMC allows a TIFF graphics file to be uploaded from the file system of the R/3 GUI to a standard text in the R/3 word processor SAPscript. (TIFF is a registered trademark of the Aldus Corporation.)
When uploading, the TIFF graphic is converted either into a black and white raster image (parameter type=BMON ) or as a color raster image with a maximum of 256 colors (parameter type=BCOL).
The black and white raster images ( BMON) can be printed using the following printer types:
PCL-5 printer
PostScript printer
Kyocera PRESCRIBE printer
Device type SAPWIN (with SAPlpd 32-bit as of Version 2.41 for Windows NT or Windows 95)
The color raster images (BCOL) can be printed using the following printer types:
PCL-5 printer with color capability (e.g. HP Color LaserJet). Color graphics are not printed properly on monochrome PCL-5 printers (e.g. HP LaserJet 5), because the printer cannot set the color palette as required and does not perform any gray-level conversion.
PostScript printer (color graphics are automatically converted to gray levels on black and white printers using PostScript) Device type SAPWIN (with SAPlpd 32-bit as of Version 2.41 for Windows NT or Windows 95) During TIFF graphic import, the basic set " Baseline TIFF 6.0 " of the TIFF specification 6.0 is supported.
To maintain compatibility with earlier versions of the report RSTXLDMC, it is also possible to convert the TIFF graphic directly into a black and white raster image for a particular printer type when uploading. These are the three printer types PCL-5 (parameter type=PCL ), PostScript (parameter type=POST) and Kyocera PRESCRIBE (parameter type=PRES ). A raster image uploaded in this manner can only be printed using the appropriate printer type.
Besides TIFF raster graphics, direct printer commands in the respective printer language (PCL-5, PostScript or Prescribe) can also be contained in the file which is to be uploaded (printer macros). They are then transferred to the standard text unmodified.
The graphics are output by inserting the standard text into the document which is to be printed, directly or using an INCLUDE command. The printer commands, which for example draw a company logo on the page, are only output if the print request is processed by the printer driver corresponding to the macro type, otherwise they are ignored. Example: A macro of type PCL is contained in a print request. If the request is output to a printer with type HPLJIIID (to which the driver HPL2 is assigned), the macro data is sent to the printer. If the request is printed on a printer of type POSTSCPT (to which the driver POST is assigned), the output of the macro data is suppressed.
In the standard text, the printer commands are inserted between the HEX ... ENDHEX command lines in hex notation. Various report parameters allow the graphic or printer macro to be placed on the page or at the current text position. Note: When the /:HEX command line which precedes the macro appears in the text, a line break is generally made before the graphic is output. The output of the macro therefore begins in the next text line at the left window border of the current page window, as long as a shift to the right is not specified (see below).
If your own printer macros are uploaded and not TIFF files, you must ensure yourself that the normal (text) output of the driver is not impaired when the printer commands are inserted in the output from the uploaded file. The printer drivers pass the data contained in the file to the printer unmodified, therefore without control over the individual actions this triggers on the printer. For example, syntax errors should not be generated by the PostScript commands (type POST), or form feeds should not be contained in the file (unless this was intended) for PCL-5 (type PCL).
Restrictions:
In general, the output of graphics generated via RSTXLDMC from R/3 is not suitable for mass printing (that is, unless you are using the "Graphic resident on printer" feature): the R/3 spooler has to hold significantly more data in its output files. If the graphics occur several times in a spool request, the data also reoccurs. Apart from this, the network is more heavily loaded in sending the increased volume of data to the printer and the printer output is slowed significantly (varies according to printer model) if raster graphics are output as well as the text.
If your graphics reside on your printer during a printing job, the degree of 'correctness' with which they are printed depends on the amount of memory available in your printer. R/3 print drivers are unable to determine whether the amount of memory available is enough! If one of the graphics that you have marked as resident is not displayed, try reloading the graphic and switching off the parameter "Graphic resident on printer".
When printing black and white graphics on PCL-5 printers, image data is compressed in order to greatly reduce the file size.
The output of graphics and macros on PCL-5 printers, PostScript printers and device type SAPWIN (type BMON, BCOL, PCL, POST) is adapted to the page orientation used, that is if landscape is used instead of portrait, the graphic is also turned when output. This is not the case for the PRESCRIBE printers (type BMON, PRES)! With these printers, the graphic is not automatically turned when landscape is used, but appears on the page in the identical position as for portrait. You are therefore recommended not to output raster images when printing in landscape on PRESCRIBE printers.
PRESCRIBE printers do not support the resolutions 200 and 600 dots per inch when printing raster images.
Not all PCL-5 compatible printers support the resolutions 200 and 600 dots per inch when printing raster images.
TIFF graphics with compression type 2 ("CCITT Group 3 1-Dimensional Modified Huffman run length encoding ") can currently not be imported although this is a component of the Baseline TIFF 6.0 specification for monochrome images.
Color TIFF graphics with full color representation (ie. a lot more than 256 colors) are automatically converted into 256 gray levels when uploading with type BCOL.
When TIFF graphics are converted to black and white raster images (type BMON, PCL, POST, PRES) there is no default simulation of gray levels or colors of the original image on the printer (for example, by using different tones of gray). Each pixel of the original image is converted to a white or black pixel on the printer according to its intensity value.
The parameter "Number of TIFF gray levels" does, however, allow a simulation of gray/colour tones of the original image through levels of gray on the printer, when using type PCL, POST or PRES. This parameter is ignored for type BMON.
The conversion of TIFF graphics can be so time-consuming that it is recommendable to execute the report RSTXLDMC in batch processing. Note: in batch, the file is always read from the file system of the application server (ie. not from the file system of the GUI).
The length of an individual text in the text file is limited. When importing TIFF graphics with very large dimensions, especially if more than 2 gray levels are used, a termination can therefore occur when saving the standard text ("EXPORT_TOO_MUCH_DATA"). This restriction can only be avoided by reducing the TIFF graphics. Note: The display of a raster image in Postscript or PRESCRIBE format needs from two to three times as much space as displaying in PCL-5.
When processing very large TIFF images on PostScript printers, a print termination can occur with PS error message "limitcheck". In this case the internal memory of the printer is insufficient to scale the required raster image. This implementation limit cannot be influenced by changing the report parameters when importing.
Requirement
The file which is to be uploaded can contain the following formats/ commands:
Baseline TIFF 6.0 raster image files. The image information of the TIFF file is converted into black and white/color raster images when uploading. Note: As the TIFF format allows a variety of variants, only a basic set of TIFF 6.0 formats is supported here described in the TIFF 6.0 specification as Baseline TIFF 6.0.
PCL : PCL-5, Hewlett Packard Printer Control Language 5 for HP LaserJet 3, 4, 5 series and compatible printers. The data is output by the printer driver HPL2 only.
PRES: Kyocera PRESCRIBE for Kyocera laser printers. The data is output by the printer driver PRES only.
POST: Adobe PostScript or EPS format (encapsulated PostScript ) for PostScript printers. The data is output by the printer driver POST only. In the upload, one of the end-of-file markers (CTRL-D, hex $04) which may be contained in the PostScript file is not transferred.
For PostScript files which contain a bounding box entry (for example, all EPS files) the macro/graphic can be scaled to a size specified by the user. In this case, a small lead text and trailer are generated by the report for the macro data and inserted in the standard text.
Parameters of RSTXLDMC
File name
Path and file name of the file to be uploaded in the file system of the R/3 frontend (dialog processing) or in the file system of the application server (batch processing)
Type
Way which the data contained in the file is to be converted. Possible values are BMON, BCOL, PCL, POST and PRES. With parameter values BMON and BCOL, a TIFF 6.0 file is expected. This is converted into either a black and white raster image (BMON) or a color raster image (BCOL). These raster images are printer-independent and can be printed using various printer types (see above).
With parameter values PCL, POST and PRES, either a TIFF 6.0 file or a file with printer commands in the appropriate printer langauge is expected. If the file is a TIFF file, it is converted into a black and white raster image for the printer type specified in the parameter. The presence of a TIFF file is recognized automatically. If the file is not a TIFF file, the file contents are regarded as the printer macro of the respective type. Data loaded with type PCL, POST or PRES can only be printed on the respective printer type.
Resolution for TIFF raster images
Resolution which should be used when importing a TIFF raster image, in dots per inch (dpi). If an allowed value is entered here, this overrides the resolution information in the TIFF file. The allowed values are:
75 dpi
100 dpi
150 dpi
200 dpi (not for type PRES, for PCL only HP LaserJet 4,5 series)
300 dpi
600 dpi (not for type PRES, for PCL only HP LaserJet 4,5 series)
Changing the resolution affects the size of the graphic on the printer. If a resolution of 300 dpi is stated in the TIFF file and this parameter is set to 75 dpi, the graphic is four times as big when printed as at the outset.
Note: Kyocera PRESCRIBE printers do not support 200 and 600 dpi resolutions.
Note: Not all PCL-5 printers support resolutions 200 and 600 dpi, for example HP LaserJet 3 series does not, but LaserJet 4 and 5 series do.
Graphic Resident on Printer
Normally, graphics that occur more than once in a printing job (a company logo that appears on each page, for example) are sent to the printer repeatedly each time they are needed. In order to avoid this kind of redundancy, you can select this checkbox on the selection screen. The R/3 print driver then stores the graphic in the printer's memory and the printer retrieves the 'resident' graphic memory every time that re-occurs in your job.
Caution: Whether or not the printer correctly reproduces the graphic depends on the amount of memory available in the printer during the printing job! You should avoid using this feature with color graphics since they take up a lot more memory than monochrome graphics.
This parameter can only be used with types "BMON" and "BCOL".
Absolute positioning
Determines whether the macro/graphic is positioned absolutely or is to be output at the current text position. If this checkbox is selected, the graphic is positioned absolutely (parameters "X-position" and "Y-position" are used), if this checkbox is not selected, the graphic is positioned at the current text position (parameters "Reserved height" and "Shift to right" are used)
Absolute X-position
Horizontal position (space from left border) of the macro/graphic, if absolute positioning is required. This is the parameter XPOS of the HEX command.
Absolute Y-position
Vertical position (space from upper border) of the macro/graphic, if absolute positioning is required. This is the parameter YPOS of the HEX command.
Reserve height automatically
If this checkbox is selected, the system automatically inserts the actual height of the graphic during printing into the subsequent "Reserved height" parameter.
Reserved height
If positioned at the current text position, this parameter specifies the horizontal spacing to be reserved for the macro/graphic, which must not be printed with text from the paragraph. This is the parameter HEIGHT of the HEX command.
Shift to right
If positioned at the current text position, this parameter specifies the space between the left border of the macro/graphic and the left border of the page window. If this value is increased, the macro/graphic is shifted to the right. This is the parameter LEFT of the HEX command.
Unit of measurement for positioning
The unit of measurement in which the position values (X,Y, height, shift) are specified. Possible values are CM (centimeters), MM (millimeters), IN (inches), PT (typographic point = 1/72 inch), TW (1/20 point = 1/1440 inch)
Text title
Comment used for the attribute "Title" of the standard text generated as well as as a comment line in the text itself
Line width
Number of columns to be used in the standard text when generating the HEX...ENDHEX command lines. The default value is 132
Text name
Name of the standard text to be generated. If an * character occurs in the name, it is replaced by the value of the parameter "Printer type". For example, if the entry is ZHEX-IMAGE1-* and the printer type = PCL, the text name ZHEX-IMAGE1-PCL is generated. The default value for the name is ZHEX-MACRO-<printer type>, but the standard text can be named as required (take into account customer reserve). Standard texts are client-dependent!
Note: The name of a standard text can be up to 32 characters long !
Text ID
ID of the standard text to be generated. The default value is ST (general standard texts)
Text language
Language key of the standard text to be generated. The default value is the logon language
PostScript scaling
Flag which determines how the macros/graphics of type POST are handled. If set to 'X', the report expects a PostScript comment line in the file
%%BoundingBox llx lly urx ury (e.g. %%BoundingBox -1.5 0 21.4 14.1)
as present, for example, in all EPS files, in which the dimensions and the position of the macro/graphic are specified (if a bounding box comment is not included, 0 0 1 1 is assumed as the default value). This information is then used by the report to insert PostScript commands which scale the macro/graphic to the size specified in the parameters "Width" and "Height" (listed below).
If the flag is set to ' ' (blank), the PostScript file is transferred to the standard text without any additions (any transformations to the coordinate system used by the printer driver must already be contained in the file).
The flag must be set to 'X' for the import of TIFF files for type POST.
Width according to PS scaling
Required width of the macro/graphic if the flag PostScript scaling is set. Can remain at zero for the import of TIFF files, the size is then determined by the resolution of the graphic.
Height according to PS scaling
Required height of the macro/graphic if the flag PostScript scaling is set. Can remain at zero for the import of TIFF files, the size is then determined by the resolution of the graphic.
If you want to scale the PostScript graphic with these parameters, one of the two values, width or height, can be specified with zero. The graphic is then scaled so that the width-to-height ratio remains unchanged and the original graphic is not distorted.
Unit of measurement for PS scaling
Unit of measurement in which the parameters "Width" and "Height" are specified. Possible values are CM (centimeters), MM (millimeters), IN (inches), PT (typographic point = 1/72 inch), TW (1/20 point = 1/1440 inch)
Number of TIFF gray levels
Number of gray tones which are to be used on the printer for displaying the original image. Note: This parameter is only evaluated when using types PCL, POST or PRES!
Possible values are 2,4,9. With the default value 2, each pixel of the original image is converted either to a white or a black pixel on the printer. With the value 4, each pixel of the original image is converted on the printer with 4 pixels, which simulate 4 different gray levels. With the value 9, each pixel of the original image is converted on the printer with 9 pixels which simulate 9 different gray levels.
Note: With values 4 or 9 the resolution of the image is doubled or tripled. The restrictions on the possible resolutions (see previous parameter) then apply for the resulting resolution.
Output
Individual steps of the upload procedure are logged in the report list generated and, if necessary, errors reported. The uploading of TIFF graphics, in particular, is cancelled if there is a variant which is not supported. A message to this effect is then issued. If execution is successful, the report generates a standard text with the key specified in the parameters. If the standard text already exists, a window appears with a warning before the text is overwritten.
Regards,
Ameer Baba.

How to adjust fields display width?

work in jdev 11.1.2.3.
in the form VISUAL DESIGNER, all fields looks same length, and there is no width attributes to adjust. When it runs, some fields display too long.
How to adjust fields display width during design?
Thanks.

Hi,
You dont need to redo it again , unless you have changed properties after initial drag and drop.
If you have changed , use the value #{bindings.yourAttribute.hints.displayWidth} for columns property.
<af:inputText value="#{bindings.name.inputValue}"
label="#{bindings.name.hints.label}"
required="#{bindings.name.hints.mandatory}"
*columns="#{bindings.name.hints.displayWidth}"*
maximumLength="#{bindings.name.hints.precision}"
shortDesc="#{bindings.name.hints.tooltip}" id="it38">
<f:validator binding="#{bindings.name.validator}"/>
</af:inputText>
Thanks,
Naresh

Is there a way to adjust the column width of only one cell

Using iWork '09: specifically Keynote '09 and want to adjust the column width of just one cell in the column, not the other cells in the whole column just this one individual cell. Have no idea how to do it though. Checked the manual and this discussion group as well as youtube and found nothing.

Scott Fox wrote:
Using iWork '09: specifically Keynote '09 and want to adjust the column width of just one cell in the column, not the other cells in the whole column just this one individual cell. Have no idea how to do it though. Checked the manual and this discussion group as well as youtube and found nothing.
Perfectly normal, this feature is unavailable.
Keynote, Numbers and Pages use quite the same code to build tables which are in fact spreadsheets and this code doesn't offer this feature.
As you don't give many details, look at the merge cells feature.
Given your exact problem, it may be a soluce.
Yvan KOENIG (VALLAURIS, France) mercredi 7 octobre 2009 18:26:05

I want to adjust the column width of "From", "Subject" and "Date". in the AT&T email within Firefox browser

My computer runs under Windows Vista Home Premium, and Firefox browser 3.6.13. Within the Firefox browser, it shows an AT&T email window (www.sbc.yahoo.com). There are several columns such as subject, date, etc. I was able to adjust such column width before. Now I cannot do it. (Also I can adjust column width if I run in the Internet Explorer. I have another computer running Window 7 professional, same set up with Fire Fox and AT&T email, I am able to adjust the column width so I can show the full subject line.

Start Firefox in [[Safe Mode]] to check if one of the add-ons is causing the problem (switch to the DEFAULT theme: Tools > Add-ons > Themes).
* Don't make any changes on the Safe mode start window.
See:
* [[Troubleshooting extensions and themes]]
You can also try to set the pref layout.frames.force_resizability to true on the about:config page.
See also http://kb.mozillazine.org/about%3Aconfig

How can I set column width in JTable?

How can I set column width in JTable?

Also, read the JTable API before posting questions. You will find a link to the Swing tutorial on "How to Use Tables", which contains an example of doing exactly this.

How to set dynamic column width for analysis item

Dear Experts,
I have a query view which is added in the web template as an analysis item. The web item properties on width is not working - I tried entering a value in the width but when I execute the template, the query view's width still stays the same.
Module com.sap.ip.bi.rig.ColumnWidth don't seem correct because I don't want the column width to be static. As my number of columns may change, I wanted the overall width of my query view to stay the same.
Appreciate any ideas which can solve this issue
Thanks and Regards,
huimin
BW newbie

Hi Huimin,
I don't think it is possible to fix the width of the Analysis webitem since it dynamically adjusts its width based on the text maxlength within its cells. Unless you use com.sap.ip.bi.rig.ColumnWidth where the cols are static, you cannot achieve this.
Even if you do override the css settings using a cell padding or something, the portal settings would override the same. How about using a Report webitem to insert tables/charts & check if the width can be adjusted here - just a thought.
--Priya

How to set initial column widths for a table

What I'd like to do is to control the initial column widths for a table.
I'm building the table by using a class which extends AbstractTableModel. This class takes care of setting the headers and reading the data for the table.
If I do the following:
VarTableModel vtm = new VarTableModel(vi);
JTable jt = new JTable(vtm);
JScrollPane jsp = new JScrollPane(jt);
frame.getContentPane().add(jsp);
frame.setVisible(true);
I will see a table in my window. The widths of the columns are equal and are a function of the horizontal dimension of the window.
I have tried to set the width of a column by doing the following:
TableColumn aColumn;
aColumn = jt.getColumn(vtm.getColumnName(0));
aColumn.setWidth(40);
But this has no effect on what gets displayed. I can force the widths that I want by using 'setMaxWidth' but this has the unfortunate side effect of not allowing the user to make the column wider if they want.
What I'd like is a way to specify the widths of the columns when initially displayed and then let the user adjust to their liking.
I'm sure that there is a way to do this, but I don't seem to understand where to intervene in the process to produce the effect that I want.
Any help or suggestions will be greatly appreciated!

Table.setAutoResizeMode(JTable.AUTO_RESIZE_OFF);
add this line and try ur codeThanks for the suggestion! Unfortunately, it doesn't seem to do the trick. Here is an abbreviated segment of my code:
vtm = new VarTableModel(vi);
JTable jt = new JTable(vtm);
// we want a horizontal scrollbar, so turn resizing off
// and we want to control column widths
jt.setAutoResizeMode(JTable.AUTO_RESIZE_OFF);
aColumn = jt.getColumn(vtm.getColumnName(0));
aColumn.setWidth(40);
. // same kind of thing for each column
aColumn = jt.getColumn(vtm.getColumnName(4));
aColumn.setWidth(400);
JScrollPane jsp = new JScrollPane(jt);
frame.getContentPane().add(jsp);
frame.setVisible(true);
If I do the above, the table gets displayed with each of the five columns the exact same width. So, the sizing of the columns is happening somewhere else despite turning auto resizing off.
Where is that occurring and how can I intervene so that I can control the widths of the columns on initial display and still allow the user to adjust the widths if they so choose?

How to adjust the column size

Hi All,
I have a table UI element and due to length of header my column is expanded in width. Kindly assist how I can adjust the column length so the look and feel is good. I am using NWDS 7.0 sp 05.
Thank you
Regards,
Jaspreet Kaur Grewal

Hi Jaspreet ,
Try to use less letter in header for table.
Refer to http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/601ca4c3-6e64-2a10-3380-949f9cdddd46?quicklink=index&overridelayout=true
Hope it migh helps
Regards
Arun

How to set the column width of JTable

I want do remember the column width and write it to a file, when the window is started , the column width is read from the file and the table is set as that. I also want the column width is not fixed and can be changed by mouse.But I am always failded.
How to do? would you please help me!
Thanks a lots.

To "remember" the column widths, add a mouse listener to the table header. Upon mouseReleased(), get the column widths and save them to your file. When the application starts next time, get the stored widths and set them using:
table.getColumn("XXX").setPreferredWidth(...);
By default, your columns are adjustable, but you can use:
table.getTableHeader().setResizingAllowed(true);

How to extract the column width in ALv report if its executed in background

I am executing an ALV report in background , in front end i am getting data properly, in back end for some columns some of the digits are missing.For example if PO no is of 10 digits it will display only 8 becos column size is like that , how to extract coulmns in back ground.
I have executed in background and checked the spool and for some of the columns width is not sufficient to display comeplete data so please suggest how to extract the columns sizes if executed inj background for an ALV

Hi Deepthi,
you can try with the above mentioned suggestions ,if its worked its fine ,
If not use Docking container instead of custom container, For ALV in back ground jobs, its suggest to use docking container instead of custom container , below you can find the declaration for docking container and code to use docking and custom container in your program for fore and back ground.
or you can use docking container alone for both operations.
Data : G_DOCK1 TYPE REF TO CL_GUI_DOCKING_CONTAINER,
IF CCON IS INITIAL. (ccon is container name )
*Check whether the program is run in batch or foreground
    IF CL_GUI_ALV_GRID=>OFFLINE( ) IS INITIAL.
*Run in foreground
      CREATE OBJECT CCON
        EXPORTING
          CONTAINER_NAME = 'CON1'.
    CREATE OBJECT GRID1
        EXPORTING
          I_PARENT = parent_1.
ELSE.
*Run in background
      CREATE OBJECT GRID1
        EXPORTING
          I_PARENT = G_DOCK1.
    ENDIF.
ENDIF.
B&R,
Saravana.S

How can I modify column width in a spreadsheet report without using an Excel template

I currently use the LabVIEW Report Generation toolkit in LabVIEW 2011SP1 to create simple spreadsheet reports that I can build/print without having Microsoft Office products installed. I really like being able to do this, and it allows me to generate nice on-demand data reports - I'm also not tied to having Office installed on the system I'm using, so this works on just about any test fixture I can install the software on.
I recently have a requirement that I must have variable-length columns in my report. I currently use the VI "Append Text Table to Report" in order to create a text table, but the column width requirement is that all columns must be equal width UNLESS I use an Excel Template file to define my column widths.
My questions are:
Is it possible to create a text table and define per-column widths without using an Excel Template? If so, how? My report mainly has a lot of small numerical values for the columns, but some columns contain system names or status messages - I really hate the longer text blocks wrapping and taking up so much real-estate when if I could control the column widths I can get all my data on a single line.
I'll admit I haven't tried this myself yet, but if I use an Excel Template will that require me to have Excel installed on the PC in order to print/generate reports?
Is there a recommended way (with an example) of generating a text table in a report with or without using the "Append Text Table to Report" VI that allows me to have custom column widths that doesn't require me to manually build a custom print page? If I do have to create a custom print page, what would be the most straightforward approach?
Thanks!
-Danny

Sure, I'll provide a pared down example that demonstrates my use-case:
I have a control to the VI that takes in a 2D array of strings representing the data I want printed in a table. I am generating a standard report, adding a table to the report, and printing it. The first VI is "New Report.vi", the second VI is "Append Table to Report.vi", and the third is "Print Report.vi", all found standard in the Report Generation palette.
Note that the "Append Table to Report.vi" has an input parameter "Column Width" with a default value of (1). This input parameter is a single input parameter, which defines the column widths of ALL the columns in my table - hence, with the VI the way it is, all my columns will be 1 inch wide.
I find myself needing to be able to define per-column widths, not just a single global column width parameter.
The only way I have found to do this is by using an Excel template file. The "New Report.vi" takes in a "template" parameter, and if used, the report generation toolkit can be set to ignore the "Column Width" input parameter on the "Append Table to Report.vi" by setting the width value to -1. Instead it will launch Excel, open the template file provided, build the table using the template, will close Excel, and will attach the generated table to the report. However, I have a strict requirement that Microsoft Office NOT be required to be installed on the computer.
So, without using Excel, is there a way to generate a table in a report and define the width of each column individually?
-Danny

How to optimize the column width in Table Control

Hi all,
When I am displaying fields in Table Control, the columns are displayed in full length, and I am unable to see all the fields at once.
So as in grid , where we optimize the column width using layout, do we had any property for TC to do so.
thanks for your help.
Points would be awarded .
Regards,
Anil .

Hi,
In Se51, you can do this one, ust open your table control and resize the TC, there is no direct option to do this for entire TC, you need to do this field by field, and arrage the TC to adjust in a Single screen. In the field parameters, you have the field lenghts, there you can minimize the length of a field
Regards
Sudheer

How to adjust pacman column widths

Similar Messages

Maybe you are looking for