Thursday, July 31, 2008

11 Things you may not know about GTViewer (and possibly should be using)

I have put together a list of things in GTViewer that I see users wanting to do, but are not aware that they already have the capability to do them. Many of the features in this list are new or relatively new, but some have been available since version 1.0. I hope this list will show you something new that you are unfamiliar with or reacquaint you with an older feature that you might now be able to use.


1. Feature Tooltips

Version 7.0.x.17+. The Feature Tooltip functionality provides tooltips containing a feature’s attribute information by simply hovering the mouse cursor over a feature. The features that have tooltips and the information displayed in the tooltips are specified in the .GTM file. While this feature is relatively simple in what it is does, it can provide a very quick way to see important information with minimal user interaction.



For more information on Feature Tooltips, click here.


2. Redline Posting

Version 7.0.x.24+. Redline posting added to GTViewer to support GT/Field. However, the need for redline posting is not something unique to GT/Field, so the Post functionality was enabled even if you are not using GT/Field. The Post functionality is configured in the .GTM file and can be used to copy the user’s current session graphics (redlines) to a path on the user’s machine or a network accessible location (via a UNC name). The file that gets copied can be a .gtg file, a .csv files, a set of shapefiles, or an XML file. All redline elements that have been copied are internally marked so that they will not be copied again, or the redlines can be deleted from the user’s session. A variety of other options are available to specify how the copied file will be named and if a redline marker is to be placed on each feature whose edits have been posted (so you will know which feature have been inspected, edited, etc.).






3. Export to Shapefiles

Version 5.0.x.8+. GTViewer has had the ability to export session graphics (Redlines) to a set of shapefiles for some time now. If redlines have embedded data (such as those created by GT/Field or other inspection or inventory applications), this data will be added to the shapefile’s .dbf file. This functionality is not new, but it may have been overlooked by users that could benefit from the functionality. It is located under Draw/Export/Export as Shapefile.








4. Links and Session Links

Version 2.0.x.38+. The Link functionality allows external documents or files specified in a feature’s attribute data to be viewed. This files can be detail drawings, internal worlds, associated documents, etc. The Link functionality has grown considerably since it was introduced and now can automatically show image previews in the Attribute Info dialog and launch URLs. Session Links have also been provided to allow a Link to be placed as a redline symbol that links to an external document or URL.







For more information on Links and Session Links, click here.

5. Address Queries (Geolocating)

Version 5.0.x.1+. GTViewer supports a special Address Query which is different from the regular locate queries because it can handle street segments with address ranges. If you query for a specific address, it will find the street segment that contains the address number in its range and then will interpolate its location on the segment. Not everyone has street segment data with address ranges, but if you do, this query can be very useful.
For more information on the Address query, click here.

6. Right Mouse Attribute Info Review
Version 5.0.x.1+. GTViewer has always been very cognizant of the need to minimize the users required effort to perform a task. The concept of constantly switching modes to zoom in or out, and then to review a feature is very distasteful to GTViewer’s philosophy The Multimode Attribute Info command review attributes on a feature, and can also zoom in, zoom out, or go back to the previous view all in a single mode. The Right Mouse Attribute Info Review is another example of this approach. The user can right mouse in any mode and get a list of features that can be review at that point or any linked files that might be accessible. Since this feature was not available from the beginning, many users may not be aware of it. I have seen many users switch back to Attribute Info mode to review a feature attribute when all they had to do was right click.


For more information on the right-click review, click here.

7. GPS Tracking in View (Toolbar button)

Version 5.0.x.22+. A new toolbar button was added to unbind the GPS indicator from the view so that it will not keep setting to view to its location. If a user has the GPS tracking, it is sometimes frustrating if another area needs to be viewed temporarily and the GPS keeps moving the view back to the users physical location. Obviously, the user could turn the GPS tracking off, but for temporary work in another area, a quick click of this toolbar button is all that is needed. When the work in the other area is completed, simply click the button again and the GPS will resume its tracking in the view.



8. Fit Redlines (Toolbar button)

Version 7.0.x.25+. Backed by popular demand, the Fit Session Graphics command was added to the toolbar. The Fit Session Graphics functionality has always been available in GTViewer, but not on the toolbar. Many users use the Fit Session Graphics command to return to the area they have been working in (since it will fit only the redlines that have been drawn).



9. Latitude/Longitude Coordinate Readout and Locates

Version 5.0.x.4+. GTViewer has always been able to show System coordinates (internal units) and Computed Coordinates (real-world units) on the status bar for the mouse cursor’s current location. The Query/Locates XY command will also use the current coordinate readout settings as its units for the locate. The ability to show the coordinate readout as Latitude and Longitude was added as well as the ability to use the Locate XY command to locate on a Latitude/Longitude coordinate. It does take some configuration before the coordinate readout can use latitude and longitude (because you have to define the coordinate system of your data in the .gtm file), but it provides a new way to look at your data as well as a new way to locate a point in it. The Options/Settings dialog provides the ability to change the Coordinate Readout and the Coordinate Readout Precision.

For more information on the Coordinate Readout, click here.

