Is there a way to gracefully start and stop UE, meaning that the tasks will resume where they have been stopped?
Just some observations:
1) It seems that "Save all" does not save the entire status. At least I have lost once a big part of the task list. The lost part was added to a previously existing task list, it contained postings for download of attachements with erasure of the posting bodies.
2) When re-starting the program, I could not find a way to instantaneously resume with the pending tasks. I tried to connect to the newsserver by downloading new headers, and then the remaining tasks resumed after some time (more than a minute!) as well.
3) It seems there is no explicit "connect" or "disconnect" functionality, and these are handled implicitely through the task list. When exiting UE, does it automatically save the latest status?
4) Finally, when stopping/exiting UE with a large task list and starting again afterwards, the startup takes quite some time (I have seen that happening for more than 1 minute) and during that time the window with the progress bar is clogging and covering all other windows in the center of the screen.
Gracefully start and stop UE
is it linux related?
the program has mechanism to preserve all the data.
as to settings there is additional option properties->general->settings backup.
task queue and newsgroup headers are saved so the content is safe even during the save operation.
when you exit UE it saves the latest status, no need to disconnect anything.
try to enable error log in properties->general if normal exit you should see "logout" in the log, if you don't see logout but see only login maybe it is another problem with wine.
the program has mechanism to preserve all the data.
as to settings there is additional option properties->general->settings backup.
task queue and newsgroup headers are saved so the content is safe even during the save operation.
when you exit UE it saves the latest status, no need to disconnect anything.
try to enable error log in properties->general if normal exit you should see "logout" in the log, if you don't see logout but see only login maybe it is another problem with wine.
Maybe the non-saving of the status was really related to some Wine errors that I was encountering. These errors are rare now, but they happen once every few days.
I have checked in log.txt that
--Logout--
--Login-- (v1.3.1)
are generated.
BTW, I am attaching a trace of the errors that happen infrequently, the last one occured 5 days ago.
I have checked in log.txt that
--Logout--
--Login-- (v1.3.1)
are generated.
BTW, I am attaching a trace of the errors that happen infrequently, the last one occured 5 days ago.
the errors happened on very start, resource related in the third party GUI library which i'm using, i.e. wine related since i never saw them in windows, i could try to put an exception catcher but it is likely it will crash a bit later then, probably low on resources, wine in unstable state, windows early versions had similar problems.
as to logout while the program is running you should see "login" when you exited it adds "logout" with nothing else.
as to logout while the program is running you should see "login" when you exited it adds "logout" with nothing else.