Search Issue Tracker

Fixed

Fixed in 2022.3.61f1, 6000.0.46f1, 6000.1.0b13, 6000.2.0a8

Votes

0

Found in

2022.3.59f1

6000.0.41f1

6000.1.0b9

6000.2.0a6

Issue ID

UUM-99153

Regression

No

SettingsService.NotifySettingsProviderChanged() Doesn't Call OnDeactivate for Existing SettingsProviders when new ServiceProvider is created

-

Steps to reproduce:
1. Open the attached “Repro2097282.zip” project
2. Click Edit → Project Settings
3. Observe the Console Window of the created ServiceProvider’s ID
4. Open the “MySettings” tab in Project Settings
5. Observe the “OnActivate” call in the Console Window with the same ID
6. In the Project Browser, create a new folder
7. Observe the Console Window that a new ServiceProvider is created
8. In Project Settings, switch to another tab that is not “MySettings”
9. Observe the Console Window

Expected result: The “OnDeactivate” call is shown with the first ServiceProvider’s ID
Actual result: The “OnDeactivate” call is shown with the newly created ServiceProvider’s ID

Reproducible in: 2022.3.59f1, 6000.0.41f1, 6000.1.0b9, 6000.2.0a6

Reproducible on: Windows 11
Not reproducible on: No other environment tested

  1. Resolution Note (fix version 6000.2.0a8):

    Editor: Fixed SettingsService.NotifySettingsProviderChanged() not calling OnDeactivate() for existing providers.

  2. Resolution Note (fix version 6000.1.0b13):

    Editor: Fixed SettingsService.NotifySettingsProviderChanged() not calling OnDeactivate() for existing providers.

  3. Resolution Note (fix version 6000.0.46f1):

    Editor: Fixed SettingsService.NotifySettingsProviderChanged() not calling OnDeactivate() for existing providers.

  4. Resolution Note (fix version 2022.3.61f1):

    Editor: Fixed SettingsService.NotifySettingsProviderChanged() not calling OnDeactivate() for existing providers.

Add comment

Log in to post comment

All about bugs

View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.