PDATChartLib

 

Official Website for additional information/Registration: http://www.gack-apps.com/PDAT

Release Date: 01/04/2005
Version: 1.6
Price: $15.00 USD


NOTE: Requires PDAT Pro!!! Work around for PDAT/Adv users is available...see included sample project for instructions on using a STUB/Launcher compiled with PDAT Pro to handle this library for your PDAT/Adv application!
This library is NOT...I repeat NOT compatible with PDAT/Adv. PDAT/Adv apps can add a STUB launcher application that was compiled with PDAT Pro and still add graphs! The STUB/Launcher gets ran from within your PDAT/Adv application using Call "crid", "type" and thats it!

This Update adds 1 new action (one for Line graphs using series!). Fixes rendered for maximizing chart area, and for previous inability to tap a bar graph with a zero value to retrieve its label. Now you can tap anywhere above a bar to get its label and value!

 

SPECIAL NOTES:

As of v1.6 you can now also include a PDAT field name (in brackets!) inside most of the string literal parameters such as the form title and HAxisLabel. ie: "Graph for [MNTH]". The PDAT field [MNTH] being a field NOT in the db passed for graphing but a field on the calling form!

This lib will quite likely be the LARGEST of the PDAT libs. When coupled with some simple premeditated data mining/preparation with the help of DBX lib, you can format a db, summarize your data in practically any way you want, then just send the DB to the LIB with the appropriate parameters to present it in a visually appealing manor for you users!

With this lib...I'll be pushing the memory limits in terms of the size of the lib. So if size becomes an issue, that may hamper some of my plans...but I'm very optimistic at this point! Also, this library was entirely written and compiled using HB++ which has never been done before, so we are charting not only PDAT db's, but NEW GROUND as well. Compatibility and memory requirements are all yet great unknowns. As such TRY IT BEFORE YOU BUY IT. Make sure the library functions correctly within your app.

Action Reference:

Chart.Basic dbName, DataField, DataLabel, Title, HAxisLabel, Bar|Line, 3D|Plain, Green|Blue|Red

This action takes the PDAT db passed to it (dbName) and plots the values in the PDAT field (DataField) stepping through the database from the first to the last record. Logically, this database and all databases passed to this library for graphing need to have few enough records in it so that it can be graphed and still be visually useful on the small PDA screen. Trial and error will determine what is best for you, but I typically find that keeping the number under 20 is most readable but ultimately depends on the graph type and device resolution. Trial and error.

As of v1.6 you can now also include a PDAT field name (in brackets!) inside most of the string literal parameters such as the form title and HAxisLabel. ie: "Graph for [MNTH]". The PDAT field [MNTH] being a field NOT in the db passed for graphing but a field on the calling form!

The additional parameters set form title, axis label and specify chart options. Details below

Code:
Chart.Basic dbName, DataField, DataLabel, Title, HAxisLabel, Bar|Line, 3D|Plain, Green|Blue|Red


Parameters explained:
dbName: String name of your Database...CAse senSItive toO! ie: "MyPDATdb-DATA"
DataField: Four Char PDAT field that contains the value to be graphed! ie: "FLD1"
DataLabel: Text that describes the Value "mg/dl" if blood sugar values are graphed for example.
Title: Text that will be used for the chart form's title.
HAxisLabel: Text that will serve as the Horizontal Axis label. No Label for vertical axis.
Bar|Line: Select one, either Bar or Line as the graph type!
3D|Plain: Show 3D Graph or 2D (plain), Only effects Bar Graphs. Again select either 3D or Plain.
Green|Blue|Red: Select ONE, this is the color of the graph!


An example is:
Code:
Chart.Basic "GackGraph-DATA", "VALU", "mg/dl", "Blood Sugar Trend", "BS in mg/dl", "Bar", "3D", "Green"

Back to Top


Chart.Basic.Field dbName, DataField, FieldAsLabel, Title, HAxisLabel, Bar|Line, 3D|Plain, Green|Blue|Red

This action takes the PDAT db passed to it (dbName) and plots the values in the PDAT field (DataField) stepping through the database from the first to the last record. Logically, this database and all databases passed to this library for graphing need to have few enough records in it so that it can be graphed and still be visually useful on the small PDA screen. Trial and error will determine what is best for you, but I typically find that keeping the number under 20 is most readable but ultimately depends on the graph type and device resolution. Trial and error.

As of v1.6 you can now also include a PDAT field name (in brackets!) inside most of the string literal parameters such as the form title and HAxisLabel. ie: "Graph for [MNTH]". The PDAT field [MNTH] being a field NOT in the db passed for graphing but a field on the calling form!

The additional parameters set form title, axis label and specify chart options. Details below

Code:
Chart.Basic.Field dbName, DataField, FieldAsLabel, Title, HAxisLabel, Bar|Line, 3D|Plain, Green|Blue|Red


Parameters explained:
dbName: String name of your Database...CAse senSItive toO! ie: "MyPDATdb-DATA"
DataField: Four Char PDAT field that contains the value to be graphed! ie: "FLD1"
FieldAsLabel: Four Char PDAT field that contains the text value to be display opposite the VALUE, as a label.
Title: Text that will be used for the chart form's title.
HAxisLabel: Text that will serve as the Horizontal Axis label. No Label for vertical axis.
Bar|Line: Select one, either Bar or Line as the graph type!
3D|Plain: Show 3D Graph or 2D (plain), Only effects Bar Graphs. Again select either 3D or Plain.
Green|Blue|Red: Select ONE, this is the color of the graph!


An example is:
Code:
Chart.Basic.Field"GackGraph-DATA", "VALU", "CLAS", "Blood Sugar Trend", "BS in mg/dl", "Bar", "3D", "Green"

Back to Top


Chart.Basic.Date dbName, DataField, DateAsLabel, Title, HAxisLabel, Bar|Line, 3D|Plain, Green|Blue|Red

This action takes the PDAT db passed to it (dbName) and plots the values in the PDAT field (DataField) stepping through the database from the first to the last record. Logically, this database and all databases passed to this library for graphing need to have few enough records in it so that it can be graphed and still be visually useful on the small PDA screen. Trial and error will determine what is best for you, but I typically find that keeping the number under 20 is most readable but ultimately depends on the graph type and device resolution. Trial and error.

As of v1.6 you can now also include a PDAT field name (in brackets!) inside most of the string literal parameters such as the form title and HAxisLabel. ie: "Graph for [MNTH]". The PDAT field [MNTH] being a field NOT in the db passed for graphing but a field on the calling form!

The additional parameters set form title, axis label and specify chart options. Details below

Code:
Chart.Basic.Date dbName, DataField, DateAsLabel, Title, HAxisLabel, Bar|Line, 3D|Plain, Green|Blue|Red


Parameters explained:
dbName: String name of your Database...CAse senSItive toO! ie: "MyPDATdb-DATA"
DataField: Four Char PDAT field that contains the value to be graphed! ie: "FLD1"
DateAsLabel: Four Char PDAT Date field name. This value will be graphed opposite the numeric value.
Title: Text that will be used for the chart form's title.
HAxisLabel: Text that will serve as the Horizontal Axis label. No Label for vertical axis.
Bar|Line: Select one, either Bar or Line as the graph type!
3D|Plain: Show 3D Graph or 2D (plain), Only effects Bar Graphs. Again select either 3D or Plain.
Green|Blue|Red: Select ONE, this is the color of the graph!


An example is:
Code:
Chart.Basic.Date "GackGraph-DATA", "VALU", "DATE", "Blood Sugar Trend", "BS in mg/dl", "Bar", "3D", "Green"

Back to Top

 


 

Chart.Basic.Range dbName, DataField, DataLabel, DataDate, sDate, eDate, Title, HAxisLabel, Bar|Line, 3D|Plain, Green|Blue|Red

This action takes the PDAT db passed to it (dbName) and plots the values in the PDAT field (DataField) stepping through the database from the first to the last record. To facilitate in reducing the number of records that are actually graphed, this action accepts 3 (three) PDAT date field names which are used to filter out records not within the specified date range. sDate and eDate are Date fields ON the calling form that will serve as Starting and Ending Date ranges.

This action is easily negated if you have the Database Extreme Library (DBX). This was mainly added to assist those without the DBX library to help them filter the main app database to reduce the number of records sent to be graphed.

As of v1.6 you can now also include a PDAT field name (in brackets!) inside most of the string literal parameters such as the form title and HAxisLabel. ie: "Graph for [MNTH]". The PDAT field [MNTH] being a field NOT in the db passed for graphing but a field on the calling form!

The additional parameters set form title, axis label and specify chart options. Details below

Code:
Chart.Basic.Range dbName, DataField, DataLabel, DataDate, sDate, eDate, Title, HAxisLabel, Bar|Line, 3D|Plain, Green|Blue|Red



Parameters explained:
dbName: String name of your Database...CAse senSItive toO! ie: "MyPDATdb-DATA"
DataField: Four Char PDAT field that contains the value to be graphed! ie: "FLD1"
DataLabel: Text that describes the Value "mg/dl" if blood sugar values are graphed for example.
DataDate: Four Char PDAT field: This is the name of the DATE field in the DATABASE being graphed, NOT on the form.
sDate: Four Char PDAT field: This is the name of the DATE field ON the form calling this action. Used as starting date value.
eDate: Four Char PDAT field: This is the name of the DATE field ON the form calling this action. Used as ending date value.
Title: Text that will be used for the chart form's title.
HAxisLabel: Text that will serve as the Horizontal Axis label. No Label for vertical axis.
Bar|Line: Select one, either Bar or Line as the graph type!
3D|Plain: Show 3D Graph or 2D (plain), Only effects Bar Graphs. Again select either 3D or Plain.
Green|Blue|Red: Select ONE, this is the color of the graph!


An example is:

Code:
Chart.Basic.Range "GackGraph-DATA", "VALU", "mg/dl","DATE", "sDTE", "eDTE", "Bloog Sugar Trends", "BS in mg/dl", "Bar", "Plain", "Blue"

Back to Top


Chart.Basic.Range.Field dbName, DataField, FieldAsLabel, DataDate, sDate, eDate, Title, HAxisLabel, Bar|Line, 3D|Plain, Green|Blue|Red

This action takes the PDAT db passed to it (dbName) and plots the values in the PDAT field (DataField) stepping through the database from the first to the last record. To facilitate in reducing the number of records that are actually graphed, this action accepts 3 (three) PDAT date field names which are used to filter out records not within the specified date range. sDate and eDate are Date fields ON the calling form that will serve as Starting and Ending Date ranges.

This action is easily negated if you have the Database Extreme Library (DBX). This was mainly added to assist those without the DBX library to help them filter the main app database to reduce the number of records sent to be graphed.

As of v1.6 you can now also include a PDAT field name (in brackets!) inside most of the string literal parameters such as the form title and HAxisLabel. ie: "Graph for [MNTH]". The PDAT field [MNTH] being a field NOT in the db passed for graphing but a field on the calling form!

The additional parameters set form title, axis label and specify chart options. Details below

Code:
Chart.Basic.Range.Field dbName, DataField, FieldAsLabel, DataDate, sDate, eDate, Title, HAxisLabel, Bar|Line, 3D|Plain, Green|Blue|Red



Parameters explained:
dbName: String name of your Database...CAse senSItive toO! ie: "MyPDATdb-DATA"
DataField: Four Char PDAT field that contains the value to be graphed! ie: "FLD1"
FieldAsLabel: Four Char PDAT field that contains the text value to be display opposite the VALUE, as a label, IN the Db being graphed, NOT on the calling form.
DataDate: Four Char PDAT field: This is the name of the DATE field in the DATABASE being graphed, NOT on the form.
sDate: Four Char PDAT field: This is the name of the DATE field ON the form calling this action. Used as starting date value.
eDate: Four Char PDAT field: This is the name of the DATE field ON the form calling this action. Used as ending date value.
Title: Text that will be used for the chart form's title.
HAxisLabel: Text that will serve as the Horizontal Axis label. No Label for vertical axis.
Bar|Line: Select one, either Bar or Line as the graph type!
3D|Plain: Show 3D Graph or 2D (plain), Only effects Bar Graphs. Again select either 3D or Plain.
Green|Blue|Red: Select ONE, this is the color of the graph!