10. Symbol Palettes

Version 2.0.x.4+. Symbol Palettes have provided an easy way to place your standard feature symbols as redlines early on in GTViewer’s life. Symbol Palettes are defined in the .GTM file and can be specified in groups with descriptions and can have predefined, scaled sizes to match existing facilities. This feature is certainly not new to GTViewer, but since it has to be defined in the .GTM file before it can be used, some users may not be aware of it.




11. Copy Highlighted Elements to Session

Version 2.0.x.25+. The Tools/Highlighted Elements to Session feature has been a subtle, yet powerful tool for some time. Simply put, this feature takes any highlighted element and converts it to redline graphics in the session category. By itself, this feature doesn’t do very much. However, if you use a Thematic Query that highlights a particular circuit, or a trace application that highlights trace results, or count features in a polygon with the Feature Counting functionality, you now have something significant that can be converted to session graphics. Once this data is in the session category, it can be shared with other GTViewer users, exported as a .DGN or Shapefiles, posted, edited, printed, etc.


















































Tuesday, July 29, 2008

GTViewer version 7.0.1.32 is Available



Version 7.0.x.32 of GTViewer is available.

-----------------------
07.00.00.32 - 07/29/08
-----------------------

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

-----------------------
07.00.00.31 - 07/25/08
-----------------------

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



Monday, July 14, 2008

PGTV Control version 7.0.0.26 is Available



Version 7.0.x.26 of the PGTV Control is available.


------------
07.00.00.26 - 7/10/08
------------


- FIX - #5028 - Using the filter string mode for methods using the display string, elements without data could cause problems.

- FIX - #5037 - Range computation for Group elements was not correct.

- FIX - #5054 - Modifed ASCII Read Function to account for end of file. Modified to reflect change made in 5052. Does not directly affect device platform because it only supports .gtx file.

- FIX - #5059 - Multiple Ascii datasets would sometimes get corrupted position pointers when opening .gtx file.

- NEW - #5063 - Enabled Property is now supported.

------------
07.00.00.25 - 06/13/08
------------

- FIX - #263 - The element picklist was corrupted after the use of a Feature Delete.

------------
07.00.00.24 - 06/09/08
------------

- FIX - #262 - GetFeatureInfo was not handling Data Only Elements correctly when coordinate values were requested.

GTV Control version 7.0.0.65 is Available



Version 7.0.x.65 of the GTViewer .NET Control is available.

Several versions rolled into one blog posting.


------------
07.00.00.65 - 07/13/08
------------
- FIX - #5127 - Current locale not being set in GTV_Lib.dll.


- FIX - #5128 - ASCII to Element was not working for characters greater than 127. Used when reading .gts files.

------------
07.00.00.64 - 07/10/08
------------

- FIX - #5121 - Problems with Unicode only mapped TrueType fonts (such as Wingdings) where the character code is greater than 127.

------------
07.00.00.63 - 07/09/08
------------

- FIX - #5117 - Text characters in a .gts file greater than ASCII code 127 were not getting read correctly.

------------
07.00.00.62 - 07/08/08
------------

- FIX - #5098 - Style Map was not being reset after loading a .gts file.

------------
07.00.00.61 - 07/02/08
------------

- FIX - #5083 - GetDisplayFilterString was not taking the category display status into account.

- FIX - #5084 - Category Display Status now supported by GetDisplayFilterString and SetDisplayFilterByFilterString.

------------
07.00.00.60 - 06/30/08
------------
- NEW - #5064 - Added GetDisplayFilterString method.

- NEW - #5065 - The SetDisplayFilterByFilterString method will now support *:*.0 and *.*.1 for global changes.

- CHG - #5066 - Darkened the control Enabled=false color.

------------
07.00.00.59 - 06/29/08
------------

- FIX - #5052 - Reading to the end of the data.txt and data.tab was not recognized as the end of the file for ASCII files (when using a .gts or .gtm file).

- FIX - #5057 - Multiple Ascii datasets would sometimes get corrupt position pointers when opening .gtx file.

- NEW - #5061 - Enabled Property is now supported.

------------
07.00.00.58 - 06/20/08
------------

- CHG - #5033 - Persistent Highlight has been changed from Document level to View level. Each view now has its own persistent highlighting.

- FIX - #5034 - Weighted Persistent Highlighted was not working correctly.

- FIX - #5035 - Range computation for Group elements was not correct.

------------
07.00.00.57 - 06/20/08
------------

- NEW - #5007 - Dynamic Highlight Functionality added.

- FIX - #5012 - All Data retrieval methods were not working propertly with .gtm files.

- CHG - #5013 - All Single Key data support has been removed.

- FIX - #5017 - Exporting of Element to Ascii Format did not work with embedded data.

- FIX - #5026 - Using the filter string mode for methods using the display string, elements without data could cause problems.

- FIX - #5028 - Right Mouse click did not press Finish Softbutton for Freehand, Rectangle, Circle, and Ellipse.

- FIX - #5029 - Delete button on Keyboard was not linked to Delete Softbutton for Delete Redline mode.

- FIX - #5030 - Adding new elements after a .gts file was loading would overwrite elements from previous session.

------------
07.00.00.56 - 06/17/08
------------

- NEW - #5005 - Added SetDisplayFilters method.

- NEW - #5006 - Added GetFeaturesInRange method.

------------
07.00.00.55 - 06/15/08
------------

- FIX - #262 - GetFeatureInfo was not handling Data Only Elements correctly when coordinate values were requested.

- FIX - #263 - The element picklist was corrupted after the use of a Feature Delete.

------------
07.00.00.54 - 05/20/08
------------

- NEW - #261 - The AcceptKeyboardInput property has been added.



Pocket GTViewer version 7.0.x.12 is Available


Pocket GTViewer version 7.0.x.12 is now available.

This version requires the Trimble GPS components version 2.3.

-----------
07.00.00.12 - 07/13/08
-----------

- FIX - #5129 - Problems with TrueType symbol fonts. Introduced with 5126.

-----------
07.00.00.11 - 07/11/08
-----------

- FIX - #5126 - Problem converting multibyte characters to unicode for text and symbol element display.

-----------
07.00.00.10 - 05/28/08
-----------

- FIX - PGTV #1003 - Fix for certain character sets (non-English).

-----------
07.00.00.09 - 04/16/08
-----------

- FIX - PGTV #1001 - Complex Shapes (Type 3, Extended Style 2) with a style rule containing only a Color and no border color would draw the complex shape's border with the element's shape border color. This has been changed to use the color in the style rule if the style rules defines only a color and no border color.

- NEW - PGTV #1002 - Upgraded to PFTools 2.3. Requires upgraded PFTools installed on device when using GPS.
- ssfAnt_LogSuperCorrect is no longer supported.
- intComSat_ActivationCode is no longer supported.

-----------
07.00.00.08 - 4/2/08
-----------

- CHG - Evaluation timeout extended.


Sunday, June 29, 2008

GTData version 7.0.0.9 is Available



Version 7.0.0.9 of GTData is available.

-----------
07.00.00.09 - 6/29/08
-----------

- FIX - #5063 - Computing element ranges with Data Only elements was causing the range to be invalid.

-----------
07.00.00.08 - 6/23/08
-----------

- FIX - GTD #1025 - GTShapeConv - Filter Value was listed as a Fixed value.

- NEW - GTD #1026 - GTShapeDbfConv - Filter Value info now displayed.

- NEW - GTD #1027 - GTShapeDbfConv - Will now accept a and an = as the entry delimiter.

- FIX - GTD #1028 - GTShapeDbfConv, GTShapeConv - FilterAttribute did not work well with Float type attribute.

- FIX - GTD #1029 - GTShapeConv - The OrFlag had to be set manually for FilterAttribute entries, this is now done automatically.

- FIX - GTD #1030 - GTShapeConv - The AngleInDegrees flag did not work.

- NEW - #5039 - GTQuery - Support added for the "GIS1:" marker in the Filter file descriptions generated by the FME plug-in 1.0.0.31+.




Wednesday, June 25, 2008

New Features in the GTViewer FME Plug-In

Version 1.0.0.31 of the GTViewer FME Plug-In has two new features: (1)an Enhanced Filter Creation mode and (2) an option to automatically prepend the destination feature name to the gti_styleName format attribute.

As users are creating more and more complex feature sets with the FME Plug-in, it has become apparent that the default filter file creation method in the FME Writer Plug-in has become insufficient. By default, filter files have been created for each category using the following simply procedure:


1) create a default group called Features

2) add each new filter id (which is tied to the Style Name) as a new component.


This approach is very simple and always works. The user also has the ability to define his or her own more complex filter file definition and the FME plug-in will continue to use the same filter ids as they are defined.

While the GTViewer G/Tech Loader (used to convert Intergraph’s G/Technology data to the GTViewer format) has very little in common with the FME Plug-in, the two applications do have a few conceptual commonalities. Primarily, in both conversion approaches, the Filter Id and the Style Definition are tied together to simplify the conversion process and symbology definition. Therefore, each filter id generated by both conversion methods are mapped to a specific style definition. For example, if you have a Pole feature with a dozen different symbologies, then there will be a dozen different filter ids created in the filter file and each one will be mapped to its own unique style definition. As the different styles are created for a specific feature with the G/Tech Loader, the feature and component numbers of the original feature are taken from the GIS and used to group all of the different styles/filter ids together and form a Group of all the feature’s individual styles. This approach worked so well that GTQuery was modified to accept a Feature and Component number list in addition to a filter id list when defining a query. Now, only the original G/Tech feature and component number are needed to identify a feature in the query definition instead of trying to determine all of the individual filter ids that were used to specify the individual feature’s styles. This approach overcomes the problem of new filter ids being introduced as new styles are used by the GIS; all filter id with a common Feature number are automatically treated as a single feature.

The new Enhanced Filter Creation Mode in the FME Plug-in mimics much of the G/Tech Loader’s approach to filter id so that it can provide richer filter file creation. The original GIS feature and component number may or may not be available to FME; however, the FME Plug-in can still operate in similar fashion by generating its own feature and component number based on the Feature name and Style names used in the conversion. In FME, the Feature name is the name you define on the Destination features (as Feature Type Name).

In the example below, the Streets destination is shown:





With the Enhanced Filter Creation mode:
  • The Streets feature will be given a unique Feature Number.
  • All Street features will be added to a Group called “Streets”.
  • Each different style used (different values of gti_styleName) for the Streets feature will be given a unique component number for that feature.
In the example shown above, the gti_styleName format property is assigned the value of the CFCC value (which is the type of road and makes it possible to assign each different road type a different symbology).



The second new feature in the FME Plug-In is the ability to automatically prepend the Feature name to the value assigned to the gti_styleName format property. In the past, it was necessary to use a Concatenator to generate the appropriate string for gti_styleName:


While using the Concatenator transformer is not difficult, it did require defining the concatenation for each feature using attribute driven symbology. When using a single attribute to drive symbology, this task becomes implicit; you just connect the driving attribute to the gti_styleName property in the destination. With the Use Feature in StyleName option active, the Destination feature name and a hyphen (“ – “) are automatically prepended to the gti_styleName value when creating the filter name.


In previous versions of the plug-in, you needed something like this:





However, with the Use Feature Name in StyleName active, you only need to connect the symbology driving attribute to the gti_styleName format attribute:



You will still need to use a Concatenator if you want to use multiple attributes multiple attribute to drive the symbology, but the Concatenator’s specification will still be simplified since it does not need to specify the Feature name.

The Use Feature in StyleName is not required and if you wish to use the explicit approach used by previous versions of the plug-in, simply turn this option off in the Destination parameters.



Using the new feature with exsting Workspaces
If you are using workspaces created with previous versions of the plug-in, the new options will not appear in the Parameters section in the Workbench Navigator. However, you can use the gtiParameters.txt file to define these options:

UseFeatureNameInStyleName=1 or 0
FilterCreationMode=enhanced
or standard

To use the gtiParameter.txt file, create a file with the desired entries and place this file in the output directory. The FME plug-in will look for this file each time the data is converted. If the file is present, the plug-in will use any settings it may define.

Examples:

To get a better idea of the effect these new features will have on a filter file created by FME, I will walk through an example of the new setting combinations and show the filter file created for each:

File Creation Mode: Standard Use Feature Name in Stylename: No





This example produces the same output as all previous versions of the FME Plug-in: one group called Features, with each different gti_styleName value added as a different component.


File Creation Mode: Standard Use Feature Name in Stylename: Yes



With the Use Feature Name in StyleName set to yes, the Destination feature name is automatically prepended to the style name (“STREETS – “ in this example).


File Creation Mode: Enhanced Use Feature Name in Stylename: No



With the Filter Creation Mode set to Enhanced, this version of the filter file is somewhat different from the previous two examples. Two groups are created, one for “Streets” and one for “Water”. All of the street types and water type are created as separate components within each feature group. The “GIS1:” tag and “Group:” tag are used in the description fields instead of the “FME:” tag used by the standard mode. This difference helps the FME plug-in manage the different mode of filter creation and also is supported by GTQuery to allow feature and component specifications.

File Creation Mode: Enhanced Use Feature Name in Stylename: Yes



This final example shows the filter file with both the Enhanced Filter Creation Mode and the Use Feature Name in Stylename option active. In addition to the information discussed in the previous example, a few other items of interest are worth pointing out. With the Enhanced mode, the unique Feature numbers that are generated (1 and 2 in this example) which is the second item in each record. Also, the component numbers (the 3rd item in each record) are now unique for each group. The Water group also demonstrates the entry that gets generated if the gti_styleName is empty.








GTVx version 7.0.x.20 is Available



Version 7.0.x.20 of GTVx is available.

-----------------------
07.00.00.20 - 06/25/08
-----------------------

- FIX - GTV #1038 - Computing element ranges with Data Only elements was causing the range to be invalid.


- FIX - #5002 - Weight setting in Thematic Query dialog did not work.

-----------------------
07.00.00.19 - 05/23/08
-----------------------

- CHG - GTVX #1037 - Default Stroke Angle for Style rules has been changed to 5 degrees instead of 15.

- FIX - GTVX #1038 - Style Rule object was not getting set for Draw methods. Initial rendering could be different without any style rules defined.

Friday, June 13, 2008

GTViewer version 7.0.1.30 is Available



Version 7.0.x.30 of GTViewer is available.

-----------------------
07.00.00.30 - 06/13/08
-----------------------

- FIX - GTV #1038 - Computing element ranges with Data Only elements was causing the range to be invalid.

-----------------------
07.00.00.29 - 05/13/08
-----------------------

- NEW - GTV #1032 - FontMap_NoJust entry added to dgnExport.ini.

- CHG - GTV #1037 - Default Stroke Angle for Style rules has been changed to 5 degrees instead of 15.



Thursday, June 12, 2008

TechEd 2008 in Orlando



