Suggestion for autoclose?

[fbungarz]

Not sure what people here think about an idea I just had.
Some routine tasks in PSu can take quite a lot of time, for example, compacting the database, backup, verifying folders and files and then importing new ones.
I'd like to run such tasks at the end of the day and when successful have the option to automatically shut down the application. But perhaps that is not a good idea?

[G8DHE]

I like the idea, but it does mean that if there are any actions that need carrying out, say after Verifying, then the close won't happen only to be found perhaps the next morning?
But in general yes perhaps an extension the the Scheduled Verify options with Compact and Backup would be sufficient?

[RobiWan]

But perhaps that is not a good idea?

I think it depends on your preferences.

I myself newer use compact database"or backup. I do this outside PSU.
And "verify folder" are tasks I'm running scheduled on times I'm not on my PC.

If I want to start or end PSU, it should happen “now” and not after a long time

[Hert]

While not exactly what you're asking for, since v2024.2 you can schedule a Verify Folder to run when closing down the application.

ScheduleClose.png (29.63 KiB) Viewed 6238 times

[G8DHE]

Just tried that and it runs a Verify instantly after OK and then again when the application closes is this right ?

[Hert]

Just tried that and it runs a Verify instantly after OK and then again when the application closes is this right ?

That is correct. When you schedule a Verify Folder it always runs it now...and after that when the trigger occurs again.

[roddyt]

have the option to automatically shut down the application.

Not something I would have any interest in, but I'm curious as to why you need to shut down the application. I hardly ever shut it down (and that goes for most applications I use regularly). I don't know if I am missing something by leaving it running all the time.

[G8DHE]

Thanks Hert! I see you have removed the extra instant Verify when you set it up for a scheduled Verify on Close

[fbungarz]

Thanks everyone for their ideas/input/feedback.

If I want to start or end PSU, it should happen “now” and not after a long time

To clarify: of course I do not want this to happen when PSU starts. I mentioned in my original post that I would like to be able to schedule a task like compacting and then have PSU shut down afterwards.

And "verify folder" are tasks I'm running scheduled on times I'm not on my PC.

Well, that's why I thought it might be nice to have an option to shut down the program afterwards.

Iuse profile in SyncBack that at night automatically does an incremental backup of my database on Backblaze and it then shuts down the PC. That external backup requires that the PSU databases (main+thumbs) are closed and not locked. So, if I run something like verify or compacting and then leave the PC, SyncBack cannot backup the database and then shut the computer down.

Not something I would have any interest in, but I'm curious as to why you need to shut down the application.

Everyone is different, but I don't like leaving the computer running when I am not using it. First, it just consumes energy for no reason. Then, I have experienced that applications generally become unstable even even freeze, when they are not shut down for a long time. And in my experience PSU typically is a lot faster after a restart - especially after having compacted the database.

I myself newer use compact database"or backup. I do this outside PSU.

Though I occasionally use SQLite Express for compacting, but I do this mostly from inside the application (I believe Hert once mentioned on the forum that this is better than using external tools, because the internal compacting in PSU adds some additional routines).

While not exactly what you're asking for, since v2024.2 you can schedule a Verify Folder to run when closing down the application.

Great. Perhaps we could do that with other time-consuming tasks too - like compacting?
But rather than scheduling it for every time when the program shuts down, it would be nice to be able to do this occasionally only. Thus, that this runs immediately after scheduling and then again when the application shuts down seems not ideal. The reason that I would want to schedule compacting the database would be so, I can work on the database now and then run the compacting when I am done and close the application...