An example is:

Code:
Chart.Basic.Range.Field dbName, DataField, FieldAsLabel, DataDate, sDate, eDate, Title, HAxisLabel, Bar|Line, 3D|Plain, Green|Blue|Red

Back to Top


 

Chart.Basic.Range.Date dbName, DataField, DateAsLabel, DataDate, sDate, eDate, Title, HAxisLabel, Bar|Line, 3D|Plain, Green|Blue|Red

This action takes the PDAT db passed to it (dbName) and plots the values in the PDAT field (DataField) stepping through the database from the first to the last record. To facilitate in reducing the number of records that are actually graphed, this action accepts 3 (three) PDAT date field names which are used to filter out records not within the specified date range. sDate and eDate are Date fields ON the calling form that will serve as Starting and Ending Date ranges.

This action is easily negated if you have the Database Extreme Library (DBX). This was mainly added to assist those without the DBX library to help them filter the main app database to reduce the number of records sent to be graphed.

As of v1.6 you can now also include a PDAT field name (in brackets!) inside most of the string literal parameters such as the form title and HAxisLabel. ie: "Graph for [MNTH]". The PDAT field [MNTH] being a field NOT in the db passed for graphing but a field on the calling form!

The additional parameters set form title, axis label and specify chart options. Details below

Code:
Chart.Basic.Range.Date dbName, DataField, DateAsLabel, DataDate, sDate, eDate, Title, HAxisLabel, Bar|Line, 3D|Plain, Green|Blue|Red



Parameters explained:
dbName: String name of your Database...CAse senSItive toO! ie: "MyPDATdb-DATA"
DataField: Four Char PDAT field that contains the value to be graphed! ie: "FLD1"
DateAsLabel: Four Char PDAT DATE field that contains the text value to be display opposite the VALUE, as a label, IN the Db being graphed, NOT on the calling form.
DataDate: Four Char PDAT field: This is the name of the DATE field in the DATABASE being graphed, NOT on the form.
sDate: Four Char PDAT field: This is the name of the DATE field ON the form calling this action. Used as starting date value.
eDate: Four Char PDAT field: This is the name of the DATE field ON the form calling this action. Used as ending date value.
Title: Text that will be used for the chart form's title.
HAxisLabel: Text that will serve as the Horizontal Axis label. No Label for vertical axis.
Bar|Line: Select one, either Bar or Line as the graph type!
3D|Plain: Show 3D Graph or 2D (plain), Only effects Bar Graphs. Again select either 3D or Plain.
Green|Blue|Red: Select ONE, this is the color of the graph!


An example is:

Code:
Chart.Basic.Range.Date dbName, DataField, DateAsLabel, DataDate, sDate, eDate, Title, HAxisLabel, Bar|Line, 3D|Plain, Green|Blue|Red

Back to Top


Chart.Filter dbName, DataField, DataLabel, DataDate, DataFilter, FilterDBName, FilterField, Title, HAxisLabel, Bar|Line, 3D|Plain, Green|Blue|Red
Chart.Filter.Field dbName, DataField, FieldAsLabel, DataDate, DataFilter, FilterDBName, FilterField, Title, HAxisLabel, Bar|Line, 3D|Plain, Green|Blue|Red
Chart.Filter.Date dbName, DataField, DateAsLabel, DataDate, DataFilter, FilterDBName, FilterField, Title, HAxisLabel, Bar|Line, 3D|Plain, Green|Blue|Red

These 3 (three) actions all are identacle only differing by the value expected for the 3rd (Third) parameter. This third parameter (DataLabel vs FieldAsLabel vs DateAsLabel) determines what is displayed opposite the VALUE (DataField) when the graph is tapped by the user. As with the previous actions, DataLabel is a string literal, while FieldAsLabel and DateAsLabel require a 4 (four) character PDAT field name of a field IN THE DB being graphed, that will be used to describe or Label the data value.

