>> WHY?
Because the browser is making "a request". The request to open the popup. If it also wanted to run some code on the server side, that would be a separate request. That's do'able (on my side) but is a bad idea because you can't guarantee which of the 2 requests will run first. So "setting" a value in one, and then "using" it in the other would work some of the time, but not at other times.
>> is this a limitation? or a bug?
It's not a bug
- and I'm not sure if it's a limitation. It's just the way that a request/response architecture works.
>> then how can I pass parameters to the popup window?
there is a "parameters" option for the button itself. This takes the form of
'parameter=value&anotherparameter=someothervalue'In the destination procedure you can "store"the parameter in the SessionQueue
p_web.StoreValue('parameter')And then in that procedure you just use the SessionValue as you would naturally do.