Navigation Menu

[Kurt Hansen]

The orientation are part of the printstring you get from the wxprintdialog(.nul, prtstring, ok )
If you want to be sure if the orientation if rigth, you can manipulate it like this:
myprintstring = replace( prtstring, “portrait”, “landscape” )

Sorry to hear that Neil Robinson passed away.

I use simpol NG 2.06, I newer downloaded NG version 2.10, but I need it now doe to the new grid features. At the moment it seems not possible to download from the web page.

Plase can anyone send me a .zip copy of Superbase NG 2.10 by mail to my mail acount
mail ku**@**6.dk

Thanks in advance

Kurt Hansen

[Kurt Hansen]

Hi Neil

Possibly the title in report window was equal to the title in the report
header. I have changed the report title, but it doesn't help.

To be precise:

a) The problem with the cleaned up of the window comes only if I use the
parameter gr.centeroverdisplay = .true

On windows XP the remaining of the window on its original position are
shown together with adopted wrong background between the buttons as
shown on the attachment (I have tried both workstation several notebooks)

On Windows 7 (same WS HW) the problem isn't that big, but it still has
the problem with the wrong background between the buttons.

b) The problem with the parameter gr.startat100percent = .true are
mostly not fulfilled on Windows XP but works as intended on Windows 7
although I use exact the same HW and Simpol App.

(Glad that most people have changed to windows 7 now a days 🙂

As there are none possibilities to refresh/resize the preview window
from the App. I will leave the gr.centeroverdisplay line out of the app
not to give the user a bad experience.

Ciao, Kurt

Den 13-02-2013 22:56, Neil Robinson skrev:
> On 12/02/2013 09:25, Kurt Hansen wrote:
>>
>> Stumbled over a problem when displaying a report in the preview window:
>>
>> The graphic around the keys in the preview window are not cleaned up
>> (see attachment), and the report is shown at 70% instead of 100%.
>
> You need tomake sure you give the report a unique title for he caption, since the code that switches to 100% uses the sendkeys()
> function and appactivate() to bring the window to front.
>
>> To me it seems the report is shown in a sort of modal window without
>> getting CPU time for the final steps to be carried out? I have tried to
>> run the report in a separate thread. But it didn't help
>
> It should have worked, but like I said, did you give it a unique title?
>
> It turns out that the wxPrintout.printpreview() doesn't really have anything we can grab. It is a one shot type of command (not
> happy about that, but better than no print preview I suppose).
>
>
>>
>> Sample graphic report:
>>
>> …
>> … (report definition)
>> …
>> gr.startat100percent = .true
>> gr.centeroverdisplay = .true
>> gr.dialogdata = me.printer
>> gr.run(errmsg, erridx, error=err) :// Show report
>>
>>
>> The problem is not specific to release 1.73 I always had this problem.
>>
>> Am I doing something wrong or are there a work around for this?
>>
>> The problem is common to both Windows XP and Windows 7. Redrawing after
>> minimizing the window does the necessary cleanup.
>
> Let me know if the above helps you out.
>
> Ciao, Neil
>

[Kurt Hansen]

The problem is solved in Simpol release 1.73 -Thanks

/Kurt

Den 14-01-2013 16:38, Kurt Hansen skrev:
> Problem with Graphic Report:
>
> 1)
> I have a problem with a Graphic Report witch I'm not able to solve:
>
> If the sort order clause are set to anything other than ""; then all
> records are shown twice in the report and the records are not sorted as
> required
>
> sample: gr.setorderclause("City, Surname")
>
> The actual report is only based on one vola table. I have tested with a
> sbme1 table to. Here the same problem appears.
>
> Any ideas?
>
> 2)
> What is the syntax of the select where clause if more than one table are
> used in a report?
> (I have tried "tablename1.fieldname1, tablename2.fieldname2,…” as used
> in Simpol Personal, but this raises an error 5500)
>
> Ciao
>
> Kurt

[Kurt Hansen]

Den 02-02-2013 12:52, Kurt Hansen skrev:
> Hi
>
> Does Simpol have a equivalent to the Superbase function FN ansi()?
>
> Ciao
>
> Kurt

Problem solved!
(Ansi conversatation omittet, changed to charset=ISO Latin 1 in my HTML
export tool with Danish letters) 🙂

Ciao, Kurt

[Kurt Hansen]

