| Numéro d’ID de bogue |
BUG-000128026 |
| Envoi | January 17, 2020 |
| Dernière modification | May 5, 2025 |
| S’applique à | ArcGIS Pro SDK for .NET |
| Version trouvée | 2.4.3 |
| Système d’exploitation | Windows OS |
| Version du système d’exploitation | 10.0 64 Bit |
| Statut | Will Not Be Addressed
L’équipe de développement a examiné le problème ou la demande et a décidé qu’ils ne seraient pas traités. Pour d’autres explications, reportez-vous à la section Informations supplémentaires correspondant au problème.
|
Informations supplémentaires
'Active' Tools can be activated multiple times within their lifespan. The most obvious case is when a user clicks on the tool on the ribbon. When the tool is activated, the OpenAsync method is called on its associated embeddable control (assuming it has one) along with the OnToolActivateAsync(...) method. This is probably the expected workflow for tool add-in developers.
However, a tool which is '_already active_' can still be reactivated many times, even when the user does not '_explicitly_' reactivate it by clicking on the tool on the ribbon - such as when the tool is already active and a view is being initialized (eg a new map view is being opened) usually because the user has switched views.
When a user switches map views (or scene views), the active map tool will be reactivated (even though it is already active) meaning the OpenAsync method is called along with the OnToolActivateAsync(...) method.
Note: In the case of a new (map or scene) view being activated, if the map tool is already the active tool, the OpenAsync method is called '_twice_' in succession, once when the new view is being initialized and once when the active view changed event fires internally. This is also true of the OnToolActivateAsync(...) method.
There are likely other situations where tools get reactivated and add-in developers should code the tools and associated embeddable controls accordingly.
Étapes pour reproduire
ID de bogue: BUG-000128026
Logiciel: