Copyright 2010 by gINT Software. All rights reserved worldwide.
gINT Update README.TXT file
gINT 8 README.TXT
NOTES:
1. Some of the documentation below is in tabular form and requires that you view this document in a fixed font, e.g., Courier New. If in Windows Write, place the cursor at the beginning of the document, hold down the Ctrl and Shift keys and then press the End key. This will highlight the entire document. Or use the Edit menu, Select All. Then use the Character:Font menu item to select a fixed font (e.g., Courier).
2. Items marked "(Requires 8.2 licensing)" indicates that the feature will not function unless you have been licensed for 8.2. To check, select Help:About gINT anywhere in the program. If the version is 8.2.xxx then you are licensed. If it read 8.1.2.xxx then you are not and a VIP maintenance renewal is required to obtain this licensing. Please contact the gINT sales department (sales@gintsoftware.com) for renewal details.
====================
8.2.007 08Mar2010
====================
1. We have changed our Internet meeting software from WebEx to Live Meeting. This has lead to the removal of the "gINT Software Internet Meeting Site" command under the Help:Internet Links menu. Live Meeting uses a different method.
2. The graph report properties "Round Min down to nearest" and "Round Max up to nearest" (independent and dependent axes) are ignored if the min/max axis values are explicitly set.
3. Under certain conditions, repeating text on graph reports are limited in the number of repetitions they make to the number of data sets on a page. This is very useful for making legends identifying each data set. However, there are times when you want to use repeating text on a graph report that have nothing to do with legends and you do not wish to be limited by the number of data sets on the page. Under these conditions, mark the "Do not limit repetitions to number of data sets" check box property under the "Repeat" tab of the text entity properties dialog.
====================
8.2.006 31Jan2010
====================
1. Maintenance release
====================
8.2.005 20Jan2010
====================
1. (Requires 8.2 licensing)
In the graph report properties dialog under the "Override Line/DM Expressions" tab, the "Number of decimal places on overflow values" properties (1 through 6) specify the number of decimal places that are shown for overflow data if the "Print Value" option is selected for the "Overflow Option" ("Data Representation" tab) property.
2. (Available to all version 8 licenses)
The export file format for the EVS PGF export was changed so that it could be read directly by the EVS software.
3. (Available to all version 8 licenses)
Input:Surfaces application, TIN surfaces:
A. The TIN display now uses the surface line color specified in the surface properties dialog.
B. Checking the "Do not display" check box on the main surface screen will hide the TIN display.
4. (Available to all version 8 licenses)
In a True Rectangle entity, if there is an expression that returns a numeric value in either the override height or width expression properties, if that value is less than or equal to 0, the entity will not output. Previously, the entity output with the design-time height or width values when this occurred. The design-time height and width are now only used if the override expression properties are blank or return a non-numeric value.
5. (Requires 8.2 licensing)
The Frame Offset X and Frame Offset Y properties of fence reports (Data Frame tab) all literal values or expressions to offset the fence frame and associated entities (body entities and header/footer entities with the Placed on Fence Posts property marked) to a location on the final output different than the design-time location. This is useful in conjunction with export of multiple reports to a gINT Drawing file. If expressions are used for these properties they must be on a project or report variable level.
6. (Available to all version 8 licenses)
The cone penetrometer method for liquid limit determination allows for the one point method as per BSI 1377. This requires that the penetration be between 15 and 25 millimeters, inclusive. If there are two liquid limit determinations, two one point calculations are run and the average is used as the liquid limit. With three or more liquid limit determinations the liquid limit is determined as the moisture content at a penetration of 20 millimeters as taken from a best fit straight line through the liquid limit results.
7. (Available to all version 8 licenses)
In Graph report properties, Data Representation tab, best fit line section, the "Minimum number of data points" property sets the minimum number of data points that are required for a best fit line to be calculated. If blank, a best fit line will be calculated with 2 or more data points.
8. (Available to all version 8 licenses)
Entities in the Symbol Design:Fixed Curves on Graphs application have Print Order properties (Configuration tab). By default, these entities are at print order 0. Each entity can be at a different print order. This is quite useful, actually crucial, if you have solid fills on closed polylines in the fixed curve definition.
On graphs, the grid lines are at a print order of -1, lines and data markers at a print order of +2, and posted values at a print order of 0. If you wanted the fixed curve entities to appear under the grid lines, set the fixed curve entities to a print order less than -1.
9. In Graphic Input Mode, the "Number of Additional Pages Expression" property of the log report is not supported. They will not be shown in this mode whether there are data on them or not.
10. The SQLWhereValueDate and SQLWhereValueText functions return the properly delimited date value/text string for use in an SQL Where clause.
Where [TABLE].[Field] = <<SQLWhereValueDate(<<ABC.Xyz>>)>>.
Accounts for the database type. For example:
Where [TABLE].[Date Type Field] = #8/6/2009# (or #<<TABLE.Some field containing a date>>#)
works in ACCESS but the following is required in SQLServer:
Where [TABLE].[Date Type Field] = '8/6/2009'
The way to write the above is:
Where [TABLE].[Date Type Field] = <<SQLWhereValueDate(8/6/2009)>>
As gINT supports more back-end databases, these procedures will be adjusted to account for their different requirements.
The SQLWhereValueText also accounts for inclusion of the delimiter character in the text value. For example, if the text value is A-A', the function would return 'A-A'''. This is the proper syntax for the SQL expression.
11. (Available to all version 8 licenses)
By default PointID Text in the Site Map application and the Site Layout views in all Output applications are set to print opaque, that is, entities under the text extent rectangle are covered by the text. The "PointID Text Print Opaque" command allows turning this property on and off. It is found in the Site Map application under the Site Map:PointID Display menu and in the Site Layout views under the Settings menu. This setting is stored in your local setup.gsh file and only affects your copy of gINT.
Note that this property only affects the Site Layout views and the preview screen in the Site Map application. It is not used in the design view in the Site Map application.
12. (Requires version 8.2 licensing)
To avoid working with negative numbers, some coordinate conversion programs generate south latitudes and west longitudes as positive values. If the gINT Google Earth facility is used with such coordinates, the placement of the points will be in the wrong hemisphere. If your coordinates specify west or south as positive, bring up the Additional Modules:Google Earth:Google Earth Setup dialog in Input and mark the "South latitude is positive" or "West longitude is positive" check boxes as appropriate.
13. (Works with all gINT versions that support multiple pages per sheet in graphic text documents)
You have a graphic text document with multiple pages per sheet and you wish to print the page numbering in the header or footer. You have a text entity with the following expression:
Page <<Pg>> of <<NPgs>>
This will not work properly. Let's say you have 4 pages per sheet and 7 pages of output. You will generate two physical sheets of paper but the above will print 4 times on the first sheet and 3 times on the second and the number of pages would be 7, not 2.
To obtain the result you want in this case ("Page 1 of 2" on the first sheet and "Page 2 of 2" on the second), in the text entity that prints the numbering, set the following properties:
A. Main Tab - Text Expression:
Page <<Calc(1 + ((<<Pg>> - 1) \ 4))>> _
of _
<<Calc(1 + ((<<NPgs>> - 1) \ 4))>>
B. Configuration Tab - Output Condition:
(<<Pg>> Mod 4) = 1
Change the "4" to whatever number of pages per sheet are specified in your report.
14. In Input, the Tools:Consolidate Project Structure command will leave the Site Map and Surfaces tabs whether they have data or not. Remove them via the Additional Modules menu if you wish.
15. The Export to Google Earth dialog allows selection of PointIDs to be exported. If blank, all PointIDs in the current project that have the required coordinates will be exported.
16. The Output Override X property of column entities must be relative, that is, the amount specified must an offset from the design position. This is done by starting the literal value or expression with the "@" character. If the expression is a User System Data item, the expression in the USD must begin with the "@" character.
17. (Available to all version 8 licenses)
GEO5 Version 10 now supports multiple borehole import into the Terrain module. That is the same file as exported in Input under the File:GEO5:Export GEO5 Profile and Soil Data menu item. However, to do so you will need to add a LOCATIONS section to that file export. This section contains the name, east, north, and elevation for each borehole. To generate this section you must modify your GEO5 profile and soil data target file to the following structure:
**SOILS
NAME,HATCHNAME,HATCHCOLOR,BASIC_GAMA,BASIC_EFF_PHI,BASIC_EFF_C,NY,OCR,EOED,EDEF
**LOCATIONS
BOREHOLE,X,Y,Z
**PROFILE
BOREHOLE,TOPDEPTH,BOTTOMDEPTH,SOIL
Then open your existing export correspondence file that uses this target file and click the Refresh [All] button. Map the new LOCATIONS group to the table with your coordinates (usual POINT) and then map the 4 fields. An example correspondence file:
SOILS,GEO5 SOILS
NAME,<<GEO5 SOILS.ItemKey>>
HATCHNAME,<<GEO5 SOILS.Hatch Name>>
HATCHCOLOR,<<GEO5 SOILS.Hatch Color>>
BASIC_GAMA,<<GEO5 SOILS.Unit Weight>>
BASIC_EFF_PHI,<<GEO5 SOILS.Effective Friction Angle>>
BASIC_EFF_C,<<GEO5 SOILS.Effective Cohesion>>
NY,<<GEO5 SOILS.Poissons Ratio>>
OCR,<<GEO5 SOILS.Over Consolidation Ratio>>
EOED,<<GEO5 SOILS.Oedometric Modulus>>
EDEF,<<GEO5 SOILS.Deformation Modulus>>
LOCATIONS,POINT
BOREHOLE,<<POINT.PointID>>
X,<<POINT.East>>
Y,<<POINT.North>>
Z,<<POINT.Elevation>>
PROFILE,LITHOLOGY
BOREHOLE,<<LITHOLOGY.PointID>>
TOPDEPTH,<<LITHOLOGY.Depth>>
BOTTOMDEPTH,<<LITHOLOGY.Bottom>>
SOIL,<<LITHOLOGY.GEO5 Soil>>
The LOCATIONS section is only used by the Terrain module and is ignored in other modules. Note that if you have a LOCATIONS section in your export file and try to import into an earlier version of a GEO5 module, you will get an error.
18. (Available to all version 8 licenses)
LatLongConv function: When passing in a decimal degrees value it will return a degree minutes seconds format. The degrees and minutes are always integers. The seconds are decimal numbers and can be formatted using an optional seconds formatting argument (fourth argument). If not provided, the program rounds the seconds to the nearest 0.0001 second. For example:
<<LatLongConv(<<TABLE.Field>>,,,"0.00")>>
would return seconds to two decimal places.
19. (Available to all version 8 licenses)
One additional difference between the "Format" function you may be used to in VBA and VB compilers and gINT is that formatting "123" with the format string "0.#" would return "123." in VB and VBA but "123" in gINT.
20. (Available to all version 8 licenses)
The "Cancel" button in the records selection dialog of the Utilities:Lib Merge/Copy application has been replaced with two buttons: "Cancel Current" and "Cancel Merge". The latter has the same behavior as the previous "Cancel" button in that it cancels the current table and skips any remaining tables, the former cancels the current table merge but continues the process.
====================
8.2.004 17May2009
====================
1. (Requires 8.2 licensing)
The "Show in Children" check box property of project fields will show the marked field or fields in all one-to-one children of current table. The data from the marked fields is not replicated in the child tables, only shown. These would be "virtual" fields in the child tables. More than one field in a table can have the property marked.
The virtual fields are placed to the right of the key fields in the grid in the order that they appear in the parent table with the same column widths as in the parent table. The caption will be surrounded in curly brackets, e.g., {Lab Sample Number}, to indicate that they are virtual fields.
The following field types do not have this property:
Keys
Memos
Bitmap, Drawing, and Any File
GintPointSort
GintUpdated
Further, no fields in Project-level tables will have this property.
Examples of possible usage:
A. You are using the gINT standard component description tables where there is a one-to-one child table of the parent material description table for soil and rock components. The parent table contains the bottom depth and graphic. It would be useful to see the values of these two fields in the child tables.
B. You are using the gINT standard lab tables and you have a field for lab sample number in the LAB SPECIMEN table. Setting this property in that field will show it in all the top-level child tables. This is very useful for lab technicans where, in many cases, they log their test samples by the lab number, not the borehole and depth.
2. If there are any field rules specified for any fields in a table, the gINT Rules:Recalculate Current Table command can be run. Previously this command was only available in tables where gINT Rules were run on save events.
3. Previously on importing with a correspondence file, the import log would show a warning list for all source fields referenced in the correspondence file that did not exist in the source file. Experience and comments from users showed that this class of warning was more confusing than helpful and we have discontinued its use.
We have also suppressed the "overwrite not allowed" message in the import log file when importing into an ItemKey table where the "Keep data in clone" property is marked. This mainly applies to the AGS DICT table.
4. On importing data into fields that have required lookups, if imported data are not in the lookup list, the data are import but messages are written to the import log file. For example:
Data not found in required lookup lists for table 'PROJECT':
Field 'PROJ_CONT', Value 'AAAAA Site Investigations'
Field 'PROJ_ENG', Value 'ZBest Consulting'
Data not found in required lookup lists for table 'POINT':
Field 'HOLE_CKBY', Value 'D.E.F.'
Field 'HOLE_CREW', Value 'I. Core'
Field 'HOLE_EXC', Value 'ACME Z-99'
Field 'HOLE_EXC', Value 'Backhoe'
Field 'HOLE_EXC', Value 'Cable Percussion & Rotary Coring'
Field 'HOLE_EXC', Value 'CME 56'
Field 'HOLE_FLMD', Value 'WATER'
Field 'HOLE_LOG', Value 'A. Bore'
Data not found in required lookup lists for table 'GEOL':
Field 'GEOL_GEOL', Value 'G'
Field 'GEOL_GEOL', Value 'GR'
Field 'GEOL_GEOL', Value 'LC'
5. In import of alignments from LandXML files, if there are elevation values associated with the alignment, they will be imported into the Z1 field in the child grid.
6. In a split screen tab configuration in Input, the child grid can be sized vertically and the top of the child grid will be stored with the project so that it will be in the same position when returning to that tab between gINT sessions. The value stored is a percentage of the available height so that the relative position will be the same regardless of monitor resolution.
====================
8.2.003 23Feb2009
====================
1. Data Design
A. (Requires 8.2 licensing)
On adding the Point Sort field (under the Table menu) in the POINT table (Input or Data Design:Project Database) a message box will appear that asks if you want to use the built-in gINT sorting method. If this is selected, the field will be read-only and gINT will automatically assign sort values. The algorithm used is the same as that used in the sample gINT Rule GR016 (http://www.gintsoftware.com/support_gintrules.html).
Once the gINT sorting method is used for this field, you can stop it for being used and implement your own method by removing and readding the field or just bring up field properties and uncheck the "gINT Method" property.
B. Added "PointID,ItemKey,ItemKey2,DateTime" key set.
C. (Requires 8.2 licensing)
You can assign a file note (up to 255 characters) library, data template, or project files. This value is inherited when a project is created from a data template or another project. There are two ways to set this value and three ways to read the value.
To set the value manually, choose Help:User File Versioning, this results in a dialog that will show the user file version for the library and if appropriate (app specific) either the data template or current project. If the user has write access to the library, project, or data template the value can be changed here as well.
To set the value using gINT Rules, use the UserFileVersion property of the GintConfig object. Using this property with a supplied filename (full path) the value can be read or written (again if the user running the gINT rule has write access to the file specified) e.g.:
gINTRules.GintConfig.UserFileVersion(gINTRules.GintConfig.LibraryFile) = "TEST"
If gINTRules.GintConfig.UserFileVersion(gINTRules.GintConfig.LibraryFile) <> "This is a test" Then
gINTRules.GintConfig.UserFileVersion(gINTRules.GintConfig.LibraryFile) = "This is a test"
End If
To put the value on a report use the GetUserFileVersion function with a supplied filename (full path). e.g.:
Library Version: <<GetUserFileVersion(<<LibFileSpec>>)>>
Project Version: <<GetUserFileVersion(<<ProjFileSpec>>)>>
Report Data Template Version: <<GetUserFileVersion(<<DataTemplate>>)>>
D. In the table properties dialog for an ItemKey key set table in a project database, the "Number of Fields shown in drop down" specifies the number of fields in the table that will be shown when the table is used as a lookup list.
E. On adding Alignment support in Input, the order of the coordinate fields in the child grid was North and then East. Although this is typically how many organizations order coordinates, it is opposite of polyline and baseline coordinate dialogs where many people were copying coordinates. This lead to improper coordinates. Therefore, we have reversed the default order when adding Alignment support to East and then North. This change does not affect existing projects and you can always change the order like with any other non-key field in gINT by clicking and dragging the column header of whatever field you wish.
F. In Input, in the grid context menu "Add Field" has been added where appropriate. For library tables "Add Field" is disabled if the library is read-only.
G. The "Reference to Current Field" command has been removed from the Table menu Input and Data Design. It can still be found under Tables:References and in the grid context menu in both applications.
2. Licensing
A. License Information, License Level and gINT Network Users have been relocated under the Help:Licensing menu. This change was made to reduce the number of menus under Help. More items will be added in the near future.
B. Clicking on 'Help:License:gINT Network Users' now launches default web browser displaying Sentinel Network Key usage. If user is not on a network license, a dialog stating "You are not using a network license." is displayed.
C. Previously when using network license keys, if the number of license seats were exceeded, gINT would first use WAN seats before using LAN seats, now gINT will work progressively outward from the local machine when trying to locate a seat, first looking for a local key then looking for a LAN seat then looking for a WAN seat.
3. Localization
A. (Requires 8.2 licensing)
On gINT startup, if the Windows language is not US English and the gINT language had never been set inside the program, a dialog will appear asking what language is to be used. If a language other than US English is selected and you are not licensed for version 8.2 or later, a dialog will appear at the end of startup saying that this capability is not available. The program will then restart in US English.
B. (Requires 8.2 licensing)
The keyboard short cuts have been localized to Spanish and Czech to reflect either the commonly used short cuts in those languages or keys for gINT-specific commands that match the first or second character of the command label in those languages.
4. Functions
A. Sql and SqlList have been enhanced to automatically concatenate multiple fields, for example where you may have:
<<SqlList(<<cr>>,_
Select [TABLE].[Field1] & " - " & [TABLE].[Field2] _
From [TABLE] _
Where ...._
)>>
You can now use the following equivalent syntax:
<<SqlList(<<cr>>,_
Select [TABLE].[Field1]," - ",[TABLE].[Field2] _
From [TABLE] _
Where ...._
)>>
B. When using the European Numeric Format option (File:System Properties dialog, Output tab), formatting must NOT be done until all calculations are completed. For example:
<<Let(Variable = <<Format(<<Calc(<<TABLE.Field 1>> * 28.6)>>,0.00)>>)>>_
<<Format(<<Calc(<<Get(Variable)>> * 28.4)>>,0.00)>>
The above will result in an incorrect result since "Variable" will be in European format, e.g., "58,234". gINT will interpret this as 58 thousand, not 58. For the above to work, the Format needs to be removed from the Let.
5. Entities
A. In log reports, if the tick Width property is blank on a column entity with a Vertical Scale Ticks tab the program draws the tick across the full width of the column.
B. On a well graphic column on a log form, if you have created an above ground detail using negative depths and specified left and/or right section lines on the entity (Lines tab), these lines will continue into the column header area, that is, above 0 depth. You can suppress above 0 depth sections of these lines by marking the "Suppress Vertical Lines at Negative Depths" property check box which is also under the Lines tab.
C. The "Column Height" property under the "Text Columns" tab of the text entity properties dialog can now be an expression. The "Column Display Height" can be used at design-time to show a column height when that property is an expression. The "Column Display Height" property is cleared if the "Column Height" is not an expression, that is, blank or a number.
6. Reports
A. In Output:Fences, the minimum and maximum distance axis values are in relation to the Initial Baseline Offset value. For example, if the initial baseline offset is 1000 and you specify a minimum distance axis value of 1500, the fence will start 500 from the beginning of the baseline, that is, the first 500 distance units will not be shown. If the minimum distance axis value is left blank, the fence will start at the Initial Baseline Offset. You cannot have a minimum distance axis value less than the Initial Baseline Offset value.
B. (Requires 8.2 licensing)
The "Distinct records from each table" property of Graph Report properties (under the Independent Data tab) forces decoupling of data from multiple tables so that they output that their specific depths. This applies only to graph reports with a key set of "PointID,Depth". It is rare that you need this option but it is possible that with output of data from extended key set PointID,Depth tables, where the key sets are different, you could get data points plotting redundantly. If that occurs, mark this property.
7. Import/Export
A. (Requires 8.2 licensing)
gINT project data can be exported to formats that can be read by the GEO5 analysis modules (http://www.gintsoftware.com/geo5.html). See Help:Manuals, gINT Manuals, "Integrating GEO5 with gINT".
B. (Requires 8.2 licensing)
When alignments are imported from LandXML files, any adjacent duplicate coordinates are automatically eliminated.
C. (Requires 8.2 licensing)
LandXML Site Map import: The layer properties were moved from the system properties dialog to the import dialog. A tab was also added for other properties in the site map import dialog.
D. Our PDF driver will now work with 64bit Windows XP and Vista.
E. gINT will show options to import and export to .XLSX (Excel 2007 format) in all places where Excel files are selected if Excel 2007 exists on your computer. It will also show the option for .XLS format as well.
F. On import to tables that either have hidden counters (Readings tables and the Alignment Coordinates table) or non-unique keys, the overwrite options Never, Empty Fields, and Named fields act as "Never", that is, data will not be imported if there are any data currently. The overwrite option Records acts like Data Sets, that is, if either option is select, all the existing data associated with the dataset being import will be deleted and replaced by the imported data.
The reason for this behavior is that with these types of tables, gINT has no way to accurately map between specific records in the source and target.
8. Interface
A. The Help:Manuals command dialog has added descriptions and a clearer look and feel to how manuals are organized. Any additional manuals that users wish to add can be included in the docs folder, as always, and will still be available in gINT by clicking on the Additional Files button at the bottom left of the new Manuals Dialog.
B. When the tree view is active in Input, the "+" button at the upper right expands all groups, the "-" button collapses all groups except the group with the currently selected table. If there are no groups in the project these buttons will not appear.
C. A "Quit" button has been added to the spell check dialog. This is in case you are spell checking a very large table and wish to terminate the process.
D. Text Macros and Spellcheck are now available in Graphical Input mode. These commands are accessed from the Tools menu.
E. Help:Legal Notices menu item has been added to create a place to list trademarks and registered trademarks of products referenced in gINT.
9. Setup and Configuration
A. When the /setup = "path to setup file" command line is used in the gINT desktop icon, if the SETUP.GSH file does not exist in the specified folder, it will be created. Previously, the SETUP.GSH file had to exist in the specified folder for the option to take affect.
B. You have stored project photos in a folder called "Photos" under your project folder. You e-mailed someone else in the company your project file and the Photos folder. Your project folder was g:\gint\projects\. Theirs was h:\data\gint\. As long as the Photos folder is under their project folder, gINT will still find it.
C. You use the Windows Group Policy Deployment facility to push out new installations and updates. See the System Administrator's Guide (admin_guide_8.pdf).
10. Miscellaneous
A. The View:Go To Zone in the Site Layout view in all output applications zooms to the selected zone. This is the same command that is in the Input:Site Map application.
B. (Requires 8.2 licensing)
Many times alignments stored in projects are not physical features on the ground like a road or levee alignment. They may also be fence baselines that you wish to retrieve for output a number of times through the course of the project or for different fence reports. In some cases, some alignments will be true physical features and others will be baselines. You may not want to show baselines on site maps. The "Do not display on Site Maps" boolean field in the ALIGNMENTS table suppresses the display of the alignment on site map entities (logs and fence reports), site maps on the top or bottom face of a 3D fence cube, site map reports, and the Site Map application in Input. The only place an alignment with this property marked will be seen is in the Site Layout view in Output:Fences.
Note that the baseline selected as the fence baseline will always be shown on site map entities on fence reports, even if the the do not display field is marked.
The do not display field was not included with the initial release of the alignments capability. To add it, open your project in Input or Data Design:Project Database and select the Additional Modules:Alignment Support menu item. It will ask if you wish to remove the tables or add missing items to the tables. Mark the add missing items option and click OK. The new field will be added to the end of the parent table fields. You can move it to any position. Remember to update your data template.
C. Due to the nature of Microsoft ACCESS, files will "bloat" (get much bigger) during certain operations. gINT will sense that this happens and automatically compact the file. For most files this is not a significant issue. However, with very large projects this can delay moving around gINT significantly. You can suppress this automatic compacting in the File:System Properties dialog under the "General" tab. Mark the "Suppress Automatic File Compaction" option.
11. New Web Posts
A. Documentation Changes:
The following documents are new with this release:
Using Google Earth With gINT tutorial (google_earth_tutorial_8.pdf)
Using gINT Lab Testing tutorial (lab_testing_tutorial_8.pdf)
Integrating GEO5 With gINT user guide (geo5_integration_8.pdf)
System Administrator's Guide (admin_guide_8.pdf)
The following major changes or additions have been made to existing documents:
rewritten: Welcome to gINT (welcome_to_gint_8.pdf)
rewritten: Installation and Licensing Guide (installation_and_quick_start_8.pdf)
AGS With Lab Testing appendix added to Using gINT with AGS3 Version 3.1 (ags3_and_gint_8.pdf)
Using Alignments section added to Advanced Output Options tutorial (advanced_output_tutorial_8.pdf)
Tree View section added to Performing Data Entry tutorial (data_entry_tutorial_8.pdf)
These new and updated documents can be downloaded with the Help:Check for gINT Update or manually from http://www.gintsoftware.com/support_doc.html.
B. A new gINT Rule Add-In GRA009 has been added to the Web site (http://www.gintsoftware.com/support_gintrules.html). This Rule Imports Sieve Analysis data from Excel into the current project.
====================
8.2.002 30Sep2008
====================
1. (Requires 8.2 licensing)
The LandXML Site Map Import command, located under the File:Import/Export menu in all gIDraw applications, will import site map entities. Currently these are:
Boundaries
Breaklines
Data Points
CG Points
Contours
Alignments and TIN surfaces are ignored and can be imported into the Alignments table and the Surfaces application in Input, respectively.
On invoking the command a dialog appears requesting the following information:
File Name: Select the file to import.
Major Contour Increment: Optional. If specified, the program places major contours in one layer and the others in another. This allows you to turn off the minor contours by making that layer hidden. If blank, all contour entities will be placed in one layer.
Unspecified Text Height: Optional. All of the entity types have text associated with them. However, only CG Points actually provide a text height. With the other entities, the text height is unspecified. If a value is not provided "1" is used. The value is in coordinate units. Therefore, if the site map units are meters, the text heights will be in meters.
In applications that allow layers, the entities, by default, are imported the following layers:
BOUNDARIES
BRAKELINES
DATAPOINTS
CGPOINTS
CONTOURS_MAJOR
CONTOURS_MINOR
CONTOURS
CONTOURS_MAJOR and CONTOURS_MINOR are used if the Major Contour Increment is specified, otherwise the CONTOURS layer is used for all contours.
These default layers can be overridden using with properties specified under the File:System Properties dialog, LandXML Site Map Import tab. The follow three properties are specified for each entity layer:
Layer Name
Layer Color
Entity colors same as Layer Color
Regardless of whether the default or user-defined layer names are used, the program creates a layer for text entities associated with each of the entity types named ENTITY_LAYER_NAME_TEXT. For example, if your boundary entities layer is called BOUNDARIES, the associated text layer will be called BOUNDARIES_TEXT. The text layer is given the same layer color as the main layer and its entities inherit the layer color if the main layer's Entity colors same as Layer Color property is marked. This configuration allows you to turn off the associated text, if you wish.
For gIDraw applications that do not support text entities (symbols), text entities are not imported.
2. (Requires 8.2 licensing)
The gINTRules.BatchModeType property informs you of the type of batch process that is running by returning one of the following values:
gr_BatchMode_Convert: Convert Projects
gr_BatchMode_Import: Importing data
gr_BatchMode_Recalc: Recalculating current table
0: No batch mode running.
For example, you might wish to not run gINT Rules during a project conversion. To do so, place the following code at the top of your Sub Main procedure:
If gINTRules.BatchModeType = gr_BatchMode_Convert Then
Exit Sub
End If
The property is a finer-grained version of the gINTRules.BatchMode property which merely returns True if any batch process is running, False if not.
3. (Requires 8.2 licensing)
The "Plot order of bars and lines" property of the column bar chart vs depth entity (under the Data Representation tab) specifies whether the data scale and vertical scale ticks print before or after the bars. This has significant visual effect if the bars are solid filled. In this case, with the bars plotting over the lines, the lines will not be seen where the bars plot. With the lines plotting over the bars, the lines will always be seen, regardless of the fill type of the bars.
4. (Requires 8.2 licensing)
The gINTRules.GoogleEarth.AddScreenOverlay method allows displaying a logo or any other graphic image to a specific screen location on the Google Earth interface. The "Google" logo at the lower right of the screen is an example. The arguments are:
Name As String: Name associated with the image. This appears in the folder list at the right of interface. This can be empty ("").
Description As String: Description associated with the image. For example, your company name, Web site, and phone number. This appears in the folder list at the right of interface. This can be empty ("").
ImageFile As String: The name and location of the image file. The formats supported are:
JPG BMP TIF TGA PNG JPEG TIFF PPM PGM
The location can be either on disk or a URL on the Internet:
g:\my images\google earth\my logo.jpg
http://www.gintsoftware.com/downloads/ge_icons/gint_logo.gif
ImageHandlePointX As Double: The X coordinate point on the image that will be moved to the screen coordinates defined below. The value unit can be a fraction or number of pixels (see description below).
ImageHandlePointXUnits As grGoogleEarthImageUnits: See description below.
ImageHandlePointY As Double: The Y coordinate point on the image that will be moved to the screen coordinates defined below. The value unit can be a fraction or number of pixels (see description below).
ImageHandlePointYUnits As grGoogleEarthImageUnits: See description below.
ScreenX As Double: The X coordinate point on the screen to which the image handle point will be moved. The value unit can be a fraction or number of pixels (see description below).
ScreenXUnits As grGoogleEarthImageUnits: See description below.
ScreenY As Double: The X coordinate point on the screen to which the image handle point will be moved. The value unit can be a fraction or number of pixels (see description below).
ScreenYUnits As grGoogleEarthImageUnits: See description below.
grGoogleEarthImageUnits can be one of the following constants:
gr_GE_ImageUnits_Fraction
gr_GE_ImageUnits_Pixels
That is, the unit values can be a fractional part of the image or screen (1 = far right/top, 0 = far left/bottom) or a number of pixels.
Call gINTRules.GoogleEarth.AddScreenOverlay("gINT Logo", _
"www.gintsoftware.com", _
"http://www.gintsoftware.com/downloads/ge_icons/gint_logo.gif", _
1, _
gr_GE_ImageUnits_Fraction, _
0, _
gr_GE_ImageUnits_Fraction, _
0.8, _
gr_GE_ImageUnits_Fraction, _
20, _
gr_GE_ImageUnits_Pixels)
The above will place the gINT logo (located on our Web site) lower right corner (ImageHandlePointX = 1, ImageHandlePointY = 0) at 80% of screen horizontally and 20 pixels above the bottom of the screen.
5. (Requires 8.2 licensing)
Fence alignment lines can have scales placed on them anywhere alignments are shown. In all locations, the following properties are associated with the scales:
Major Division: Distance between major division ticks and numbers in coordinate units.
Major Tick Length: Length in coordinate units.
Number of Minor Divisions: The number of minor divisions for each major division. The minimum value is 2.
Minor Tick Length: Length in coordinate units.
Number Height: The text height of the scale numbers in coordinate units. Scale numbers print at each major division.
Number Font: Text font
Number Offset: Offset of number above the major tick in coordinate units.
Number Angle Offset: The angle of the scale numbers relative to the alignment at the location of the number. The default of 0 degrees indicates that the baseline of the number is parallel to the alignment section. The allowable values are 0 to 90 degrees.
The only required properties are the Major Division and the Major Tick Length. If you wish to see the station numbers, you will need to provide the Number Height. If you wish to have minor divisions, you will need to provide the number of minor divisions and the minor tick length.
For specifying alignment scales in the Input:Site Map application and in all Site Layout views in Output, the properties are set in Input:Site Map under the Site Map:Alignment Scale Display menu. The properties here are stored in the library and require literal values, that is, no expressions can be used.
For showing alignment scales on site map entities (log and fence reports), there is an "Alignment Scales" tab under the entity's property dialog. Here all the properties, except the font, can be expressions.
For showing alignment scales on fence, graph, and site map reports, there is an "Alignment Scales" tab under the report's properties dialog. Here all the properties, except the font, can be expressions.
On fence reports, alignment scales only when a site map is shown in a 3D view.
On graph reports, alignment scales only apply when a site map is shown on the graph.
6. (Available to all gINT version 8 clients)
The Print Order property is now exposed for all entities in the Symbol Design:Data Marker application.
7. (Requires 8.2 licensing)
At output time if the report variables dialog is canceled, the output is terminated. This is new behavior but makes it consistent with all other behavior in the program. This behavior only occurs with the new dialog structure which is supported if you have version 8.2 licensing.
8. (Available to all gINT version 8 clients)
gINT requires that your regional settings use a period (.) for a decimal separator and a comma (,) for a thousands separator. If this is not the case, on startup the program will give you the option to have gINT change them for you. If you agree, the program will restart with the modified settings. On exiting the program your original settings will be restored.
=================
8.2.001 10Sep2008
=================
1. Initial release of 8.2. See Help:Contents:What's New in Version 8.2 and www.gintsoftware.com/upgrades.html.
=================
8.1.026 11Jun2008
=================
1. Maintenance release.
2. Updated Help file, dated 03 June 2008, is now available for download.
3. The "View Text" command caption (Correspondence Files under the File menu) has been changed to "View as Text" for clarity.
4. Clarification of the use of "" and <<Omit>> in export correspondence files:
Specifying a Source Expression of "" will export a blank into the target file. Specifying a Source Expression of <<Omit>> will suppress the export of that field to the target file when the target is not a database. For example, if exporting to Excel, target fields with the Source Expression of <<Omit>> will suppress that column in the final Excel file. With export to a database <<Omit>> acts exactly like "" since the fields in the target database already exist and <<Omit>> will not delete those existing fields.
5. Clarification of the use of the Output Condition property with repeating text entities:
The Output Condition of repeating text entities is evaluated once per output, not once per repetition. This is evaluated before the repetitions are generated so all the repetitions are output or nothing is output depending on whether the Output Condition expression returns False or True, respectively. If you want to suppress specific repetitions based on some criteria, do not use the Output Condition property. Instead, you must build the criteria into the text expression. In general:
<<IIf(some condition,repeating text expression)>>
If "some condition" returns False, nothing will be output in the above expression. For example:
<<Let(Value = <<Lookup(<<ATTERBERG.Liquid_Limit>>,_
<<DataSetKey(<<#>>)>>_
)>>_
)>>_
<<IIf(<<Get(Value)>> > 0,<<Get(Value)>>)>>
The above will only output liquid limits greater than 0.
6. If you build a .NET DLL for use with gINT Rules and include an installation project within your .NET solution, on building the solution, you will see the following warning:
Unable to find dependency 'GINT_LICENSE' (Signature='(null)' Version='1.2.1.1') of assembly 'Interop.gINT.dll'
Ignore this warning. The installer is looking for dependent files that you need to ship with your DLL. It sees a dependency within gINT for its license DLL and the installer can't find it. This is OK.
7. Clarification on offsets values generated on fence diagrams:
The FenceOffset system field generates a positive value when the borehole is left of the baseline, negative when right. Left and right are defined when you are standing on the baseline looking towards the end point, that is, when the starting point is at your back.
8. When exporting to a raster image file (JPG, BMP, etc.), setting the resolution too low can result in loss of information on the output, for example, text or lines not showing. The limit depends on color depth, page size, and your system. A resolution of 300 dpi appears to work in all cases.
9. In the Site Layout view of Output:Fences, on drawing a baseline (Fence Spec menu) the Draw Baseline menu, the repeat command button at the bottom of the screen are disabled. If the various baseline editing commands are executed from the Fence Spec menu and then the baseline is erased, the Draw Baseline menu is enabled and the editing commands are disabled. You will see this both under the Fence Spec menu and in the repeat command buttons. The general context menus will reflect the enabled/disabled properties of these commands as well.
10. On exporting to DXF in the Site Map application gINT exports all entities, including the PointIDs. These are exported to a layer called "POINTIDS". This layer is a gINT system layer in this application and is not seen in the Site Map application. You will see PointID entities (configured as text and polyline entities) when imported into a CAD application or any gIDraw application in gINT that supports text. In gIDraw applications that support layers you will also see the "POINTIDS" layer. If a DXF file exported from the Site Map application is reimported into that application, all entities on the "POINTIDS" layer will NOT be imported. System layers are only populated by the program.
11. Help Topic clarification:
The "Import Grid File (command)" help topic states:
"You can import a grid file of the form:
X<delimiter>Y<delimiter>Z
where there are no header or footer lines to the file, just coordinates. The <delimiter> can be a space, tab, or comma. For example:
625.3 205.3 1.063
625.3 305.3 6.662
625.3 405.3 10.42
725.3 205.3 2.345
825.3 205.3 2.889
725.3 305.3 2
725.3 405.3 9.706
....
This example has a space as the delimiter. The lines can be in any order but the X and Y values must be on a regular spacing."
"...the X and Y values must be on a regular spacing." Means that the points provided must fall on a rectangular grid with equal spacing in the horizontal and vertical directions and there can be no holes in that grid.
=================
8.1.025 30Jan2008
=================
1. Maintenance release.
2. In Input, in the File:Import/Export:Export to Database dialog, if a "Template to create database" is specified, by default the data in the template file is removed after the target database is created. By marking the "Do not remove data from Template" property the data remains in the template file is kept in the target database.
3. You have a table of chemical results (let's call it CHEMICALS) with one field for each chemical. For example:
Depth FERFS ANTHN etc.
(m) (ppm) (mg/kg)
You need to export to the CNMT group of an AGS file which requires the following structure:
...,"*CNMT_TYPE","*CNMT_RESL","*CNMT_UNIT",...
You would do this by creating one CNMT export group in the Data Design:Correspondence File application for each chemical. That is, you will be exporting as many times as chemicals to this group. Each group would have the following structure in the correspondence file:
CNMT,CHEMICALS
...
CNMT_TYPE,"FERFS"
CNMT_RESL,<<ExportKey>><<FieldUnits()>><<CHEMICALS.FERFS>>
CNMT_UNIT,<<FieldUnits()>><<FieldUnits(<<CHEMICALS.FERFS>>)>>
...
CNMT,CHEMICALS
...
CNMT_TYPE,"ANTHN"
CNMT_RESL,<<ExportKey>><<FieldUnits()>><<CHEMICALS.ANTHN>>
CNMT_UNIT,<<FieldUnits()>><<FieldUnits(<<CHEMICALS.ANTHN>>)>>
...
A. Each group would map the CHEMICALS table to the CNMT group.
B. The chemical type would be the literal name of the chemical.
C. The result would be the contains the data fields for that chemical. The <<ExportKey>> tells the program not to export the record if there is no result for the current chemical. The <<FieldUnits()>> says that the unit for this field is nothing. If this is omitted the program would use the field unit for the first chemical that is exported.
D. The unit exports the field unit for the current chemical. The first <<FieldUnits()>> says not to insert a unit header for this column. The second extracts the actual unit from the field for the current chemical.
An alternative to the units data is the following:
CNMT_UNIT,<<FieldUnits()>>"ppm"
This will work but if you changed the field units for a chemical you would have to remember to change the correspondence file as well. The first solution with <<FieldUnits(<<TABLE.Field>>)>> would change automatically.
Note the above samples show how the expressions will look in the Correspondence File application. Viewing the above in an ASCII editor the CNMT_TYPE expressions would look like:
CNMT_TYPE,"""FERFS"""
gINT stores the expressions using CSV (comma separate values) rules. These state that if a data field has quotes, the quotes must be doubled and the entire field surrounded in quotes.
4. The following construction in an expression will work:
...<<TABLE.Field1>> < <<TABLE.Field2>>...
This evaluates whether the value of Field1 is less than the value of Field2. The following will fail:
...<<TABLE.Field1>> <<<TABLE.Field2>>...
This is the same expression but with the space missing from the right side of the "<". The expression evaluator will not pick up Field2 properly. "<<<" will be flagged as an error. You will be instructed to either remove the third "<" if it is a typographical error or insert a space after the first "<".
Both of the expressions below will work:
...<<TABLE.Field1>> > <<TABLE.Field2>>...
...<<TABLE.Field1>>> <<TABLE.Field2>>...
The expression evaluator has no problem with the trailing ">>>". However, the program will still flag this as an error since we have seen clients who type the expressions manually (not a recommended practice; use the data tool!) inadvertently insert an extra ">". This will fail the expression under certain conditions. Further, it makes the expression more difficult to read. As with "<<<", you will be instructed to either remove the third ">" if it is a typographical error or insert a space before the last ">".
5. The behavior of the Web browser on the initial screen in gINT has changed due to popular demand. Previously, the initial Web page in a session was set to the last page accessed at the end of the previous gINT session. Now it is reset to the Home page.
6. Toolbox positioning capabilities were added to preview applications.
=================
8.1.024 20Dec2007
=================
1. Maintenance release.
2. Some multiple purpose network printers caused gINT to crash on printing or soon afterwards. This has been fixed.
3. The "PgAddl" system data item returns the additional page number on log reports. This is used in conjunction with the "Number of Additional Pages Expression" property. Returns 0 if the current page is within the main pages. If there are 3 main pages and 2 additional pages, when the page number is 1 to 3, PgAddl = 0. With Pg = 4, PgAddl = 1. With Pg = 5, PgAddl = 2. This allows writing expressions that determine which photo is to be printed on which page when photos are appended to the end of a log report. A sample test pit log report will be posted to the Web site in the next few weeks that illustrates the usage of this item.
4. Excluded zones in Site Layout view at output: If a zone is selected as "Excluded" in the Zone Filter picklist in an output application, moving into the Site Layout view, the excluded zones will be drawn in very light blue (or very light cyan if very light blue is selected as the override mark color in System Properties). Selected zones (Exclude property not marked) will be in very light green (or the override mark color in System Properties) and unselected zones in very light red. Clicking on an excluded zone will make it selected and not excluded. There is no way in the Site Layout view to mark a zone as excluded. This can only be done in the Zone Filter picklist in the main Output application view.
=================
8.1.023 29Sep2007
=================
1. Maintenance release.
=================
8.1.022 19Sep2007
=================
1. Maintenance release.
=================
8.1.021 10Sep2007
=================
1. During some technical support sessions, the support technician may need to show you something on his screen or may need to see your screen. gINT Software maintains an Internet Meeting site. This can be accessed quickly via the Help:Internet Links:gINT Software Internet Meeting Site menu item anywhere in the program.
=================
8.1.020 16Aug2007
=================
1. Clarification on some behavior of grid ticks around data frames (fences, graphs, histograms, site maps):
A. If there is no line type specified for the data frame and a side does not have division numbers, ticks will not be shown.
B. If a side does not have division numbers and the ticks are negative in length (are drawn outside the data frame), ticks will not be shown whether there the data frame is shown or not.
C. In graph applications, cut out boxes will trim full length grids but not ticks.
The above applies to both the major and minor grid ticks.
2. The User Report Variables subdialog in the report properties dialog in Output applications does not allow addition of new variables nor the changing of the existing variable names. These operations can only be done in the Report Design applications. At output time only the variable values can be changed. Like all changes to report properties made at output time, none of the changes will be saved. The changes will only be in effect until the report is changed or the application is exiting. Then the properties specified in the Report Design applications will be restored.
=================
8.1.019 01Aug2007
=================
1. We have made a number of changes to the way our output engine evaluates expressions. Theoretically these changes should lead to significant reductions in output time. The amount of time depending on the expressions used by the report forms. We have found up to 50% time savings on some forms. Our test script outputs over 200 pages using about 150 forms. That script run has been reduced about 20%. However, for the vast majority of forms of low to moderate complexity you will not notice any difference.
The biggest change is in the way our expression evaluator handles conditional functions. The idea being that only the parts that need to be evaluated will be evaluated. For example:
<<IIf(<conditional expression>,<expression to return if condition is True>,<expression to return if condition is False>)>>
With the previous coding, all three expressions were first processed before the IIf function was evaluated. Now, the code first processes the conditional expression, if that is True then only the True expression is evaluated, otherwise the False expression. This change applies to the following functions:
Case
DelimitData
FirstData
HasData
IIf
IsDate
IsDateOnly
IsNumeric
IsTimeOnly
Iterate
Like
Switch
You can use this new behavior to speed up some operations. For example, follow is a typical component model text expression:
<<FirstData(_
<<ComponentDesc([SOIL DESCRIPTION])>>,_
<<ComponentDesc([ROCK DESCRIPTION])>>,_
<<LITHOLOGY.Description>>_
)>>
The two ComponentDesc functions can entail very large expressions to be evaluated at each depth in a borehole. Previously, all three expressions were evaluated before the FirstData function was processed. Now, if there are data in the SOIL DESCRIPTION then the ROCK DESCRIPTION and the LITHOLOGY.Description will not be evaluated. However, if there are no data in the SOIL DESCRIPTION, it will still be evaluated before moving onto the ROCK DESCRIPTION.
If the SOIL and ROCK DESCRIPTIONS are each handled in one table each, the above can be optimized with:
<<FirstData(_
<<HasData(<<STRATA SOIL.Depth>>,<<ComponentDesc([SOIL DESCRIPTION])>>)>>,_
<<HasData(<<STRATA ROCK.Depth>>,<<ComponentDesc([ROCK DESCRIPTION])>>)>>,_
<<LITHOLOGY.Description>>_
)>>
The above assumes that all the soil description component fields come from one table and the rock description from another. If there is not value for the TABLE.Depth, then there is no use executing the ComponentDesc function.
WARNING: It is possible that the new evaluation process for conditional functions will cause some functions to fail that previously worked. Here is how it could happen:
<<IIf(Some condition,_
<<Let(Some Variable = XXX)>>_
Expression to evaluated if Some condition is True,_
Expression to evaluated if Some condition is False_
)>>
Now let's say that without the expression to evaluate when the condition is False has "<<Get(Some Variable)>>" as part of it. With the previous behavior the Get would return the value set in the Let, even when the condition was False. With the new behavior, the True expression, including the Let will not be evaluated and the Get in the False expression will fail. The solution to the above is simply to move the Let above the IIf:
<<Let(Some Variable = XXX)>>_
<<IIf(Some condition,_
Expression to evaluated if Some condition is True,_
Expression to evaluated if Some condition is False_
)>>
The above problem is prototypical. It can be much more complex. For example, the True expression could be a complex User System Data expression with a Let buried in it that is used by both the True and the False expressions. If an expression fails after this update and you cannot track down the problem, please contact Support for assistance.
2. If the Depth Units Page 1 property of a log report is a number or empty, that property appears on the output screen and can be modified. The program obtains this property only from the screen version of the property, not the log report property. To enforce that, the report property is disabled in the output application. If the property has an expression, the screen version of the property is suppressed and the report property is editable.
The above behavior also applies to the Axis minimum, maximum, scale, and number of divisions for both axes and in both the Output:Graph and Output:Site Map applications. That is, if the original report property was a number or blank, it will appear on the output screen and the report property will be disabled at output.
3. Clarification on some behavior of grid ticks around data frames (fences, graphs, histograms, site maps):
A. If there is no line type specified for the data frame and a side does not have division numbers, ticks will not be shown.
B. If a side does not have division numbers and the ticks are negative in length (are drawn outside the data frame), ticks will not be shown whether there the data frame is shown or not.
C. In graph applications, cut out boxes will trim full length grids but not ticks.
The above applies to both the major and minor grid ticks.
=================
8.1.018 03Jul2007
=================
1. Previously with repeating text entities only the Text property was searched for replacement of the repeat variable (<<#>>). Now the program also allows insertion of the repeat variable in the Height Override Expression property so that text heights can be adjusted for each repetition.
2. If a hot key is not assigned in a gINT Rule Add-In (e.g., My &Command would allow Alt+C to execute the command), the program automatically assigns one to one of the characters in the command label. It ensures that the hot key is not duplicated. If all the characters in the command label are used in the commands above the current command, no hot key is assigned.
=================
8.1.017 06Jun2007
=================
1. The "Horizontal Lines w/Data Edge options" property of the bar chart vs depth entity and associated column entity (Data Representation tab) draw horizontal lines at the depths of breaks in the data between the minimum and maximum data at those depths. This option only affects the three Data Edge options of the "Border Line Options" property.
2. To avoid confusion with "Trial" mode, "Demo" mode is now called "Viewer" mode. The behavior is the same.
3. The Reverse Scale property has been added to Plot vs Depth and Bar Chart vs Depth column entities. This property works exactly as it does with the non-column entities and it also reverses the data scale.
=================
8.1.016 04May2007
=================
1. The <<OutputZoneFilter>> system data item prints the list of zones used to filter the output, if any. The structure of the output is:
zone name 1(incl or excl), zone name 2(incl or excl), ...
where "incl" means the PointIDs in the named zone were included in the output and "excl" means the PointIDs in the named zone were excluded from the output.
=================
8.1.015 22Mar2007
=================
1. If you have written gINT Rules save code that is only triggered if a field value has changed (see GR010), be warned that no field will appear to change during an import. The way import is handled is that first all the data are imported and then the save code is run. The same applies when running the Recalc Current Table command. Therefore, you may wish to run this block of code if a field has changed value or the current data entry mode is not manual entry. To that end, use the gINTRules.GridData.IsManualEntryMode property. This returns True if in manual entry mode, False otherwise (import and recalc).
=================
8.1.014 15Mar2007
=================
1. In the report properties dialog of Graphic Text Documents, the "Retain Layering" property under the "Layers" tab forces the report layering to be maintained at output. If unmarked (default), all entities are placed on layer "0" regardless of the layering in Report Design.
=================
8.1.013 05Mar2007
=================
1. Software licenses can no longer be deactivated via the Internet, only by telephone or e-mail. This facility was halted because of numerous stability and security issues associated with it. Software licenses can now be transferred using a process initiated on the computer without a license. See the License book under Help:Contents. Then move to Software License and then Activating a Software License by Transfer from a Standalone License.
2. The Sentinel Protection Installer shipped with gINT 8 has been updated from version 7.3.0 to 7.3.2. According to Safenet, this new version is Vista compatible. In addition, the Sentinel Protection Server installed with this package does not crash Microsoft Internet Explorer 7.x when Internet Explorer is used to display the Sentinel License Monitor.
3. When any group is hidden the Group Sequence command is disabled. Currently groups can only be hidden using gINT Rules.
4. Correspondence Files:
a) When making a Correspondence File with multiple source groups for a target table, <<Omit>> can NOT be used on any field that will be in the final output. Fields without sources in the current group must have an empty literal as the source expression, written as six quote marks """""".
b) Multiple groups are not necessary (at least in most instances.) A group can have source field expressions from different tables. Use System Key items for the key fields, as <<PointID>> and <<Depth>>.
For fields other than PointID provide a units spec. Example:
CLSS,ATTERBERG
HOLE_ID,<<PointID>>
SAMP_TOP,<<Depth>><<FieldUnits(<<LAB SPECIMEN.Depth>>)>>
SPEC_DPTH,<<Depth>><<FieldUnits(<<LAB SPECIMEN.Depth>>)>>
CLSS_NMC,<<WC DENSITY.Water_Content>>
CLSS_LL,<<ATTERBERG.Liquid_Limit>>
CLSS_PL,<<ATTERBERG.Plastic_Limit>>
CLSS_BDEN,<<WC DENSITY.Wet_Density>>
CLSS_DDEN,<<WC DENSITY.Dry_Density>>
5. In the report properties dialog of Graphic Text Documents, the "Retain Layering" property under the "Layers" tab forces the report layering to be maintained at output. If unmarked (default), all entities are placed on layer "0" regardless of the layering in Report Design.
6. When there are more tabs than can fit on the screen, scroll buttons appears at the left/right sides of the tab area. Holding down the mouse on a scroll button moves the tabs continuously. You will see this in Input and in multiple tab dialogs.
=================
8.1.012 12Feb2007
=================
1. The sieve analysis tables in the native gINT Lab Testing facility assumes that there is only one or two tare weights used for weighing the soil retained on each sieve. One weight (from the Wt_Sieving_Tare_Coarse field in the parent grid) if the specimen is not split, two (Wt_Sieving_Tare_Coarse and Wt_Sieving_Tare_Fine) if the specimen is split. This works for labs where the procedure is to place the material in each sieve into a tare for weighing. Some labs will place the entire sieve with the material retained onto the scale. In this case the tare for each sieve will be different and the tare weights in the parent grid do not apply.
If you add a field called "Wt_Sieve_Tare" in the SV READINGS table (must be a numeric field; you can caption anyway you wish), you can input tare weights for each sieve in the test. If this field exists and all the data rows (a data row has entries for sieve size and weight of soil plus tare) have values in this field, the program will ignore the sieving tare values in the parent grid and use these values. If some of these fields have values in the data rows but not all, you will receive an error message to fill in this field for all the data rows or leave them all blank and use the sieving tares in the parent grid.
2. PDF Export:
A. The checkbox to 'View document after export' is now enabled when exporting each dataset to an individual file. When exporting each dataset to an individual file, in the displayed export file path, the file name is now replaced with "*.pdf" to signify that the created file name(s) will be based on file name expression and not on the selected file name.
B. When exporting all datasets to a single file, if a bookmark location and type is specified and then a new export file location is selected, previously selected bookmarks will be added to the newly selected file upon export.
=================
8.1.011 05Feb2007
=================
1. PDF Export:
A. We have upgraded the PDF export drivers. You must run the PDF Exporter update to export to PDF from this build forward. These new drivers also allow the new properties below.
B. PDF export attributes in File:System Properties, "Output" tab:
1. PDF image compression (low, med, high) - combo - sets compression level for raster images printed to PDF doc. Lower compression gives the best quality, higher compression gives lower quality.
2. Do not embed fonts - checkbox - If checked, fonts are not imbeded in the PDF document. This can make the documents smaller.
3. Do not add international character sets - checkbox - If checked, international character sets are not added to the PDF document. This can make the documents smaller.
2. The OHDOT_Symbol function has been updated to support the Soil and Bedrock Classification appendix dated 19 January 2007 from the OH DOT Web site. This specification adds the two new classifications: A-8a and A-8b. The former are soils that would classify as A-4a or A-4b soils but are organic. The latter are soils that would classify as A-5, A-6a, A-6b, A-7-5, or A-7-6 but are organic.
The new syntax is:
<<OHDOT_Symbol(<<Table.Size (mm) Field>>,<<Table.% Passing Field>>,<<Table.PL>>,<<Table.LL>>[,<organic True/False>])>>
The last argument, <organic True/False>, is optional (to support backwards compatibility with previous implementations). In this argument you would pass a boolean field that indicates the soil is organic or not or an expression that determines whether the soil is organic. For example:
<<OHDOT_Symbol(_
<<Union(<<SV READINGS.Reading>>,<<HYD READINGS.Particle_Size>>)>>,_
<<Union(<<SV READINGS.Percent_Finer>>,<<HYD READINGS.Percent_Finer>>)>>,_
<<ATTERBERG.Plastic_Limit>>,_
<<ATTERBERG.Liquid_Limit>>,_
<<ATTERBERG.Organic>>_
)>>
Whether a soil is organic would be indicated by checking the "Organic" field check box in the ATTERBERG table.
<<OHDOT_Symbol(_
<<Union(<<SV READINGS.Reading>>,<<HYD READINGS.Particle_Size>>)>>,_
<<Union(<<SV READINGS.Percent_Finer>>,<<HYD READINGS.Percent_Finer>>)>>,_
<<ATTERBERG.Plastic_Limit>>,_
<<ATTERBERG.Liquid_Limit>>,_
<<Calc(_
(<<ATTERBERG.Oven Dried LL>> / <<ATTERBERG.Liquid_Limit>>) < 0.75_
)>>_
)>>
In the above example you would add a field called "Oven Dried LL" to the ATTERBERG table and the above calculation classifies it as organic if the oven dried liquid limit is less than 75% of the natural moisture liquid limit.
3. gINT Rules method LookupListGetDataFnB:
Description
This method returns the value(s) and description(s) of a gINT Lookup List.
Arguments
The Lookup Name argument is the input to the method. The Lookup Value Array and Lookup Description Array arguments are for the result output.
Lookup Name, String: The name of a lookup list.
Lookup Values, String Array (output): Array of Values in the lookup list.
Lookup Descriptions, String Array (output): Array of Descriptions for the values in the list.
Return Value
The method returns True if it successfully retrieves the Lookup List values, otherwise it returns False.
Sample Usage
The following will return two string arrays containing the Values and Descriptions for Lookup List "LLTableName".
Dim bResult as Boolean
Dim sLookupValueV() As String
Dim sLookupDescriptionV() As String
'----------------------
ReDim sLookupValueV(0)
ReDim sLookupDescriptionV(0)
bResult = gINTRules.LookupListGetDataFnB("LLTableName", _
sLookupValueV, _
sLookupDescriptionV)
=================
8.1.010 22Jan2007
=================
1. If a table has a hidden key, for example, a library table with the "Hidden Key" property marked, clicking on column headers will not sort the table by that column.
2. The RTrim function returns the passed in value with any trailing spaces removed. The syntax is:
<<RTrim(<expression>)>>
=================
8.1.009 09Jan2007
=================
1. Ctrl+Arrow Right and Left now moves to the first punctuation character or space. Previously these shortcuts stopped only on spaces.
2. Double clicking on text now highlights the characters left and right of the click up to the first punctuation character or space. Previously highlighted all characters up to the nearest space.
3. A new optional argument has been added to the following two functions:
<<LatLongConv(<<expression>>[,insert spaces][,pad w/0s])>>
<<LatLongDisplay(<deg>,<min>,<sec>[,format][,pad w/0s])>>
The optional "pad w/0s" argument (True/False) inserts 0s in front of single digit minutes and seconds in components, e.g., 48°02'03.66" instead of 48°2'3.66". Default is False.
This argument only applies in the LatLongConv function when converting from a decimal value to a component value. For the LatLongDisplay function, it only applies when converting to the two component formats (LLD_CMP and LLD_CMPSPC).
4. The menu item Help:View License A&greement (EULA) displays "gINT EULA 8.pdf" in the system PDF viewer.
5. The "Minor Grid Horizontal: Tick Length" and "Minor Grid Vertical: Tick Length" properties in graph report properties (Grid Minor tab) sets the length of minor grid ticks. If blank the minor grids will be full length across the graph frame.