Den 24-01-2013 13:22, Neil Robinson skrev:
> On 23/01/2013 19:22, Kurt Hansen wrote:
>> Hi Neil
>>
>> Thanks for your help
>>
>> About 2)
>>
>> I may be wrong about the error number. If I define the select where
>> clause like "ADDRESS.Lastname,Address.Firstname,…", I get an error
>> message as shown in the attachment. I suppose the 9 rows in the error
>> message are due to the 9 colons used in the actual report.
>>
>> The current report uses only one vola table as an n:n relation between
>> two tables are handled in the program beforehand.
>>
>> To be sure I use the right table names I have also tried to read the
>> filenames in the table object (tbl).
>> Sbme files : filename = tbl.sbme.filename
>> Vola files : filename = tbl.volabase.filename
>
>
> Hi Kurt,
>
> Don't confuse filename and tablename. To get the correct tablename you need to use:
>
> tbl.tablename
>
> You are correct that the nine lines in the error refer to the 9 entries in the select statement. The bit about identifiers not
> found or not unique refers to the fact that you have a table called Adrtmp in your select statement (9 of them actually) but it
> can't find a table of that name in its list. Have you already added the data source and table to the report using:
>
> graphicreport.adddatasource()
> graphicreport.addtable()
>
> ?
>
> Ciao, Neil
>
Hi

Oh my fault Thanks. I didn't use the correct table name. Now it works!

Although I only use one table at the moment, now it also works using
both table and field names in the select clause.

I only started testing this issue using both table and field names in
the select clause to se if it had any impact on the other fault with the
gr.setorderclause

Ciao, Kurt

[Kurt Hansen]

Den 23-01-2013 17:43, Neil Robinson skrev:
> On 14/01/2013 15:38, Kurt Hansen wrote:
>> Problem with Graphic Report:
>>
>> 1)
>> I have a problem with a Graphic Report witch I'm not able to solve:
>>
>> If the sort order clause are set to anything other than ""; then all
>> records are shown twice in the report and the records are not sorted as
>> required
>>
>> sample: gr.setorderclause("City, Surname")
>>
>> The actual report is only based on one vola table. I have tested with a
>> sbme1 table to. Here the same problem appears.
>>
>> Any ideas?
>>
>> 2)
>> What is the syntax of the select where clause if more than one table are
>> used in a report?
>> (I have tried "tablename1.fieldname1, tablename2.fieldname2,…” as used
>> in Simpol Personal, but this raises an error 5500)
>>
>> Ciao
>>
>> Kurt
>>
>
> Hi Kurt,
>
> You are quire right. I don't quite understand how that second set of calls to the output row stuff ended up where it did, but I
> have repaired it.
>
> This would have affected any graphic report that used a sort order.
>
> In the process, I also discovered a rather sneaky little sorting bug that only happened in certain cases, which I have also now
> fixed. This is in the reportlib.sml, which hosts report1, and which therefore affects the downstream libraries quickreportlib.sml
> and graphicreportlib.sml.
>
> As for your second question, the select where clause is case-sensitive. It should work like:
>
> "ADDRESS.Lastname,Address.Firstname,…"
>
> I am surprised that you get an error 5500. We don't have an error with that number (that I am aware of).
>
> Ciao, Neil
>

Hi Neil

Thanks for your help

About 2)

I may be wrong about the error number. If I define the select where
clause like "ADDRESS.Lastname,Address.Firstname,…", I get an error
message as shown in the attachment. I suppose the 9 rows in the error
message are due to the 9 colons used in the actual report.

The current report uses only one vola table as an n:n relation between
two tables are handled in the program beforehand.

To be sure I use the right table names I have also tried to read the
filenames in the table object (tbl).
Sbme files : filename = tbl.sbme.filename
Vola files : filename = tbl.volabase.filename

It didn’t help.

Ciao, Kurt

[Kurt Hansen]

Den 14-01-2013 18:38, Jim skrev:
> I think that the reports in simpol are substantially the least mature
> portion of the system. There are lots of bugs, and many things that don't
> work correctly – including multi-table queries and joins.
>
> I have helped Neil a bit with some of these things, and I have looked at
> the code that does the queries and joins.
>
> That code is very complicated and obscure; I have not taken the time to
> really study and understand it. For my own purposes, it has worked better
> (taken less time) for me to make several single-table queries, then do an
> appropriate join in my own code. This is suboptimal, but until the query
> code is fixed, it is the only way – and it does work.
>
> I guess this is a good time to report on a documentation problem I found
> in the report1 code. I have already told Neil.
>
> Essentially, report1 code that worked in version 1.16 broke in version
> 1.17 because of a change in the code that was not reflected in the
> documentation.
>
> The documentation says that the prototype for tabbed_output_row is:
>
> function report1_tabbed_output_row(report1 report, report1inst
> reportinst, array columns, array currcolvals, fsfileoutputstream fpo)
>
> which has to be changed to:
>
> function report1_tabbed_output_row(report1 report, report1inst
> reportinst, array columns, array currcolvals, boolean reading,
> fsfileoutputstream fpo)
>

Hi Jim

My report is only based on one vola file (I select the records for the
report in my application beforehand.)

I just tried an old version of my app compiled with the ver. 1.6
library. It seems to work without this problem.

/Kurt

[Kurt Hansen]

Den 28-12-2012 17:49, Neil Robinson skrev:
> On 17/12/2012 16:55, Kurt Hansen wrote:
>> Hi Dan
>>
>> I'm aware of what error 64 means. I just want to point out, that
>> SBME1 files and Vola files seems not to work the same way, when EOF are
>> reached.
>>
>> SBME1 files raises an error 64 but the Vola files doesn't raise an error
>> when EOF are reached.
>>
>> /Kurt
>
> It turns out that the vola1record.select() was assigning the error value correctly, but was not passing it back to the external
> error variable. I have corrected this. The uploaded library is in the SIMPOL Demos library on the web site (after logging in and
> clicking on the File Library button).
>
> Ciao, Neil
>

Thanks. I have now implemented the new library in my application and it
works as intended.

Btw. I noticed the following warnings in the IDE during the compilation
with the new lib:

Warning: "DATESTR" repeated in project
Warning: "DAY" repeated in project
Warning: "DAYS" repeated in project
etc….

The functions "DATASTR", "DAY" and "DAYS" … are inclosed in both
db1util.sml, volatable.sml and other libs, It can be reproduced that it
appears compiling with the new and not with the old volatable.sml, but I
don't see any reason for a connection between the two events.

Any ideas?

Ciao, Kurt

>>
>>
>> Den 17-12-2012 04:47, djinks skrev:
>>> Kurt,
>>> The thread I was recalling was the Best Practices thread this group in
>>> June.
>>>
>>> -Dan
>>>
>>>
>>> On 12/16/2012 5:25 PM, djinks wrote:
>>>> Hello Kurt,
>>>>
>>>> from error.sma :
>>>> constant iERR_NORMALENDOFDATA 64
>>>>
>>>> Neil recently did an explanation for someone about this. It just means
>>>> you reached the end of file.
>>>>
>>>> In the IDE, open my demo project and search the project's files (special
>>>> icon on tool bar with binoculars and folder symbol) for
>>>> "iERR_NORMALENDOFDATA" and you will get a list of all occurances of it
>>>> in the project.
>>>>
>>>> -Dan
>>>>
>>>> On 12/15/2012 10:40 AM, Kurt Hansen wrote:
>>>>> Hi Dan
>>>>>
>>>>> Thanks;
>>>>>
>>>>> I’m now using the vola files for my relational records as intended.
>>>>>
>>>>> Working with SBME1 files I get error 64 reaching End of File (EOF)
>>>>>
>>>>> sample: rec =@ rec.select(.false, locktype = "", error = err)
>>>>>
>>>>> Using the same operation on a vola file no error 64 are set, instead I
>>>>> get rec =@= .nul
>>>>>
>>>>> sample: rec =@ rec.select(.false, error = err)
>>>>>
>>>>> Do you have the same experience?
>>>>>
>>>>> /Kurt
>>>>>
>>>>>
>>>>> Den 12-12-2012 10:37, djinks skrev:
>>>>>> Kurt,
>>>>>> I just uploaded a Volatile File Demo to the Contribution section of the
>>>>>> SIMPOL.com developer's library.
>>>>>>
>>>>>> Hope it helps.
>>>>>>
>>>>>> -Dan
>>>>>>
>>>>>> Kurt Hansen wrote:
>>>>>>
>>>>>>> Does anyone have samples where Volatables are created etc?
>>>>>>
>>>>>>> I want to use a Volatile database instead of arrays for the display of
>>>>>>> relational data, making it easy to sort the data after columns as
>>>>>>> selected by the user.
>>>>>>
>>>>>>
>>>>>>> Kurt
>>>>>>
>>>>>>
>>>>>>
>>>>>
>>
>

