Comments for McQuillen Interactive

Comment on TraceTarget and Remoting by Frank

Frank — Thu, 15 Sep 2011 03:33:33 +0000

If you walk through the Flex code, you will see what is wrong with the original code. Your original example will work if you set the filters before setting the traceTarget.level . In conclusion, just set the traceTarget.level last

Comment on Rotate the Y Axis Title in Flex Charting by CHRIS

CHRIS — Mon, 22 Aug 2011 06:55:31 +0000

A quick solution….

Comment on Rotate the Y Axis Title in Flex Charting by Bosilkovska

Bosilkovska — Fri, 01 Jul 2011 21:02:18 +0000

This is very useful!
It is the exact thing I wanted to implement in my flex charts.
All the best!

Comment on Flex 4 states, itemCreationPolicy and confusion by Simion

Simion — Wed, 25 May 2011 09:53:14 +0000

Hi, i found a problem when running my application developed on Windows on the Mac, I was trying to set the text of a label that existed on the default state and i got a null reference. I debugged the application and even my application was in the correct state when running the reationComplete handler
only the controls that appear in all the states were not null, the components from the first state(default one) that do not appear in the second state were null. This happened on Mac not on Windows, i fixed this by adding itemCreationPol;icy to the label that i wanted set

Comment on Flex 4 states, itemCreationPolicy and confusion by Zareh

Zareh — Wed, 04 May 2011 11:30:21 +0000

when itemcreationpolicy=\immediate\ its created immediately even all the children are created (you can check that in parent ) but none of preinitialize initialize even createchildren is called (funny children are created but createchildren isnt called) if you have an .as component not mxml put your init code in constructor ,

Comment on Flex Builder and Firefox cache problem by Jason Bronson

Jason Bronson — Wed, 27 Apr 2011 13:50:08 +0000

While this works well for you if you wish for your customers to not cache the new version you can use this method.

The way that I do it is to hide the real swf name using apache rewrites.
Use a .htaccess file to handle random file names and then reference it using a dynamic render swf name in php or another language like this

In .php template….
nocache_.swf

Then use this .htaccess file
Options +FollowSymlinks
RewriteEngine on
RewriteRule ^nocache_[0-9]+\.swf main.swf [NC]

This will then translate any url to main.swf behind the scenes

http://localhost/nocache_01.swf points to http://localhost/main.swf
http://localhost/nocache_02.swf points to http://localhost/main.swf
etc…

Comment on Flex 4 states, itemCreationPolicy and confusion by Yannick

Yannick — Tue, 04 Jan 2011 09:13:03 +0000

Hi!

Try the 4.5 framework.

I had the same kind of problem (a Box containing many boxes with states to have only one visible at a time).
With the ‘itemCreationPolicy=immediate’ they are all initialized at lauch, as expected.

Comment on Flex 4 states, itemCreationPolicy and confusion by Arend

Arend — Sat, 04 Dec 2010 10:00:10 +0000

Again, same issue here. Migration is becoming a nightmare because of this.

Comment on Flex 4 states, itemCreationPolicy and confusion by Gerry

Gerry — Sat, 04 Dec 2010 04:44:05 +0000

I found I can work around this by adding itemCreationPolicy=”immediate” to each individual component I want to access within a complex component in a view.
Where a component isn’t associated with a state I add a dummy state to exlude it from, otherwise you can’t use itemCreationPolicy.
Rather messy and time consuming, but the good news is you can add excludeFrom=”nothing” itemCreationPolicy=”immediate” to a container, even an mx conatiner such as a form, and all the components within it will be accessible, and I guess you still get some benefit from the lazy instantiation.

Comment on Flex 4 states, itemCreationPolicy and confusion by LePrau

LePrau — Thu, 21 Oct 2010 14:32:04 +0000

Same Problem for me, within a quite large application, I rely on the fact that (at least in flex 3) components marked with “creationpolicy=all” are created – and accessible! – before they are actually shown.
As I set a lot of properties via databinding (curly braces in mxml), a lot of my code does not work with spark. Great.

For the other way (setting values of possibly non-existing components) there is a workaround using proxy-vars.

Instead of:

function setTheName(name:String):void
{
button1.name = name;
}

use something like:

[Bindable] public var button1_name:String;
function setTheName(name:String):void
{
button1_name = name;
}