gianni said Hi Claudio, I know what $cellinfo() meaning is and you do NOT need to use it...I've mentioned it just to clearify the whole context! U9.3 = end 2009 - begin 2010 = With current quick evolution of software platform(s) a migration proposal could easily improve the whole application context. Nevertheless: Have you tried to follow the path I suggested? - Is your pre-printed module based on a single line spacing or more than one? - Is your pre-printed module based on a single character pitch or more than one? - Have you tried to change font0 in the printing section? - If yes to last question, were you able to fix either the X or the Y characters position? - Which issue is remaining open? Gianni  

Sorry Gianni, I know you're always available to help. The thing I can't understand is why, in 2017, a report design tool does not have minimum required to draw reports, like rulers. Since 1998, I used Report Builder, Rave Reports, Birth, Oracle BI Publisher, and I've always had a visual designer who is expected to draw a report, not a calculator. I do not want to question the philosophy of Uniface, which could be shared or not, but it's frustrating. I solved it in another way, but thank you anyway Claudio

Claudio said ... I solved it in another way ... Claudio  

Which is the solution adopted? Gianni

  OLIVETTI LETTERA 22           

Claudio, I am NOT understanding what you are trying to achieve... Entities are composed from fields (and labels) and could include other entities. In your post only labels are shown... Could you please re-phrase your need? Thanks, Gianni

"I have a predefined A4 sheet", maybe the right term is preprinted module, sorry! "Having all the necessary measures, how can I dimension my entity in a way that respects diagonal and horizontal offsets?" I have all the sizes of my labels in the module, but I cannot achieve the respect of offsets between labels (vertically and horizontally) when I try to resize the outer entity (which contain my text fields). So pre printed measurements in labels 2,3,4 are not respected. Sorry, hope it's understandable now... :( Claudio

Hello Claudio, the problem is overdue, several years ago when pre-printed forms existed, the only way to try to center the data in print was to print text in text using the unifield fields; if you use the graphic format each pc could print differently depending on the operating system, printer driver, etc. Ciao Claudio, il problema è annoso, parecchi anni fà quando c'erano i moduli prestampati l'unico modo per cercare di centrare i dati in stampa era quello di eseguire una stampa in formato testo usando i campi unifield ; se usi il formato grafico ogni pc potrebbe stampare diversamente in base al sistema operativo, al driver della stampante etc.

TheAleph said Hello Claudio, the problem is overdue, several years ago when pre-printed forms existed, the only way to try to center the data in print was to print text in text using the unifield fields; if you use the graphic format each pc could print differently depending on the operating system, printer driver, etc. Ciao Claudio, il problema è annoso, parecchi anni fà quando c'erano i moduli prestampati l'unico modo per cercare di centrare i dati in stampa era quello di eseguire una stampa in formato testo usando i campi unifield ; se usi il formato grafico ogni pc potrebbe stampare diversamente in base al sistema operativo, al driver della stampante etc.  

Thank you very much TheAleph, I've tried to do as you said printing in text mode. But the problem still remain...I cannot figured out how to align the text correctly respecting the offset between labels...Every time I resize the outer entity that acts as a container, everything gone wrong. I can not establish a match between mm="designer's squares". Grazie mille! ho provato a fare come hai detto stampando in modalità di testo. Ma il problema rimane...non riesco a capire come allineare il testo correttamente nel rispetto dell'offset tra le etichette...ogni volta che ridimensiono l'entità esterna che funge da contenitore, tutto si sballa. Non riesco a stabilire una corrispondenza mm="quadretti del designer". Ciao Claudio

One option is to use a specialy designed Printer Device Table where you can literally "program" your printer with (expl. PLC6 etc). And it's possible that you create your "Escape" Sequences on the fly with a little help from the GOLD; which is the ESC character. I used this a couple of times in the early 90's to print stationary of all kind. Think in 2007, there was some discussion on turf about checue printing which may give you a hint.

A more modern way may be to use the talents of HTML5/CSS to do the layouts in an HTML-widget. This will always have some interactive part as there is a dialog when you invoke the printing.

Hi Claudio, Uniface screens/printouts are built around a base cell ($cellinfo). This cell is determined from font0 definition in the configuration file you are using (.ini file) in [screen] or [printer] sections; - the first step is to recognize your pre-printed module and define how it was built. - the second step is to adapt your .ini file in this case into the [printer] section to your current need. This analysis is leading to a decision: could this custom module be printed in my standard application process or its requirements needs a dedicated process to use a customized initialization file? If you need to start a dedicated process userver or another uniface process could do the job. In the printing phase some zoom functionality could be applied; you should control it defining your Uniface report component. Everything I've detailed is available into current Uniface Library. Regards, Gianni

Thanks all, people. From chm:

$cellinfo Get an associative list with the dimensions of a character cell in pixels.

$cellinfo Return Values Returns an associative list with the width (xsize) and height (ysize) in pixels of a character cell as displayed on the screen. The dimensions are determined by the font0 setting in [SCREEN] section of usys.ini. xsize=Pixels;ysize=Pixels An empty string is returned when the function is used in batch mode or in a non-interactive Windows environment.

Use: Use only in form components.

Description $cellinfo returns the dimensions of single cell as determined by the following settings in usys.ini:

font0 in the [screen] section

CELLHEIGHT and LINESPACE in the [upi] section. CELLHEIGHT specifies the cell height (as a percentage of the cell height of Font 0) used to draw widgets. LINESPACE specifies additional spacing between text lines in the background.

These dimensions can be used as input for $windowproperties to adjust the size of the window.

Table 1. History Version Change 9.4.01 Introduced I'm with 9.3, in a report. Ulrich Merkel: Thanks for your advice, I will leave as the last soluzion the escape. I don't want to use "exotic" solutions for simple labels, I need to make a print and I want to use its integrated printing tool. Thanks anyway for your suggestions. Regards, Claudio

Hi Claudio, I know what $cellinfo() meaning is and you do NOT need to use it...I've mentioned it just to clearify the whole context! U9.3 = end 2009 - begin 2010 = With current quick evolution of software platform(s) a migration proposal could easily improve the whole application context. Nevertheless: Have you tried to follow the path I suggested? - Is your pre-printed module based on a single line spacing or more than one? - Is your pre-printed module based on a single character pitch or more than one? - Have you tried to change font0 in the printing section? - If yes to last question, were you able to fix either the X or the Y characters position? - Which issue is remaining open? Gianni