Ability to Close Currently Open Project
Original Reporter info from Mantis: WILL
-
Reporter name: Jason McMillen
Original Reporter info from Mantis: WILL
- Reporter name: Jason McMillen
Description:
It's currently the practice for Lazarus to always have a project open, however this causes a few problems as you can only save some changes to the project once you open another one or close Lazarus.
This may make you wonder well why would you want to close the current project before opening another one OR why would you want to close your project when you're going to close Lazarus anyways.
Reasons for being able to do this:
-
It gives assurance to the user that they have closed and saved all changes to their work should there be any complications while closing Lazarus.
-
It's more logical to have an empty slate when you open Lazarus than to start off looking at code for a previous project you've been working on. Especially if you work on several projects all the time.
-
You don't have to worry about inadvertently messing up your previous project or it's code by accidentally doing something before you open or create a new application/program and realize it only after having saved the changes to the project.
-
It's far less confusing if you are borrowing code from partnering projects and swapping between them to see if the latest changes would compile.
-
Some people just have more trust in saving their work before closing the IDE.
-
Makes Lazarus look more professional as a commercially viable development environment for business.
These are just my reasons, but I'm sure that there may be others.
Mantis conversion info:
- Mantis ID: 8097
- Target version: post 1.0