One of the most time-consuming processes when developing with Hexagon G/Technology is creating custom commands. The usual development approach consists of the following iterative process: During testing, only limited changes to the source code are allowed by the Visual Studio Edit and Continue function, effectively requiring multiple iterations of this sequence. The process of starting… Read More »
Consider a requirement where the centroid of a set of points needs to be retrieved within a custom command. This can be achieved using the ‘GTDataProvider.DataContext.Execute‘-method:
Whenever a user is digitizing a polygon, he expects feedback when moving the cursor before actually adding a point, the system should ‘rubberband’ the position under the cursor and only add it to a collection of points after the user left-mouse clicks in the Window. Key to rubberbending in G/Technology is responding to three events… Read More »
Fiber Couplers are used to connect Fiber Inner Ducts in a Fiber Branch Enclosure. You can connect Fiber Inner Ducts using the Fiber Feature Editor by selecting the two Fiber Inner Ducts and choosing the ‘Couple’-icon : This will connect the 2 selected Fiber Inner ducts using a Fiber Coupler. After coupling the Fiber Inner… Read More »
Introduction G/Technology provides functionality to run dynamic queries, the so called ‘Ad-Hoc queries’. A Large telecom provider in the Netherlands is moving Fiber Cables from CRAMER to FOW and AdHoc-queries provide a great tool to analyze and visualize migrated data At this provider Fiber Cables are contained by Fiber Inner Ducts who themselves are contained… Read More »
If you publish metadata, G/Technology creates a set of .raw- and .ddc files, the metadata to be stored in these tables/ddc-files is read from table G3E_METADATAKEYS. This gets truncated and filled during the metadata-publishing process by procedure MG3EPopulateMetadataKeys. This blog-entry describes how to extend the G/Technology metadata system with your own tables. Key to extending… Read More »
Intergraph has an internal database for keeping track of all kinds of software issues, if you file a Trouble- or Change Request, it will end up in this database. This database will become public available in the 3rd quarter of 2013 according to Intergraph sources at Hexagon 2013. Also, if a problem gets fixed, the… Read More »