Finally received some attention from Adobe and got an answer on this. The problem with long HTTP Authentication headers is that, by default, the Base64Encoder class will inject newline characters every 72 characters. Obviously that causes a chunk of the base-64 encoded string to be interpreted as a new header attribute, which causes the error. … Read more
I think JavaFX is more like Flex, because JavaFX is more about building applications than animations (which is, I gather, one of the sensitive distinctions between Flex and Flash). I think of JavaFX and Flex as the future heirs to Rich Internet Application programming. They’re both intended to stretch the realm of what’s possible with … Read more
The problem here is that a lot of the web discussions around this issue are a year or more old. I’m working through this same research right now, and this is what I’ve learned today. This IBM Developer Works article from August 2008 by Jorge Rasillo and Mike Burr shows how to do a Flex … Read more
human perception in general is logarithmic, also when it comes to things as luminosity, etc. … this enables us to register small changes to small “input signals” of our environement, or to put it another way: to always percieve a change of a perceivable physical quantity in relation to its value … thus, you should … Read more
In realy I advise to you don’t to use this too much… it is very expensive. Adobe need to create a native function to return this to us. But, for now… try this: You will need to cause a explicit coercion to get it! Because when you make and explicit coercion you get an Error … Read more
With AIR 2.0 you now can: if(NativeProcess.isSupported) { var file:File = File.desktopDirectory; file = file.resolvePath(“StyleLookupold.exe”); var nativeProcessStartupInfo:NativeProcessStartupInfo = new NativeProcessStartupInfo(); nativeProcessStartupInfo.executable = file; var process:NativeProcess = new NativeProcess(); process.start(nativeProcessStartupInfo); } You also need to add this to your descriptor file. <supportedProfiles>extendedDesktop</supportedProfiles>
I had this same problem. In my case I had a mx:Text block (that SHOULD have wrapped), and that mx:Text object was embedded within TWO mx:VBox containers. The only way that I got the text to wrap successfully was to do BOTH of the following: put the ‘ width=”100%” ‘ property into EACH VBox container … Read more
Mate is my pick. The first and foremost reason is that it is completely unobtrusive. My application code has no dependencies on the framework, it is highly decoupled, reusable and testable. One of the nicest features of Mate is the declarative configuration, essentially you wire up your application in using tags in what is called … Read more
A state machine is fun to write, but in this case I’d go with a signature pattern. Depending on where you want to put the handler (on the stage of the component), here’s some code that should work, though you can probably tighten it (and of course customize it to your specific need): // up-up-down-down-left-right-left-right-B-A … Read more