Subject: Re: [flexcoders] Passing values from popup window to MXML component
Yeah you can do what rohit said by adding a logout button at the same place and
toggling the visiblity.
This way,
From you main application you can do something like this.
if(loginWin. userInput. text
@yahoogroups.com
Subject: [SPAM] Re: [flexcoders] Passing values from popup window to MXML
component
Hi,
I have written a function and after checking the username and password, to
toggle the buttons, but I get the following error:
TypeError: Error #1009: Cannot access a property or method
property.
Cheers
_
From: Rohit Sharma rohit.sharma1...@gmail.com
To: flexcoders@yahoogroups.com
Sent: Mon, November 9, 2009 12:21:02 PM
Subject: Re: [flexcoders] Passing values from popup window to MXML component
You can add a logout button at the same place as login button and toggle
Hello All,
I was trying to create a login Page. The page has one main MXML application
file with couple of MXML components. The First component contains the following:
Component1.mxml:
?xml version=1.0 encoding=utf-8?
width=60% height=261
mx:Script
![CDATA[
import
You can add a logout button at the same place as login button and toggle
the visibilities of these buttons depending upon the
state of your component.
On Mon, Nov 9, 2009 at 9:58 AM, Funand Learning
funandlearni...@yahoo.comwrote:
Hello All,
I was trying to create a login Page. The
: Rohit Sharma rohit.sharma1...@gmail.com
To: flexcoders@yahoogroups.com
Sent: Mon, November 9, 2009 12:21:02 PM
Subject: Re: [flexcoders] Passing values from popup window to MXML component
You can add a logout button at the same place as login button and toggle the
visibilities
Hiya flexcoders
Trying to pass values to a SOAP request. Having some fun :-)
Working with mx:WebService - got it working by placing the SOAP
request inside of the mx:request tag and adding the namespace in
mx:application-
xmlns:typ=http://ruleburst.com/ruleserver/9.1/rulebase/types;
(code @ EOM
From: flexcoders@yahoogroups.com [mailto:flexcod...@yahoogroups.com] On
Behalf Of m_ollman
Sent: Tuesday, February 03, 2009 10:39 PM
To: flexcoders@yahoogroups.com
Subject: [flexcoders] Passing values using mx:WebService
Hiya flexcoders
Trying to pass values to a SOAP request. Having some fun
In the application I'm currently developing, end users need to log in
to utilize it. Also I need to keep track of who is logged in so that I
can input that into a local database after certain actions. I've tried
using a public variable in a commonly used class, however since an
instance of that
Hi,
I am working on an exisiting application and trying to pass value to
opup components. I don't know if I am not doing it right but the
values are not being passed and then calling the correct HHTP call
for the data. Can anyone point me to the right direction besides the
Adobe live docs,
PROTECTED] On
Behalf Of ming4u2
Sent: Wednesday, September 26, 2007 1:01 PM
To: flexcoders@yahoogroups.com
Subject: [flexcoders] Passing Values to popup components and then
passing back
Hi,
I am working on an exisiting application and trying to pass value to
opup components. I don't know if I am
I would like to attempt to separate my filter functions from my view
so that I am not duplicating code when two views share similar filter
functions. My idea was to create a class that contains a
ListCollection and all the appropriate FilterFunctions for that
collection. The
I'm using a FilterClass, which holds just the filterFunction and some
optional ways to configure the filtering.
Every collection, which needs filtering, gets an instance of this
FilterClass by assigning collection.filterFunction = filter.filterFunction;
Cheers,
Ralf.
On 5/24/07, Kevin [EMAIL
using this approach the filter functions still need to reference the
view to get optional filter parameters correct. For example, if you
want to filter based on a user inputed text field you can just do this:
collection.filterFunction = filter.filterFunction (textFld.text);
since the
I simply assign the input values to some properties of the filter whenever
they change.
Cheers,
Ralf.
On 5/24/07, Kevin [EMAIL PROTECTED] wrote:
using this approach the filter functions still need to reference the
view to get optional filter parameters correct. For example, if you want to
Hi,
I find sometimes just subclassing ArrayCollection works. This way your are
defining certain types of collections that do different things.
You can then add functionality to the class with methods or whatever. This
works well for me. Then I define the different filter functions based on
that
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 the static
attribute.
Here are some code snippets:
-- Main.mxml --
mx:Panel
17 matches
Mail list logo
