Guys

The work with my client using Flowchart.Net has me making use of the Tag property field on shapenodes for a variety of purposes, one of which is the use of a unique Guid field used in database records to associate data with shapenodes.
It would be nice if every shapenode/diagramnode/link had a Guid Id field to uniquely identify the items and for greater integration between Flowchart.net and database records.

Let me know if this does not make sense.

Doug

Stoyan
Sorry for the delay in getting back to you.
Having another field ''object type" would be fine as everyone has different needs. Given that I and probably many other developers are linking the chart to a database the use of an additional data field would be tremendous.

For instance I access a database to gather the data for charting; I record key items of information in a record structure (below) that I store information in the .Tag field which can be interrogated at anytime without going back to the database.

Having a separate data field like .tag would be great in my case for storing a unique id for the node and leave the tag to contain my other data elements.

regards
Doug :)

    Structure NodeDetails
       '
       Dim Node_ProjectID As Guid
       Dim Node_EntityID As Guid
       Dim Node_RealEntity As Boolean
       Dim Node_ParentID As Guid
       Dim Node_EntityType As enmEntityType
       Dim Node_DescOfEntity As String
       Dim Node_GroupID As String
       '
    End Structure

Stoyan

Absolutely brilliant; I hope than many developers can make use of this additional id property for linking diagram and shape nodes to their databases or for many other valid uses.

Well done; you certainly are one of the best product developers who listens to and implements user suggestions that have value to others.

regards
Doug