Comparing various ActionScript height and width properties upon initialisation on HTC Desire and the PlayBook simulator
UPDATE 10-Dec-2009: I’m pretty convinced now that this is an editor bug, not a Mac OS X bug. Essentially the editors are using default OS behaviour which I think is tailored for natural language editing rather than programme-code editing. Original post follows…
I’m currently finding in some applications that “word1.word2.word3” is being treated as a single word as far as the Option-Left Arrow and Option-Right Arrow is concerned on my Mac. This keyboard shortcut should hop word by word. But currently hops from one end to the other. Not an issue for most users, but pretty serious for a programmer working with dot-notation syntax.
I first experienced this working with ActionScript in Adobe’s Flash Builder Beta 2 and logged a bug report, but further investigation reveals that some unrelated applications show the same behaviour. I have now logged a bug with Apple, but in the meantime I would be interested to know if others are experiencing the same? Or if you are running 10.6.1 and not seeing this issue? Please add a comment – I’m still trying to work out if it is something installed on my system. I don’t think it is basic user preferences as I am seeing the same in another user-account on this system.
Editors incorrectly treating “word1.word2.word3” as a single word re opt-left and opt-right:
- FlexBuilder 3 MXML and AS editors
- FlashBuilder 4 Beta2 MXML and AS editors
- Apple Mail
- Apple OS TextFields including:
- Finder window find-file
- Safari: form-textfields & google search field
Editors showing correct opt-left opt-right behaviour:
- Adobe Flash CS4 IDE ActionScript Editor
- Adobe DreamWeaver CS4 editor
- Apple XCode editor
- Apple Finder – filename clicked and editable when renaming
- Firefox form-textfields and goodle search field
Quickly creating re-usable components based on others, augmented with additional ActionScript behaviour using MXML is as simple as can be. However, to create a component from scratch using ActionScript requires a lot of detailed knowledge of how the Flex framework works and the component life-cycle in particular.
The Flex documentation attempts to describe the lifecycle, but can leave the developer with lots of unanswered questions. When I got more involved in developing components I found chapter 19 of Programming Flex 3 good for filling in the gaps.
This week a new and free paper has been published by DevelopmentArc that also explores the component life-cycle and the application life-cycle. A very well worth while read….
Feel free to post links to other compent lifecycle resrouces in the comments.
My SimpleOscilloscope component described in an earlier post has now been updated to include a few filters controllable through setting styles. Of course like any other Flex component, it can have additional filtering applied in the normal way. I just felt like including these : alphaDecay, redMultiplier, greenMultiplier, blueMultiplier, blurX, blurY, scrollX, scrollY.
The documentation is correct, so i have no excuse, but I didn’t initially read much beyond the signature of the constructor…
public function BitmapData(width:int, height:int, transparent:Boolean = true, fillColor:uint = 0xFFFFFFFF)
I needed a transparent bitmap. Reading the default “transparent:Boolean = true”, I assumed by simply supplying width and height, a transparent bitmap is what I would get. Not so! I got a white rectangle. The reason being, that the default fill colour is 100% white. (The first pair of FFs representing the alpha in ARGB).
At first it would seem slightly unintuitive for the second default to conflict with the first, until one realises that the ‘transparent’ flag is there to indicate whether the object will support transparency or not. Not to state that it should be initially created transparent. Supporting transparency increases data size from 24 bits per pixel to 32 bits per pixel.
So what i should have done :
bmd = new BitmapData( width, height, true, 0 );
In the majority of my projects to-date, I am the sole developer on the project team. I was feeling the need to get into writing Flex components to a level that they could be distributed. Essentially making sure I use meta tags correctly and adding appropriate asdoc comments allowing other Flex developers to easily include the component as they would any other from the Flex SDK.
So, ccglib is an MIT license OpenSource project hosted on google code through which i plan to release a number of components. The first component released is SimpleOscilloscope, which plots the currently playing sound-wave. Designed to be easily sized, coloured and positioned through application of styles.
- the ccglib project on google code (get the source, or download the swc library)
- the test-bed demonstrating SimpleOscilloscope (view source enabled)
- Case-study added to my corporate site
- gotoandlearn : great tutorials on how to get started creating your own sound-wave visualisations with ActionScript
Finally got around to adding a case-study to my corporate site including a screen-cast of some of the features of my longest running project, a Flex/AIR application for communicating football moves and plays. Essentially a digital, animated version of a football tactic board.
More details and the screen-cast are on the creative-cognition case-study page.
… at the London Flash Platform User Group… tomorrow (29 Jan 2009).
Downloaded it, had a play, simple and effective. A ‘back’ button would be nice though in future versions 🙂
New Tour De Flex application looking like a very cool and a very useful resource. More information…
Basically it’s a Flex Component explorer as an AIR application and Eclipse plugin.
Just thinking I’d have preferred that the System Chrome was used in the AIR app to provide the min/max/close buttons rather than those alien windows style icons on the wrong side of the window. Mac user me! 😉