Difference: CDOverviewChartRenderEs (1 vs. 3)
Revision 32013-02-16 - RayPelegrino
Revision 22013-02-15 - RayPelegrino
| Line: 1 to 1 | ||||||||
|---|---|---|---|---|---|---|---|---|
Chart Rendering Overview | ||||||||
| Changed: | ||||||||
| < < | This page describes the process for rendering a chart and using it in your Appx program. | |||||||
| > > | Esta página describe el proceso de presentación de una chart y utilizarla en su programa APPX | |||||||
| Changed: | ||||||||
| < < | Description: | |||||||
| > > | Descripcion: | |||||||
| Changed: | ||||||||
| < < | After you have initialized your chart, provided the data to plot and set any other desired attributes, you render the chart by calling the .CHART RENDER routine. This requires just one arguement, a field to contain the name of the generated graphic file. The routine will then invoke Chart Director, which will create the graphic file. You can also pass a file name, in which case it will create that file in the default chart directory. If you pass a complete path and file name, the chart will be rendered to that location. If you pass a blank field, the API will assign a unique name for you, using the settings in the parameter file. | |||||||
| > > | Una vez que haya inicializado su chart, próvido los datos para trazar y establecer otros atributos deseados, hay que a hacer un reproducir el chart llamando a la rutina .CHART RENDER. Esto requiere un solo argumento, un campo que contiene el nombre del archivo gráfico generado. La rutina luego invocará Chart Director, que va a crear el archivo gráfico. También puede pasar un nombre de archivo, en cuyo caso se creará el archivo en el directorio gráfico predeterminado. Si pasa una ruta completa y el nombre del archivo, el gráfico se representará en esa ubicación. Si pasa un campo en blanco, el API asigna un nombre único para usted, utilizando la configuración en el archivo de parámetros. | |||||||
| Changed: | ||||||||
| < < | If you have standard colors or other attributes that should be the same across all charts, you can create your own subroutine that sets all these attributes before calling .CHART RENDER. In your applications, you would call this subroutine instead of calling .CHART RENDER directly. This would give all your charts a common look and feel.
To use the chart in an input or output process, place an alpha field on your image, drag it out to the appropriate size, and set the GUI attributes to PICTURE, Location Type of SERVER, Position to EXPAND PROP'L and check the Transparent flag. You can then pass this field to the .CHART RENDER routine, and Appx will display the completed chart on your image. Make sure the alpha field is long enough to contain the complete path and file name.
The rendered chart file is not automatically removed, it is your responsbility to clean up any chart files that are no longer needed. The End of Process Event point (for both Inputs and Outputs) is a logical choice, if you are only rendering one chart in the process. If you are rendering more than one chart in the process, you will have to use another technique.
Comments | |||||||
| > > | Si tiene colores estándar o otros atributos que deben ser las mismas en todos los gráficos, puede crear su propia subrutina que establece todos estos atributos antes de llamar .CHART RENDER. En sus aplicaciones, debe llamar a esta subrutina en lugar de llamar. CHART RENDER directamente. Esto daría a todos sus cuadros un aspecto común. Para usar la chart en un proceso de entrada o de salida, coloque un campo alfa en la imagen, arrástrela fuera al tamaño adecuado, y establecer los atributos de interfaz gráfica de usuario para PICTURE, Location Type de SERVER, Position EXPAND PROP’L y seleccionar Transparent Flag. Después, puede pasar este campo a .CHART RENDER. y APPX mostrará el cuadro completo en la imagen. Asegúrese de que el campo alpha es suficientemente largo para contener la ruta completa y el nombre del archivo. El archivo gráfico rendido no se elimina automáticamente, es su responsabilidad limpiar los archivos gráficos que ya no son necesarios. El evento End of Processs Event Point (tanto para entradas y salidas) es una opción lógica, si sólo está haciendo un gráfico en el proceso. Si usted está haciendo más de un gráfico en el proceso, usted tendrá que utilizar otra técnica. Comentarios | |||||||
| Read what other users have said about this page or add your own comments. | ||||||||
Revision 12013-02-14 - RayPelegrino
| Line: 1 to 1 | ||||||||
|---|---|---|---|---|---|---|---|---|
| Added: | ||||||||
| > > |
Chart Rendering OverviewThis page describes the process for rendering a chart and using it in your Appx program.Description:After you have initialized your chart, provided the data to plot and set any other desired attributes, you render the chart by calling the .CHART RENDER routine. This requires just one arguement, a field to contain the name of the generated graphic file. The routine will then invoke Chart Director, which will create the graphic file. You can also pass a file name, in which case it will create that file in the default chart directory. If you pass a complete path and file name, the chart will be rendered to that location. If you pass a blank field, the API will assign a unique name for you, using the settings in the parameter file. If you have standard colors or other attributes that should be the same across all charts, you can create your own subroutine that sets all these attributes before calling .CHART RENDER. In your applications, you would call this subroutine instead of calling .CHART RENDER directly. This would give all your charts a common look and feel. To use the chart in an input or output process, place an alpha field on your image, drag it out to the appropriate size, and set the GUI attributes to PICTURE, Location Type of SERVER, Position to EXPAND PROP'L and check the Transparent flag. You can then pass this field to the .CHART RENDER routine, and Appx will display the completed chart on your image. Make sure the alpha field is long enough to contain the complete path and file name. The rendered chart file is not automatically removed, it is your responsbility to clean up any chart files that are no longer needed. The End of Process Event point (for both Inputs and Outputs) is a logical choice, if you are only rendering one chart in the process. If you are rendering more than one chart in the process, you will have to use another technique.CommentsRead what other users have said about this page or add your own comments.-- JeanNeron - 2011-09-21 | |||||||
View topic | History: r3 < r2 < r1 | More topic actions...
Copyright © 2008-2024 by the contributing authors. All material on this collaboration platform is the property of the contributing authors. Ideas, requests, problems regarding TWiki? Send feedback