Additionally...These 3 (three) actions require the string name of a PDAT db that contains values used to filter the records in the main db being graphed (dbName). An example would be the "GackGraph-CLAS" in the example application that accompanies the Library download and documentation. This DB is used in the application typically as a Dynamic Popup source for the purposes of "Classifying" or "Categorizing" the record. An example again would be the popup for "Time of Day" in the example app. This popup has three options "Morning, Afternoon and Evenning" and the selection indicates the "Time of Day" or categorie for this particular record. This popup is a dynamic popup which uses the DB "GackGraph-CLAS". Passing the name of this DB(FilterDBName) and the field name(FilterField) in this DB that the Popup uses, allows these actions to even further filter the DB being graphed. The library loads a popup(on the libraries form) with these and allows the user to DYNAMICALLY create a graph of their OWN specification by selecting the CLASS from this popup, the starting and ending date ranges (also on the libraries form)...then tapping a GRAPH button on the libraries form to prepare the graph based upon their selections! Very FLEXIBLE alternative. Additionally...the user, after creating the first graph, change the criteria (select another class from the popup or change the date ranges) and AGAIN tap the graph button to prepare a second chart. This second chart will be graphed along side the previous chart as as separate series! This allows for side by side comparison of the two graphs! To see this in action, install and try the DEMO application. In total 5 (five) series can be produced and graphed at which point the graph area will need to be cleared to produce any further graphs. ALL OF THIS IS DONE from ONE LIBRARY CALL! ONE SINGLE ACTION!

As of v1.6 you can now also include a PDAT field name (in brackets!) inside most of the string literal parameters such as the form title and HAxisLabel. ie: "Graph for [MNTH]". The PDAT field [MNTH] being a field NOT in the db passed for graphing but a field on the calling form!

The additional parameters set form title, axis label and specify chart options. Details below

Code:
Chart.Filter.Date dbName, DataField, DateAsLabel, DataDate, DataFilter, FilterDBName, FilterField, Title, HAxisLabel, Bar|Line, 3D|Plain, Green|Blue|Red



Parameters explained:
dbName: String name of your Database...CAse senSItive toO! ie: "MyPDATdb-DATA"
DataField: Four Char PDAT field that contains the value to be graphed! ie: "FLD1"
<Label:> DataLabel, FieldAsLabel or DateAsLabel. Depends on which of the 3 actions is used. Identicle in use to the other actions in this library. This is the LABEL opposite the value charted, and shown when tapped.
DataDate: Four Char PDAT field: This is the name of the DATE field in the DATABASE being graphed, NOT on the form.
DataFilter: Four Char PDAT field: This is the name of the field IN the db being graphed that will be used to filter against with the selected value from FILTERDNAME's FILTERFIELD. Remember...the libary uses the FILTERDBNAME db to populate a popup with the values from FILTERFIELD in that db. The value selected here is compared to DATAFILTER in the db being graphed for a Match and include for graphing if they match!
FilterDBName: This is the string name of the db used to populate the Popup in the library form. It uses the value of the PDAT field provided as the FILTERFIELD parameter.
FilterField: Four Char PDAT field: This is the name of the field in the
Title: Text that will be used for the chart form's title.
HAxisLabel: Text that will serve as the Horizontal Axis label. No Label for vertical axis.
Bar|Line: Select one, either Bar or Line as the graph type!
3D|Plain: Show 3D Graph or 2D (plain), Only effects Bar Graphs. Again select either 3D or Plain.
Green|Blue|Red: Select ONE, this is the color of the graph!


An example is:

Code:
Chart.Filter.Date "GackGraph-DATA", "VALU", "DATE", "DATE", "CLAS", "GackGraph-CLAS", "NAME", "Blood Sugar Trends", "BS in mg/dl", "Bar", "3D", "Red"

Back to Top


Chart.Pie dbName, DataField, FieldAsLabel, Title, BottomLabel

This action takes the PDAT db passed to it (dbName) and plots the values in the PDAT field (DataField) stepping through the database from the first to the last record. Each record's field (DataField) is graphed as a "peice of the pie" The Field (FieldAsLabel) is used as the label to describe that particular wedge of the pie graph. The parameter (Title) is text that will be used as the title on the graph form. The final parameter is a label for the bottom of the graph.

As of v1.6 you can now also include a PDAT field name (in brackets!) inside most of the string literal parameters such as the form title and HAxisLabel. ie: "Graph for [MNTH]". The PDAT field [MNTH] being a field NOT in the db passed for graphing but a field on the calling form!

