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
Exporting sets makes .def files at root level. My course has hundreds of sets. Manually removing the hundreds of .def files after export is laborious and error-prone.
Proposed Solution
Having an option of a folder in which to export the .def files would significantly simplify the process of removing exported .def files, at least because I could simply delete the containing folder.
The text was updated successfully, but these errors were encountered:
I think in general the templates directory should be reorganized. It would be convenient if very few files were actually directly in that location. Set definitions should have a dedicated sub-directory. Set/Hardcopy headers also. All of the set directories would ideally be in another sub-directory also (instead of using the "set" prefix on the directory name).
Problem
Exporting sets makes .def files at root level. My course has hundreds of sets. Manually removing the hundreds of .def files after export is laborious and error-prone.
Proposed Solution
Having an option of a folder in which to export the .def files would significantly simplify the process of removing exported .def files, at least because I could simply delete the containing folder.
The text was updated successfully, but these errors were encountered: