can someone else test and/or confirm bug?

[christappan]

In a new dialog, the Server-side onDialogInitialize Event, I don't seem to be able to access page variables using e.rv as instructed in the information and as I've used in Grids in v10.

I've put a dialog on a page and for testing, made the variable display on the page correctly while I then get this:

Error executing onDialogExecute event: Error executing event 'onDialogInitialize ': command: args.add("CalledFileID",e.rv.CalledFileID) Property not found e.rv.CalledFileID subelement not found.

If anyone's willing, please just stick the following code in a simple dialog's onDialogInitialize Server-Side event:

e.javascript = "alert('" + e.rv.var1 + "');"

Then save the dialog, click save page to place it on an a5w page and put this on the a5w page above the other a5 code blocks:
dim var1 as C = "hello world"

Publish them both and open the page in local host.

Thanks.

[Peter.Greulich]

Re: can someone else test and/or confirm bug?

Chris I get an error as well. But if I do this, it works fine:


e.javascript = "alert('" + e.session.var1 + "');"

dim session.var1 as C = "hello world"

[Selwyn Rabins]

Re: can someone else test and/or confirm bug?

There is absolutely no question that page variables are being seen in the all of the server side events in the Dialog component.

You can easily verify this by putting this code in the onDialogInitialize event

dim msg as c
if eval_valid("e.rv.pagevara") = .f. then 
	msg = "Page variable not found."
else
	msg = "Variable found: " + e.rv.pagevara 
end if 

e.javascript = "alert('" + js_escape(msg) + "');"

Then when you run the component in the browser, use this url (where 'mypage' would be replaced by the name of your own .a5w page that contained the dialog)

http://localhost:11001/LivePreview/mypage.a5w?pagevara=alpha

[christappan]

Re: can someone else test and/or confirm bug?

Selwyn, it works for me when I pass the variable in the URL but not if I dim the variable on the page itself.

I created a dialog only for testing, so it's got one textbox control and nothing in any events etc except this in the onDialogInitialize:

dim msg as c
if eval_valid("e.rv.var1") = .f. then 
	msg = "Page variable not found."
else
	msg = "Variable found: " + e.rv.var1 
end if 

e.javascript = "alert('" + js_escape(msg) + "');"

I saved the dialog, then used Save Page to create the a5w page, with which I did nothing but added the following code as the first thing on the page within a5 tags (i.e. before any part of the component is loaded, etc):

dim var1 as C = "hello world"

?"var1 on the page = " + var1

I published both to localhost and when I run the page, I get "var1 on the page = hello world", then an alert box saying "Page variable not found."

How would one set a variable on the page and then access it?

[Selwyn Rabins]

Re: can someone else test and/or confirm bug?

If i understand correctly what you are saying, then you have an .a5w page that runs a dialog, and you page looks something like this:

<%a5

dim var1 as C = "hello world"

Delete tmpl_mydialog
DIM tmpl_mydialog as P
tmpl_mydialog = a5w_load_component("mydialog") ''SYSTEM GENERATED COMMENT - PLEASE DO NOT REMOVE (LOAD:mydialog)

'Override settings start -----------------------------------------
with tmpl_mydialog
.alias = "mydialog"
_dialogFilename = "mydialog"
end with 
'Override settings end -----------------------------------------

delete x_mydialog
dim x_mydialog as p
x_mydialog = a5w_run_Component(tmpl_mydialog) 'SYSTEM GENERATED COMMENT - PLEASE DO NOT REMOVE (RUN:tmpl) (EDIT:mydialog)

the 'dim var1 as c = "hello world"' is your code and the rest is generated code.

inside the dialog's onInitialize event, you want to see var1.

is that correct?

There is no way that what you are doing will work, or should even be expected to work.

var1 is not a 'pageVariable'. it is simply a local variable in a script. and since it is not being passed into the function that executes the dialog (a5w_run_component()) there is no reason why it should be visible.

pageVariables are special. they are defined in the query string. they are NOT the same as local variables in a script. this is a very important distinction.

all of the above being said, you can still make a local variable visible in the component.

you will notice that the dot variable 'tmpl_mydialog' is passed into the a5w_run_component() function.
so you could make var1 a member of this object.
e.g.

tmpl_mydialog.mylocalVariables.var1 = var1

then, inside your server side event you can refer to e.tmpl.mylocalVariables.var1
(not tmpl_mydialog, just tmpl)

[christappan]

Re: can someone else test and/or confirm bug?

As usual, Selwyn, you went further in helping than I probably deserved. Thanks.

[Selwyn Rabins]

Re: can someone else test and/or confirm bug?

you are welcome!