Code:
Chart.Pie dbName, DataField, FieldAsLabel, Title, BottomLabel



Parameters explained:
dbName: String name of your Database...CAse senSItive toO! ie: "MyPDATdb-DATA"
DataField: Four Char PDAT field that contains the value to be graphed! ie: "FLD1"
FieldAsLabel: Four Char PDAT field that contains a TEXT value to be displayed opposite the pie charts value when the wedge is tapped and held by the user..
Title: Text that will be used for the chart form's title.
BottomLabel: Text that will serve as a label for the bottom of the graph area. You may use "" (Empty double quotes) if you do not require a bottom label.


An example is:

Code:
Chart.Pie "DB-Trans-Dets-DB", AMNT, STOR, "My Pie Chart", "Bottom Label!"

Back to Top


Chart.Filter.Popup dbName, DataField, DataLabel, DataFilter, FilterDBName, FilterField, Title, HAxisLabel, Bar|Line, 3D|Plain, Green|Blue|Red

Chart.Filter.Popup.Date dbName, DataField, DateAsLabel, DataFilter, FilterDBName, FilterField, Title, HAxisLabel, Bar|Line, 3D|Plain, Green|Blue|Red

Chart.Filter.Popup.Field dbName, DataField, FieldAsLabel, DataFilter, FilterDBName, FilterField, Title, HAxisLabel, Bar|Line, 3D|Plain, Green|Blue|Red

This action is very similar to those in the Chart.Filter.Range family of actions. The only difference is the absence of the date fields to further filter you primary database. These three actions use the second database (FilterDBName) to populate a popup on the chart form. Records from the db (DbName) with the same value in its field (dataFilter) will be graphed only.

As of v1.6 you can now also include a PDAT field name (in brackets!) inside most of the string literal parameters such as the form title and HAxisLabel. ie: "Graph for [MNTH]". The PDAT field [MNTH] being a field NOT in the db passed for graphing but a field on the calling form!

The additional parameters set form title, axis label and specify chart options. Details below

Code:
Chart.Filter.Popup dbName, DataField, DataLabel, DataFilter, FilterDBName, FilterField, Title, HAxisLabel, Bar|Line, 3D|Plain, Green|Blue|Red


Parameters explained:
dbName: String name of your Database...CAse senSItive toO! ie: "MyPDATdb-DATA"
DataField: Four Char PDAT field that contains the value to be graphed! ie: "FLD1"
<Label:> DataLabel, FieldAsLabel or DateAsLabel. Depends on which of the 3 actions is used. Identicle in use to the other actions in this library. This is the LABEL opposite the value charted, and shown when tapped.
DataFilter: Four Char PDAT field: This is the name of the field IN the db being graphed that will be used to filter against with the selected value from FILTERDNAME's FILTERFIELD. Remember...the libary uses the FILTERDBNAME db to populate a popup with the values from FILTERFIELD in that db. The value selected here is compared to DATAFILTER in the db being graphed for a Match and include for graphing if they match!
FilterDBName: This is the string name of the db used to populate the Popup in the library form. It uses the value of the PDAT field provided as the FILTERFIELD parameter.
FilterField: Four Char PDAT field: This is the name of the field in the
Title: Text that will be used for the chart form's title.
HAxisLabel: Text that will serve as the Horizontal Axis label. No Label for vertical axis.
Bar|Line: Select one, either Bar or Line as the graph type!
3D|Plain: Show 3D Graph or 2D (plain), Only effects Bar Graphs. Again select either 3D or Plain.
Green|Blue|Red: Select ONE, this is the color of the graph!




An example is:
Code:
	Chart.Filter.Popup "GackGraph-DATA", VALU, "Blood Sugar", CLAS, "GackGraph-CLAS", NAME, "Popup with text", "Text example", "Bar", "Plain", "Green"

Back to Top


Chart.Line.Series dbName, [FLD1]<FLD1 Label>..., Title, HAxisLabel

This action takes the PDAT db passed to it (dbName) and plots the values in this database in a SERIES fashion. To illustrate. Lets say your app records blood sugars three times a day. Morning, Afternoon and Evenning. Each record in this DB then containing a value for each of these three reading...you would then provide (as the second parameter) a pairing of this PDAT field name (in brackets) followed by the string value to be used as a label (in < >). Each pair of [ ] and < > then constitutes a series. You can have up to TEN such pairings or SERIES! The screenshot below shows THREE series only. The parameter (Title) is text that will be used as the title on the graph form. The final parameter is a label for the bottom of the graph.

As of v1.6 you can now also include a PDAT field name (in brackets!) inside most of the string literal parameters such as the form title and HAxisLabel. ie: "Graph for [MNTH]". The PDAT field [MNTH] being a field NOT in the db passed for graphing but a field on the calling form!

Code:
Chart.Line.Series dbName, [FLD1]<FLD1 Label>..., Title, HAxisLabel



Parameters explained:
dbName: String name of your Database...CAse senSItive toO! ie: "MyPDATdb-DATA"
[FLD1]<FLD1 Label>...: Four Char PDAT field that contains the value to be graphed! ie: [FLD1], followed immediately by the string literal to use as a label in < >'s ie: <Morning>
Title: Text that will be used for the chart form's title.
BottomLabel: Text that will serve as a label for the bottom of the graph area. You may use "" (Empty double quotes) if you do not require a bottom label.


An example is:

Code:
Chart.Line.Series "GackGraph-DATA", "[VALU],<Morning>,[VAL2],<Afternoon>,[VAL3],<Evenning>", "My [MNTH] Series", "[MNTH] Sugars!"

Back to Top


 

 

 

 

 

Installing the Library Files

 

1.) Extract the PDATChartLib.dll file from the archive and copy to your PDAToolbox Installation folder. Typically something like: C:\Program Files\PDAToolBox

2.) In PDAToolbox launch the Script Editor (SE) and click the Tools Icon to access the SE's compiler options. Select the "Libraries" tab, then click "Add". Use the file selection dialog to navigate to your PDAToolbox installation folder and select the "PDATChartLib.dll" file you just extracted here in Step #1. If you have a registration code, you may enter it into the info/license dialog box at this time as well. If your trialing this library, then leave these fields blank. Your done!

*To register at a later date, return to the SE's compiler options dialog box, click the "Info/Lic" button and enter your registration information and click the OK button.

Back to TOP

 


Screen Shots

 

 

 

 

 

 

This screenshot shows an example of Chart.Simple that obviously uses the Bar chart style. Tapping and holding on the graph displays the label and value. Here we also have an example of Chart.Simple but with a different color. Note: Minimum and Maximum values are automatically calculated.
   
This example demonstrates the same database being graphed using a Line graph style. As with Bar chart style, you tap and hold a data point to see its label and value. You may also specify any one of the predefined colors for your graph as well.
This example illustrates using Chart.Basic.Date(v1.1). Here we use a PDAT date field in the record with each value and this date is displayed with the value for that record. This also shows the "Plain" bar type graph as well.
   
These images show the newly added support for devices, such as the Palm T3 that have collapsable DIA (Dynamic Input Area) to allow for larger, easier to read graphs! Obviously the perspective selected here is HORIZONTAL interpretation so the graphs are interpret in a left to right manner. VERTICLE orientation is also now added as shown below but in Landscape mode.

 

 

 
This image illustrates the new action Chart.Line.Series. It can accomodate up to TEN series on one graph! The above example shows just THREE.
Back to Top  

 


History

v1.6 01/04/2005- One new action: Chart.Line.Series for line graphs using series of lines! Fix applied to maximize chart space, and fix for Bar Graphs with a zero value...previously unable to tap them to get the label...now tap anywhere above a bar graph to get its label and value as well.
v1.5 12/26/2004- Four new actions added! 3 New actions added to the Filter Family of actions, differing from the previous actions in that these three do not filter on a date field, only the value of a popup! Also added was and action for creating Pie charts! Please note, there is a "bug" with the pie "filling" that may result in some sections of a "wedge" of the pie, not being completely colored in. Also addressed in this release is a fix for the Hi-Res line graphs. Formerly, these where not scaled and resulted in very tiny dots, ofter very hard to tap...they now scale UP. ALSO...added the ability for the Filter Family of actions that filter on the Chart's two date fields to "remember" the date last entered.
v1.4: 12/16/2004- Bug fix only. It is hoped that this release brings with it the death of the stub launcher (accept for PDAT/Adv apps). You should now be able to use this library as normal within your PDAT Pro application scripting calls to it withing the Script Editor like any other library.
v1.3: 12/15/2004- Updated to add Horizontal and Vertical orientation of graphs for ALL 9 actions. Also added DIA support!
v1.2: 12/14/2004- Updated to include 6 new actions...NINE in all!
v1.1: 12/12/2004- Updated with two new action to expand upon data labeling options!
v1.0: 12/11/2004- Initial Release. One Action that performs 3 Different Graphs!

Back to Top

 


Legal Stuff

Warranty and User License Agreement

"The Software" is "PDATChartLib" by Brian Gackenbach dba Gack-Apps.

DISCLAIMER #1 - MUST READ

This product is an "After-Market" utility for PDA Toolbox(tm) and as such, is subject to obsolescence by changes in PDA Toolbox or the Palm OS(tm) itself.  This cannot be prevented.  I may choose to stop or limit development and support of this product if such situation occurs. 

USER LICENSE AGREEMENT

This Agreement sets forth your licensed rights to use "The Software" and is granted to you upon condition that you accept the terms of this license. Your electronic indication of agreement, or your use of the program constitute acceptance of all of the terms of this license.

The program copy and documentation are furnished to make "The Software" available for your use and remain the property of Gack-Apps.

IF YOU DO NOT AGREE WITH ANY PART OF THIS LICENSE, DO NOT USE THIS SOFTWARE. Delete "The Software" and all associated files from all media on which it has been copied. 

LICENSE TERMS AND CONDITIONS

THE LICENSED PRODUCT
"The Software" comprises copyrighted computer programs and utilities for the Graphing of Palm OS(tm) application databases (PRC) created by the PDA Toolbox(tm) Application Generator. The Licensed Product in its entirety is protected by US and foreign copyright.  YOU MAY NOT DISTRIBUTE THE LICENSE CODE provided to you.

YOUR USE OF THE LICENSED PRODUCT
General Use. You have the right to use "The Software" with PDAToolBox(tm) Professional Versional and to distribute the library file itself "PDATChartLib.prc". For those purposes, you have the right to install the "The Software" and any associated files on one (1) computer. Use of "The Software" on a network or any other arrangement by which its functions are accessible to more than one user at a time is not permitted. 

LIMITATIONS ON USE
General Use Limitations. You have no right to reproduce, transfer, publish or otherwise distribute either the "The Software" software, or any components or documentation provided.

ALL RIGHTS NOT SPECIFICALLY GRANTED BY THIS LICENSE ARE RESERVED BY GACK-APPS. 

WARRANTIES, WARNING, DISCLAIMER

Warning and Disclaimer of All Warranties. THE PROGRAM IS FURNISHED "AS IS" WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, IN ALL JURISDICTIONS WHERE ALL WARRANTIES MAY BE DISCLAIMED IN THE LICENSING OF INTELLECTUAL PROPERTY.


Copyrights and Trademarks

PDAT/Advanced is copyrighted by Richard R. Sands dba Sands USA.

PDA Toolbox (PDAT) is copyrighted by Paul Prejean.

Quartus RsrcEdit is apparently not copyrighted, but is maintained by Quartus at www.Quartus.net.

Windows is a trademark of Microsoft Corporation.

And ever present...

Palm OS, Palm Computing, HandFAX, HandSTAMP, HandWEB, Graffiti, HotSync, iMessager, MultiMail, Palm.Net, PalmPak, PalmConnect, PalmGlove, PalmModem, PalmPoint, PalmPrint, and PalmSource are registered trademarks of Palm, Inc.  Palm, the Palm logo, MyPalm, PalmGear, PalmPix, PalmPower, AnyDay, EventClub, HandMAIL, the HotSync logo, PalmGlove, Palm Powered, the Palm trade dress, Smartcode, Simply Palm, WeSync, and Wireless Refresh are trademarks of Palm, Inc.

Back to Top