Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://developers.arcgis.com/qt/cpp/api-reference/esri-arcgisruntime-snapsettings.html below:

SnapSettings Class | ArcGIS Maps SDK for Qt

Creates a default SnapSettings.

• parent - The optional parent QObject.

Destructor.

Returns true to allow interactive snapping, based on the configured sourceSettings, false otherwise. Default is false.

If isEnabled is true and a user edits a geometry interactively, then when the pointer is close to an existing snappable graphic or feature, the position of the interactive edit is adjusted to coincide with ("snap to") that graphic or feature. The content of sourceSettings determines which sources of geometries can be used to snap to.

Setting this value temporarily to false may be useful if you wish to temporarily disable all snapping without affecting how snapping is currently configured. For example, changing this property will not affect the value of SnapSourceSettings::isEnabled, or if rule-based snapping has been configured by using SnapRules.

Returns true to allow interactive snapping to other features and graphics, based on the configured sourceSettings, false otherwise. Default is true.

Ignored if isEnabled is false.

Feature snapping can be combined with geometry guides by ensuring isGeometryGuidesEnabled is true.

This function was introduced in Esri::ArcGISRuntime 200.6.

Returns true to allow interactive snapping relative to the current GeometryEditor::geometry, false otherwise. Default is true.

When enabled, additional visual cues appear as temporary guides when interactively editing polygon or polyline geometries, allowing edits to be snapped to:

• coincide with an existing edge (segment) or vertex of the current GeometryEditor::geometry
• create a new segment perpendicular to the previous segment of the current GeometryEditor::geometry
• create a new segment as an extension of the previous segment of the current GeometryEditor::geometry
• create a new segment parallel to an existing segment of the current GeometryEditor::geometry

The guides shown indicate the type of snap occurring.

Ignored if isEnabled is false.

Geometry guides can be combined with snapping to other features or graphics by ensuring isFeatureSnappingEnabled is true and configuring sourceSettings appropriately.

This function was introduced in Esri::ArcGISRuntime 200.6.

Returns true to enable haptic feedback whenever a snap occurs (if supported by the device), false otherwise.

Enables haptic feedback whenever a snap occurs to a feature or graphic from a SnapSource, or geometry guide. The default value is true.

Note that the specifics of the haptic will vary on different platforms and devices, and this boolean will have no effect if the end user's device does not support haptics.

Haptic feedback should be expected when the GeometryEditor::snapChanged event happens with a SnapState of SnapState::SnappedToFeature or SnapState.snappedToGeometryGuide. You can alternatively implement your own custom haptic feedback, for example if you wish to change the type of haptic feedback, or include haptic feedback for SnapState::Unsnapped. To do this, set this boolean to false, and perform your custom haptic feedback by listening to the GeometryEditor::snapChanged event.

This function was introduced in Esri::ArcGISRuntime 200.6.

Sets the enabled to enabled.

See also isEnabled.

Sets the featureSnappingEnabled to featureSnappingEnabled.

This function was introduced in Esri::ArcGISRuntime 200.6.

See also isFeatureSnappingEnabled.

Sets the geometryGuidesEnabled to geometryGuidesEnabled.

This function was introduced in Esri::ArcGISRuntime 200.6.

See also isGeometryGuidesEnabled.

Sets the hapticFeedbackEnabled to hapticFeedbackEnabled.

This function was introduced in Esri::ArcGISRuntime 200.6.

See also isHapticFeedbackEnabled.

Defines and returns a QList of snapping sources and whether or not each is enabled for snapping.

Call syncSourceSettings to populate the QList with a SnapSourceSettings for each valid SnapSource present in the connected MapView. To use rule-based snapping, call syncSourceSettings(Esri::ArcGISRuntime::SnapRules*, Esri::ArcGISRuntime::SnapSourceEnablingBehavior) instead.

SnapSettings is connected to a MapView via GeometryEditor::snapSettings, and MapView::geometryEditor. If there is no connected MapView, or the map view and the associated map contains no valid SnapSource objects, then the QList will be empty after the synchronization call returns.

The order of SnapSourceSettings objects will match the order that the associated SnapSource objects appear in the Map::operationalLayers and MapView::graphicsOverlays collections, with objects from Map::operationalLayers appearing first, followed by MapView::graphicsOverlays objects, in order.

For SnapSourceSettings objects that correspond to a SubtypeFeatureLayer, SnapSourceSettings::source returns a QList of separate SnapSourceSettings objects representing each SubtypeSublayer.

After synchronization, the Qlist will not contain a SnapSourceSettings for any loadable SnapSource which is not yet LoadStatus::Loaded.

As snapping is used to maintain data integrity between different sources of data, only SnapSource objects that provide full resolution geometries as considered valid for creating a SnapSourceSettings object - see SnapSource for more information.

Synchronizes the sourceSettings QList based on SnapSource objects in the currently connected Map.

Call this method to populate sourceSettings with a SnapSourceSettings for each valid SnapSource present in the MapView currently connected to this SnapSettings via GeometryEditor::snapSettings, and MapView::geometryEditor. If there is no connected MapView, or the map view and the associated map contains no SnapSource objects valid for snapping, then the QList will be empty after this method returns.

The order of SnapSourceSettings objects will match the order that the associated SnapSource objects appear in the Map::operationalLayers and MapView::graphicsOverlays collections, with objects from Map::operationalLayers appearing first, followed by MapView::graphicsOverlays objects, in order. The collection will not contain a SnapSourceSettings for any loadable SnapSource which is not yet LoadStatus::Loaded when syncSourceSettings is called.

Subsequent calls will update the existing collection, accounting for SnapSource objects that have been added, removed, or moved since the last call to the same connected map. Any changes made to existing SnapSourceSettings objects, for example setting SnapSourceSettings::isEnabled, will be preserved.

Calling this method removes any rule-based snapping configuration that was previously set by calling syncSourceSettings(Esri::ArcGISRuntime::SnapRules*, Esri::ArcGISRuntime::SnapSourceEnablingBehavior), and the SnapSourceSettings::ruleBehavior of all the SnapSourceSettings objects will be SnapRuleBehavior::None.

See also sourceSettings and SnapSourceSettings.

Synchronizes the sourceSettings QList based on SnapSource objects in the currently connected Map and the given SnapRules which may affect each of them.

• rules - The rules to apply to the SnapSource objects.
• snapSourceEnablingBehavior - Whether to set SnapSourceSettings::isEnabled based on the given SnapRules, or preserve the existing values.

Call this method to configure rule-based snapping. Similarly to syncSourceSettings, this method will populate sourceSettings with a SnapSourceSettings for each valid SnapSource present in the MapView currently connected to this SnapSettings via GeometryEditor::snapSettings, and MapView::geometryEditor. In addition to populating the collection, the given SnapRules will be applied to each SnapSourceSettings, setting SnapSourceSettings::ruleBehavior appropriately for those rules. SnapRules are created by calling SnapRules::createAsync(Esri::ArcGISRuntime::UtilityNetwork*, Esri::ArcGISRuntime::UtilityAssetType*, QObject*), specifying a particular UtilityAssetType that matches the feature whose geometry will be edited using the GeometryEditor. When editing features in a utility network, it, it is important to ensure that you have synchronized the snap sources with appropriate snap rules, so that the interactive snapping behavior is configured correctly for editing that asset type.

When using rule-based snapping, SnapSourceSettings::ruleBehavior may limit or prevent snapping to a snap source, regardless of its SnapSourceSettings::isEnabled value. Values of SnapSourceSettings::isEnabled will be affected by the given value of SnapSourceEnablingBehavior.

When rule-based snapping is configured, any edits made by interactively snapping to a SnapSource geometry will use the z-value of the feature geometry, if that snap source geometry is z-aware.

The sourceSettings QList includes all valid snap sources in the map after synchronization, and therefore may include snap sources from data that is unrelated to the UtilityNetwork given when creating the SnapRules, for example graphics overlays or feature layers from separate data sources. If there is no connected MapView, or the map view and the associated map contains no SnapSource objects valid for snapping, then the QList will be empty after this method returns.

The order of SnapSourceSettings objects will match the order that the associated SnapSource objects appear in the Map::operationalLayers and MapView::graphicsOverlays collections, with objects from Map::operationalLayers appearing first, followed by MapView::graphicsOverlays objects, in order. The collection will not contain a SnapSourceSettings for any loadable SnapSource which is not yet LoadStatus::Loaded when synchronization occurs.

This function was introduced in Esri::ArcGISRuntime 200.7.

See also sourceSettings and Geometry::hasZ.

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4