Re: array parameter bug?

Hi Daniel,

I almost forgot to reply.

setPassIn(true) did not help to solve the problem.  The problem is not
if the value are retained but the problem is continues submission will
add more and more to the url until it reaches the server limit.  Thanks.


Jun

On Thu, 2004-04-29 at 02:03, Daniel P. Berrange wrote:
> On Mon, Apr 12, 2004 at 11:31:31PM +0800, Jun Yamog wrote:
> > Hi,
> > 
> > I would like to ask if there is a bug in ArrayParamter.  Using a
> > MultipleSelect or an ArrayParameter as a Global state param makes the
> > values grow larger and larger.  I have a test code that I have written
> > below to show this.  I really need this in a real world scenario.  In
> > the real world I have a form that serves as a filter of the paginated
> > results.  What happens is after a couple of filters the query string
> > gets too long.  I have tried several work-arounds, like using hidden var
> > and repopulating the multiple select. I think it boils that if the var
> > is a global and array parameter.  I need it as global since external
> > stuff uses the form and also so the paginator can pickup the current
> > state of the filter form.  
> > 
> > Try the code below, you can comment out "addGlobalStateParam" and see
> > that it does not happen anymore.  Is this a bug or am I not using
> > MultipleSelect properly? Thanks very much.
> 
> I believe that if you have a parameter as both a global state
> param /and/ assigned to a form widget, then you need to call
> 
>    m_sel.setPassIn(true)
> 
> At least I'm pretty sure this I what I used to do for one of our
> search forms that needed to accept a param passed in.
> 
> Dan.


-- 
Redhat-ccm-list mailing list
[email protected]
https://www.redhat.com/mailman/listinfo/redhat-ccm-list
Archives: https://www.redhat.com/pipermail/redhat-ccm-list/