[flexcoders] Re: Passing values using mx:WebService

2009-02-05 Thread valdhor
here could. > > > > Tracy Spratt > Lariat Services > > Flex development bandwidth available > > > > From: flexcoders@yahoogroups.com [mailto:flexcod...@yahoogroups.com] On > Behalf Of m_ollman > Sent: Wednesday,

RE: [flexcoders] Re: Passing values using mx:WebService

2009-02-04 Thread Tracy Spratt
Flex development bandwidth available From: flexcoders@yahoogroups.com [mailto:flexcod...@yahoogroups.com] On Behalf Of m_ollman Sent: Wednesday, February 04, 2009 6:33 PM To: flexcoders@yahoogroups.com Subject: [flexcoders] Re: Passing values using mx:WebService

[flexcoders] Re: Passing values using mx:WebService

2009-02-04 Thread m_ollman
FYI ws call private function button_click():void { var wsOperation:Operation = ws.Assess; wsOperation.resultFormat = "e4x"; var atCall:AsyncToken; var sQ2:String = Q2.selectedItem.data;

[flexcoders] Re: Passing values using mx:WebService

2009-02-04 Thread m_ollman
Great advice and thanks for your comments valdhor & tracey. I have re-coded the ws call in AS - and am running into the "Error parsing request: Unexpected end element assess-request" (code @ EOM) I figure that means that this call has the Unexpected end element in it: var oRequest:Object = {Q2

[flexcoders] Re: Passing values using mx:WebService

2009-02-04 Thread m_ollman
Great advice and thanks for your comments valdhor & tracey. I have re-coded the ws call in AS - and am running into the "Error parsing request: Unexpected end element assess-request" I figure that means that this is braking it: var oRequest:Object = {Q2: sQ2, Q5: sQ5}; values are tracing ok

[flexcoders] Re: Passing values using mx:WebService

2009-02-04 Thread valdhor
I have to agree with Tracy - data service calls can be very tricky with mxml; I'd rather use AS. This thread may give you some pointers: http://tech.groups.yahoo.com/group/flexcoders/message/134966 --- In flexcoders@yahoogroups.com, "Tracy Spratt" wrote: > > I like mxml for a lot of things, bu

[flexcoders] Re: Passing Values between windows

2008-06-20 Thread valdhor
It may not be best practice but create a public variable in your main (WindowedApplication) file and then access it with Application.application.myPublicVariable. This can be a custom object if you need to have more data. --- In flexcoders@yahoogroups.com, "bredwards358" <[EMAIL PROTECTED]> wrote

[flexcoders] Re: Passing values

2006-02-02 Thread Geoffrey
he class. So change the id of your > local:teamList. > > Matt > > -Original Message- > From: flexcoders@yahoogroups.com [mailto:[EMAIL PROTECTED] On > Behalf Of Geoffrey > Sent: Thursday, February 02, 2006 12:36 PM > To: flexcoders@yahoogroups.com > Subject: [flex

RE: [flexcoders] Re: Passing values

2006-02-02 Thread Matt Chotin
ebruary 02, 2006 12:36 PM To: flexcoders@yahoogroups.com Subject: [flexcoders] Re: Passing values --- In flexcoders@yahoogroups.com, "Geoffrey" <[EMAIL PROTECTED]> wrote: > > I'm trying to pass the dimensions of the main window to a component > for positioning of a po

[flexcoders] Re: Passing values

2006-02-02 Thread Geoffrey
--- In flexcoders@yahoogroups.com, "Geoffrey" <[EMAIL PROTECTED]> wrote: > > I'm trying to pass the dimensions of the main window to a component > for positioning of a popup. I keep getting the following error: > >"Error /Main.mxml:18 > The property being referenced does not have t