This repository has been archived by the owner on Mar 6, 2023. It is now read-only.
remove OK dialog on artwork write error #225
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
on batch runs, this makes the game import at every such error. the operator then needs to wake up, hit enter, and wait for the next error to come up, which is really annoying. the dialog is useless anyways because it doesn't say what the error is, it just says to look in the log... which we can do anyways, without the error message.
|
waiting for subscription to post on http://forum.kodi.tv/showthread.php?tid=70115&page=333 |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
on batch runs, this makes the game import at every such error. the operator then needs to wake up, hit enter, and wait for the next error to come up, which is really annoying. the dialog is useless anyways because it doesn't say what the error is, it just says to look in the log... which we can do anyways, without the error message.