*[A WHILE AGO ON FLASHCODERS...]* On 8/3/05, Iestyn Lloyd <[EMAIL PROTECTED]> wrote:Hi all,
i've skinned the FMX2004 scrollpane component by altering the ScrollBarAssets MC, and now i've been told that i need to have 2 completely different skins for the scrollpane - and that they need to be shown at the same time. Is this possible? If so... err.. how? :) * [SOUND OF CRICKETS CHIRPING] ie: nobody replied. * ------------------------------------------------------------------- I need to do the same thing with a Window component, and have perhaps an easier question about the ComboBox. I've been studying and working with Themes, Styles and Skinning for the V2 Components on a project with a deadline that has come and gone - we're behind! The project was developed using the V2 components early on, with the skinning of the components and final design implementation saved for last. I was recently brought into the project to do this work, and have found working with the v2 components to be, well... difficult to accomodate. I have since dug my heels in, and am doing the best I can under the circumstances. We've been successful at skinning the RadioButton and CheckBox, and have had limited success with the ComboBox. Button and Window have been the most difficult. If you look at the built-in Macromedia Help, there's lots of detailed information on the subjects. Here are my questions, and thanks in advance for any help provided! 1) Window I need to create several instances of the Window component - some with TitleBackgrounds (standard MenuBars with a Title and a Close Button), and some without. If you read the Help section [Components Language Reference/Window Component/Customizing The Window Component] you'll see what you can do with Styles and Skins. The TitleBackground is a skin element only, so if you customize the skin to delete the TitleBackground... it affects ALL instances of the Window component. I would have liked to see a Window Style setting "TitleBackgroundVisible:Boolean" which could be set to TRUE or FALSE. Or better yet, a Style setting that would accomodate ["Default", "Disabled", "CustomLinkageID"]. I started creating a custom MyWindow component that simply opens a container with a close button (the simplest form of window), but I ran into other problems. To create the window I'm struggling with, a custom built DialogBox class is called first, which creates an instance of a Window that depends on (Macromedia's built-in) PopUpManager class to manage overlapping Windows and their Modality. Without using the actual Window component, these features are unavailable without doing lots of extra research, development and testing. MY QUESTION IS: Is there any way to create more than one standard Window component that PopUpManager will recognize? It seems we are locked in when we use the Window component to ONE SKIN per document. I would love to use a standard Window component for application wide usage, but have additional custom Window implementations with custom graphics that reference elements in more than a single "Window assets" folder inside a single THEME. 2) ComboBox I edited the skin graphics for ComboBox inside the ComboBox assets folder. We're currently basing our THEME on the standard HALO THEME. Currently the highlight of the ComboBox when you pull it down is green. I looked into the ThemeColor Style setting for Halo's ComboBox and was surprised to see three possible values - ["HaloGreen", "HaloBlue", "HaloOrange"]. I dug into the components FLA file to try to figure out why there might be a limited three settings in a Style, and couldn't figure it out. Maybe you'll laugh when I say I would have appreciated a "HaloGrey" option... but I'm not laughing. Can someone please tell me how to achieve GREY??? --------------------- CONCLUSION --------------------- I would have preferred to write my own classes or custom components for this type of job, but I came into the project after those critical decisions were made. I like some of what I see from the whole Theme/Style/Skin implementation, but overall it seems kludgy and weird to me. I didn't even talk about the most basic Button component yet, which I overrided immediately and created a custom component for. There is nothing more difficult than skinning a Button that you need to use everywhere, but looks different than the default Buttons that come with the program. Can anyone shed some light on my predicament? -steve warren _______________________________________________ Flashcoders mailing list [email protected] http://chattyfig.figleaf.com/mailman/listinfo/flashcoders
