Description:
The application currently remembers the last file path location opened when locating the assets folder and items.otb file. However, this is annoying when the assets folder and items.otb are stored in different locations. It would improve usability if the application could independently remember the file path locations for opening the assets folder during launch and locating the items.otb in the OTB Editor.
Current Behavior:
- The application currently remembers the last file path location for both the assets folder and items.otb file.
Proposed Improvement:
- Introduce independent file path memory for the assets folder and items.otb.
- Allow the application to remember the last accessed file path for the assets folder separately from the file path for locating the items.otb.
Benefits:
- Enhanced flexibility for users with assets and items.otb stored in different locations.
- Streamlined workflow by eliminating the need to navigate through the file system when launching the application and using the OTB Editor.
Description:
The application currently remembers the last file path location opened when locating the assets folder and items.otb file. However, this is annoying when the assets folder and items.otb are stored in different locations. It would improve usability if the application could independently remember the file path locations for opening the assets folder during launch and locating the items.otb in the OTB Editor.
Current Behavior:
Proposed Improvement:
Benefits: