You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
In DataType form. Some Category types selects "Extension (VSE)" or "Library (VSS)" in Project Type(s) field. But if you change to a different Category type, it doesn't de-select the entry.
Use Ctrl + Down cursor to cycle through categories
Compare to just selecting the category with all Project Type(s) checkboxes deselected
Expected behavior
When changing Category, only select the Project Type(s) relevant by default. This will have an impact for VSID databases covering both VSEs and VSSs, where the user changes retrospectively the category. But this is a very unlikely edge case.
Screenshots
If applicable, add screenshots to help explain your problem.
Platform (please complete the following information):
OS Windows 11
Notes Client Version 14.0 FP1
64-Bit
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered:
Describe the bug
In DataType form. Some Category types selects "Extension (VSE)" or "Library (VSS)" in Project Type(s) field. But if you change to a different Category type, it doesn't de-select the entry.
Area Affected
[ ] VoltScript Interface Designer NSF - Extension Projects
[ ] VoltScript Interface Designer NSF - Script Library Projects
[ ] Code Generation
[ ] API Doc Generation
[ ] Documentation
[ ] Extension Samples
[ ] Script Library Samples
[x] Administration area
To Reproduce
Steps to reproduce the behavior:
Expected behavior
When changing Category, only select the Project Type(s) relevant by default. This will have an impact for VSID databases covering both VSEs and VSSs, where the user changes retrospectively the category. But this is a very unlikely edge case.
Screenshots
If applicable, add screenshots to help explain your problem.
Platform (please complete the following information):
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: