Steven,
Make sure you don't add a semi-colon at the end of the expression. If there is a semi-colon, the expression is interpretted as a statement, and the only statement that actually returns a non-zero value is "return theexpression;" If you just have "theexpression;" then this is just interpretted as another statement, and since there is no return statement encountered, it returns 0. I know, this is very easy to get wrong, but it's the way it would have to work if it were a c++ field, and we want to make flexscript as close to c++ as possible. When you remove the semi-colon, this is a special, flexscript-only rule that explicitly interprets the expression as a return statement, which allows you to not have to worry about always writing the return expression.
On the other one, we should improve the automatic scaling, as well as the precision of the numbers, but the graph is essentially correct. If you only have about 100 trucks go through your model each week, then the average number of trucks that travel through the gate each hour, which this graph is trying to show, will be less than 1, and the variances (the gray lines) will be huge because your samples are so small. The graph apparently isn't very good at displaying such low numbers coupled with high variances. I'll admit that this graph doesn't give you any useful information (except perhaps the daily and weekly averages), but at the same time, what useful hourly information would someone try to get out of a model that only has 100 containers going through it each week? Anyway, I'm really just grumbling a bit here, because I see your point, and we need to work on making the graph look more useful for any situation.
Last edited by Anthony Johnson; 06-12-2009 at 09:35 AM.
|
