Add buttons to Validate report to fix problems

[GoogleCodeExporter]

The built-in Validate function would be better if the results included a way to 
fix the problem right there rather than having to correct each one manually.

For example, if Validate finds a manifest references to a missing file there 
could be a button for that error that when pressed would delete that line from 
the manifest.

For files that are not included in the manifest, perhaps 2 buttons - one to add 
it to the manifest, another to delete the file. 

I am using Sigil to split a book that is too big for my device into parts. This 
creates a LOT of errors that are tedious to fix. Fixing them all takes a lot of 
time to fix them all. If I could click a button, or select check boxes, this 
would allow me save me a lot of time.

Original issue reported on code.google.com by KanyonK...@gmail.com on 19 Jul 2013 at 3:48

[GoogleCodeExporter]

I agree - it would be great if errors like:

The <item> element's "media-type" attribute has value "application/xxxx", but 
the file's media type is "application/yyyyy"

could be solved with a mouseclick.

Original comment by fischer....@gmail.com on 24 Jul 2013 at 8:44

[GoogleCodeExporter]

Original comment by john@nachtimwald.com on 24 Jul 2013 at 10:07

[GoogleCodeExporter]

At least it should open the manifest file and move the cursor to the location 
of the error when DoubleClick-ing on the error in the Validation Results 
window. 

This would give the user the choice to deal with it manually (maybe its a 
simple typo).
Just the feature to open where the error was found would be of tremendous help.

Actually i just created an issue on this. Should be easier to implement too. 

Original comment by edys...@gmail.com on 15 Aug 2013 at 7:10

[GoogleCodeExporter]

Original comment by john@nachtimwald.com on 3 Nov 2013 at 2:26

• Changed state: Closed