<br><div class="gmail_quote">On Mon, Dec 14, 2009 at 12:32 PM, Peter Plessas <span dir="ltr"><<a href="mailto:plessas@mur.at">plessas@mur.at</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div><div></div><div class="h5"><br>
</div></div>What about this:<br>
Perhaps indicate the successful loading of those files in the post<br>
window instead of posting an error message when the files are not around.<br>
I routinely check the Pd window for errors at startup, and stumble<br>
accross the gem.conf "error" messages. Wait, hu? What's there? (relief)<br>
oh, only the new gem feature. :-)<br>
Since gem.config is an optional and probly very useful mechanism<br>
changing the way the file loading mechanism reports back might make the<br>
current "problem" much less of an issue?<br>
<br></blockquote><div><br>From the usability perspective, that's trivial. Don't say error when there's no error. What about "foreach error: no more elements in array"? :) Just think how many people feel alerted just when Make says "Nothing to do" :))<br>
When there is no conf file found anywhere, that case could throw an error - of course only if at least one conf file is required or recommended.<br><br></div></div>Andras<br>