App state fragility

Bugs and issues - current donor version.
Post Reply
Message
Author
candomez
Posts: 22
Joined: 06.08.2010, 18:49

App state fragility

#1 Post by candomez » 21.05.2023, 06:15

Would it be possible to update FreeCommander.hist.ini in real time, as each change occurs?
Since as it stands now, if FC exits abnormally or crashes, then the open tabs list and any similar history is lost.

horst.epp
Posts: 460
Joined: 15.11.2008, 20:18

Re: App state fragility

#2 Post by horst.epp » 21.05.2023, 17:20

Bad suggestion.
There may be dependend settings to be made
and in your case only half of it are stored if a crash occurs.
How often do your FC or OS crash while you are changing settings.
And how many changes to you make that you loose a lerge amount of lines or time.
Windows 11 Home x64 Version 23H2 (OS Build 22631.3296)
Everything Version 1.5.0.1371a (x64), Everything Toolbar 1.3.2, Listary Pro 6.3.0.67
FreeCommander XE 2024 Build 905 64-bit donor

candomez
Posts: 22
Joined: 06.08.2010, 18:49

Re: App state fragility

#3 Post by candomez » 21.05.2023, 19:38

You don't understand. And you're making guesses. This post is for the developer; just let him respond.

candomez
Posts: 22
Joined: 06.08.2010, 18:49

Re: App state fragility

#4 Post by candomez » 23.05.2023, 00:53

So when I open a new tab, for example, can that info be written to the history file (or wherever), so that the app's working state is recorded, while the app is actually open.

horst.epp
Posts: 460
Joined: 15.11.2008, 20:18

Re: App state fragility

#5 Post by horst.epp » 23.05.2023, 09:52

candomez wrote: 21.05.2023, 19:38 You don't understand. And you're making guesses. This post is for the developer; just let him respond.
Where is it stated that only Marek is allowed to respond to postings here ?
Marek can still respond even others made comments or questions.
Thats how discussion forums are working .
Windows 11 Home x64 Version 23H2 (OS Build 22631.3296)
Everything Version 1.5.0.1371a (x64), Everything Toolbar 1.3.2, Listary Pro 6.3.0.67
FreeCommander XE 2024 Build 905 64-bit donor

User avatar
Dreamer
Site Admin
Posts: 6113
Joined: 19.08.2007, 23:40

Re: App state fragility

#6 Post by Dreamer » 23.05.2023, 17:45

If the program is crashing often, try to find the reason and report it, please, it's not normal.

Workaround for the suggestion - main menu - Tools - Save Settings.

It's possible to create a toolbar button for "Save Settings" and even keyboard shortcut, so if you open the new tabs, you can save settings and opened tabs.

User avatar
Forez
Posts: 1312
Joined: 30.01.2016, 12:05
Location: In front of a PC monitor

Re: App state fragility

#7 Post by Forez » 25.05.2023, 22:10

Dreamer wrote: 23.05.2023, 17:45 If the program is crashing often, try to find the reason and report it, please, it's not normal.
I have been using FC for years, recently x64 portable - and despite numerous updates of it and my operating system I still get now and the a crash without a reason / pattern [i.e. to me they seem random]
horst.epp wrote: 21.05.2023, 17:20 Bad suggestion
[...]
how many changes to you make that you loose a lerge amount of lines or time.
As a result of those crashed I sometimes annoyingly loose both info and time, because I relay heavily on Tabs - which are not automatically saved in real time

So for me personally it would be a valuable addition, if Tabs would be remembered despite crashes of FC
Dreamer wrote: 23.05.2023, 17:45 Workaround for the suggestion - main menu - Tools - Save Settings.

It's possible to create a toolbar button for "Save Settings" and even keyboard shortcut, so if you open the new tabs, you can save settings and opened tabs.
I cannot possibly be clicking my Save The Settings icon after each Tab operation - and thus my losses occur, especially in a heat of workload

candomez
Posts: 22
Joined: 06.08.2010, 18:49

Re: App state fragility

#8 Post by candomez » 30.05.2023, 02:34

Dreamer wrote: 23.05.2023, 17:45 Workaround for the suggestion - main menu - Tools - Save Settings.
Tools > Save Settings isn't a work-around though, because it doesn't update FreeCommander.hist.ini, which is the file that tracks the opened tabs state, etc. In fact, it appears that file is only updated when you close the app... which of course kind of runs counter to using the app.

But if nothing else, it would certainly be helpful if that file at least got updated by Tools > Save Settings, especially since I have a script that periodically kicks off that operation and backs up my settings.

User avatar
Dreamer
Site Admin
Posts: 6113
Joined: 19.08.2007, 23:40

Re: App state fragility

#9 Post by Dreamer » 30.05.2023, 18:06

Opened tabs are saved in FreeCommander.ini file and this file is saved if the option "Save Settings" is used.

Tested:
- use default settings
- disable the tab options "Close all not locked tabs when the program ends" and the other "Close all tabs..." option below
- restart FC
- open multiple tabs
- use option "Save Settings"
- end task FreeCommander in Task Manager
- start FC

candomez
Posts: 22
Joined: 06.08.2010, 18:49

Re: App state fragility

#10 Post by candomez » 30.05.2023, 20:58

That's not what happens during a crash. And while there's tab info in FreeCommander.ini as well, Save Settings doesn't update FreeCommander.hist.ini, which is absolutely part of the app state's record.

Here's the bottom line: No matter which files/settings we're talking about, the app state lacks resilience. That's a fact. I.e. it's just not sufficiently preserved in real time. So if the system crashes for example, when you restart FC, you'll find that you won't get back the state you had previously - even if you just did a Save Settings beforehand. But even if a Save Settings had saved the apps state, it's limited in being a manual ad hoc step. So therefore what's ideal is if the app state is automatically recorded in real time, as changes occur, independent of whether the user randomly happens to do a Save Settings. This idea is a very common software feature/consideration by the way - it's not an exotic request.

So really at this point, how about if we finally just let @Marek weigh in.

Post Reply

Who is online

Users browsing this forum: No registered users and 34 guests