an additional button in the print preview toolbar and in the context menu (via right clicking at the report preview canvas) calls the "settings definitions" dialog, that allows users to configure interactively 90% of the features of foxypreviewer.
that means, that every user can determine lots of things related to his report preview definitions.
users may choose very easilly how the toolbar will appear in the next section, what buttons will be visible, the buttons size, what output types will be available. from the toolbar or the context menu, click at this button, to open the dialog.
now this dialog contains a pageframe with 4 different pages, that i'll describe below:
1 - general page
- language - the combobox lets you change all your report dialogs, tooltips, and captios between 12 languages available: english, portuguese, spanish, french, german, greek, turkish, italian, polish, indonesian, czech, persian. at the source folder of foxypreviewer you'll find the foxypreviewer_locs.dbf table. please update it from times to times, because every time that a new feature is added, some new strings are included there
- toolbar visibility - here you define if in the next report preview session the toolbar will be visible, invisible, or if it will follow the resource file settings
- dock position - determines how the toolbar will appear in the next session, undocked or docked. the combo allows you define the dock position as well.
- canvas count - determines how many pages will be shown in the preview. choose between 1, 2 or 4 pages at the same time
- zoom level - determines the zoom level that will be used in the next session
- window state - choose between, normal, minimized or maximized report preview window
- miniatures per page - determines the maximum quantity of miniatures that will be shown per page when you choose miniatures preview mode
- quiet mode - determines if the progressbar will appear during the report generation and during the output generation. if you include the "nodialog" clause in your report, this setting will be ignored
- progressbar type - choose between the default progressbar (not beautiful at all) or the coolest windows compatible progressbar, compatible with all windows versions, a courtesy of carlos alloatti and dorin vasilescu. picture below:
- version - at the bottom-left part of the dialof form you can see easilly some details of the current version used. please report this version information if you report a bug, or need some feedback
2 - controls page
- size of buttons - determines the size of the buttons to be used. 16x16 or 32x32. internally, foxypreviewer stores 2 button size options. users may choose between these options. if you want to use your own buttons, go to the image folder, and replace with your own buttons. make sure to use the same file names. after recompiling, your foxypreviewer.app version will show your pictures. below you can see the toolbar in the big size (32x32)
- printing preferences button - determines the visibility of "printing preferences" button in the toolbar and context menu
- preferences options: "global printer prompt options" - shows the vfp9 default printer prompt dialog. this is the most flexible dialog, it allows your user to determine the printer for the output, change preferences, access an uninstalled printer from the lan, etc. the disadvantage is that if the user clicks on the "cancel" button, the report preview will be closed.
- preferences options: "setup property sheet for the current printer" - shows the preferences dialog for the current printer. this will not allow you to switch to another printer, but if the user clicks on "cancel", the preview will be restored.
- copies - determines if the copies spinner will be shown in the toolbar. this control will allow your users to change the quantity of copies for the current report session.
- save report - determines if the "save" button will be available in the toolbar and context menu. see in the next section how to determine which output file options you can make available.
- available printers - determines if a combobox with all the available printers will be visible. this cotrol will allow users to swith the printer output during the preview.
- send report by e-mail - determines if the email button will be visible. see in the 4th page information ( in the "email" tab ) more instructions of usage
- miniatures - determines if the miniatures preview form button will be visible in the preview toolbar and context menu
- find - determines if the search button will be available in the preview toolbar and context menu
- max pages to search - determines the quantity of pages that the search engine will store information. when you have a really big report, of more than 200 pages, users will notice a very important performance difference, because during the report generation it will be saving information of all the fields from the report. set the numeric value of "-1" to tell foxypreviewer to perform the searches in all pages
3 - output page
here you can define what output options you'll have available in the "save report" menu, like in the picture below:
- save as image file - determines if the save to image option will be available in the output options menu
- save as pdf
- save as html
- save as rtf
- save as xls
- save as txt / csv / xl5
- output path - allows userd to determine the path / directory where the output files will be saved
4 - email page
in this page you have several emailing options. choose the one that you find the most appropriate for your case, os, etc.
- email mode - choose between mapi, cdo, or your custom procedure.
- mapi - will fire your default mapi compatible app, like outlook express, office outlook, windows live mail, showing your report as an attachment. all you have to do is click on the "send" button. this does not always work. please advice your users to make some tests before using this option.
- cdo - uses cdo2000 component included in windows 2000 and later. it allows you to send emails using a smtp server. all settings must be accurate in order to make this work. for example, below is the configuration for a hotmail or live account to send emails. you may check also in sergey berezniker's blog for more information on how to send using msn, yahoo or gmail email messages using cdo: http://www.berezniker.com/category/topic/email
- custom procedure - you can use your own procedure to send the current report. use foxypreviewer property "cemailprg", and fill it with the name of the prg responsible for sending emails. this prg receives as a parameter the file name of the file created that you will send as attachment. have a look at the samples provided, the file mysendmail.prg shows how you would need to make your custom procedure.
Foxypreviewer general info