Tuesday, November 25, 2008

New Style Rule Tool in the GT/Metadata Explorer

The released version of the GT/Metadata Explorer has a new feature not seen in the beta versions. On the Find Feature tab, you can query any feature in the GIS by selecting the feature type and providing attribute value criteria, specifying a feature’s FID, or performing a query defined in the metadata. Beta versions provided the user with the ability to show Attribute Info, to perform a Connectivity Search, and to perform an Ownership search. The released version provides a new Style Rule Info command which will display all style rules associated with the selected feature, indicate which rules are triggered by the selected feature’s attributes values, and provide a detailed explanation as to why a style rule is selected or rejected.

In the example below, a Guy query is performed with several Guy features resulting in the result list. A specific Guy is selected in the results to enable the Attribute Info, Style Rule Info, Connectivity Search, and Ownership Search commands.



If the Style Rule Info button is pressed, the following form is displayed showing all of the style rules associated with the selected Guy feature. The Style Rules are evaluated to determine which style rule will be triggered based on the selected feature’s attribute values. The trigger rule is highlighted in Yellow:



An additional Feature of the Style Rule Info form is the Explain button. By selecting a style rule from the list, the Explain button. Pressing the Explain button will show a detailed explanation as to why the selected style rule was trigger or rejected.

If the triggered style rule is selected and the Explain button is pressed, the following form is displayed:



This form shows a decomposition of the selected style rule in a tree view. At the bottom of the form, a list of the selected feature’s attributes is presented along with the associated values and types. In the example above, the Style Rule is:

STATE=’In Service’ AND (GUY_TYPE = ‘SPAN’ OR GUY_TYPE = ‘SPAN GUY’)

The selected feature’s STATE attribute is set to ‘In Service’ and the GUY_TYPE is set to ‘SPAN’. The style rule is decomposed into 3 clauses:

GUY_TYPE = ‘SPAN GUY’

GUY_TYPE = ‘SPAN’

STATE = ‘In Service’

Each clause is evaluated to show if it is True (green) or False (red).

The two GUY_TYPE clauses are then OR’ed together, one is TRUE and one is FALSE, so the resulting value is TRUE.

The STATE clause is evaluated to TRUE and AND’ed with the result of the two GUY_TYPE clauses being OR’ed together, and is also TRUE.

The final result (top of the tree) is TRUE and is why the Style Rule is triggered.

A Record View of the Explanation is also available. While the information provided is the same as that shown in the Tree View, the Record View provides a slightly different perspective.



We can also select rejected Style Rule as shown in the following example:









New Vertex Edit Commands in GTViewer

GTViewer Version 8.0 provides a new set of Vertex Edit commands to enhance the redline edit capabilities. GTVx has had vertex edit capability for several years in the form of Add New Vertex and Delete Vertex. These two commands plus the new Break at Vertex command are now available in GTViewer and GTVx.

The Vertex Edit commands can be very useful when editing redline element such as Lines and Shapes that have vertex points defining their geometries. By using the Select command, a redline element can be selected for edit (it changes to the highlight color and the vertex nodes are shown with handles). The user has always been able to click on a vertex handle and drag the version to a new location. With the new vertex commands, the user can now perform three more types of edits.

Add New Vertex

To add a new Vertex to a Line or Shape, select the element, then right click on the spot to insert the new vertex. When the right click is pressed, a menu will display with the available options. The Add New Vertex option can be selected:

Once the new vertex is added, a new vertex handle will display:


The new Vertex can be moved around just like any other vertex in the selected element:




Delete Vertex

If you right-click the mouse on one of the vertex handles, you will get different options. The Delete Vertex and Break at Vertex option will be enabled. If you select Delete Vertex, the selected vertex will be deleted:



The deleted vertex is removed and the geometry of the element is updated to reflect the change:

Break At Vertex

The Break at Vertex option is new to both GTVx and GTViewer. By right-clicking on a vertex, the Break at Vertex option will be available on the menu.

For a line element, two new line elements will be created. The selected vertex will now be a coincident point for the two elements, but not shared by the elements. For a shape element, a line will be created with the starting and ending point at the selected vertex.


Once an element is broken at a vertex, the vertex can be moved independently of the other element:

Monday, November 24, 2008

GTI Releases the GT/Metadata Explorer



Graphic Technologies, Inc. (GTI) today announced a new product called the GT/Metadata Explorer. This product is a companion application for Intergraph’s G/Technology GIS System and provides a cache of tools for navigating, reporting, validating, and editing the G/Technology metadata as well as querying, tracing, and reporting the G/Technology GIS data. The GT/Metadata Explorer is ideal for getting a grip on the complexities of the G/Technology metadata, identifying metadata problems, traversing feature connectivity and ownership, and making metadata modifications.

The GT/Metadata Explorer’s provides the user with a very easy way to visually traverse the many relationships defined by the G/Technology metadata. For example, a user can “point-and-click” navigate from a Legend definition to a Feature hosted by that Legend, then to the Style Rules associated with the Feature, and finally to the Style Definition used by the Feature’s Style Rule. Another example would be to navigate from a Feature’s definition to the Feature’s Components, then to the Component’s Attributes, and even to the Component Attribute’s Value List. The GT/Metadata Explorer also provides the ability to edit commonly changing parts of the G/Technology metadata including the Style Rules, Style Definitions, and Value List tables.
The GT/Metadata Explorer also provides the ability to find a specific feature in the GIS data by
querying on one or more of the feature’s attribute values or by the feature’s Feature Id. The attribute information for the queried feature can be displayed showing all associated database records, and the queried feature’s style rule information can be analyzed to see which rules in the metadata are actually triggered by the feature along with an explanation of why each rule is rejected or accepted. More advanced feature analysis can also be performed with a Connectivity Search which visually traces the feature’s connectivity relationships to analyze how the feature is connected to other features in the GIS data. An Ownership Search is also provided to traverse the parent/child relationships of the queried feature in a visual way.

The GT/Metadata Explorer leverages technology GTI developed for its G/Technology Data Extraction tools which export Intergraph’s G/Technology GIS data to other formats. Building on the strengths of these tools, the GT/Metadata Explorer is very easy to use and requires only a connection to the Oracle database to operate; no setup or configuration is required, and support for multiple G/Technology databases is provided. For more information on the GT/Metadata Explorer or other GTI products, please visit http://www.gti-us.com/.

Sunday, November 16, 2008

GTV .NET Control Version 8.0.0.14 is Available


The GTViewer .NET Control for Windows version 8.0.0.14 is Available.
------------
08.00.00.14 - 11/16/08
------------

- FIX - #5582 - Problem with Feature Tooltips and Point features. Introduced
with #5202.

------------
08.00.00.12 - 10/21/08
------------
- FIX - #5550 - Shape with Hole element did not default to the right fill color when defining a ColorValue in the style rules.
------------
08.00.00.11 - 10/20/08
------------

- NEW - #5546 - TapAndHoldDelay property added so that the tap and hold delay
and be set to a custom value. Default has also been changed
from 300 milliseconds to 800.
------------
08.00.00.10 - 10/15/08
------------
- NEW - #5540 - Zoom Center action can now be set to Center View (default), Trigger
an Event, or do nothing. The ZoomClickAction property has been added. The ZoomClickActionEvent has been added.

------------
08.00.00.09 - 10/13/08
------------
- FIX - #5536 - The FeatureTooltipEvent did not check to see if the event has
been handled before raising it. This probablem affected C# apps that did not handle the event.

------------
08.00.00.08 - 10/10/08
------------
- FIX - #5531 - DataFile returned blank when a .gtx file was opened.
------------
08.00.00.07 - 10/09/08
------------
- NEW - #5526 - DataFile property added to return the session's parent data file.

------------
08.00.00.06 - 10/03/08
------------

- NEW - #5444 - PromptDefaultComparison supported in Queries.
- NEW - #5446 - Support for Ends With, Contains, and Exact Matches for queries.
- FIX - #5458 - Emphasize Session Graphic mode was not graying out shape element
using a BorderColor style property.

- FIX - #5460 - Changes to the drawing of shape using ShapeBorderColor to match
GTViewer.

- FIX - #5497 - Softbutton status would not be updated until a mouse move event
occurred. For a UMPC, this does not happen. Related to #5148.

- NEW - #5500 - DrawingAllowed Property added.

