Copyright 2007 by gINT Software. All rights reserved worldwide.
gINT Update README.TXT file
gINT 7 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 font.
====================
7.1.057 10Oct2007
====================
1. Maintenance release.
====================
7.1.056 17May2007
====================
1. Maintenance release.
====================
7.1.055 15May2007
====================
1. Maintenance release.
====================
7.1.054 15Mar2007
====================
1. Maintenance release.
====================
7.1.053 11Feb2007
====================
1. Maintenance release.
====================
7.1.052 21Dec2006
====================
1. Maintenance release. 051 introduced a problem with field replace where all replaced field names became "PointID". Also, certain text vs. depth entity configurations could generate overlapping text with 051. 052 fixes these problems.
====================
7.1.051 18Dec2006
====================
1. Maintenance release.
====================
7.1.050 19Nov2006
====================
1. Maintenance release.
2. If you find that your boundary text (e.g., termination notes at the bottom of a log column) print lower than they have before, it is because we have finally changed the code to handle boundary text properly with different vertical alignments. Previously you had to add a blank line at the top of the boundary text expression when the text was middle, base, or bottom justified. This didn't quite look right and it was not obvious. This build properly accounts for the vertical alignment. To fix the added space problem, in Reports:Logs, bring up the properties of the entity, move to the Boundary Text tab and remove the blank line at the top of the "Text Below Last Line" property. Our apologies for this inconvenience. If you need help on this procedure please call for support or e-mail support@gintsoftware.com.
====================
7.1.049 25Oct2006
====================
1. Maintenance release.
====================
7.1.048 15Oct2006
====================
1. Maintenance release.
====================
7.1.047 17Sep2006
====================
1. Maintenance release.
====================
7.1.046 27Aug2006
====================
1. Maintenance release.
====================
7.1.045 13Aug2006
====================
1. Maintenance release.
====================
7.1.044 24Jul2006
====================
1. Maintenance release.
====================
7.1.043 26Jun2006
====================
1. Maintenance release.
====================
7.1.042 04Jun2006
====================
1. Maintenance release.
====================
7.1.041 18May2006
====================
1. Maintenance release.
====================
7.1.040 20Apr2006
====================
1. Maintenance release.
2. Updated Help File is now available.
====================
7.1.039 26Mar2006
====================
1. Maintenance release.
====================
7.1.038 12Mar2006
====================
1. Maintenance release.
====================
7.1.037 21Feb2006
====================
1. Maintenance release.
2. We believe we have fixed a long running problem in property dialogs where drop down combo controls were being cleared on saving the dialog and the combo would not allow selection of any of the choices. This was a rare and intermittent problem and the only way to clear it was to exit the program. We finally were able to reproduce it at will and this update should eliminate the problem. Please let us know if you encounter it again.
3. The OHDOT_Group_Index function returns Group Index value as a whole number as per Ohio Department of Transportation specifications dated 01 November 1995:
GI = 0.2A + 0.005AC + 0.01BD
where:
A = %<200 greater than 35 and not exceeding 75, 0 - 40
B = %<200 greater than 15 and not exceeding 55, 0 - 40
C = LL greater than 40 and not exceeding 60, 0 - 20
D = PI greater than 10 and not exceeding 30, 0 - 20
This expression is modified from the original specification as per the verbal direction of the DOT. The lower bound on the ranges has been changed from 1 to 0. Note that, again as per the DOT direction, the Ohio DOT AASHTO classification is not changed by the Group Index nor is the Group Index changed by the classification. Both are determined independently of one another.
The syntax is:
<<OHDOT_Group_Index(<<Table.Size (mm) Field>>,<<Table.% Passing Field>>,<<Table.PL>>,<<Table.LL>>)>>
If you are using the standard gINT lab testing tables, this would be:
<<OHDOT_Group_Index(<<SV READINGS.Reading>>,_
<<SV READINGS.Percent_Finer>>,_
<<ATTERBERG.Plastic_Limit>>,_
<<ATTERBERG.Liquid_Limit>>_
)>>
If your are using this function in a repeating text entity, for example, printing the group index associated with each test result on a graph, rewrite as:
<<OHDOT_Group_Index(<<SV READINGS.Reading>><<#>>,_
<<SV READINGS.Percent_Finer>>,_
<<ATTERBERG.Plastic_Limit>>,_
<<ATTERBERG.Liquid_Limit>>_
)>>
where "<<#>>" is the "repeat variable." This is the same syntax as with all the gINT classification functions.
====================
7.1.036 29Jan2006
====================
1. Maintenance release.
2. The "Do not embed fonts into exported PDF documents" property in the System Properties dialog (General tab) has been removed from the program. Fonts will now always be embedded. We have found under certain, unknown conditions, some text in the PDF will be incorrect if fonts are not embedded. We are researching the problem.
3. In Input, the File:Import/Export:Export Contouring Data command has the following special behavior: If the "Which Depth" property (Depth Table Filter tab) is set to "Last" and the Field containing Z value field value is the deepest in a PointID, that PointID will not be exported. For example, let's say you wish to export a surface defining the bottom of a layer. If in a particular PointID that layer is the bottom-most layer, that data will not be exported. To do so would be misleading. We don't know the bottom depth of that layer in that hole. The hole did not extend deep enough.
====================
7.1.035 23Jan2006
====================
1. Maintenance release.
====================
7.1.034 22Dec2005
====================
1. Maintenance release.
2. In modifying the code two releases back, we inadvertently turned off the automatic deletion of our temporary files when the program was done with them. This has been fixed with this release. Unless you have explicitly saved files in the gINT temporary files folder (see File:System Properties for the location), you can safely delete all the files in that folder.
====================
7.1.033 04Dec2005
====================
1. Maintenance release.
====================
7.1.032 08Nov2005
====================
1. Maintenance release.
2. The "Lines to Log Extent" of Plot vs Depth entities (logs and fences) will extend the plot line from the first data point vertically to the top of the log and from the last data point vertically to the bottom of the log. However, if there are boundary depths derived from the "Boundary Depth Expression" property, the line vertical extensions will only go up and down to the nearest boundary depth.
====================
7.1.031 18Oct2005
====================
1. Maintenance release.
====================
7.1.030 13Oct2005
====================
1. Maintenance release.
2. When borrowing a net license, if a file called "borrowtime.txt" exists within "borrowlock" folder, the number of days to borrow the license is retrieved from this file. If number of days was retrieved from this file, the dialog for specifying amount of days does not get displayed. The "borrowlock" folder must be under the folder holding the network license and it must have read and view rights only for the gINT user. If the "borrowlock" folder is missing the "borrowtime.txt" file, the user is prevented from borrowing a network license. If the "borrowlock" folder is missing or has read-write rights for the user, there is no restriction on borrowing a network license.
3. Some older gINT ACCESS databases (libraries, projects, data templates) when converted to ACCESS 2000 format using the Utilities:Repair/Compact Databases application cannot be opened in ACCESS. ACCESS does nothing on selecting the file for open. No error messages are given. These files are fine, that is, the data and structure are intact. There is a problem in the header portion of the files. We have found no method to repair those files completely within gINT. A three step approach is required:
A. Select the file or files in Utilities:Repair/Compact Databases and hold the Ctrl+Shift keys as the [Execute] button is click with the left mouse button.
B. Open the file or files in ACCESS 2000 or later. You will get an error message. Click Ok and leave ACCESS.
C. Repair the file or files once more in gINT but this time just click the [Execute] button without the Ctrl+Shift keys.
4. With large surface grids you may not be able to import the entire grid into one surface record in Input:Surfaces. You may bring them in as multiple records with different names. To avoid having multiple surface legends reported by the Surface Legends entity on output, give all the related surfaces the same Description, Line Type, Line Color, and Line Thickness properties. Only one surface legend with then appear.
====================
7.1.029 10Sep2005
====================
1. Maintenance release.
2. The Depth Offset property of blocks works incorrect on vertically repeating logs/sheet. The Depth Offset Expression property assumes that the design-time vertical position of the entities associated with the block are relative to the log footer line. That is, if the depth offset worked out to end up at the bottom of the body on the last page, the depth offset would be 0 and the entities would appear as the user intended. This works with all log structures except for multiple logs on a page vertically. The program assumes the footer line is that of page 1. On logs repeated vertically on a page, this is incorrect. The "page 2" footer is the footer on each log segment on the page. We have fixed the program to work properly with multiple logs per sheet vertically, however, existing reports will have these "floating" blocks print their entities in the wrong position once this update is installed. Previously clients moved the offset entities until the vertical placement was correct. This fix eliminates that step.
To fix existing logs, bring up the properties of the affected log reports and move to the "Report Structure" tab. Subtract the Page 1 Footer Height from the Page 2 Footer Height and add the remainder to whatever Offset Y value you may have in the block that has the Depth Offset property set.
For example, let's say that the Page 1 Footer Height is 0.5" and the Page 2 Footer Height is 0.75". After the code update you will find that the entities associated with the block that has a Depth Offset property will print 0.25" lower than before. Subtracting the Page 1 from the Page 2 Footer Height, the difference is 0.25. Add that to the Offset Y property of the block insert entity that has the Depth Offset set. If there is no Offset Y property set, just insert 0.25 in the Offset Y property.
If you have questions, please call (707 838 1271) or e-mail (support@gintsoftware.com) technical support. If necessary we will make the changes for you.
====================
7.1.028 29Aug2005
====================
1. Maintenance release.
====================
7.1.027 16Aug2005
====================
1. Maintenance release.
2. Right clicking on a column header in the Input and Library Data applications now brings up a context menu. Previously there was no response on right clicking on a column header, only in the grid.
3. In the quick net transfer of a network license to a workstation, the program must access an Internet server to check the date and time. Rights to make that connection are required. If the rights exist and access to the Internet server fails, it may be that the port that gINT is attempting to use may be blocked. You can specify the port to use under the File:System Properties dialog, General tab. The field is "Internet Time Server (NTP) Override Local Port". The default port value is 0 which means that the program will use a random available port.
====================
7.1.026 13Jul2005
====================
1. Maintenance release.
====================
7.1.025 24Jun2005
====================
1. Maintenance release.
2. In the Preview screen of Output applications, if you bring up the Print dialog and click on the "Printer" button, you will receive the following message:
Changing printers in preview is not allowed.
Text sizes can change with different printers and the preview process has already adjusted all text as per the current printer.
To change printers you must exit preview, make the change, and then repreview or just print directly.
For the same text size and font different printers can print the same text to different sizes. During the building of the report during the preview process, the program makes some adjustments to text placement based on querying the text properties of the current printer associated with the report. Once the preview is complete those adjustments can no longer be made. Changing printer in Preview could therefore lead to text not filling an area you would expect it to fill or overflowing boundaries that shouldn't be overwritten.
====================
7.1.024 12Jun2005
====================
1. Maintenance release.
2. With Bar Chart and Plot vs Depth column entities, the line thickness and color of the Data Scale ticks are taken from the thickness and color properties of the vertical lines through the body, also under the Data Scale tab. The line types of the ticks are always Solid, regardless of the line type of the vertical lines through the body.
====================
7.1.023 08Jun2005
====================
1. Maintenance release.
====================
7.1.022 30May2005
====================
1. Under the "General" tab of the System Properties dialog, the "Marked Entity Override Color" allows you to change the default entity marking color (very light green). This is in response to some clients who are color blind to that color and who had difficulty distinguishing marked from unmarked colors. This setting only affects marking black entities in all gIDraw applications and marking PointIDs in the Site Layout view in Output applications. For other entity colors, an algorithm is used to determine the marked color. The list of available colors in this property shows your color list in the Symbols:Colors application plus a choice of "None", that is the default color is not overridden. This latter choice is the default. Black, White, and Very Light Red are excluded from the list. The latter because very light red is used for PointID entity colors in Site Layout view. You may name these colors differently so the program actually excludes colors "0", "16777215", and "255", respectively.
2. DXF files require the degree symbol (°) to be replaced by "%%d" for proper translation on import to AutoCAD. We have found some non-AutoCAD systems that use other codes for this symbol and which do not interpret "%%d" properly. Under the "DXF Files" tab of the System Properties dialog, the "Override Degree Symbol" allows you to substitute a string of text to replace the degree symbol on export. It is also used to replace the substituted string with a degree symbol on import. If left blank, the default is the AutoCAD "%%d" string is used.
3. You can borrow a standalone license seat from a computer licensed on a network via the Help:License Information dialog button "Borrow network license seat". If the workstation is not licensed, you would borrow the license through the usual process.
====================
7.1.021 18May2005
====================
1. Maintenance release. Mainly import/export issues.
2. You can import a grid file into the Surfaces application in Input of the form:
X<delimiter>Y<delimiter>Z
where there is 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
....
The lines can be in any order but the X and Y values must be on a regular spacing.
3. AGS export in the Input application only lists records under the FILE and DICT groups that are referenced in the AGS file.
====================
7.1.020 06May2005
====================
1. Maintenance release.
====================
7.1.019 05May2005
====================
1. Maintenance release.
====================
7.1.018 20Apr2005
====================
1. Added compatibility for non-English versions of Microsoft Windows.
====================
7.1.017 10Apr2005
====================
1. Maintenance release.
====================
7.1.016 06Apr2005
====================
1. Maintenance release.
====================
7.1.015 31Mar2005
====================
1. Maintenance release.
====================
7.1.014 30Mar2005
====================
1. Maintenance release.
2. DXF Export:
In conjunction with the Print Order property, Solid White fills can be used in polylines to blot out background entities. However, DXF export does not support print order and the color white is translated to black. For these reasons, white polyline fills are automatically suppressed when exported to DXF. This applies to both the Main and Background fills.
3. The ElevFromDepth and ElevToDepth functions do not work in header/footer entities on fence, graph, and site map reports. In these cases the set number needs to be referenced for the calculation to be performed. For example, if you print the bottom elevations of all holes on a fence diagram, the expression would be:
<<Calc(_
<<Lookup(<<POINT.Elevation>>,<<DataSetKey(<<#>>)>>)>> - _
<<PlungeFactor(<<#>>)>> * _
<<Lookup(<<POINT.HoleDepth>>,<<DataSetKey(<<#>>)>>)>>_
)>>
where "<<#>>" is the repeat variable and would be replaced with 1, 2, etc. by the properties specified in the "Repeat" tab of the text entity. To write the above as:
<<ElevFromDepth(<<Lookup(<<POINT.HoleDepth>>,<<DataSetKey(<<#>>)>>)>>)>>
will not work. Besides accounting for the set number, the two functions would need to accommodate any overwrite elevation expression in the fence report properties which, except for <<TABLE.Field>>, cannot be handled.
====================
7.1.013 29Mar2005
====================
1. Maintenance release.
====================
7.1.012 24Mar2005
====================
1. In the Symbols:Material, Sampler, Well, and General applications, the page properties dialog has a "Caption" property under the "Name" property. This is optional. If used, the caption will be shown in lookup lists instead of the name. This feature was implemented in response to the AGS 3.1 specification which requires material symbol names to be numeric values (101, 102, etc.). To make the data in Input more understandable, the caption can be used to show "Clay", "Silty Sand", etc. The names (101, 102, etc.) will still be stored in the database. The captions only appear in lookup lists and in the output of variable legend entities if the "Name" is requested. Like with lookups, the caption will be used only if there is a value, otherwise the name is shown.
To quickly add or edit captions, the page list (File:Page:List menu item) in these applications has a "Caption" column.
====================
7.1.011 16Mar2005
====================
1. gINT Rules:
The gINTRules.GridData.ForceRefresh method is used in conjunction with Add-Ins. It forces the retrieval of the data from the database into the grid for the current recordset. You would only need this if the Add-In made changes to the data in the database and then you needed to refresh the grid with the updated data. If you write such an Add-In:
A. Make sure the "Save Reqd" property is marked. If you are working on the data in the database, you need to ensure that any changes have been saved. Also, the ForceRefresh method is ignored if there are changes in the grid data.
B. At the end of your Add-In procedure, insert the line:
gINTRules.GridData.ForceRefresh
If there are pending changes or the method is called in a non-Add-In procedure, it is ignored.
2. The "Text not pushed down by text above" property of the "Wrap" tab of Text vs Depth and Text vs Depth Column entities (logs and fences) suppresses the default behavior that prevents text from overwriting. That is, normally if a line of text is at a depth of 5 and then next record prints text at a depth of 5.01, the text at 5.01 would be pushed down to avoid overlapping the text above. Marking this property prints the text at the specified depth with no consideration of text above it.
This property is useful when you have the "Output Override X" property set up so that text could never overlap because of horizontal offset. This is sometimes done with documentation of water levels. This could be accomplished by setting the "Line Height" property to a very small number, for example, 0.0001. However, if the text printed in a record has multiple lines, the text within the record will overlap. Thus the reason for the "Text not pushed down by text above" property.
====================
7.1.010 08Mar2005
====================
1. Maintenance release.
====================
7.1.009 03Mar2005
====================
1. Maintenance release.
====================
7.1.008 28Feb2005
====================
1. First public release of gINT version 7.