I discovered an uninitialized variable bug in the patch I posted for
multiple databases.
In the constructor for "Display", the member variable "search_policy"
should be initialized to NULL.
search_policy = NULL;
It is actually for the "search_policies" feature, which is probably
redundant due to "allow_in_form". So, once the code for
"search_policies" is stripped away, the above problem will
be irrelevent.
/Raj
Gilles Detillieux wrote:
> According to Rajendra Inamdar:
> > One of the motivations behind the search_policies attribute was to
> > make the user selection persistent over multiple search sessions. If
> > the selection is not persistent, it is very likely that the user may
> > not notice that something changed. It is not clear if "allow_in_form"
> > can be used to achieve similar effect.
>
> Yes, the whole idea behind this attribute is not only to allow certain
> attributes to be overridden by input parameters, but also to propagate
> these parameters to the follow-up search form and buttons. The only
> thing it doesn't do is make a select list out of the attribute.
>
> To do that, you can use build_select_lists. Its whole purpose is to
> make select lists out of any input parameter, so that the selected
> value is propagated to the follow-up search form.
>
> See http://dev.htdig.org/htdig-3.2/hts_selectors.html for details.
>
> --
> Gilles R. Detillieux E-mail: <[EMAIL PROTECTED]>
> Spinal Cord Research Centre WWW: http://www.scrc.umanitoba.ca/~grdetil
> Dept. Physiology, U. of Manitoba Phone: (204)789-3766
> Winnipeg, MB R3E 3J7 (Canada) Fax: (204)789-3930
------------------------------------
To unsubscribe from the htdig3-dev mailing list, send a message to
[EMAIL PROTECTED]
You will receive a message to confirm this.
