not sure u need an essay to describe the errors (if help is sufficiently
well done as it is in evo).
if u popup something like 'unable to parse', shpould probably display
what it couldnt parse - since its basicvally debug for an internal
error.
On Tue, 2002-08-20 at 11:27, Chris Toshok wrote:
> I added support for an actual result for searches (god I can't believe
> we hadn't added this earlier...) This should help with LDAP
> autocompletion (as soon as I write the code), since if the search
> completes successfully we'll be able to cache the results.
>
> Right now, the following results are available:
>
> SUCCESS (the query worked, heh)
> TIME_LIMIT_EXCEEDED (mostly useful for ldap/active directory)
> SIZE_LIMIT_EXCEEDED (mostly useful for ldap/active directory)
> INVALID_QUERY (if the backend failed to parse the sexp)
> OTHER_ERROR (another backend error that doesn't map to the above)
> UNKNOWN (points to an internal error, since it's never sent by the
> backend and is only used by the front end if the returned code isn't one
> of the above).
>
> in the non-SUCCESS case, evo will pop up a dialog after the search
> result is returned. The real question I have is what the strings should
> be - the ones I committed probably won't remain as is, but they're a
> good first pass at least. Here's the code mapping from result to
> string:
>
> switch (status) {
> case E_BOOK_VIEW_STATUS_SUCCESS:
> return;
> case E_BOOK_VIEW_STATUS_SIZE_LIMIT_EXCEEDED:
> str = _("More cards matched this query than either the server is \n"
> "configured to return or Evolution is configured to display.\n"
> "Please make your search more specific or raise the result
>limit in\n"
> "the directory server preferences for this addressbook.");
> break;
> case E_BOOK_VIEW_STATUS_TIME_LIMIT_EXCEEDED:
> str = _("The time to execute this query exceeded the server limit or
>the limit\n"
> "you have configured for this addressbook. Please make your
>search\n"
> "more specific or raise the time limit in the directory
>server\n"
> "preferences for this addressbook.");
> break;
> case E_BOOK_VIEW_STATUS_INVALID_QUERY:
> str = _("The backend for this addressbook was unable to parse this
>query.");
> break;
> case E_BOOK_VIEW_STATUS_OTHER_ERROR:
> case E_BOOK_VIEW_STATUS_UNKNOWN:
> str = _("This query did not complete successfully.");
> break;
> }
>
> Anyone have any thoughts/suggestions?
>
> Chris
>
> _______________________________________________
> evolution-hackers maillist - [EMAIL PROTECTED]
> http://lists.ximian.com/mailman/listinfo/evolution-hackers
_______________________________________________
evolution-hackers maillist - [EMAIL PROTECTED]
http://lists.ximian.com/mailman/listinfo/evolution-hackers
