Closed Yoshitaka-Fukushima closed 1 month ago
For AvailablePeopleAttributes, AvailableFaceAttributes, AvailableVehicleAttributes, and AvailableLPRAttributes I'm setting null when no attribute permission is set, so it's the (i) option.
@Yoshitaka-Fukushima
I tried with option (ii), setting an empty list instead of null, and it seems that the attributes are hidden as expected. @Yoshitaka-Fukushima
@alexnaicuorbnet Thank you for checking. I would like you to change to be (ii), but wait a moment. We are now checking OSS side implementation just in case.
@alexnaicuorbnet We checked and OSS implementation is correct.
Could you change to be (ii)?
Parameter "AvailableFaceAttribures" exists but blank ("gender" and "age" are not set).
And please implement the same logic also for AvailablePeopleAttributes, AvailableVehicleAttributes, and AvailableLPRAttributes.
Fixed in v2.0.1
Test version plug-in v2.0.0 as of 29th Oct.
Phenomenon When these two roles are disabled,
Expected work on face watchlist window (sample application)
Current
Question There is corresponding parameter "AvailableFaceAttribures" in SetCurrentUser I/F.
When both age and gender is disabled, which do you set? (i)Parameter "AvailableFaceAttribures" itself does not exist (ii)Parameter "AvailableFaceAttribures" exists but blank ("gender" and "age" are not set).
I am checking OSS side behavior in parallel.
@alexnaicuorbnet