The TechEd 2008 Deveveloper’s Conference was in Orlando last week. I have always attended MEDC (Mobile and Embedded Developer’s Conference) before, but it has now been merged into TechEd. I believe that I prefer the more focused content of MEDC, but if my only way to get this information is to go to TechEd, then it is not too bad of an alternative. However, there were only 11 Windows Mobile session at TechEd 2008.

There is always a flavor to a Microsoft conference. I don’t know if this is directed by the powers that be or simply a natural alignment to the new features they are providing (or a combination of both). This year, the flavor definitely tastes of LINQ (Language Integrated Query). LINQ is undeniably an interesting concept that directly integrates SQL-like statement into the language syntax of any .NET language (VB.NET, C#, etc.). What makes this new feature somewhat interesting is that the SQL statements can be applied to data in arrays, enumerable objects, XML, and databases. So, the SQL way of querying a database can now be directly applied to data in your application, not just databases.

It also appears that most of the new language features we get from Visual Studio 2008 are directly related to LINQ: Anonymous Types, Extension Methods, Lambda Expressions, Implicitly typed locals, and Object Initializers. All of these new features were added just to support LINQ. One session on the Visual Studio 2008 IDE revealed that there wasn’t much added to the IDE because all of the developers were working on LINQ. On the downside, while LINQ does run on Windows Mobile, it will only work with your application data and does not work with SQL CE. There are a lot of things in the Compact Framework I would have rather had than a partially implemented version of LINQ.

While just about every session had to work LINQ in somehow, there were a couple of other technologies that were shown off. The Windows Presentation Manager (WPF) has developed a good deal since last year and can really produce some spectacular looking demos. The new support in Visual Studio 2008 for WPF is nice, but really seems to be early in its development. All of the WPF sessions seem to highlight a few points: it has great potential, it’s not here yet, and you will need a graphic designer to properly use it. A common phrase I heard in the session is “I’m not a graphic designer, so my WPF doesn’t look very good.” Nevertheless, I still found the Technology compelling enough to pursue. As an aside, Silverlight, which is an offshoot of WPF, came across as a very immature technology. Maybe it will mature quickly.

The Window Communication Foundation (WCF) was also a popular topic. It is just the extension of Web Services to what it probably should have been in the first place.

The Windows Workflow Foundation (WF, because WWF was already taken), was new to me and looks really interesting. An oversimplified description of it would be a project type in Visual Studio that lets you create a flow chart or diagram of your business logic and then can add the code behind the items in the diagram. The WF demos were compelling, but I have to question how well it really works in the real world. The demos used very simplistic logic. How well WF scales to a real application would be interesting to know. I think time will tell on this technology. It will become really popular or just disappear.

Another interesting thing about TechEd 2008 is what they didn’t talk about. Normally, these conferences are all using beta versions of something that hasn’t been released. I went to MEDC two years in a row and all they talked about was Whidbey (VS2005). Then it was all about Orcas (VS2008). With the exception of running VS2008 service pack 1 betas and a Silverlight beta, everyone was pretty content with the released software (quite a change from previous conferences). Does this mean there isn’t anything new in the queue or they are just taking a little longer to ramp up to the new stuff.

All and all, I was pretty pleased with the conference. Visual Studio 2008 looks good enough now to upgrade to (although I may wait until SP1 until I start upgrading all of my projects). Check out the full video and text of Bill Gates’ key: http://www.microsoft.com/presspass/exec/billg/speeches/2008/06-03teched.mspx

Monday, May 19, 2008

GTData version 7.0.0.7 is Available



Version 7.0.0.7 of GTData is available.

-----------
07.00.00.07 - 05/19/08
-----------

- NEW - GTFontEdit - GTD #1017 - Ability to change a font from a text font to a symbol font and vice versa has been added to the Modify menu.

- FIX - GTLabelGtg - GTD #1018 - Was not supporting Symbol Element for Mode 4.

- FIX - GTConv - GTD #1019 - Tag linkages Id values were overflowing if greater than a signed short's high value. Changed to an unsigned short value.

- NEW - GTInterGtg - GTD #1020 - OmitValue added.

- NEW - GTInterGtg - GTD #1022 - RequiredAttributeValue and OmitAttributeValue added.

- CHG - GTShapeConv - GTD #1023 - Maximum shapefile part count raised from 1500 to 10000. Maximum shapefile point count rasied from 100000 to 200000.

- FIX - GTShapeConv - GTD #1024 - Actual Range would report the wrong range when multipart lines and shapes were present.




GTVx version 7.0.x.18 is Available



Version 7.0.x.18 of GTVx is available.

-----------------------
07.00.00.18 - 05/19/08
-----------------------

- NEW - GTD #1003 - Export to Shapefile now supports Shape with Hole Elements.

- FIX - GTD #1004 - Export to Shapefile now forces all filenames to be upper case so that they are consistent with one another.

- NEW - GTVX #1026 - The SetDisplayProperty and GetDisplayProperty methods now support: SuppressEditDisplayUpdate

- FIX - GTV #1027 - Support for Shape with Holes has been added to the DGN export functionality. Shape with Hole elements are converted to linestrings.

- FIX - GTVX #1028 - Complex Shapes (Type 3, Extended Style 2) with a style rule containing only a Color and no border color would draw the complex shape's border with the element's shape border color. This has been changed to use the color in the style rule if the style rules defines only a color and no border color.

- NEW - GTVX #1029 - The FeatureTooltipOmitBlankValues Data Property has been added. It can be used with GetDataProperty, SetDataProperty, and in the Additional Properties section in the .GTM file.

- FIX - GTV #1031 - Stroking Circles, Ellipses, and Arc could overflow some point buffer in the export to .dgn routines after the default stroke angle was reduced to 5 degrees in an earlier version.

- NEW - GTVX #1033 - New Event for Feature Tooltips:

void FeatureTooltip(long id, long count, long categoryId, long offset, long dataId, long key1, long key2, double x, double y);

New property for GetDataProperty and SetDataProperty:

FeatureTooltipMode

- NEW - GTVX #1034 - New Method:

long GetControlWindowHandle();

- FIX - GTVX #1035 - Selection of filled Shape elements was limited to borders only.

- FIX - GTVX #1036 - Fill Color and Border Color were not being drawn correctly for Shape with Hole elements.

- CHG - GTVX #1037 - Default Stroke Angle for Style rules has been changed to 5 degrees instead of 15.


GTV Control version 7.0.0.53 is Available



Version 7.0.x.53 of the GTViewer .NET Control is available.

Several versions rolled into one blog posting.

------------
07.00.00.53 - 05/17/08
------------


- FIX - #242 - The token did not work when used in the
AttributeInfoFilterString property.

- NEW - #243 - GT/Field features will now use their GT/Field feature name instead of the default "Session Graphics" identifier in picklists.

- FIX - #244 - Capture Point with Confirmation was moving the point on a mouse event.

- FIX - #255 - Setting the current Mode to None would not clear the soft button panel.

- NEW - #256 - New Method to clear softpanel without changing modes:

bool ClearSoftButtonPanel()

- NEW - #257 - New Methods to support reference points:

bool ClearReferencePointList()

bool AddReferencePoint(double x, double y, bool flag );

- NEW - #258 - New Event:

void CaptureModeMouseMove(CaptureModeEventType eventType, int id, double x, double y, double z, bool zValid)

- FIX - #259 - The GetDateProperty method did not return the correct value for DefaultScale.

- NEW - #260 - New Methods:

bool SetDisplayStatusList(int categoryId, int[] displayStatusList, double[] minThresholdList, double[] maxThresholdList, int count)

bool GetDisplayStatusList(int categoryId, out int[] displayStatusList, out double[] minThresholdList, out double[] maxThresholdList)

------------
07.00.00.52 - 05/04/08
------------

- NEW - #241 - New Methods:

bool SetDisplayStatusList(int categoryId, int[] filterList, int count)

bool GetDisplayStatusList(int categoryId, out int[] filterList)

------------
07.00.00.51 - 05/04/08
------------

- CHG - #240 - Shape with Hole rendering has been switch to the Windows API rendering
for desktop version.

- FIX - #239 - Overview mode was not using the correct view id when setting the initial range for an overview.

------------
07.00.00.50 - 04/26/08
------------
- CHG - #238 - The Data Monitor 2 Group Id property has been changed from an integer to a string.

------------
07.00.00.49 - 04/25/08
------------

- NEW - #235 - DM2_FitItems method added.

- NEW - #236 - DM2_UpdateItemViewFilterByGroupIdAndStyleId method added.

- NEW - #237 - View_None added to the list of View constants.

------------
07.00.00.48 - 04/24/08
------------

- FIX - #232 - Picklist with more than 10 data monitors would cause problems.

- NEW - #233 - DeleteItemsByGroupId, UpdateItemStyleIdByGroupId, and UpdateItemViewFilterByGroupId will now accept the group id of -1 to represent all group ids.

- NEW - #234 - New version of DM2_UpdateItemViewFilterByGroupId has been added to provide bitwise operations (AND, OR, XOR).

------------
07.00.00.47 - 04/23/08
------------

- NEW - #224 - IsFilePassworded method has been added.

- NEW - #225 - File Error Status and Info.

- NEW - #226 - Alternate GTViewer File can now be supplied to OpenFile so that you can override the GTViewer filter specified in a .gts file.

- FIX - #227 - Feature tooltips were not showing the tooltip heading.

- NEW - #228 - FeatureTooltipOmitBlankValues now supported in Additional Properties section and GetDataProperty and SetDataProperty methods.

- FIX - #229 - FeatureTooltipMinThreshold and FeatureTooltipMaxThreshold were not correctly implemented.

- FIX - #230 - CreateSession now closes any open file and performs a license check.

- FIX - #231 - CreateSession was not setting the Document Id correctly after a successful call.



PGTV Control version 7.0.0.23 is Available



Version 7.0.x.23 of the PGTV Control is available.



------------
07.00.00.23 - 05/19/08
------------
- NEW - #198 - Emphasize Color supported.


- FIX - #199 - Complex Shapes (Type 3, Extended Style 2) with a style rule containing only a Color and no border color would draw the complex shape's border with the element's shape border color.
This has been changed to use the color in the style rule if
the style rules defines only a color and no border color.

- NEW - #243 - GT/Field features will now use their GT/Field feature name instead of the default "Session Graphics" identifier in picklists.

- FIX - #255 - Setting the current Mode to None would not clear the soft button panel.

- NEW - #256 - New Method to clear softpanel without changing modes:

bool ClearSoftButtonPanel()

- NEW - #257 - New Methods to support reference points:

bool ClearReferencePointList()

bool AddReferencePoint(double x, double y, bool flag );

- FIX - #259 - The GetDateProperty method did not return the correct value for DefaultScale.

Wednesday, April 30, 2008

GTData Version 7.0.0.6 is Available



Version 7.0.0.6 of GTData is available.


-----------
07.00.00.06 - 04/30/08
-----------

- NEW - GT2Shape - GTD #1003 - Shape With Hole Elements are now supported.

- FIX - GT2Shape - GTD #1004 - All filenames are converted to lower case so that they will be consistent with one another.

- NEW - GTConv - GTD #1005 - CellHeaderLevelMode added to allow a cell to use the cell header's level if it is not equal to 0.

- NEW - GTTextQuery - GTD #1006 - The StartsWith entry is now supported to filter text by requiring it to start with the specified string. Entry is repeatable.

- NEW - GTTextQuery - GTD #1007 - The OmitStartsWithText entry was added and if set to 1, the StartWith text from #1006 will be removed from the text string.

- NEW - GTTextQuery - GTD #1008 - The -tf flag was added to support the creation of a file containing all of the text meeting the search criteria. The -fid flag was also added to also place the text element's filter id in the text file output.

- NEW - GTTextQuery - GTD #1009 - The Filter Id was updated to support hypenated list of filter ids.

- FIX - GTQuery - GTD #1010 - The FilterId entry did not support token replacement.

- FIX - GTConv, GTSum - GTD #1012 - Attribute Linkage index not correct in some cases.

- NEW - GTTextQuery - GTD #1013 - The -xy flag was added to embed coordinate info in each record.

- NEW - GTSumGtg - GTD #1014 - Added to GTData.

- NEW - GTSplitGtg - GTD #1015 - The -x1, -y1, and -min flags added.

- NEW - GTTextQuery - GTD #1016 - The IgnoreSubElements entry has been added to tell how many sub elements to skip in a group before processing. The default is 0.


Friday, April 25, 2008

GTViewer 7.0.x.28 is Available



Version 7.0.x.28 of GTViewer is available.

-----------------------
07.00.00.28 - 04/25/08
-----------------------
- NEW - GTD #1003 - Export to Shapefile now supports Shape with Hole Elements.


- FIX - GTD #1004 - Export to Shapefile now forces all filenames to be upper case so that they are consistent with one another.

- FIX - GTV #1027 - Support for Shape with Holes has been added to the DGN export functionality. Shape with Hole elements are converted to linestrings.

- FIX - GTV #1028 - Complex Shapes (Type 3, Extended Style 2) with a style rule containing only a Color and no border color would draw the complex shape's border with the element's shape border color. This has been changed to use the color in the style rule if the style rules defines only a color and no border color.

- NEW - GTV #1029 - The FeatureTooltipOmitBlankValues Data Property has been added. It can be used with GetDataProperty, SetDataProperty, and in the Additional Properties section in the .GTM file.

- FIX - GTV #1030 - GT/Field did notshow icons correctly for required GPS values.

- FIX - GTV #1031 - Stroking Circles, Ellipses, and Arc could overflow some point buffer in the export to .dgn routines after the default stroke angle was reduced to 5 degrees in an earlier version.


Monday, April 21, 2008

GTV Control version 7.0.0.46 is Available



Version 7.0.x.46 of the GTViewer .NET Control is available.

Several versions rolled into one blog posting. Major additons to the .NET control are support for the .GTM and .GTS files in the Pro version as well as an enhanced version of the Data Monitor (called DM2) and Log File support.


------------
07.00.00.46 - 04/21/08
------------

- FIX - #218 - Complex Shapes (Type 3, Extended Style 2) with a style rule containing only a Color and no border color would draw the complex shape's border with the element's shape border color.
This has been changed to use the color in the style rule if
the style rules defines only a color and no border color.


- NEW - #219 - DM2_EventMode property has been added.

- FIX - #220 - DM2_DeleteItem did not work correctly.

- NEW - #221 - DM2_DeleteItemsByGroupId was added.

- FIX - #222 - DM2_UpdateItem was not passing double values correctly to the dll and thus not working correctly.

- NEW - #223 - Constants provided for Views: View_0, View_1, ... View_9 and View_All. These values can be used with the Data Monitor View Filter value.

------------
07.00.00.45 - 04/14/08
------------

- NEW - #214 - Emphasize Color support added. EmphasizeSessionGraphicsColor property added to GetDataProperty and SetDataProperty.

- NEW - #215 - SetViewLike method added: bool SetViewLike(GTVControl ctrl)

- FIX - #216 - Graphic engine objects were not getting released when a file closed.

- FIX - #217 - CreateSession methods were private instead of public.

------------
07.00.00.44 - 04/13/08
------------
- NEW - #207 - Style Def and Map File support added.

- NEW - #208 - UDLS Def File support added.

- NEW - #209 - Filter File support added.

- NEW - #210 - .GTM File support added.

New Properties:
String SessionFile

New Methods:
bool CreateSession(String sessionFile, String gtviewerFile, String password)

- NEW - #211 - Log File support added.

New Properties:
int LoggingLevel

New Methods:

String GetLogfileName()
bool LogMessage( int level, String msg )

- NEW - #212 - DM2 methods added:

public bool DM2_AddStyleItem( int styleId, DM2_Style style)
bool DM2_GetStyleItemCount(int styleId, out int count )
public DM2_Style DM2_GetStyleItem(int styleId, int pos)
public bool DM2_AddItem(DM2_Item item)
public DM2_Item DM2_GetItem( String itemId )
public bool DM2_ClearAllItems()
public bool DM2_ClearAllStyleItems()
public bool DM2_ClearStyleItems(int styleId)
public bool DM2_DeleteItem( String itemId )
public bool DM2_UpdateItem(String itemId, double x, double y, double rotation)
public bool DM2_UpdateItemStyleId(String itemId, int styleId)
public bool DM2_UpdateItemViewFilter(String itemId, int viewFilter)
public int DM2_UpdateItemStyleIdByGroupId(int groupId, int styleId)
public int DM2_UpdateItemViewFilterByGroupId(int groupId, int viewFilter)
public int DM2_GetItemCount()
public bool DM2_GetItemsAtPoint(double x, double y, out ArrayList itemList)

- FIX - #213 - Magnify view was not scaled correctly when coordinate factor 2 was not 1000.



Monday, April 07, 2008

PGTV Control version 7.0.0.22 is Available



Version 7.0.x.22 of the PGTV Control is available.


------------
07.00.00.22 - 04/07/08
------------

- CHG - #158 - Description for Reviewed Session Graphics has been changed from "Session Graphic" to the element's filter name.

- FIX - #162 - Fillable element using the Border Color style property were not inverting their color when drawn on the same color background.

- NEW - #163 - MaxZoomLevel, MaxZoomScale, and MinZoomScale added to Additional Properties section.

- NEW - #164 - GetDataProperty and SetDataProperty now support: MinZoomLevel, MaxZoomLevel, MinZoomScale, MaxZoomScale

- NEW - #165 - GetFontList method added.

- FIX - #167 - Drawing Text Accents would cause problems.

- FIX - #168 - Adjustments to Shape With Holes rendering.

- FIX - #169 - Rendering of character id greater than 127 would not display correctly.

- FIX - #170 - Data Monitor items were not having the Text Accent correctly initialized which could cause strange graphics to appear.

- FIX - #188 - Fixes to ClearCustomMenuItems.

- FIX - #197 - Flicker Highlight did not work when the ShapeBorderColor style property was used.

Tuesday, March 25, 2008

GTData version 7.0.0.5 is Available



Version 7.0.0.5 of GTData is available.

-----------
07.00.00.05 - 03/25/08
-----------

- NEW - GTQuery - The -de flag has been added so that query output files with no records are automatically deleted.

- NEW - GTQuery - The -uu flag has been added along with the UpdateDataFile to alternately use an update Data file.

- NEW - GTUpdateGtg1, GTUpdateData, GTQueryDelRec, GTAppendQuery, GTIncUpdMgr - have been added to GTData.

- FIX - GTShapeConv - NULL_TYPE elements mixed in with valid elements would generate and unknown type error and end the conversion. These elements are now ignored.

- CHG - GTExtract - GTV #1012 - Symbol Fonts are no longer filtered by usage for extract files.

- CHG - GTExtract - GTV #1013 - Color tables are no longer filtered by usage for extract files.

- NEW - GTInterGtg - GTD #1001 - IngnoreSimilarNames setting added.

- FIX - GTConfig - GTD #1002 - Carriage return was getting introduced for codelist table name.

GTVx version 7.0.x.17 is Available



Version 7.0.x.17 of GTVx is available.

-----------------------
07.00.00.17 - 03/25/08
-----------------------

- FIX - GTVX #1014 - Feature Tooltips would not work on unselectable categories.

- FIX - GTVX #1018 - When SetAddElementRedrawMode is set back to 1, it did not clear any cached elements and they would not draw until the view is rerendered.

- FIX - GTVX #1019 - Flicker Highlight did not work when the ShapeBorderColor style property was used.

- FIX - GTVX #1023 - New Method:

BOOL ExportSessionGraphicsAsShp(long mode, LPCTSTR table, LPCTSTR path, LPCTSTR baseFilename)

- FIX - GTVX #1025 - Separator line on Feature Tooltip would sometime be added at the end unecessarily.