The bit component set is, as claimed, infinitely easier to skin than MM’s components. Just drop the skin folder into your library and skin away. There a few caveats though:
TextInput component: The skin is misnamed in the library for some reason. Duplicate the textInputSkin movie clip and export the duplicate for actionscript with the name […]
While the vast majority of the components in the bit component set are compatible with Flash player 7, the combobox isn’t, and my client wanted player 6 compatibility (yes, despite the new stats that are out). Now I thought the problem might be due to the use of getNextHighestDepth, but in fact Keith thought of […]
I just finished bug-fixing an app of mine I made quite some time ago that uses the built-in Flash UI components. Looking at the finished product, the interface lacked a bit of polish, I thought; the components looked really good when they came out of the box a year or so ago, but now they […]
There are a few reasons why you would use a TextField and UIScrollbar instead of TextArea: making the scrollbar a different size than the text, Inputting the text visually instead of through the component properties, and changing the look of the surrounding border. In the bit component set, VertScrollbar and HorScrollbar don’t have built-in TextField […]
I’m running into issues mixing the Bit component set and MM’s built-in components. The trouble I’m having is that I need a datagrid, which is not included in the bit component set, so I have to use MM’s version. Now the Macromedia datagrid includes MM’s scrollbar and text input components, so the original Bit components […]