also, have you put text in p_1 already? Because the order that Flash wants
is you setTextFormat on the text field, and then you put the text in it.
HTH
Gabino
Really? I thought it was the other way around - put text in, then set
the format, *unless* you are using
of input fields).
Regards,
Morten
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Peter B
Sent: Wednesday, April 16, 2008 5:23 PM
To: Flash Coders List
Subject: Re: [Flashcoders] code review
also, have you put text in p_1 already? Because the order
: Morten Barklund [EMAIL PROTECTED]
To: Flash Coders List flashcoders@chattyfig.figleaf.com
Sent: Wednesday, April 16, 2008 10:33 AM
Subject: RE: [Flashcoders] code review
Hi,
It is the other way around. setTextFormat is for formatting text currently
in the textfield (optionally text
Your code is correct and yes you can access text fields like that. I would
double check that main_content is named correctly as well as the text
fields.
On Tue, Apr 15, 2008 at 11:13 AM, Lehr, Theodore M (N-SGIS)
[EMAIL PROTECTED] wrote:
What is wrong with this code:
for (i=1; i6; i++) {
Hi Theodore
Have you tried it without the loop?
i=1;
_root.main_content[p_+i].setTextFormat(portNavOff);
_root.main_content[p_+i].text=hello world!;
also, have you put text in p_1 already? Because the order that Flash wants
is you setTextFormat on the text field, and then you put the text in
apart from the _root reference whichis never a good idea
check you lower-case / upper-case naming on your textfield
Flash will treat P_1 and p_1 as different fields.
in your loop your only mapping references to p_1, p_2, p_3 ... etc etc
and fields named P_1, P_2, P_3 ... etc will never be
If you aren't you should
Knee jerk reaction:
Nobody should use any pattern. They CAN use patterns if it benefits
the project, benefits their mental health and provides for a better
product. I probably read too much into it but pattern worship is
useless, crippling and annoying.
- A
Per
Hear hear.
Patterns are no magic bullet.
Alias
On 25/09/06, Andreas Rønning [EMAIL PROTECTED] wrote:
If you aren't you should
Knee jerk reaction:
Nobody should use any pattern. They CAN use patterns if it benefits
the project, benefits their mental health and provides for a better
product.
1. Comment your code!
Ah, yes, of course. Sorry about that. I'll comment it right away.
2. Are you using the MVC pattern? It's not really clear from the
code, but it looks somewhat like it
nope, I don't use pattern. I just want to make the HistoryList and
HistoryItem 'talk' to each other. I
Anggie Bratadinata wrote:
This is the simple app I created a few days ago, about which I'd like to
have your expert advice on how to improve it or maybe how to code it in
a much better way.
1. Comment your code! It looks structured enough, so adding comments should be
easy. If you use FDT,
10 matches
Mail list logo
