Save As does not update Recent Files list
Posted: Fri Jan 23, 2026 7:05 pm
A minor workflow issue observed in **LXPlan version 2.3.9 (19927 1)**.
### Issue Summary
When using **File → Save As** to save an existing plan under a new filename, the newly created file is **not added to the Recent Files list**.
### Steps to Reproduce
1. Open an existing plan
2. Select **File → Save As**
3. Save the file with a new name (e.g., adding a date stamp)
4. Open the **Recent Files** menu
### Actual Result
* The newly saved file does not appear in the Recent Files list
* User must manually browse to the file location and open it
* Once opened via the file browser, it then appears in Recent Files as expected
### Expected Result
* The newly saved file should immediately appear in the Recent Files list after a successful Save As operation
### Impact
This has caused occasional confusion when saving multiple versions of a plan (e.g., iterative saves with date-based filenames), as it can appear that the file was not saved or was overwritten when it was actually created correctly but not listed yet.
This is a minor issue, but addressing it would improve versioning workflows and reduce user friction.
For context, I’ve been using LXPlan regularly and recommending it to my students, great software overall.
Thank you for your time and continued development.
### Issue Summary
When using **File → Save As** to save an existing plan under a new filename, the newly created file is **not added to the Recent Files list**.
### Steps to Reproduce
1. Open an existing plan
2. Select **File → Save As**
3. Save the file with a new name (e.g., adding a date stamp)
4. Open the **Recent Files** menu
### Actual Result
* The newly saved file does not appear in the Recent Files list
* User must manually browse to the file location and open it
* Once opened via the file browser, it then appears in Recent Files as expected
### Expected Result
* The newly saved file should immediately appear in the Recent Files list after a successful Save As operation
### Impact
This has caused occasional confusion when saving multiple versions of a plan (e.g., iterative saves with date-based filenames), as it can appear that the file was not saved or was overwritten when it was actually created correctly but not listed yet.
This is a minor issue, but addressing it would improve versioning workflows and reduce user friction.
For context, I’ve been using LXPlan regularly and recommending it to my students, great software overall.
Thank you for your time and continued development.