"Reload Last Setting," in Brightness Curve Transformation with Mask, Crashes PWP

[jfoster]

"Reload Last Setting," in Brightness Curve Transformation with Mask, Crashes PWP

To reproduce:

1. Open PWP 8.0.516

2. Create Color Chart Test Pattern

3. Add Brightness Curve Transformation

4. Create an Amount Mask within the Brightness Curve Transformation

5. Make a mark on the mask with the Paint tool.

6. Click the OK box to close the Brightness Curve Transformation

7. Add another Brightness Curve Transformation to the image.

8. In this Transformation, load the Mask that was previously created.

9. In the Gear Menu of the Brightness Curve Transformation, select "Reload Last Settings"

10. Note that PWP crashes.

Jeff

[jsachs]

While this does not crash on my computer, it also does not do what I would expect, namely to reset the initial mask from step 8 before loading the saved mask from step 6. I will fix this for the next release and hopefully this will also fix the crash you are seeing.

When you save or load settings files (including re-loading the last settings), it is important to realize that while information is included in the settings file to rebuild the Amount masks associated with the transformation, this does not extend to saving and reloading the mask if it was built starting with some other image that was selected as the initial mask image. Saving and restore this information would require saving information to rebuild the initial image and that it turn could depend on other transformations. If you want to save settings without this limitation, you need to use a script or workspace script file.

In the example you gave, it should have rebuilt the mask starting with an empty mask instead of the initial mask image that was in effect when the settings file was created.

I am looking at adding a mechanism to issue a warning when reloading a settings file created from a transformation with an Amount mask built on an initial mask image.

[jsachs]

Please let me know if 8.0.517 fixes the crash.

[jfoster]

Seems to be fixed in 8.0.517.

Thanks.

Jeff