[Kurt Hansen]

Hi Dan

I'm aware of what error 64 means. I just want to point out, that
SBME1 files and Vola files seems not to work the same way, when EOF are
reached.

SBME1 files raises an error 64 but the Vola files doesn't raise an error
when EOF are reached.

/Kurt

Den 17-12-2012 04:47, djinks skrev:
> Kurt,
> The thread I was recalling was the Best Practices thread this group in
> June.
>
> -Dan
>
>
> On 12/16/2012 5:25 PM, djinks wrote:
>> Hello Kurt,
>>
>> from error.sma :
>> constant iERR_NORMALENDOFDATA 64
>>
>> Neil recently did an explanation for someone about this. It just means
>> you reached the end of file.
>>
>> In the IDE, open my demo project and search the project's files (special
>> icon on tool bar with binoculars and folder symbol) for
>> "iERR_NORMALENDOFDATA" and you will get a list of all occurances of it
>> in the project.
>>
>> -Dan
>>
>> On 12/15/2012 10:40 AM, Kurt Hansen wrote:
>>> Hi Dan
>>>
>>> Thanks;
>>>
>>> I’m now using the vola files for my relational records as intended.
>>>
>>> Working with SBME1 files I get error 64 reaching End of File (EOF)
>>>
>>> sample: rec =@ rec.select(.false, locktype = "", error = err)
>>>
>>> Using the same operation on a vola file no error 64 are set, instead I
>>> get rec =@= .nul
>>>
>>> sample: rec =@ rec.select(.false, error = err)
>>>
>>> Do you have the same experience?
>>>
>>> /Kurt
>>>
>>>
>>> Den 12-12-2012 10:37, djinks skrev:
>>>> Kurt,
>>>> I just uploaded a Volatile File Demo to the Contribution section of the
>>>> SIMPOL.com developer's library.
>>>>
>>>> Hope it helps.
>>>>
>>>> -Dan
>>>>
>>>> Kurt Hansen wrote:
>>>>
>>>>> Does anyone have samples where Volatables are created etc?
>>>>
>>>>> I want to use a Volatile database instead of arrays for the display of
>>>>> relational data, making it easy to sort the data after columns as
>>>>> selected by the user.
>>>>
>>>>
>>>>> Kurt
>>>>
>>>>
>>>>
>>>

[Kurt Hansen]

Hi Dan

Thanks;

I’m now using the vola files for my relational records as intended.

Working with SBME1 files I get error 64 reaching End of File (EOF)

sample: rec =@ rec.select(.false, locktype = "", error = err)

Using the same operation on a vola file no error 64 are set, instead I
get rec =@= .nul

sample: rec =@ rec.select(.false, error = err)

Do you have the same experience?

/Kurt

Den 12-12-2012 10:37, djinks skrev:
> Kurt,
> I just uploaded a Volatile File Demo to the Contribution section of the
> SIMPOL.com developer's library.
>
> Hope it helps.
>
> -Dan
>
> Kurt Hansen wrote:
>
>> Does anyone have samples where Volatables are created etc?
>
>> I want to use a Volatile database instead of arrays for the display of
>> relational data, making it easy to sort the data after columns as
>> selected by the user.
>
>
>> Kurt
>
>
>

[Kurt Hansen]

Den 22-11-2012 15:56, Neil Robinson skrev:
> On 22/11/2012 11:05, Kurt Hansen wrote:
>>
>> Hi
>>
>> After compiling my application in new Simpol version 1.7 I get error 41
>> "Parameter not found".
>>
>> I have tried to trace the problem. It arises at this command:
>>
>> graphicreport1formvar.addgraphic(graphicreport1rectangle,……………,error=err)
>>
>> I'm not able to find out witch parameter is missing, what has changed?.
>> If I compile my app. with the lib files from version 1.6 the error
>> disappears.
>> ———–
>>
>> To find the reason I tried the sample "Working With printform1" in the
>> documentation (see attachment). This also raises error 41.
>>
>> Ciao
>>
>> Kurt
>>
>
> Hi Kurt,
>
> In order to make things consistent between controls and graphics, the parameter name for addgraphic was changed from name to
> printname. Sorry about that. I will update the documentation as well.
>
> Ciao, Neil
>
Thanks problem solved.

I like that the problem abut the font size seems solved 🙂

Ciao

Kurt

[Kurt Hansen]

Den 06-03-2012 11:43, Neil Robinson skrev:
> On 27/02/2012 16:14, Kurt Hansen wrote:
>>
>> CASE: On my form some wxformedittext objects with the ongotfocus
>> event set, a dialog are triggert for further selections.
>>
>> As the dialog is closed, the ongotfocus event seems to trigger the
>> event again and again and again….., and so it is impossible to
>> close the dialog.
>>
>> Is there a solution for this? I know it may be possible to set the
>> setcaptureable parameter and use the onmousemask functions. I want
>> to avoid this if possible.
>>
>> I have tried the wxformvar.clearfocus() function but it didn't help
>>
>> Any suggestion?
>>
>> Kurt
>
> Hi Kurt,
>
> The problem that you are hitting is that when the dialog closes, the
> form receives focus again and that creates a brand new event. To prevent
> it, either place focus somewhere else on the form before closing the
> dialog window, or use some form of flag to indicate that you have
> already done the lookup. I would suggest that if the field is not empty,
> it shouldn't show the dialog. So in that case, put it on the onlostfocus
> event and only trigger the dialog if the wxformedittext is empty. That
> will solve your existing problem and probably be more user friendly as well.
>
> Ciao, Neil

Hi Neil

Thank, I will tray it out
(In between I'm using the onmousemask function)

Kurt

[Kurt Hansen]

Thanks

(Sorry I didn't se your answer before sending my correction)
I am using my own application object with among others contains my file
and table objects.

Kurt

Den 14-07-2011 23:31, Neil Robinson skrev:
> More or less. The general approach is to add datasources (sbme files,
> ppcs objects), to the datasources of the application, and using the
> datasource, open the tables in appwindow. The datasources cannot be
> opened more than once if they are sbme files, you will get locked out.
> They are opened for exclusive access, so you need to reuse the sbme1
> object, thus the datasources ring in the application object. As a
> shortcut for small applications, I tend to add the tables to the
> application object as well, nowadays in a special type with a property
> for each.
>
> Ciao, Neil
>
> On 14/07/2011 18:11, djinks wrote:
>> I think you are supposed to reuse the table object that you opened
>> the first time. My understanding ( and I'm new at SIMPOL so could be
>> wrong) is that you open it once and add the table to the application
>> object once it is opened and then pass the application object to
>> whatever function requires it. Storing the table in the app object
>> occurs in the myapplication.new function.
>>
>> See the addressbookapplication.new function in
>> SIMPOLprojecttutorialaddressbookaddressbook.sma
>>
>> -Dan
>>
>> On 7/14/2011 11:35 AM, Kurt Hansen wrote:
>>>
>>> Error using the same filename to open the same file twice
>>>
>>> 1) Opening SBME Files for display in forms etc.:
>>> =================================================
>>>
>>> sbme1 fil sbme1table adr …. fil =@ sbme1.new("adr.sbm","O", err
>>> ) …
>>>
>>>
>>> 2) Afterwards opening the same SBME Files for reports in another
>>> part of the same app.:
>>> ========================================================================
>>>
>>>
>>>
> sbme1 fil
>>> sbme1table adr …. fil =@ sbme1.new("D:SimpolADR70adr.sbm","O",
>>> err ) …
>>>
>>>
>>> The sample mentioned above works as intended, but if in part 2) the
>>> file are opened without specification of the path, that is with the
>>> same statement as in part 1), an error 3 are raised (3="Locked
>>> out")
>>>
>>> To me it seems that is the same sbme file can be opened twice, but
>>> using the same filename for doing this twice isn’t permitted?
>>>
>>> Caio
>>>
>>> Kurt
>>>
>

[Kurt Hansen]

Sorry, there is an error in my conclusion.
The filename with the path is accessing a copy of my sbme file.
So it seems that the file can only be opened once. Is that correct?
(That is I has to apply the same file object in both cases)

Ciao

Kurt

Den 14-07-2011 17:35, Kurt Hansen skrev:
>
> Error using the same filename to open the same file twice
>
> 1) Opening SBME Files for display in forms etc.:
> =================================================
>
> sbme1 fil
> sbme1table adr
> ….
> fil =@ sbme1.new("adr.sbm","O", err )
> …
>
>
> 2) Afterwards opening the same SBME Files for reports in another part of
> the same app.:
> ========================================================================
>
> sbme1 fil
> sbme1table adr
> ….
> fil =@ sbme1.new("D:SimpolADR70adr.sbm","O", err )
> …
>
>
> The sample mentioned above works as intended, but if in part 2) the file
> are opened without specification of the path, that is with the same
> statement as in part 1), an error 3 are raised (3="Locked out")
>
> To me it seems that is the same sbme file can be opened twice, but using
> the same filename for doing this twice isn’t permitted?
>
> Caio
>
> Kurt
>

[Kurt Hansen]

Den 15-06-2011 14:43, Neil Robinson skrev:
> On 12/06/2011 11:22, Kurt Hansen wrote:
>>
>>
>> I have tried the new report engines in release 1.5 and got the
>> following problems. Am I doing anything wrong?
>>
>> 1) gr =@ graphicreport1.new(paperwidth=me.paperwidth,
>> paperheight=me.paperheight, …… In the Print Preview window the
>> paper is always shown as A4 portrait despite of the selected paper
>> format. It is possible e.g. to print a report in A4 Landscape
>> although it is shown as A4 Portrait in the preview window
>
> Hi Kurt,
>
> You need to grab the printer information once first (dialogdata) and
> then assign that to the graphic report property called dialogdata. use
> the replace() function to switch portrait to landscape in the string
> before you assign it, like this:
>
> gr.dialogdata = replace(mydialogdata, "portrait", "landscape")
>
> That will do what you want.
>

In my app the dialog data property wasn't set at all (=.nul). I tried
the printerdialog and got the textstring with the needed printerdialog
data. for the report. I have to play further with this issue but it
seems to work. -Thanks

Is it possible too read the current dialogdata string without using the
printer dialog?.

>> 2) gr.addcontrol(graphicreport1formtext, ….. textrgb =
>> color.txtfldfg, backgroundrgb = 0x0fff0f, backgroundvisible= .true,
>> ….) Using the possibility to add background colours to the fields
>> in the graphic report the frames are also shown. Isn't it possible
>> to deactivate the frame or set the colour to the same as the
>> background colour?. (It doesn't take the borderrgb parameter)
>
> I have noticed that, but haven't seen a way to prevent it. I checked and
> I can't see any method of controlling those properties yet. What you
> could do is to make the background invisible and place a colored
> rectangle beneath the control.
>

That's is also my conclusion, I've had the same problem and conclusion
as I years ago made my own report solution using wxformtext objects.
Here I made the report easy to read using a soft bag ground colour in
each 2'nd line using the wxgraphicrectangle object.

>>
>> 3) gr.addcontrol(graphicreport1formtext, ……..
>>
>> Adding background colours gives a messy layout in reports wenn some
>> data fields are emty, becourse empty fields are not shown at all.
>> I've had the same problem in my own object solutions for displaying
>> relational data in the WXForms. Here I had to make a Work around
>> adding the text "—" to all empty data fields on the form (not in
>> the database).
>
> If you want fixed size colored areas, turn off the background and use
> colored rectangles in the correct locations.
>

Yes I also do it that way now. (Just to be sure if it is a known issue)

>>
>> 4) Fonts are shown/printed bigger as selected
>
> This has been an ongoing problem with the wxprint stuff. There are
> currently a number of workarounds in place to reduce the size inside the
> SIMPOL code. Try setting the following properties:
>
> gr.reportform.wrapkludgevalue = .toval("1.15", .nul, 10)
> gr.reportform.fontresizekludgevalue = .toval("0.7", .nul, 10)
> gr.reportform.wrapcharcountkludgevalue = .toval("1", .nul, 10)
>
> Tweaking these properties is how you work on it for wrapped fields. How
> far off are your sizes? If necessary, pass in a smaller size for now,
> but mark the code so that when we finally track it down, you can remove
> the fix (use a constant for example).

The size seems to bee around 130% (Font defined as 9 point looks like
font 12 point, font 16 => font 21 point).

Ciao

Kurt

>
> Ciao, Neil
>
>> — Any ideas?
>>
>> Ciao
>>
>> Kurt
>

[Author]

Posts