easy to fix that (your gonna smack yourself when you see how easy it is!) <@assign local$uservarnames value="<@varnames scope='user'>">
<@rows array=local$uservarnames> user$<@col num=1> = <@var name="user$<@col num=1>"><br> </@rows> (: ----- Original Message ----- From: "MJPinckard" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Thursday, July 15, 2004 6:34 PM Subject: Re: Witango-Talk: Returning all variables within a scope > Unfortunately that seems to return just a list of names, and doesn't > include the values. I'm looking for something like zipcode=95123 > HeatEnergy=558, etc... this just returns zipcode and HeatEnergy (as a > single column array). > > Thanks anyway, but still looking.... > > Maggie > > Alan Wolfe wrote: > > ><@varnames scope="user"> > > > >that will give user scope, you can do any scope. > > > ><@argnames> returns a list of the post and search arguments (: > > > >if you cant figure out your problem, if you post the symptoms, it might be > >obvious what the issue is. > > > >If it's not obvious, there are several witango veterans that do witango > >consulting that could help you out (Ben Johansen I know for one). > > > >----- Original Message ----- > >From: "MJPinckard" <[EMAIL PROTECTED]> > >To: <[EMAIL PROTECTED]> > >Sent: Thursday, July 15, 2004 6:10 PM > >Subject: Witango-Talk: Returning all variables within a scope > > > > > > > > > >>What would the syntax be to capture all the variables in a specified > >>scope (e.g in the manner that the debugging prints all "request" and > >>"user" variables to screen)? > >> > >>I'm having an intermittent problem, and I'd like to log the user's > >>variables when the problem occurs, so I can identify the problem. My > >>thought is to capture variables whenever the error conditions are met > >>during the next few weeks (the testing period before go-live on this > >>code). My testers don't normally have debugging turned on, and if I turn > >>debugging on and reload the screen, the intermittent problem clears, so > >>I can't get details. > >> > >>I'm looking for something along the lines of <@PURGE scope="request">, > >>only to print, not purge. I tried <@var scope="request"> but it didn't > >>work. > >> > >>"Well it works for me" and "just reload, it'll go away" while accurate, > >>is not satisfying to my users. > >> > >>Thanks for your help. > >> > >>Maggie Pinckard > >>============= > >>Principal Research Associate > >>Enduse Forecasting > >>Lawrence Berkeley Laboratory > >>[EMAIL PROTECTED] > >>________________________________________________________________________ > >>TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf > >> > >> > > > >________________________________________________________________________ > >TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf > > > > > ________________________________________________________________________ > TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf ________________________________________________________________________ TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf
