[Bug?] Exposure time finder calibration doesn't have UI for multi exposure

[echo-bravo-yahoo]

System

UVtools v4.3.2 X64
Operative system: Microsoft Windows 10.0.19045 X64
Processor: Intel(R) Core(TM) i7-8700 CPU @ 3.20GHz
Processor cores: 12
Memory RAM: 21.00 / 31.94 GB
Runtime: win10-x64
Framework: .NET 6.0.29
AvaloniaUI: 11.0.10
OpenCV: 4.8.1

Sreens, resolution, working area, usable area:
1: 1920 x 1080 @ 100% (Primary) (On this)
    WA: 1920 x 1040    UA: 1920 x 1040
2: 1080 x 1920 @ 100%
    WA: 1080 x 1880    UA: 1080 x 1880

Path:       C:\Program Files\UVtools\
Executable: C:\Program Files\UVtools\UVtools.exe
Loaded file: UVtools_demo_file.sl1s [Version: 0] [Class: SL1File]

Printer and Slicer

• Printer: N/A
• Slicer: N/A

Description of the bug

The UI for exposure calibration test references a multi-exposure setting, but doesn't have UI to configure it. Multiple brightness appears to only work by anti-aliasing.

How to reproduce

Open UVtools with a completely default install/no configuration. Go to Calibration > Exposure time finder. Attempt to find settings for "Multiple exposure times per layer."

Files

No response

[echo-bravo-yahoo]

After importing sliced .goo file, UVTools now has the fields I expected in exposure time finder. I looked for ways to configure the printer I'm using in UVTools and couldn't find any - would a "Import printer settings from slicedfile" option in the File menu make sense? Alternatively, rendering the "Multiple exposures" section in the "Exposure time finder" dialog with help text ("your current printer doesn't support ... please import a sliced file ...") could help.

[echo-bravo-yahoo]

Now the "Exposure time finder" dialog does not actually overwrite the file I imported to be able to see the settings.

[echo-bravo-yahoo]

Ok... This workflow worked for me:

1. Import a sliced .goo file so UVTools knows printer dimensions & believes multi exposure times will work.
2. Generate a non-patterned exposure test. UVTools remembers the printer settings.
3. Generate a patterned exposure test. Doing this directly fails (no test is generated, and I'm still viewing the imported, sliced .goo from earlier).