- FIX - #5501 - ActivateDrawCircle, ActivateDrawEllipse, ActivateDrawDelete,
ActivateDrawFreehand, ActivateDrawLine, ActivateDrawArea, and ActivateDrawRectangle will now return false if drawing is not allowed.

------------
08.00.00.05 - 09/22/08
------------

- FIX - #5425 - Only the last MrSID raster file defined with RasterPC was being
drawn.

- FIX - #5426 - ActivateCaptureMode will now return false for Point and Point with
Zoom when the allowCancel is true or allowInteractive is false.

- FIX - #5428 - ActivateCaptureMode will now return false for Point With Confirmation, Point with Confirmation and Zoom, Line and Area when the
allowInteractive is false.

- FIX - #5430 - AllowCapture flag did not work for Point_With_Confirmation and
Point_With_Confirmation_And_Zoom.

------------
08.00.00.04 - 09/16/08
------------
- FIX - #5396 - ActivateMagnifyMode always returned True even when no file was
open.

- FIX - #5397 - Magnify Mode could not be activated via the Mode property.
- FIX - #5398 - Mode set to None when a file is closed.
- NEW - #5400 - SendMouseClick and SendMouseMove method have been added.
- CHG - #5401 - New Capture Modes: Capture_Point_With_Zoom, Capture_Point_With_Confirmation_And_Zoom, Capture_GPS_Point_With_Zoom.

- FIX - #5402 - UDLS definitions using TrueType fonts were failing.
- FIX - #5405 - PointCaptured event was not being fired when the Finish button was
pressed in Capture_GPS_Point mode.

- CHG - #5407 - Point_With_Keys capture mode added to CaptureMode structure to be
compatible with the PGTV Control. Capture mode is not supported in the GTV Control.
- CHG - #5409 - Documentation renamed to GTV-PGTV-Control.doc.

------------
08.00.00.03 - 09/11/08
------------
- CHG - #5370 - FeatureTooltipMinimumThreshold and FeatureTooltipMaximumThreshold
will also be accepted for FeatureTooltipMinimumZoom and FeatureTooltipMaximumZoom with GetDataProperty and SetDataProperty.

- NEW - #5371 - Non-Category MrSID raster support added.
- FIX - #5373 - Default Background color with .gtm files was not always getting
set to the right color with an explicit BackgroundColor entry in the .gtm file.

- NEW - #5374 - The Raster Display flag can be used with the OpenFile and
CreateSession methods so that the default setting can be used for the initial view and the view does not have to be refreshed to set the initial raster display.

- FIX - #5375 - FeatureTooltipMaximumThreshold and FeatureTooltipMinimumThreshold
were not working (as defined in [Additional Properties]).

- FIX - #5377 - CurrentColorId, CurrentStyleId, CurrentWeight, CurrentExtendedStyle
will now ignore out of range values.

------------
08.00.00.02 - 09/08/08
------------
- FIX - #5363 - MinorPerMajor Data Property did not work correctly with
SetDataProperty.

- FIX - #5365 - FixedSymbolScale not returning correct value.

- FIX - #5366 - The FeatureToolTipMinimumScale, FeatureTooltipMaximumScale,
FeatureTooltipMinimumZoom, FeatureTooltipMaximumZoom, FeatureToolTipOmitBlankValues properties with SetDataProperty were all returning false.

- FIX - #5367 - The FeatureToolTipMaximumScale property was returning the wrong value with GetDataProperty.

- FIX - #5368 - FeatureToolTipMinimumScale did not work when set to 0.

------------
08.00.00.01 - 09/06/08
------------
- NEW - #5310 - LastExportFeatureCount has been added to GetDataPropert and will
return the number of elements last exported.

- FIX - #5321 - SetCurrentData always returned false.

- FIX - #5326 - The EmphasizeSessionGraphics Data Property was returning an
invalid value.

- FIX - #5331 - FeatureTooltipMinimumScale did not work with GetDataProperty or
SetDataProperty.

- FIX - #5342 - FixedSymbolScale and FixedSymbolZoom were returning each other's
values with GetDataProperty.

- FIX - #5344 - The MeasurePrecision data property was not working.

- FIX - #5346 - The FeatureToolTipMaximumZoom and FeatureTooltipMinimumZoom data
properties did not work with GetDataProperty and SetDataProperty.

- FIX - #5347 - CoordinateReadoutMode did not work with GetDataProperty and
SetDataProperty.

- FIX - #5349 - FixedSymbolScale, FixedSymbolZoom, DefaultScale, DefaultZoomLevel,
MeasureFactor will return False for values less than or equal to 0 with SetDataProperty.

- FIX - #5350 - MinZoomLevel, MaxZoomLevel, MinZoomScale, MaxZoomScale,
FeatureToolMinimumZoom, and FeatureTooltipMaximumZoom will now return
false if set to a value less than 0 with SetDataProperty.

- FIX - #5353 - Problem reading Arc and Ellipse elements from a .GTS file.

- NEW - #5354 - Upgraded from VS2005 to VS2008. Still supports VS2005 and still uses the .NET Framework 2.0.

- NEW - #5355 - Toolbox Icon set to GT Logo.

- NEW - #5356 - FileVersion property of GTVControl.dll set to auto-increment.

------------
07.00.00.79 - 08/23/08
------------
- FIX - #5288 - Capture Line and Area modes were not working correctly.
------------
07.00.00.78 - 08/22/08
------------
- NEW - #5278 - Basic Printing Functionality: Print, PrintPreview, PringPage Setup.
- NEW - #5279 - The CoordinateReadoutPrecision and CoordinateReadout data properties are now available.

- FIX - #5280 - EmphasizeSessionGraphics data property did not return True when set.

- FIX - #5284 - Raster basepath was not correct when using .gtm or .gts files.

PGTV .NET Control version 8.0.0.4 is Available


The PGTViewer .NET Control for Window Mobile version 8.0.0.4 is available.

------------
08.00.00.04 - 11/16/08
------------

- NEW - #5541 - Zoom Center action can now be set to Center View, Trigger an Event, or do nothing. The ZoomClickAction property has been added. The ZoomClickActionEvent has been added.
- NEW - #5547 - TapAndHoldDelay property added so that the tap and hold delay and be set to a custom value. Default has also been changed from 300 milliseconds to 800.
- FIX - #5581 - Problem with Feature Tooltips and Point features. Introduced with
#5204.
------------
08.00.00.03 - 10/09/08
------------
- NEW - #5527 - CurrentFile, SessionFile, and DataFile Properties added to match interface with the desktop version of the control.
------------
08.00.00.02 - 10/03/08
------------
- NEW - #5445 - PromptDefaultComparison supported in Queries.
- NEW - #5447 - Support for Ends With, Contains, and Exact Matches for queries.
- FIX - #5459 - Emphasize Session Graphic mode was not graying out shape element using a BorderColor style property.
- FIX - #5498 - Softbutton status would not be updated until a mouse move event
occurred.
- NEW - #5502 - DrawingAllowed Property added.
- FIX - #5503 - ActivateDrawCircle, ActivateDrawEllipse, ActivateDrawDelete,
ActivateDrawFreehand, ActivateDrawLine, ActivateDrawArea, and ActivateDrawRectangle will now return false if drawing is not allowed.

------------
08.00.00.01 - 9/23/08
------------

- FIX - #5364 - MinorPerMajor Data Property did not work correctly with
SetDataProperty.

- FIX - #5399 - Mode set to None when a file is closed.

- FIX - #5403 - UDLS definitions using TrueType fonts were failing.

- NEW - #5404 - New Capture Modes: Capture_Point_With_Zoom, Capture_Point_With_Confirmation_And_Zoom, Capture_GPS_Point_With_Zoom.

- FIX - #5406 - PointCaptured event was not being fired when the Finish button
was pressed in Capture_GPS_Point mode.

- NEW - #5408 - SendMouseClick and SendMouseMove method have been added.

- CHG - #5410 - Documentation renamed to GTV-PGTV-Control.doc.

- CHG - #5411 - Folder under Start/Program files changed to PGTV Control.

- FIX - #5427 - ActivateCaptureMode will now return false for Point, Point with
Keys, and Point with Zoom when the allowCancel is true or allowInteractive is false.

- FIX - #5429 - ActivateCaptureMode will now return false for Point With
Confirmation,Point with Confirmation and Zoom, Line and Area when
the allowInteractive is false.

- FIX - #5431 - AllowCapture flag did not work for Point_With_Confirmation and
Point_With_Confirmation_And_Zoom.

- NEW - #5433 - GetDataRange method added.

- NEW - #5435 - ColorTable property added.

- FIX - #5436 - GetFontList did not work.

- FIX - #5437 - SetDataProperty and GetDataProperty would not work with
PointFeatureToleranceMode.

- NEW - #5438 - MaxRecordsReturned added to GetDataProperty and SetDataProperty.

- CHG - #5439 - Default MaxRecordsReturned changed from 75 to 100.

------------
07.00.00.30 - 8/24/08
------------
- FIX - #5281 - EmphasizeSessionGraphics data property did not return True
when set.

- NEW - #5282 - The CoordinateReadoutPrecision and CoordinateReadout data
properties are now available.

- NEW - #5291 - EmphasizeSessionGraphics property has been added.

Friday, November 14, 2008

GTVx version 8.0.x.7 is Available



Version 8.0.x.7 of GTVx is available.

-----------------------
08.00.00.07 - 11/14/08
-----------------------
- FIX - #5564 - Problem introduced with #5442. The Mode 2 for QueryInitialize did not work.

- FIX - #5580 - Problem with Feature Tooltips and Point features. Introduced with #5205 and #5206.

-----------------------
08.00.00.06 - 10/23/08
-----------------------
- FIX - #5553 - Updates to the Feature Tooltips to match the changes made in GTViewer.

- NEW - #5554 - Data Monitor Bitmap Selection Tolerance can be adjusted with the DMBitmapSelectionTolerance Data Property.

-----------------------
08.00.00.05 - 10/08/08
-----------------------

- FIX - #5525 - Raster paths were not resolved correctly when a session file referenced a .gtx file.

-----------------------
08.00.00.04 - 10/06/08
-----------------------
- FIX - #5518 - DMAddBitmap was not working correctly.

-----------------------
08.00.00.03 - 10/06/08
-----------------------

- FIX - #5486 - Requery populated the wrong prompt when hidden prompts were used in the query definition.

- FIX - #5489 - ElementDeleted event are now stored and send after all of the elements are deleted instead of sending as they are deleted.

- CHG - #5492 - Highlighted Text and symbols changed so that it doesn't bold (added in #5002-3).

-----------------------
08.00.00.02 - 09/28/08
-----------------------

- NEW - #5443 - PromptDefaultComparison supported in Queries.
- FIX - #5449 - The Get Range call on a session category with no element would fail, yet the check to determine if a category is out of range and should be skipped was still processed and could possibly overflow.

- FIX - #5453 - Better cleanup of bitmap resources when view closes or changes size.

- FIX - #5454 - Unreleased memory when invalid filter file was loaded.

- FIX - #5455 - Better bitmap resource management for initial screen.

- FIX - #5457 - Emphasize Session Graphic mode was not graying out shape element using a BorderColor style property.

- NEW - #5473 - GetDisplayFilterString and SetDisplayFilter methods have been added.

- FIX - #5475 - Count Options did not disable a mode's sub-options when the mode was not active.

- FIX - #5477 - In the Count Options dialog, the Count Highlighted Features in Shape option was available even when no shape was selected.

- FIX - #5483 - Better resource management with logo bitmap displayed when no file is open.

- NEW - #5484 - Updated to InstallShield 2009.

-----------------------
08.00.00.01 - 09/14/08
-----------------------

- FIX - #5154 - Adjustments to Style Manager to prevent style gaps at boundary threshold values.

- NEW - #5157 - Sorting of Query Result records on all columns and support for clicking on column headers for sorting.

- FIX - #5159 - Error message incorrect for Invalid Address Query.

- NEW - #5208 - The PointFeatureToleranceDependent and PointFeatureToleranceFixed entries has been added to the Data Property List and Additional Properties section.

- NEW - #5209 - The PointFeatureToleranceMode entry has been added to the Data Property List.

- NEW - #5210 - PointFeatureTolerance was not working for both fixed and zoom dependent features.

- FIX - #5231 - Cancel and Requery buttons would swap places on a resize.

- FIX - #5240 - Moving Selected elements did not clear the previous Style object, and if the last object changed a text symbol, the moved element would end up with a different symbol.

- CHG - #5271 - Image Preview Tabs in Attribute Info Dialog will now show the image Filename in the title bar.

- FIX - #5272 - Column Headers were not being set correctly in the Link tabs in the Attribute Info dialog when more than one records was present.

- FIX - #5273 - When Multiple Link records were available for a single Link definition, the grid view was not correctly initialized to display all of the link records.

- CHG - #5274 - All Link Tabs in the Attribute Info dialog will now use the records on a row approach even if there is only one record.

- FIX - #5275 - Location based detail needed to turn off border mask when locating on the detail.

- NEW - #5378 - Add Vertex to Selected Element.

- CHG - #5379 - Delete Vertex will now reselect the modified element.

- FIX - #5380 - Breaking an element at a vertex did not refresh the view.

- CHG - #5381 - Breaking a shape will now create a linestring. The end points of the line string will be the breaking vertex.

- FIX - #5387 - The CurrentColor could not be set greater than 5 in a Session file (.gts or .gtx) and can go to 7.

- CHG - #5389 - New Product logos are now used.

GTViewer Version 8.0.x.15 is Available



GTViewer version 8.0.x.15 is available.

-----------------------
08.00.00.15 - 11/14/08
-----------------------

- FIX - #5565 - Problem introduced with #5442. The Mode 2 for QueryInitialize did not work.

- FIX - #5576 - Problem with Feature Tooltips and Point features. Introduced with #5205 and #5206.

- NEW - #5577 - DefaultGPSReceiverType has been added to the Additional Properties section so that the default GPS receiver type can be specified in the .gtm file.

- NEW - #5578 - The GTVx.doc is now delivered with GTViewer as it contains the API specification for GTViewer.

- NEW - #5579 - The GTViewer-DOTNET-Interface.doc interface is now delivered with GTViewer.



Monday, November 10, 2008

Using Visual Studio .NET to develop External Applications for GTViewer

Almost from its beginning, GTViewer has been extendible with External Applications. These External Applications can be for tracing, data collection, importing data, data monitors, etc. GTViewer has been supporting External Applications though a technique called Dependency Injection. An External Application is written as a COM object with an interface to GTViewer; then entries in the .GTM File define the COM objects that can be used with the dataset. GTViewer dynamically adds the External Applications to its menus when the dataset is opened and will launch the External Applications when they are selected. The External Applications are run inside of GTViewer and appear seamlessly integrated.

In the past, almost all GTViewer External Applications were written in Visual Basic 6 (VB6). There were a few written in Visual C++ and even some written in Excel (VBA), but the majority were in VB6. Not only is VB6 getting a little long in the tooth (released in 1998), but Visual Basic .NET and the .NET Framework have finally gained acceptance as a development platform and the .NET savvy development crowd is rapidly growing.

Strangely enough, GTViewer has been able to support .NET External Applications all along, and GTI had even provided a template .NET application several years ago. However, until Microsoft ended its support for VB6 in March 2008, the idea of using .NET for the development of External Applications had gained little traction.

There are many advantages to using Visual Studio .NET when developing GTViewer External Applications. With Visual Studio .NET 2005 or 2008, the development environment alone is enticing enough to move from VB6 to Visual Studio .NET. The .NET Framework also provides many benefits from a developer’s point of view such as the Command Language Runtime, Advanced Memory Management, and a rich set of base classes to work with. GTViewer External Applications written with VB6 were also difficult to debug. The GTViewerAppDebugger control had to be used, and it had its own set of limitations. With Visual Studio .NET, the GTViewerAppDebugger is no longer needed and debugging an External Application has never been simpler.

The disadvantages of using Visual Studio .NET when developing GTViewer External Application are also worth mentioning. First, VB6 and VB.NET are similar, but definitely not the same. Some degree of learning is required when moving from one to the other. On the other hand, Visual Studio .NET is not limited to VB.NET and if a developer is more comfortable with C++ or Java, then C# is an alternative to VB.NET. However, the “.NET” part of these languages is still something that will need to be learned even if it is pretty easy to do. The second disadvantage is that the .NET Framework will now be a requirement for the external applications to run. While most machines will have some version of the .NET Framework installed already, the latest versions are usually not. You can, however, target the version of the .NET Framework you want your applications to use and can possibly eliminate this problem by using an older version of the .NET Framework that you know is already installed. In the worst case, you will simply have to deploy an appropriate version of the .NET Framework with your External Applications.

I have prepared a fairly detailed document (download here) describing exactly how to extend GTViewer with an External Application using Visual Studio .NET 2005 or 2008. This document goes through the standard items that will be required in all GTViewer External Applications written with .NET and also presents a full example. The example is the Highlight by Phase application which highlights all electric features in the view to a color corresponding to their phase. The example works with GTI standard Electric/Gas demo dataset, but it can be easily modified to work with most electric data.

Sunday, November 09, 2008

GTViewer Version 8.0.x.14 is Available



GTViewer version 8.0.x.14 is available.

-----------------------
08.00.00.14 - 10/4/08
-----------------------

- NEW - #5562 - UseLocateZoomAsMinimum entry has been added to Additional Properties to force Thematic Queries to use the query specified locate zoom as a minimum zoom level.


- NEW - #5563 - mode has been added to the base location options with Links. This option will extract the filename from the path in the File attribute.


-----------------------
08.00.00.12 - 10/22/08
-----------------------

- FIX - #5552 - Feature Tooltips with a blank heading would put an empty line at the beginning of the tooltip.

- NEW - #5554 - Data Monitor Bitmap Selection Tolerance can be adjusted with the DMBitmapSelectionTolerance Data Property.

-----------------------
08.00.00.11 - 10/16/08
-----------------------

- CHG - #5533 - If FeatureTooltip Entries are longer than 200 characters, they will now automatically be broken into smaller lines for extracts.

- NEW - #5534 - Set GPS Reference Point has been added to right mouse menu.

- NEW - #5537 - Clear GPS Reference Point has been added to right mouse menu.

- NEW - #5538 - Attribute Info dialog box now support sorting rows when column is clicked.

- NEW - #5539 - Data Monitor Bitmap Selection Tolerance can be adjusted with the DMBitmapSelectionTolerance Data Property.

- NEW - #5542 - ResetFeatureTooltips entry is now supported in the Additional Properties section of the .gtm file and can be used in the addprop.ini file.

-----------------------
08.00.00.10 - 10/06/08
-----------------------

- CHG - #5521 - If the Keep GPS Indicator in View mode is on and the Locate Single Find option is on, a query with one record will automatically use the Set Ref Point command instead of the Locate command.


- FIX - #5522 - DMAddBitmap was not working correctly.

-----------------------
08.00.00.09 - 10/02/08
-----------------------

- CHG - #5491 - Highlighted Text and symbols changed so that it doesn't bold (added in #5002-3).

-----------------------
08.00.00.08 - 09/29/08
-----------------------


- FIX - #5485 - Requery populated the wrong prompt when hidden prompts were used in the query definition.


- FIX - #5487 - QueryActivate was not populating prompt beyond 3 prompt when Requery was used.

-----------------------
08.00.00.07 - 09/28/08
-----------------------

- FIX - #5474 - Count Options did not disable a mode's sub-options when the mode was not active.

- FIX - #5476 - In the Count Options dialog, the Count Highlighted Features in Shape option was available even when no shape was selected.

- FIX - #5478 - Better resource management in Printing.

- FIX - #5479 - Fix to problem introduced in 5451 with Text Element pen resource management.

- FIX - #5480 - Uninitialized Variables on GetAttributeInfoFromElement was leaving uninitialized variable in TestPointOnElement calls.

- FIX - #5481 - Better resource management in Symbol Dialog box.

- NEW - #5482 - Updates to the GTViewer.doc document.

-----------------------
08.00.00.06 - 09/26/08
-----------------------

- NEW - #5442 - PromptDefaultComparison supported in Queries.

- FIX - #5448 - The Get Range call on a session category with no element would fail, yet the check to determine if a category is out of range and should be skipped was still processed and could possibly overflow.

- FIX - #5450 - Better cleanup of bitmap resources when view closes or changes size.

- FIX - #5451 - Better cleanup of pen resources for Text Element drawing.

- FIX - #5452 - Unreleased memory when invalid filter file was loaded.

- FIX - #5456 - Emphasize Session Graphic mode was not graying out shape element using a BorderColor style property.

- FIX - #5461 - Static information used by GPS Reference point was corrupting .gtx files (problem introduced with 5414).

- NEW - #5462 - Keep GPS indicator in view switch is automatically turned off when a query form is displayed.

- NEW - #5463 - Queries can now have default Display Preset associated with them.

- FIX - #5465 - Export to shapefile did not export element without embedded data (problem introduced with 5417).

- FIX - #5466 - Export to shapefile did not export group elements if they did not have embedded data.

- FIX - #5467 - Export to shapefile was reading elements with an embedded style as an element with embedded data.

- NEW - #5470 - Set GPS Reference Point from Query Results has been added.

- NEW - #5472 - GetDisplayFilterString and SetDisplayFilter methods have been added to the View object.


-----------------------
08.00.00.05 - 09/22/08
-----------------------

- NEW - #5417 - Export to Shape will allow any embedded record to be selected.

- FIX - #5418 - GTField encoded string are now displayed and exported correctly.

- CHG - #5419 - GTViewer will convert GT/Field Table.Attribute names to just the Attribute name when the table is the same as the attribute prefix. Export Data and Export to Shapefile are affected by this change.

- CHG - #5423 - GTViewer's Export Data feature will now will consolidate records using the same table but with different attributes.

-----------------------
08.00.00.04 - 09/18/08
-----------------------

- NEW - #5414 - GPS Reference Point added.

- NEW - #5415 - Trimble Simulation session are now saved in the registry.

- NEW - #5416 - Installation upgraded to InstallShield 2009.

-----------------------
08.00.00.03 - 09/15/08
-----------------------

- CHG - #5395 - Update to the new program icons.

-----------------------
08.00.00.02 - 09/14/08
-----------------------
- FIX - #5386 - Color Combo box was not setting to the session active color.


- FIX - #5388 - App Timer for Application Timeout was causing final cleanup from being finished.

-----------------------
08.00.00.01 - 09/14/08
-----------------------

- FIX - #5340 - Problem with Locate Address processing the locate twice when clicking on the result.

- FIX - #5341 - Locating on an Address would some times be zoom in close and some times not for the same feature.

- NEW - #5382 - Vertex Edit functionality (Add Vertex, Delete Vertex, Break element at Vertex) has been added.

- NEW - #5383 - Feature Tooltip button added to toolbar.


- NEW - #5384 - New Product logos are now used.

- CHG - #5385 - New End User License Agreement.

-----------------------
07.00.00.35 - 08/29/08
-----------------------

- NEW - #5318 - DefaultGTM.ini support added.

GTViewer Version 8.0 is Released




GTI announces the release of GTViewer Version 8.0. Other products in the GTViewer suite including GT/Field, GTData, GTVx, and the GTViewer .NET Controls have also been updated to Version 8.0.

GTViewer 8.0 includes a variety of productivity enhancing features and refinements including Feature Tooltips, a GPS Reference Point feature, and advanced Redline edit capabilities. GTVx, the ActiveX Control version of GTViewer, has also been updated to Version 8.0 and keeps pars with GTViewer's new features.

GT/Field 8.0 is a dramatic upgrade from previous versions. It now provides a GUI-based, forms-driven Administrative tool for creating and maintaining Data Collection applications. GT/Field is no longer an add-on to GTViewer or Pocket GTViewer, but is instead a stand-alone application designed specifically for the best data collecting experience. Along with the new Administrator, GT/Field provides two versions of the client: GT/Field Pro for Windows laptops and tablets, and GT/Field for Windows Mobile for devices.

GT/Data 8.0 provides several new tools as well as many new features for its existing toolset. New tools include GTSumGtg and GTDataSum which provide statistical information about GTViewer data. The GT2CSV tool has also been provided to generate .csv files from GTViewer data on the command-line (as it can be done within GTViewer). A new set of tools has also been provided for more sophisticated Incremental Data Update support and to determine the data differential between two GTViewer datasets.

The GTViewer .NET controls have matured in Version 8.0 to become very capable and very powerful development tools; in fact, both GT/Field 8.0 clients were built using the the new GTViewer .NET controls. The .NET Controls can be used with VB.NET or C# (Visual Studio 2005 or 2008) to add GTViewer’s functionality to any .NET application. While similar in concept to the GTViewer ActiveX Control (GTVx), the .NET controls were designed specifically for .NET development and take advantage of many features this development platform offers. The .NET Controls can be used to build custom applications specific to your workflows, or they can be used to integrate GIS capabilities into your existing mobile or desktop applications.