Great tool and I second the request for more command line switches when used from a script, especially for the refresh interval. It seems odd that this is set to 'off' by default since the aim of the program is to show the progress of a rescue.
Great app and look forward to this new feature in v0.4! :)
As another idea, it would be useful if the app did not forget what log file was passed in from the commandline if it doesn't exist yet. In a script it would be quite common to start ddrescueview with a log that doesn't exist, and then start ddrescue with the same log file which would then be created and displayed. I'm currently working around this by creating an empty file first.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I will try to get back to development in the next days and implement the command line switches.
I found it reasonable to have the refresh interval off by default. The program does not determine if the mapfile is currently being written to, or if it is an old, archived file. In the latter case, it would be a waste to update the file every 30sec. I could perhaps add a File modification date detection to the routine which opens a map file. Then automatically enable refreshing (30sec) if the file has a recent (< 5min ) modification date. What do you think of this?
Regarding your other idea, I do not like the concept of opening a file that does not already exist. It would also need considerable code changes. Your current workaround seems reasonable to me. Let me know if you experience other problems with the usage of ddrescueview in a script.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Thanks for the program very much! Helps to visualize the rescue process and get a kind of surface/heads map.
I also used "modding" of the source code to get the program automatically update the map from the logfile/mapfile every time the logfile modification date is changed with check interval set in the "auto-update every ...". So, I think such a feature will be useful (auto-update on change + minimal interval of 5 sec.).
Also, I propose to ignore empty or incomplete file - !and do not crash the program!, just try a little bit later, when the logfile is completely updated by ddrescue.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
If you are willing to share, you can email me your mod that auto-updates the mapfile on change. If it is robust and cross-platform compatible it might get used in the next release.
Which version of ddrescueview did you use when you encountered a crash with an empty or incomplete mapfile? 0.4 alpha2 should not crash with such files.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Great tool and I second the request for more command line switches when used from a script, especially for the refresh interval. It seems odd that this is set to 'off' by default since the aim of the program is to show the progress of a rescue.
Great app and look forward to this new feature in v0.4! :)
As another idea, it would be useful if the app did not forget what log file was passed in from the commandline if it doesn't exist yet. In a script it would be quite common to start ddrescueview with a log that doesn't exist, and then start ddrescue with the same log file which would then be created and displayed. I'm currently working around this by creating an empty file first.
Hello Richard,
I will try to get back to development in the next days and implement the command line switches.
I found it reasonable to have the refresh interval off by default. The program does not determine if the mapfile is currently being written to, or if it is an old, archived file. In the latter case, it would be a waste to update the file every 30sec. I could perhaps add a File modification date detection to the routine which opens a map file. Then automatically enable refreshing (30sec) if the file has a recent (< 5min ) modification date. What do you think of this?
Regarding your other idea, I do not like the concept of opening a file that does not already exist. It would also need considerable code changes. Your current workaround seems reasonable to me. Let me know if you experience other problems with the usage of ddrescueview in a script.
Thanks for the program very much! Helps to visualize the rescue process and get a kind of surface/heads map.
I also used "modding" of the source code to get the program automatically update the map from the logfile/mapfile every time the logfile modification date is changed with check interval set in the "auto-update every ...". So, I think such a feature will be useful (auto-update on change + minimal interval of 5 sec.).
Also, I propose to ignore empty or incomplete file - !and do not crash the program!, just try a little bit later, when the logfile is completely updated by ddrescue.
If you are willing to share, you can email me your mod that auto-updates the mapfile on change. If it is robust and cross-platform compatible it might get used in the next release.
Which version of ddrescueview did you use when you encountered a crash with an empty or incomplete mapfile? 0.4 alpha2 should not crash with such files.
There is now a new version, ddrescueview 0.4 alpha 3, that adds command line switches for most of the program's settings.