ThinkGeo Cloud
ThinkGeo UI Controls
ThinkGeo Open Source
Help and Support
External Resources
ThinkGeo Cloud
ThinkGeo UI Controls
ThinkGeo Open Source
Help and Support
External Resources
This is an old revision of the document!
This class represents the holding place for transactions that have not yet been committed.
This is the default constructor and is typically not used.
RoutingTransactionBuffer(Dictionary<String,RouteSegment>,Collection<String>,Dictionary<String,RouteSegment>)
N/A
N/A
This method will clear all the items in AddBuffer, EditBuffer and DeleteBuffer.
This method allows you to add RouteSegments to the transaction buffer.
None
This method allows you to add a placeholder to represent a RouteSegment to be deleted.
This does not remove a RouteSegment from the TransactionBuffer but rather it add a “to be deleted record”. In this way when the TransactionBuffer if processed we know what records need to be deleted.
This method allows you to add a Feature to be updated.
None
N/A
N/A
N/A
N/A
N/A
N/A
N/A
It is recommended that you use this dictionary for reviewing and not for adding new items. The reason is that the Add, Delete and Edit methods to various validation checks. For example if you call the DeleteRouteSegment twice it will handle the case that you really only want to delete the record once. Another example is if you edit a record twice it will replace the existing edit with the new one.
This property gets the dictionary buffer that holds RouteSegments to be deleted.
It is recommended that you use this dictionary for reviewing and not for adding new items. The reason is that the Add, Delete and Edit methods to various validation checks. For example if you call the DeleteRouteSegment twice it will handle the case that you really only want to delete the record once. Another example is if you edit a record twice it will replace the existing edit with the new one.
This property gets the dictionary buffer that holds RouteSegments to be updated.
It is recommended that you use this dictionary for reviewing and not for adding new items. The reason is that the Add, Delete and Edit methods to various validation checks. For example if you call the DeleteRouteSegment twice it will handle the case that you really only want to delete the record once. Another example is if you edit a record twice it will replace the existing edit with the new one.