Forum - Public Discussion and Support
https://www.ghisler.ch/board/
I think you're just plain wrong then. Lots of apps have well functioning crash recovery.Dalai wrote: Yeah, well, that's where you don't get my point. I think that it won't help in most cases, only in some cases in which the data has been written to disk correctly.
And that's as far as I read, since it became obvious you're the same person who was blocked. I won't waste my time for another round of you flawed logic/reasoning,thinly veiled hostility and arrogance.sirsilver wrote:first you start by CLAIMING
That'd be cool. Isn't there a trick to call that function periodically?Hacker wrote:Yup, that one is very useful. I don't think it would hurt anyone if there was an ini option AutoSaveSettingsEveryXMinutes=10.cm_ConfigSaveSettings
Roman
Not to mention that corruption can be avoided.Hacker wrote:Dalai,I don't get it. If a system crashes, say, once a week, and TC saves its config every ten 10 minutes for half a second, why do you assume that in most cases the system crashes exactly during those 0,5 seconds while TC is saving its config? All else being equal, the chance of this happening is 1:1200.I think that it won't help in most cases
Roman
Dalai wrote:In short: if you really want to make sure that TC saves your settings you have to force the system to flush the file-system buffer (only TC's data of course), thus writing the data to disk. Otherwise you can't be sure it really gets there correctly (uncorrupted). To make one thing clear: I'm not talking about the cache of the drive/disk itself, only the OS's buffer/cache. If the data is still on the drive's cache, it's out of TC's, and even the OS's, hand.
It's like you're trying to make fun of yourself. You've been complaining about one thing for several posts, and now you just point out that there's a solution to that and that it's a non-issue.Crash recovery is a different thing than just saving the settings file at intervals. I just wanted to point out that just saving wincmd.ini probably won't achieve much because the OS decides when to write it to disk, unless you force it to do so (and at this point, I don't know if it can be done). You have to know how the system works/behaves before making a concept of some auto-save/crash recovery/backup or whatever you call it.avada wrote:Lots of apps have well functioning crash recovery.
I just said that that's the way TC (or any other program) would have to take. I don't know if such a function exists and whether it can be used in this case, if it would make things better or not. That's not so difficult to understand, is it?You've been complaining about one thing for several posts, and now you just point out that there's a solution to that and that it's a non-issue.
Code: Select all
'On Error Resume Next
'//Purpose: create an copy of 'WINCMD.INI' every x minutes.
'//Put this script as text file 'WINCMD.INI_Backup.VBS' in TC folder and launch it.
'//Create a text file 'WINCMD.INI_Backup.NO' in TC folder to stop this script from executing.
'//Delete 'WINCMD.INI_Backup.NO' and launch 'WINCMD.INI_Backup.VBS' to run it again.
'-----------------------------------------------------------------------------------
Set FSO = Wscript.CreateObject("Scripting.FileSystemObject")
Const Seconds = 1000 '// 1000ms=1Second
Const Minutes = 60000 '// 60*1000=1Minute
Const HalfHour = 180000 '// 1800*1000=1/2hour
Const Hours = 3600000 '// 3600*1000=1hour
Const HalfDay = 43200000
Do While(true)
N = Now
'W = WeekdayName( Weekday(N), true)
D = Year(N) &"-"& Right("00" & Month(N), 2) &"-"& Right("00" & Day(N), 2)
T = Right("00" & Hour(N), 2) & Right("00" & Minute(N), 2) & Right("00" & Second(N), 2)
FSO.CopyFile "WINCMD.INI", "WINCMD.INI - Kopie " & D &"_"& T & ".INI"
If fso.FileExists ("WINCMD.INI_Backup.NO") Then WScript.Quit
Wscript.Sleep 2*Hours '//SLEEP in milliseconds
Loop
This AHK script should tell TC to save its settings every 10 minutes (600000 ms):That'd be cool. Isn't there a trick to call that function periodically?
Code: Select all
#Persistent
#NoEnv
SetTimer, SaveTcSettings, 600000
Return
SaveTcSettings:
PostMessage, 1075, 580, , , ahk_class TTOTAL_CMD
ReturnSpeaking from the future, I thought I'd try implementing this for my interest and for that of others.Hacker wrote: ↑2016-06-13, 14:21 UTC avada,This AHK script should tell TC to save its settings every 10 minutes (600000 ms):That'd be cool. Isn't there a trick to call that function periodically?HTHCode: Select all
#Persistent #NoEnv SetTimer, SaveTcSettings, 600000 Return SaveTcSettings: PostMessage, 1075, 580, , , ahk_class TTOTAL_CMD Return
Roman
I though setting cm_ConfigSaveSettings for alt+tab might work as a workaround. But apparently TC doesn't get a chance to capture it.
An Alt+Tab key event is normally not sent to an application, but directly handled by Windows. To process Alt+Tab, an application would need to install a hook procedure. Funnily enough, despite not hooking Alt+Tab (<== my bold assumption based on shallow, surface-level observations), TC allows to define a (non-functional) Alt+Tab hotkey.
I know. I tried.elgonzo wrote: ↑2020-11-12, 19:50 UTCAn Alt+Tab key event is normally not sent to an application, but directly handled by Windows. To process Alt+Tab, an application would need to install a hook procedure. Funnily enough, despite not hooking Alt+Tab (<== my bold assumption based on shallow, surface-level observations), TC allows to define a (non-functional) Alt+Tab hotkey.