Version 7.0g represents a bug fix release and encompasses the following products:
GINO v7.0g
GINOGRAF v7.0c
GINOSURF v7.0c
GINOMENU v7.0g
GINOMENU-X v3.3e
GINOMENU Studio v7.0f
Product Enhancements Database
Bug-Fix Database
| PER | Product Name | Summary | Version |
| 1260 | GINO Library | Added option of use of Helvetica hardware font in example programs to improve output on X-Windows devices | 7.0f |
| PUR | Product Name | Summary | Version |
| 1680 | XWIN - X Windows | The internal line join type has been changed from Mitre to Round to prevent extra 'noise' when drawing small jagged lines | 7.0b |
| 1693 | A modification to the driver has been made so that it correctly detects a user window resize action irrespective of GINO events, so that the correct information is available to an external controlling GUI such as Motif (via xwinao). | 7.0g | |
| 1684 | WOGL - Windows OpenGL Driver | A problem switching between different colour material modes has been fixed. | 7.0d |
| 1685 | Generating PNG and JPEG metafile output from this driver is now operational linking the appropriate dll's at run-time as required. | 7.0f | |
| 1659 | MWIN - Microsoft Windows Driver | A memory leak when using the private backing store nomination options (gMwinao, gMwindc) has been fixed. | 7.0a |
| 1690 | Hardware clipping has been extended to hardware character strings which has corrected a previous problem with some angled strings drawn within a deformed viewport. | 7.0f | |
| 1677 | IMAGE - Windows Bitmap Driver | The header information for true colour BMP files was incorrect causing the file to be interpreted incorrectly by some applications (e.g. Paint). This has been corrected. | 7.0c |
| 1688 | GUIWIN - GINOMENU Windows GUI Driver | A system crash occurred in GINLIBVC.DLL when using the routine gDisplayStr() from a GINOMENU application. This has been fixed. | 7.0e |
| 1666 | GINO Library | A clipping problem clipping limits just off 0.0 caused the polygon to be ignored. This has been fixed. | 7.0a |
| 1672 | Error codes retuned from file handling system routines now contain system error code value (rather than simply -1) | 7.0b | |
| 1679 | Coordinate values are now returned correctly in gReturnInternalPoints2/3D when using a 3D device driver (e.g. OpenGL). | 7.0d | |
| 1683 | There was a problem with the placement of hardware stepped characters (ie. when hardware angled characters are requested, but where the device cannot generate them). This affected the display of surface axes labels displayed adjacent to the axes. | 7.0e | |
| 1656 | GINO.NET Interface | The routine Gino.PutImageFile was missing from the .NET interface to GINO. This has been added. | 7.0a |
| 1657 | GINOGRAF | A problem with displaying axes annotation associated with small values has been fixed. | 7.0a |
| 1682 | The routine ggEnqAxesAnnotation() has been modified to return the actual number of decimal places and power factor used in the specified axes, according to the current scaling, rather than the values set by the routine ggSetAxesAnnotation(). | 7.0b | |
| 1689 | Utilizing the missing value option failed to prevent a log scaling warning message if the missing value chosen was -'ve. The warning has been switched off in these circumstances as with a use of ggMoveToGraphPoint to a -'ve 'missing' value on log axis. | 7.0c | |
| 1660 | GINOSURF | The routine gsFillTriangulatedContourMap() incorrectly used the first colour fill index at the top of the data range instead of at the bottom. This has been corrected so the index array is used correctly. | 7.0a |
| 1673 | A problem triangulating data sets with large data values (>100,000) has been fixed. | 6.5c | |
| 1648 | GINOMENU for Windows | A problem occurred when enquiring the contents of an array grid cell when not visible due to the scrolled position - a value of zero was always returned. This has been fixed to return the correct contents. | 7.0a |
| 1649 | Using the routine gmClearGraphicsFrame() did not work correctly if the drawing mode was in a non-default state. The mode is now set to default as part of the clearing operation. | 7.0a | |
| 1655 | The length of the TTY widget prompt string has been increased from 32 to 256 characters. | 7.0a | |
| 1658 | An error in the F90 interface to GINOMENU meant that the text and value array colour settings were not set are requested. This has been fixed. | 7.0a | |
| 1664 | The algorithm for sorting table box entries has been re-written to be almost instantaneous. | 7.0b | |
| 1665 | Attempting to utilize Japanese character sets results in mixed results in different widgets. These have been resolved. | 7.0b | |
| 1667 | Using an error box from an active window now reverts control back to that active window rather than switching back to the master window and making all windows active. | 7.0b | |
| 1669 | A problem using gmSaveTextToFile() with large Table Box widgets has been fixed. | 7.0b | |
| 1674 | Using the GOPENPRINTER option for gmPrintTextWidget() caused only a blank page to be output. This has been fixed, so the complete file is now printed. | 7.0c | |
| 1675 | The TabStop Editor was incorrectly constructed when an application was using grid mode. Grid mode is temporarily switched off now during its operation. | 7.0c | |
| 1678 | A problem supplying NULL array grid axis lables through the setting of the gmXText and/or gmYText widget properties has been fixed. | 7.0d | |
| 1681 | Using error box and browser controls now correctly revert focus to last window and maintain current active window where relevent. | 7.0f | |
| 1686 | Incorrect fonts were setup when a second attempt to initialise GINOMENU was made. This has been fixed, allowing multiple initialisation and close sequences to be made in one application. | 7.0f | |
| 1691 | An application which re-initialised GINOMENU failed to display any graphics frames on the second loop. This has been fixed. | 7.0g | |
| 1692 | A problem suppliying small return string buffers to GINOMENU enquiry routines has been fixed. | 7.0g | |
| 1650 | GINOMENU Studio | Internal logic prevented docking panes to be added to Master MDI forms. This has been corrected | 7.0a |
| 1651 | When adding a text entry to a scroll bar, the incorrect scroll bar properties were highlighted for this widget. This has been corrected. | 7.0a | |
| 1652 | Due to the now permanent availability of the Code Editor, there were a number of circumstances, when switching focus, whereby the recently editied contents of a widgets callback code block could be lost. These have been eliminated. | 7.0d | |
| 1653 | Any internal local variables are now added after the user's 'local variable' code block to allow use of implicit none etc. | 7.0a | |
| 1661 | The name of the project manifest file (recorded in the resource file) matched the name of the project rather than the source file name. This has been corrected. | 7.0b | |
| 1662 | Problems with linking occurred if library or module paths settings contain spaces within. All file and path names are now encompassed between quotes to prevent this. | 7.0c | |
| 1663 | Studio has been updated to cater for the changed format of the Absoft v 10 compile time and link error messages. | 7.0c | |
| 1668 | The F90 code generation was found to to faulty in some circumstances where string arguments contained commas. This has been fixed. | 7.0c | |
| 1676 | Changing the name of a widget did not change the uses of that widget in any menu bar entry or tree view widget code blocks when requested. This has been fixed. | 7.0f |
Page 1 of 1 |