Flash/Flex itemEditor Rendering Problem!

Hi,
I've created a simple checkbox itemEditer within a DataGrid
control. It works swimmingly... you check the box and the data does
what it's supposed to do (in this case just grab the ID's of the
item's that are checked).
However, the problem begins when a user decides to scroll up
and down the DataGrid to have a peak at those item's not displayed.
You can see an example here (click the 'Renew Contracts' button to
see the Contract ID's of what you have checked) -
click me!
As you can see, when a user scroll's and flash renders the
newly displayed items, it randomly checks and un-checks the
checkboxes on the right but if you click the 'Renew Contracts'
button again, you'll see that it hasn't actually affected what you
litterally checked (which suggests it is infact a rendering issue).
Any help on making flash behave itself and display check's in
checkboxes that have actually been checked by the user would be
much appreciated.

try this code:
- deleted the InlineCheckbox
- changed parts in the actionscript
Does this fit you needs?
please note the that the array [ i ] (
ContractsRequest.Contract [ i ] )are removed by the editor in the
forum
<?xml version="1.0" encoding="utf-8"?>
<mx:Application xmlns:mx="
http://www.adobe.com/2006/mxml"
xmlns:InlineCheckbox="*">
<mx:Script>
<![CDATA[
import mx.controls.CheckBox;
[Bindable]
public var SelectedContracts:String;
public function RenewContractsClick():void
SelectedContracts = "";
if(ContractsRequest.Count > 1)
for(var i:int = 0; i < ContractsRequest.Contract.length;
i++)
if(ContractsRequest.Contract
.Selected == true)
SelectedContracts += ContractsRequest.Contract.ContractID
+ ",";
else
if(ContractsRequest.Contract
.Selected == true)
SelectedContracts = ContractsRequest.Contract.ContractID
+ ",";
]]>
</mx:Script>
<mx:Model id="ContractsRequest">
<Contracts>
<Contract>
<ContractID>5657</ContractID>
<OrganisationID>10332</OrganisationID>
<OrganisationName>VBI GROUP
PLC</OrganisationName>
<StartDate>01/04/2002</StartDate>
<EndDate>31/03/2003</EndDate>
<Product>04253 HELPDESK SUPPORT FACTS 1
YEAR</Product>
<SON>S026866</SON>
<LineNumber>10</LineNumber>
<SONLN>S026866/10</SONLN>
<SiteCount>1</SiteCount>
<Selected>true</Selected>
</Contract>
<Contract>
<ContractID>1737</ContractID>
<OrganisationID>10332</OrganisationID>
<OrganisationName>VBI GROUP
PLC</OrganisationName>
<StartDate>01/08/2000</StartDate>
<EndDate>31/07/2001</EndDate>
<Product>04253 HELPDESK SUPPORT FACTS 1
YEAR</Product>
<SON>S012877</SON>
<LineNumber>40</LineNumber>
<SONLN>S012877/40</SONLN>
<SiteCount>1</SiteCount>
<Selected>true</Selected>
</Contract>
<Contract>
<ContractID>10242</ContractID>
<OrganisationID>10332</OrganisationID>
<OrganisationName>VBI GROUP
PLC</OrganisationName>
<StartDate>01/03/2004</StartDate>
<EndDate>28/02/2005</EndDate>
<Product>06979 SM TRISCAN 1 YEAR</Product>
<SON>S041431</SON>
<LineNumber>10</LineNumber>
<SONLN>S041431/10</SONLN>
<SiteCount>1</SiteCount>
<Selected>true</Selected>
</Contract>
<Contract>
<ContractID>18500</ContractID>
<OrganisationID>10332</OrganisationID>
<OrganisationName>VBI GROUP
PLC</OrganisationName>
<StartDate>27/05/2007</StartDate>
<EndDate>26/08/2007</EndDate>
<Product>SC001 VBI QTR SUPPORT CONTRACT
</Product>
<SON>S061685</SON>
<LineNumber>10</LineNumber>
<SONLN>S061685/10</SONLN>
<SiteCount>1</SiteCount>
<Selected>true</Selected>
</Contract>
<Contract>
<ContractID>12996</ContractID>
<OrganisationID>10332</OrganisationID>
<OrganisationName>VBI GROUP
PLC</OrganisationName>
<StartDate>01/03/2005</StartDate>
<EndDate>28/02/2006</EndDate>
<Product>06979 SM TRISCAN 1 YEAR</Product>
<SON>S049498</SON>
<LineNumber>10</LineNumber>
<SONLN>S049498/10</SONLN>
<SiteCount>1</SiteCount>
<Selected>true</Selected>
</Contract>
<Contract>
<ContractID>376</ContractID>
<OrganisationID>10332</OrganisationID>
<OrganisationName>VBI GROUP
PLC</OrganisationName>
<StartDate>01/03/2000</StartDate>
<EndDate>28/02/2001</EndDate>
<Product>06979 SM TRISCAN 1 YEAR</Product>
<SON>BN7511</SON>
<LineNumber>10</LineNumber>
<SONLN>BN7511/10</SONLN>
<SiteCount>1</SiteCount>
<Selected>true</Selected>
</Contract>
<Contract>
<ContractID>14669</ContractID>
<OrganisationID>10332</OrganisationID>
<OrganisationName>VBI GROUP
PLC</OrganisationName>
<StartDate>06/11/2005</StartDate>
<EndDate>31/01/2006</EndDate>
<Product>08245 VBI SUPPORT 3 MONTHS</Product>
<SON>S053098</SON>
<LineNumber>10</LineNumber>
<SONLN>S053098/10</SONLN>
<SiteCount>523</SiteCount>
<Selected>true</Selected>
</Contract>
<Contract>
<ContractID>12997</ContractID>
<OrganisationID>10332</OrganisationID>
<OrganisationName>VBI GROUP
PLC</OrganisationName>
<StartDate>01/03/2005</StartDate>
<EndDate>28/02/2006</EndDate>
<Product>06979 SM TRISCAN 1 YEAR</Product>
<SON>S049499</SON>
<LineNumber>10</LineNumber>
<SONLN>S049499/10</SONLN>
<SiteCount>1</SiteCount>
<Selected>true</Selected>
</Contract>
<Contract>
<ContractID>10243</ContractID>
<OrganisationID>10332</OrganisationID>
<OrganisationName>VBI GROUP
PLC</OrganisationName>
<StartDate>01/03/2004</StartDate>
<EndDate>28/02/2005</EndDate>
<Product>06979 SM TRISCAN 1 YEAR</Product>
<SON>S041432</SON>
<LineNumber>10</LineNumber>
<SONLN>S041432/10</SONLN>
<SiteCount>1</SiteCount>
<Selected>true</Selected>
</Contract>
<Contract>
<ContractID>10674</ContractID>
<OrganisationID>10332</OrganisationID>
<OrganisationName>VBI GROUP
PLC</OrganisationName>
<StartDate>01/06/2004</StartDate>
<EndDate>31/08/2004</EndDate>
<Product>08210 VBI PERIODIC CHARGE FOR S/W
SUP</Product>
<SON>S042626</SON>
<LineNumber>20</LineNumber>
<SONLN>S042626/20</SONLN>
<SiteCount>1</SiteCount>
<Selected>true</Selected>
</Contract>
<Contract>
<ContractID>10906</ContractID>
<OrganisationID>10332</OrganisationID>
<OrganisationName>VBI GROUP
PLC</OrganisationName>
<StartDate>01/06/2004</StartDate>
<EndDate>31/08/2004</EndDate>
<Product>08245 VBI SUPPORT 3 MONTHS</Product>
<SON>S043294</SON>
<LineNumber>10</LineNumber>
<SONLN>S043294/10</SONLN>
<SiteCount>1</SiteCount>
<Selected>true</Selected>
</Contract>
<Contract>
<ContractID>17070</ContractID>
<OrganisationID>10332</OrganisationID>
<OrganisationName>VBI GROUP
PLC</OrganisationName>
<StartDate>29/08/2006</StartDate>
<EndDate>28/11/2006</EndDate>
<Product>SC001 VBI QTR SUPPORT CONTRACT
</Product>
<SON>BN9230</SON>
<LineNumber>10</LineNumber>
<SONLN>BN9230/10</SONLN>
<SiteCount>626</SiteCount>
<Selected>true</Selected>
</Contract>
<Contract>
<ContractID>3832</ContractID>
<OrganisationID>10332</OrganisationID>
<OrganisationName>VBI GROUP
PLC</OrganisationName>
<StartDate>01/09/2001</StartDate>
<EndDate>31/08/2002</EndDate>
<Product>06979 SM TRISCAN 1 YEAR</Product>
<SON>S020524</SON>
<LineNumber>10</LineNumber>
<SONLN>S020524/10</SONLN>
<SiteCount>1</SiteCount>
<Selected>true</Selected>
</Contract>
<Count>83</Count>
</Contracts>
</mx:Model>
<mx:DataGrid editable="true" right="10" left="10" top="40"
bottom="40" dataProvider="{ContractsRequest.Contract}">
<mx:columns>
<mx:DataGridColumn editable="false" headerText="Contract"
dataField="ContractID" width="70"/>
<mx:DataGridColumn editable="false"
headerText="Organisation" dataField="OrganisationName"
width="250"/>
<mx:DataGridColumn editable="false" headerText="Start
Date" dataField="StartDate" width="100"/>
<mx:DataGridColumn editable="false" headerText="End Date"
dataField="EndDate" width="100"/>
<mx:DataGridColumn editable="false" headerText="Product"
dataField="Product"/>
<mx:DataGridColumn editable="false" headerText="SON/Line
No." dataField="SONLN" width="120"/>
<mx:DataGridColumn editable="false" headerText="No. Sites"
dataField="SiteCount" width="70"/>
<mx:DataGridColumn editable="true" headerText=""
dataField="Selected" width="70" itemRenderer="mx.controls.CheckBox"
rendererIsEditor="true" editorDataField="selected"/>
</mx:columns>
</mx:DataGrid>
<mx:Button label="Renew Contract(s)..." right="10"
bottom="10" click="RenewContractsClick()"/>
<mx:Text x="10" y="12" text="{SelectedContracts}"/>
</mx:Application>

Similar Messages

  • How to use a Flash/Flex GUI for DW Extensions

    I am creating a DW extension for an image and flash gallery.
    The extension will be accessible from the Insert menu. Once
    clicked, it would present me with a Flash/Flex form to
    search/browse for images/swf by file name or tags. Once I select an
    image/swf and clicked OK, it would insert into my webpage the
    absolute URL associated with the image/swf. The problem is I am not
    aware of how to create an extension with a Flash/Flex GUI.
    Any suggestions would be greatly appreciated.
    Thanks,
    srtr4k

    You should check out the Flash panels and Dialogs section of
    the Dreamweaver API reference. Here is a link.
    http://help.adobe.com/en_US/Dreamweaver/10.0_API_Ref/WS4FB61645-9C4E-4667-B6D4-0E5F553BEF4 F.html
    This gives you direct access to Flash panels and dialogs from
    the Dreamweaver Javascript API. Adobe is working on a document for
    how to create CSXS based Flash Extensions. CSXS based extensions
    only work as a floating panel that surface themselves in the
    Windows, Extensions menu.
    -Scott Richards
    Dreamweaver Team

  • Flash Builder Embed FXG - Problem

    Hi,
    I am working on creating an asset library using AS 3 project in Flash builder. I want to embed the fxg graphics referencing with a Class,
    [Embed(source='Sample.fxg')]
    private var myInstance:Class;
    I get the following error :
    no transcoder registered for mimeType 'text/fxg'    Main.as    /Project/src    line 9    Flex Problem
    The flex sdk version is  4.1.0.16076 and this doesn't with previous versions either.
    I can create instance of SpriteVisualElement to have fxg embedded, but this requires a flex project and I don't it is the best way to create a library for managing assets.
    Unable to create a AS3 project seems to be a quite limitation for traditional flash/flex development.
    Any help would be appreciated.
    Thanks,
    Kiran

    Hi Kiran,
    Usually I do put my reusable assets in a Flex Library Project (and also the FXG converted to MXML graphics). I don't embed the FXG documents.
    I usually convert the FXG documents to MXML graphics so that I can use it as a component in my application.
    Regards,
    Pablo Souza

  • Compiling an existing as3 packag with flex sdk (for a flash/flex/as beginner)

    Hi
    I am new to flash, flex, mxml, and actionscript (with a strong background in c, python, and scheme and some background in Java, VBA, and Javascript). I have a website for which I would like to develop some simple swf content. Basically, I would like to load esri shp files at runtime (and display a series of them as an animation) using these APIs.
    I have read through some flex getting started material, but I have found that there is no better way to learn a framework/language than to look at and modify existing code. Happily, I've found a sample that is both salient to my project and about the right level of complexity.
    I have the Flex SDK 3 and have created some simple movies. However, I haven't managed to compile the example as3 source code to a successful swf movie. I'd like to write mxml for layout/structure and as3 for functionality, and compile with mxmlc, period. Most examples I've found use of Flex Builder, Adobe Air plugins, other IDEs, etc and so they aren't very helpful.
    Here is a link to the content I'm interested in, and more importantly the as3 source packages (zip or browesable) that I'd like to compile. There are two: ManualCartogramTest.as and USStatesCartogramExample. I can use mxmlc to compile either one sucessfully, but the resulting swf file displays nothing. It seems that I should use the ManualCartogramTest class to create an instance of it, but none of my efforts have worked.
    Can anyone help out? How should I generate the swf movie given one of these packages? What key piece am I missing?
    Jeff
    For completeness, here is another example using the shp/dbf packages (from the creator) that I just can't figure out what to do with.

    1. Perhaps this wasn't the right forum.
    2. I had to use set -use-network=false to enter "local-with-filesystem" mode. Unfortunately, it took a while before I finally used a flash player that told me the problem instead of silently failing. The linux standalone or linux debugger from adobe was key! Gnash, swfdec, and my firefox plugin hid the problem.

  • Understanding Flash Player Text Rendering

    Hello Adobe!
    I'm the lead flex dev for
    Mixbook, and we are working hard
    to understand exactly how Flash Player 9 renders text. We have
    built a custom PDF Generation engine that uses WebKit on the Mac
    for text, but there are some incompatibilities that we have been
    running into. Is there a resource you can point me to so that we
    can learn more about how flash player 9 renders text?
    We're using Flex 2.01, and I've already read through all the
    included class documentation for flash.text. So far, we've spent
    most of our time with flash.text.TextLineMetrics and
    flash.text.TextFormat to help us understand how Flex works. Please
    contact me and let us know how we can work to resolve this.
    Thanks,
    Andrew

    Here is some information regarding how to make a SWF obey
    text size changes with the browser. The developer of the Flash
    content would need to implement this ability.
    http://aralbalkan.com/745

  • Why does Flash/Flex Builder 4 Premium downgrade to Standard when I install Flash Player Debug?

    Why does Flash/Flex Builder 4 Premium downgrade to Standard when I install Flash Player Debug?
    I installed a corporate install of Flex/Flash Builder 4 Premium, and verified that it was the Premium version was installed.  The Start Page said that Flash Player was needed to display the text, so I installed Flash Player 10 Debug -- first download link from here:
    http://www.adobe.com/support/flashplayer/downloads.html
    When I then started Flex Builder 4, the splash screen showed Premium, but as soon as the Start Page was visible, it showed "FB Adobe Flash Builder 4 Standard" --- Help | About showed Standard, and the splash screen from then on showed Standard.
    A Google search showed a work around for this, but it requires a license for Premium, which I don't have because our corporate install has it built-in:
    http://bloginblack.de/2010/05/adobe-master-collection-cs5-breaks-flash-builder-4-premium-a nd-how-to-fix-it/
    1. Anyone know how to resolve this?
    2. Can Adobe fix this?
    Thanks!

    I had similar problem. I was involved in Flash Builder prerelease program and few months later I installed Adobe CS5 Master Collection. After that I had a same situation.  Best thing was, my Flash Builder Beta was Premium version but acted like Standard, and FB from CS5 was Standard but acted like Premium. I removed CS5 and beta version of CS5. used CS5 Cleaning Fix and then reinstalled my apps.
    I was lucky that I didn't have many big projects involved in FB beta or CS5 workspaces, I heard some guys had problems with migrated workspace configurations but I don't know what was the problem.

  • Weird rendering problems?

    Hello
    I recently stopped making videos to have a break, but now I'm back...but Im encountering strange rendering problem.
    I am using Adobe Premiere Pro CC, my PC specs are
    Intel core i5 2.8GHz
    4GBs RAM
    GeForce GTX 760 (Asus OC version)
    64 bit Windows 8.1
    Now to the problem. I render the video normally, everything normal. But when I play the video back, the audio is in sync at the beginning, then starts to slowly unsync itself as the video progresses.
    But it doesn't stop there. The video randomly speeds ahead, and then jumps back about 5 seconds. The video continues for about 30 seconds, speeding up, then skips back again.
    I've tried exporting the video & audio separately, but to no avail.
    I've tried multiple file formats and bitrates and sizes, same problem.
    It should be noted that the video plays fine in the program, just after it's exported, things go bad.
    I know this may be hard to fix, but any help appreciated.
    If you need any more info, just ask.
    Thank you.
    Edit: it should be noted that I changed my graphics card recently, that may or may not be the cause.

    HMm... My video is 30fps but at the end Theres a bit of an Easter egg where an images flashes rapidly, possibly in between frames, could this be the cause?
    thanks for your help, though I won't be able to get on my computer for about 15 hours now, I'll keep you updated via my phone.

  • Removing div with flash/flex from page crushes browser

    Hallo to all Flex experts !
    For an application based on dojo ( javascript ) we prototype
    the migration to flex -
    The application is very big, we already work on it more than
    2 years, so we try to make the migration smooth by implementing
    parts of the application in flex.
    To do that, we dynamically open a div with an <object>
    / <embed> in it, and close it on demand, by calling
    javascript from flex, and simply remove the div from the document.
    Problem is: this results in a browser crash ! (linux, FF 2,
    Flash 9.0.31)
    So, what is the recommended way to do that ( without crashing
    the browser) ? how do we gracefully remove a flash/flex from the
    page ?
    Cheers,
    Ron

    or [simple typo funonmars ;-) ]
    my_vars.send("
    http://some.com/file.php","_blank","POST");
    I used it a few times today for just the type of thing you're
    describing... it should do what you're after.

  • Artifacts flashes on video rendered by After effects CS5

    Hello,
    Since one or two months, when I render a AVI with CS5, I have some artifacts on my videos.
    Those artifacts occur mainly at the begining of the video (first 10 sec), It's like very short flashes (one frame).
    After 10 sec it's almost good.
    Even when I render a black video (no layer, nothing in composition), I have this issue.
    If someone have a lead?
    Thx U
    Rendering a Black video:
    One different type of artifact on this composition, but same king of short flashes:

    I have the problem with all AVI / with quicktime export (no conpression)
    With a export with  h.264 codec, the problem disapear...
    About my sources, it can happend in any case, because as I told you, with just an emplty composition, I have the problem.
    I will try to download the last update.

  • Rendering problem in output of Pages 5.1

    Has anyone else seen a print rendering problem when trying to print a table in Pages 5.1?
    All my text in tables is jagged and lower-resolution than other text:
    (Printed from Pages 5.1 (1769) on a HP Color LaserJet CP2025 from a retina MacBook Pro original model running Mavericks 10.9.1.)
    To see the problem, you must look at the full size image. Right-click to open it in a new tab.
    The type is set to Helvetica 12 pt black.
    The borders are set to 0.5 pt black. The top two lines have a border on all sides.
    The top line's border is nearly invisible; on the full size image you should see a faint blueish line.
    The middle line's box box is supposed to be&#8232; a full box, but it is missing two sides. But at least this hairline renders properly.
    The pdf of the same file looks fine on screen, even at high magnification. The problem only shows up in print.
    The same problem exists in Numbers (where I first experienced it):
    https://discussions.apple.com/message/24695801#24695801

    I see you followed Jerry's advice to post over here, and haven't got any responces, so I'll at least try to get a little more information into the discussion.
    Since the document prints to pdf correctly, but not to the actual printer, it seems likely that it is a print driver issue. In the Numbers discussion on the issue, the original person with the issue was using a HP printer with a postscript driver. Since the HP support site was not very clear about whether a driver for that printer on Mavericks even existed, and the recommendation for a generic driver was for a PCL driver, not postscript, I suspect that they were not using a recommended configuration. It would probably be helpful to know the details about your printer and print driver.
    Do you have access to more than one printer to test this on?
    The new versions of Numbers and Pages are doing something strange in terms of how they copy tables to the system clipboard; the pdf version is no longer available, only bitmap images. Print to pdf, however seems to still get the pdf data. I don't think this should have anything to do with the data getting to the print driver, but it does seem consistent with your results.

  • Spry Menu Bar 2.0 (1.0) - Handling of widget generated CSS, placement and rendering problems in CSS

    Hello:
    I wanted to repost my question to re-frame the issue based on what I have learned thus far.
    I am working on a website that has been developed using the Spry Menu Bar Framework UI (2.0) I.0, that has some peculiar rendering problems that affect IE 6 in particular.  The CSS is reprinted below.
    In particular, when I post the widget generated CSS in the head as it is orginally situated by the framework, the menu bar works fine.  However, it seemed to me that I should be able to reduce page weight (an important consideration considering my target population) by placing it in the general style sheet governing the entire site.
    When I place the styles at the beginning of the style sheet the menu doesn't render at all in any of the browsers (IE 6+, Firefox, Opera, Safari, Netscape, etc.) as it conflicts with the general rules governing links that appear later in the style sheet.  When I place the styles specific to the Menu bar at the end of the style sheet, then the menu bar renders properly in all browsers except IE 6.
    The odd thing is that the only way to ensure that the menu bar works in IE 6 is to keep the menu related styles in the head of each page.  This raises problems related to page weight (not an insurmountable consideration if no other solution can be found) but still an issue.  Likewise I need to support IE 6, again given the target audience/population.  The issue obviously has something to do with specificity, but I am not certain that is the only consideration at work here.  I have not tried the !important selector in regard to the menu, as IE 6 seems to only partially support this.
    Thanks in advance for any advice or insight that can be provided.  Thanks in particular to Martin for his contributions to my earlier question related to this issue.
    Steve Webster.
    The CSS governing the horizontal menu bar is as follows:  (currently the following CSS is embedded in the head of the web page)
    <style type="text/css">
    /*  -- Begins Spry Menu Widget 2.0 (1.0) Horizontal menu bar Custom styles --  */
    /* BeginOAWidget_Instance_2141544: #MenuBar */
    /* Settable values for skinning a Basic menu via presets. If presets are not sufficient, most skinning should be done in
       these rules, with the exception of the images used for down or rightpointing arrows, which are in the file SpryMenuBasic.css
         These assume the following widget classes for menu layout (set in a preset)
       .MenuBar - Applies to all menubars - default is horizontal bar, allsubmenus are vertical - 2nd level subs and beyond are pull-right.
        .MenuBarVertical - vertical main bar; all submenus are pull-right.
       You can also pass in extra classnames to set your desired top levelmenu bar layout. Normally, these are set by using a preset.
        They only apply to horizontal menu bars:
            MenuBarLeftShrink - The menu bar will be horizontally 'shrinkwrapped' to be just large enough to hold its items, and left aligned
            MenuBarRightShrink - Just like MenuBarLeftShrink, but right aligned
            MenuBarFixedLeft - Fixed at a specified width set in the rule '.MenuBarFixedLeft', and left aligned. 
            MenuBarFixedCentered -  - Fixed at a specified width set in the rule '.MenuBarFixedCentered',
                            and centered in its parent container.
            MenuBarFullwidth - Grows to fill its parent container width.
        In general, all rules specified in this file are prefixed by #MenuBar so they only apply to instances of the widget inserted along
       with the rules. This permits use of multiple MenuBarBasic widgets onthe same page with different layouts. Because of IE6 limitations,
        there are a few rules where this was not possible. Those rules are so noted in comments.
    #MenuBar  {
        background-color:transparent;
       font-family: Arial, Helvetica, sans-serif; /* Specify fonts on onMenuBar and subMenu MenuItemContainer, so MenuItemContainer,
                                                    MenuItem, and MenuItemLabel
                                                    at a given level all use same definition for ems.
                                                    Note that this means the size is also inherited to child submenus,
                                                    so use caution in using relative sizes other than
                                                    100% on submenu fonts. */
        font-weight: normal;
        font-size: 17px;
        font-style: normal;
        padding:0;
    /* Caution: because ID+class selectors do not work properly in IE6, but we want to restrict these rules to just this
    widget instance, we have used string-concatenated classnames for our selectors for the layout type of the menubar
    in this section. These have very low specificity, so be careful not to accidentally override them. */
    .MenuBar br { /* using just a class so it has same specificity as the ".MenuBarFixedCentered br" rule bleow */
        display:none;
    .MenuBarLeftShrink {
        float: left; /* shrink to content, as well as float the MenuBar */
        width: auto;
    .MenuBarRightShrink {
        float: right; /* shrink to content, as well as float the MenuBar */
        width: auto;
    .MenuBarFixedLeft {
        float: left;
        width: 80em;
    .MenuBarFixedCentered {
        float: none;
        width: 80em;
        margin-left:auto;
        margin-right:auto;
    .MenuBarFixedCentered br {
        clear:both;
        display:block;
    .MenuBarFixedCentered .SubMenu br {
        display:none;
    .MenuBarFullwidth {
        float: left;
        width: 100%;
    /* Top level menubar items - these actually apply to all items, and get overridden for 1st or successive level submenus */
    #MenuBar  .MenuItemContainer {
        padding: 0px 0px 0px 0px;
        margin: 0;     /* Zero out margin  on the item containers. The MenuItem is the active hover area.
                    For most items, we have to do top or bottom padding or borders only on the MenuItem
                    or a child so we keep the entire submenu tiled with items.
                    Setting this to 0 avoids "dead spots" for hovering. */
    #MenuBar  .MenuItem {
        padding: 10px 10px 10px 4px;
        background-color:#000088;
        background-image:url(../ACLCO%20Graphics%20-%20Web%20site%20Parts/Nav igation%20Bar%20Segment-Dark.png);
        background-repeat:repeat-x;       
    #MenuBar  .MenuItemFirst {
        border-style: none none none none;
    #MenuBar .MenuItemLast {
        border-style: none none none none;
    #MenuBar  .MenuItem  .MenuItemLabel{
        text-align:center;
        line-height:1.4em;
        color:#ffffff;
        background-color:transparent;
        padding: 0px 18px 0px 5px;
        width: 10em;
        width:auto;
    .SpryIsIE6 #MenuBar  .MenuItem  .MenuItemLabel{
        width:1em; /* Equivalent to min-width in modern browsers */
    /* First level submenu items */
    #MenuBar .SubMenu  .MenuItem {
        font-family: Arial, Helvetica, sans-serif;
        font-weight: bold;
        font-size: 15px;
        font-style: normal;
        background-color:#000088;
        padding:0px 2px 0px 0px;
        border-width:0px;
        border-color: #cccccc #cccccc #cccccc #cccccc;
        /* Border styles are overriden by first and last items */
        border-style: solid solid none solid;
    #MenuBar  .SubMenu .MenuItemFirst {
        border-style: none;
        padding: 0px;
    #MenuBar  .SubMenu .MenuItemFirst .MenuItemLabel{
        padding-top: 0px;
    #MenuBar .SubMenu .MenuItemLast {
        border-style: none none none none;
    #MenuBar .SubMenu .MenuItemLast .MenuItemLabel{
        padding-bottom: 10px;
    #MenuBar .SubMenu .MenuItem .MenuItemLabel{
        text-align:left;
        line-height:1em;   
        background-color:transparent;
        color:#ffffff;
        padding: 10px 10px 10px 10px;
        width: 240px;
    /* Hover states for containers, items and labels */
    #MenuBar .MenuItemHover {
        background-color: #2E35A3;
        background-image:url(../ACLCO%20Graphics%20-%20Web%20site%20Parts/Nav igation%20Bar%20Segment%20Light2.png);
        background-repeat:repeat-x;
    #MenuBar .MenuItemWithSubMenu.MenuItemHover .MenuItemLabel{
        background-color: transparent; /* consider exposing this prop separately*/
        color: #ffffff;
    #MenuBar .MenuItemHover .MenuItemLabel{
        background-color: transparent;
        color: #ffffff;
    #MenuBar .SubMenu .MenuItemHover {
        background-color:#2E35A3;
    #MenuBar .SubMenu .MenuItemHover .MenuItemLabel{
        background-color: transparent;
        color: #ffffff;
    /* Submenu properties -- First level of submenus */
    #MenuBar .SubMenuVisible {
        background-color: transparent;
       min-width:0%;  /* This keeps the menu from being skinnier than theparent MenuItemContainer - nice to have but not available on ie6 */
        border-style: none none none none;
    #MenuBar.MenuBar .SubMenuVisible {/* For Horizontal menubar only */
        top: 100%;    /* 100% is at the bottom of parent menuItemContainer */
        left:0px; /* 'left' may need tuning depending upon borders or padding applied to menubar MenuItemContainer or MenuItem,
                        and your personal taste.
                       0px will left align the dropdown with the content area of theMenuItemContainer. Assuming you keep the margins 0
                        on MenuItemContainer and MenuItem on the parent
                        menubar, making this equal the sum of the MenuItemContainer & MenuItem padding-left will align
                        the dropdown with the left of the menu item label.*/
        z-index:10;
    #MenuBar.MenuBarVertical .SubMenuVisible {
        top: 0px;   
        left:100%;
        min-width:0px; /* Do not neeed to match width to parent MenuItemContainer - items will prevent total collapse */
    /* Submenu properties -- Second level submenu and beyond - these are visible descendents of .MenuLevel1 */
    #MenuBar .MenuLevel1 .SubMenuVisible {
        background-color: transparent;
        min-width:0px; /* Do not neeed to match width to parent MenuItemContainer - items will prevent total collapse*/
        top: 0px;    /* If desired, you can move this down a smidge to separate top item''s submenu from menubar -
                    that is really only needed for submenu on first item of MenuLevel1, or you can make it negative to make submenu more
                    vertically 'centered' on its invoking item */
        left:100%; /* If you want to shift the submenu left to partially cover its invoking item, you can add a margin-left with a
                    negative value to this rule. Alternatively, if you use fixed-width items, you can change this left value
                    to use px or ems to get the offset you want. */
    /* IE6 rules - you can delete these if you do not want to support IE6 */
    /* A note about multiple classes in IE6.
    * Some of the rules above use multiple class names on an element forselection, such as "hover" (MenuItemHover) and "has a subMenu"(MenuItemWithSubMenu),
    * giving the selector '.MenuItemWithSubMenu.MenuItemHover'.
    * Unfortunately IE6 does not support using mutiple classnames in aselector for an element. For a selector such as '.foo.bar.baz', IE6ignores
    * all but the final classname (here, '.baz'), and sets thespecificity accordingly, counting just one of those classs assignificant. To get around this
    * problem, we use the plugin in SpryMenuBarIEWorkaroundsPlugin.js to generate compound classnames for IE6, such as 'MenuItemWithSubMenuHover'.
    * Since there are a lotof these needed, the plugin does not generate the extra classes formodern browsers, and we use the CSS2 style mutltiple class
    * syntax for that. Since IE6 both applies rules where
    * it should not, and gets the specificity wrong too, we have to order rules carefully, so the rule misapplied in IE6 can be overridden.
    * So, we put the multiple class rule first. IE6 will mistakenly apply this rule.  We follow this with the single-class rule that it would
    * mistakenly override, making sure the  misinterpreted IE6 specificity is the same as the single-class selector, so the latter wins.
    * We then create a copy of the multiple class rule, adding a '.SpryIsIE6' class as context, and making sure the specificity for
    * the selector is high enough to beat the single-class rule in the "both classes match" case. We place the IE6 rule at the end of the
    * css style block to make it easy to delete if you want to drop IE6 support.
    * If you decide you do not need IE6 support, you can get rid of these,as well as the inclusion of the SpryMenuBarIEWorkaroundsPlugin.jsscript.
    * The 'SpryIsIE6' class is placed on the HTML element by the script in SpryMenuBarIEWorkaroundsPlugin.js if the browser isInternet Explorer 6. This avoids the necessity of IE conditionalcomments for these rules.
    .SpryIsIE6 #MenuBar .MenuBarView .MenuItemWithSubMenuHover .MenuItemLabel /* IE6 selector  */{
        background-color: transparent; /* consider exposing this prop separately*/
        color: #ffffff;
    .SpryIsIE6 #MenuBar .MenuBarView .SubMenu .MenuItemWithSubMenuHover .MenuItemLabel/* IE6 selector  */{
        background-color: transparent; /* consider exposing this prop separately*/
        color: #ffffff;
    .SpryIsIE6 #MenuBar .SubMenu .SubMenu  /* IE6 selector  */{
        margin-left: -0px; /* Compensates for at least part of an IE6 "double padding" version of the "double margin" bug */
    /* EndOAWidget_Instance_2141544 */
    /* Ends Spry Menu Bar Widget 2.0 (1.0) Horizontal Menu Custom styles */
    </style>
    The CSS governing the site generally is reproduced below:  (my belief is that it is the a:link, a:visited,  a:hover, a:active styles that may be in conflict).
    @charset "utf-8";
    body  {
        font: 100% Verdana, Arial, Helvetica, sans-serif;
       min-height: 0; /* This is necessary to overcome the "haslayout" bugthat is found in Windows 7 in conjuction with IE8.  For Moreinformation see: URL -- http://reference.sitepoint.com/css/haslayout.html */
        margin: 0; /* it's good practice to zero the margin and padding of the body element to account for differing browser defaults */
        padding: 0;
        text-align:center; /* This allows for the centering of the container and overcomes a bug inherent in IE 5 */
        color: #000000;
        list-style-image: none;
        background-color: #FCFCFC;
    h1,h2,h3,h4,h5,h6 {
    color:#000066;
    a:link {
        color: #151A96;
        text-decoration: underline;
    a:visited {
        text-decoration: underline;
        color: #1B8DCD;
    a:hover {
        text-decoration: none;
        color: #F30A0A;
    a:active {
        text-decoration: underline;
        color: #151A96;
    #container {
        width: 960px;   
        margin: 0 auto; /* the auto margins (in conjunction with a width) center the page */
        text-align: left; /* this overrides the text-align: center on the body element. */
        background-image:
        url(../ACLCO%20Graphics%20-%20Web%20site%20Parts/Website%20Midsection %20_960.png);
        background-repeat: repeat-y;
    #header {
           padding: 0;  /* this padding matches the left alignment of the elementsin the divs that appear beneath it. If an image is used in the #headerinstead of text, you may want to remove the padding. */
            width:960px;
            height:332px;
            background-image:
            url(../ACLCO%20Graphics%20-%20Web%20site%20Parts/Website%20Header_960 .png);
            background-repeat:no-repeat;
    #header h1 {
        margin-right: 0px; /* zeroing the margin of the last element in the #header div will avoid margin collapse - an unexplainable space between divs. If the div has a border around it, this is not necessary as that also avoids the margin collapse */
        padding: 0; /* using padding instead of margin will allow you to keep the element away from the edges of the div */
        display:none;
    #header img {
        display: none;
    #Main_nav_contents {
        padding: 0;
        margin-top: 0px;
        height: 39px;
        width: 950px;       
        padding-top: 275px; 
        padding-left: 39px;
        z-index: 3; 
    #MenuBarVertical {
        margin-bottom: 50px;
        padding-top: 50px;
        padding-bottom:200px;
        padding-left: 15px;
        padding-right: 15px;
    .mainContent_left {
       margin: 0;/* the right margin on this div element creates the columndown the right side of the page - no matter how much content thesidebar1 div contains, the column space will remain. You can removethis margin if you want the #mainContent div's text to fill the#sidebar1 space when the content in #sidebar1 ends. */
        padding-left:30px;
        padding-right:20px; /* remember that padding is the space inside the div box and margin is the space outside the div box */
        width: 600px;
        float: left;
    .sidebar_right {
        float: right; /* since this element is floated, a width must be given */
        width: 270px; /* the actual width of this div, in standards-compliant browsers, or standards mode in Internet Explorer will include the padding and border in addition to the width */
        margin-top: 30px;
        margin-left:0;
        margin-right:10px;
        font-size:90%;
    .mainContent_right {
        margin-left: 10px;
        padding-left:30px;
        padding-right:20px;
        width: 600px;
        float: right;
    .sidebar_left {
        float: left; /* since this element is floated, a width must be given */
        width: 270px; /* the actual width of this div, in standards-compliant browsers, or standards mode in Internet Explorer will include the padding and border in addition to the width */
        margin-top: 30px;
        margin-left:30px;
        margin-right:0;
        overflow: hidden;
        font-size:90%;
    .main_content_centered {
        width: 650px;
        margin-left: 155px;
    .main_content_centered_header {
        margin-left: 75px;
    .sidebar_textbox {
        margin: 0px;   
        width: 260px;
        padding: 2px;
    .sidebar_textbox_header {
        width:255px;
        height:58px;
        background-image:url(../ACLCO%20Graphics%20-%20Web%20site%20Parts/Por trait%20Textbox%20Header.png);
    .sidebar_textbox_background_middle {
         width: 255px;   
        padding-top: 12px;   
        padding-bottom: 10px;
        background-image:url(../ACLCO%20Graphics%20-%20Web%20site%20Parts/Por trait%20Textbox%20Middle.png);
        background-repeat: repeat-y;
    .sidebar_textbox_content {
       /* The width and padding are set as follows to accomodate quirks inbrowser rendering and to ensure that text is contained within thebackground of the text box */
        width: 230px;
        padding-left: 20px;
        padding-right: 40px;
    .sidebar_textbox_footer {
        width:255px;
        height:64px;
    background-image:url(../ACLCO%20Graphics%20-%20Web%20site%20Parts/Port rait%20Textbox%20Footer.png);
    #issues_menu a:link {
        color: #151A96;
        text-decoration: none;
        font-weight:bold;
    #issues_menu a:visited {
        color: #151A96;
        font-weight:bold;
        text-decoration: none;
    #issues_menu a:hover {   
        color: #F30A0A;
        font-weight:bold;
        font-style: oblique;
        text-decoration: none;
    #issues_menu a:active {
        color: #151A96;
        font-weight:bold;
        text-decoration: none;
    #archives {
        padding-top: 15px;
        padding-right: 15px;
        padding-bottom: 20px;
        padding-left: 0px;
    .landscape_textbox {
        width: 500px;
        margin-right: 0px;
        margin-left: 30px;
        padding-top:35px;
        padding-bottom: 25px;
        font-style: normal;
        font-weight: normal;
    .landscape_textbox_hdr {
        width:500px;
        height:38px;
        margin:auto;
        padding:0;
        background-image:
    url(../ACLCO%20Graphics%20-%20Web%20site%20Parts/Landscape%20Textbox%2 0Header.png);
    .landscape_textbox_middle {
        width:auto;
        margin:auto;
        padding-top: 12px;
        padding-bottom: 12px;
        background-image:url(../ACLCO%20Graphics%20-%20Web%20site%20Parts/lan dscapte%20Textbox%20Middle.png);
        background-repeat:repeat-y;
    .landscape_textbox_content {
        width:450px;
        padding:25px;
    .landscape_textbox_ftr {
        width:500px;
        height:44px;
        margin:auto;
        padding:0;
        background-image:url(../ACLCO%20Graphics%20-%20Web%20site%20Parts/Lan dscape%20Textbox%20Footer.png);
    #footer {
        padding: 0; /* this padding matches the left alignment of the elements in the divs that appear above it. */
        width: 960px;
        height: 222px;
        background-image:
        url(../ACLCO%20Graphics%20-%20Web%20site%20Parts/Website%20Footer%20_ 960.png);
        background-repeat:no-repeat;
    #footer p {
       margin: 0px; /* zeroing the margins of the first element in the footerwill avoid the possibility of margin collapse - a space between divs */
        padding:0px; /* padding on this element will create space, just as the the margin would have, without the margin collapse issue */
        text-align:center;
        margin-left: 50px;
        margin-right: 50px;
        padding: 10px;
        font-size: small;
    #footer h5 {
    text-align:center;
    .fltrt { /* this class can be used to float an element right in your page. The floated element must precede the element it should be next to on the page. */
        float: right;
        margin-left: 8px;
    .fltlft { /* this class can be used to float an element left in your page */
        float: left;
        margin-right: 8px;
    .clearfloat { /* this class should be placed on a div or break element and should be the final element before the close of a container that should fully contain a float */
        clear:both;
        height:0;
        font-size: 1px;
        line-height: 0px;
    .dropcap {
        display: block;
        float: left;
        line-height: 80%;
        font-size: 250%;
        font-weight: bolder;
        color: #000066;   
        padding: .03em .1em 0 0;
    .red_arrows {
        list-style-position: outside;
        list-style-image: url(../ACLCO%20Graphics%20-%20Web%20site%20Parts/Arrow%20Large.png);    
    .blue_bullets {
        list-style-position: outside;
        list-style-image: url(../ACLCO%20Graphics%20-%20Web%20site%20Parts/Bullet%20Medium%20Fu ll.png);   
    .attention {
        color: #F30A0A;
        font-size:x-large;
        font-family: Georgia, "Times New Roman", Times, serif;
        font-style: italic;
        font-weight:900;
    .attention_small {
        color: #F30A0A;
        font-size:large;
        font-family: Georgia, "Times New Roman", Times, serif;
        font-style: italic;
        font-weight:900;
    .table {
        table-layout:fixed;
    .blue {
        color: #00F;
    #container .mainContent_left p .blue {
        color: #0303A0;

    Hi Nancy:
    The specific code that I am referring to is the CSS code governing the styling of the spry menu widget that only works in IE 6 if, and only if, it remains in the head of the web page.  If removed and placed in a stylesheet, the IE plugins fail to compensate for the IE 6 "gap" bug.  As I said, it doesn't make sense to me that, assuming specificity is addressed, that these can not be included in an external style sheet.  I am looking for a) an explanation why they must remain embedded in the web page; and 2) any means by which I might be able to export them.
    I will reproduce the specific css style (code) below:  it should also be visable through reveal source --
    Thanks again, Steve Webster.
    The CSS governing the horizontal menu bar is as follows:  (currently the following CSS is embedded in the head of the web page)
    <style type="text/css">
    /*  -- Begins Spry Menu Widget 2.0 (1.0) Horizontal menu bar Custom styles --  */
    /* BeginOAWidget_Instance_2141544: #MenuBar */
    /* Settable values for skinning a Basic menu via presets. If presets are not sufficient, most skinning should be done in
       these rules, with the exception of the images used for down or rightpointing arrows, which are in the file SpryMenuBasic.css
         These assume the following widget classes for menu layout (set in a preset)
       .MenuBar - Applies to all menubars - default is horizontal bar, allsubmenus are vertical - 2nd level subs and beyond are pull-right.
        .MenuBarVertical - vertical main bar; all submenus are pull-right.
       You can also pass in extra classnames to set your desired top levelmenu bar layout. Normally, these are set by using a preset.
        They only apply to horizontal menu bars:
            MenuBarLeftShrink - The menu bar will be horizontally 'shrinkwrapped' to be just large enough to hold its items, and left aligned
            MenuBarRightShrink - Just like MenuBarLeftShrink, but right aligned
            MenuBarFixedLeft - Fixed at a specified width set in the rule '.MenuBarFixedLeft', and left aligned. 
            MenuBarFixedCentered -  - Fixed at a specified width set in the rule '.MenuBarFixedCentered',
                            and centered in its parent container.
            MenuBarFullwidth - Grows to fill its parent container width.
        In general, all rules specified in this file are prefixed by #MenuBar so they only apply to instances of the widget inserted along
       with the rules. This permits use of multiple MenuBarBasic widgets onthe same page with different layouts. Because of IE6 limitations,
        there are a few rules where this was not possible. Those rules are so noted in comments.
    #MenuBar  {
        background-color:transparent;
       font-family: Arial, Helvetica, sans-serif; /* Specify fonts on onMenuBar and subMenu MenuItemContainer, so MenuItemContainer,
                                                    MenuItem, and MenuItemLabel
                                                    at a given level all use same definition for ems.
                                                    Note that this means the size is also inherited to child submenus,
                                                    so use caution in using relative sizes other than
                                                    100% on submenu fonts. */
        font-weight: normal;
        font-size: 17px;
        font-style: normal;
        padding:0;
    /* Caution: because ID+class selectors do not work properly in IE6, but we want to restrict these rules to just this
    widget instance, we have used string-concatenated classnames for our selectors for the layout type of the menubar
    in this section. These have very low specificity, so be careful not to accidentally override them. */
    .MenuBar br { /* using just a class so it has same specificity as the ".MenuBarFixedCentered br" rule bleow */
        display:none;
    .MenuBarLeftShrink {
        float: left; /* shrink to content, as well as float the MenuBar */
        width: auto;
    .MenuBarRightShrink {
        float: right; /* shrink to content, as well as float the MenuBar */
        width: auto;
    .MenuBarFixedLeft {
        float: left;
        width: 80em;
    .MenuBarFixedCentered {
        float: none;
        width: 80em;
        margin-left:auto;
        margin-right:auto;
    .MenuBarFixedCentered br {
        clear:both;
        display:block;
    .MenuBarFixedCentered .SubMenu br {
        display:none;
    .MenuBarFullwidth {
        float: left;
        width: 100%;
    /* Top level menubar items - these actually apply to all items, and get overridden for 1st or successive level submenus */
    #MenuBar  .MenuItemContainer {
        padding: 0px 0px 0px 0px;
        margin: 0;     /* Zero out margin  on the item containers. The MenuItem is the active hover area.
                    For most items, we have to do top or bottom padding or borders only on the MenuItem
                    or a child so we keep the entire submenu tiled with items.
                    Setting this to 0 avoids "dead spots" for hovering. */
    #MenuBar  .MenuItem {
        padding: 10px 10px 10px 4px;
        background-color:#000088;
        background-image:url(../ACLCO%20Graphics%20-%20Web%20site%20Parts/Nav igation%20Bar%20Segment-Dark.png);
        background-repeat:repeat-x;       
    #MenuBar  .MenuItemFirst {
        border-style: none none none none;
    #MenuBar .MenuItemLast {
        border-style: none none none none;
    #MenuBar  .MenuItem  .MenuItemLabel{
        text-align:center;
        line-height:1.4em;
        color:#ffffff;
        background-color:transparent;
        padding: 0px 18px 0px 5px;
        width: 10em;
        width:auto;
    .SpryIsIE6 #MenuBar  .MenuItem  .MenuItemLabel{
        width:1em; /* Equivalent to min-width in modern browsers */
    /* First level submenu items */
    #MenuBar .SubMenu  .MenuItem {
        font-family: Arial, Helvetica, sans-serif;
        font-weight: bold;
        font-size: 15px;
        font-style: normal;
        background-color:#000088;
        padding:0px 2px 0px 0px;
        border-width:0px;
        border-color: #cccccc #cccccc #cccccc #cccccc;
        /* Border styles are overriden by first and last items */
        border-style: solid solid none solid;
    #MenuBar  .SubMenu .MenuItemFirst {
        border-style: none;
        padding: 0px;
    #MenuBar  .SubMenu .MenuItemFirst .MenuItemLabel{
        padding-top: 0px;
    #MenuBar .SubMenu .MenuItemLast {
        border-style: none none none none;
    #MenuBar .SubMenu .MenuItemLast .MenuItemLabel{
        padding-bottom: 10px;
    #MenuBar .SubMenu .MenuItem .MenuItemLabel{
        text-align:left;
        line-height:1em;   
        background-color:transparent;
        color:#ffffff;
        padding: 10px 10px 10px 10px;
        width: 240px;
    /* Hover states for containers, items and labels */
    #MenuBar .MenuItemHover {
        background-color: #2E35A3;
        background-image:url(../ACLCO%20Graphics%20-%20Web%20site%20Parts/Nav igation%20Bar%20Segment%20Light2.png);
        background-repeat:repeat-x;
    #MenuBar .MenuItemWithSubMenu.MenuItemHover .MenuItemLabel{
        background-color: transparent; /* consider exposing this prop separately*/
        color: #ffffff;
    #MenuBar .MenuItemHover .MenuItemLabel{
        background-color: transparent;
        color: #ffffff;
    #MenuBar .SubMenu .MenuItemHover {
        background-color:#2E35A3;
    #MenuBar .SubMenu .MenuItemHover .MenuItemLabel{
        background-color: transparent;
        color: #ffffff;
    /* Submenu properties -- First level of submenus */
    #MenuBar .SubMenuVisible {
        background-color: transparent;
       min-width:0%;  /* This keeps the menu from being skinnier than theparent MenuItemContainer - nice to have but not available on ie6 */
        border-style: none none none none;
    #MenuBar.MenuBar .SubMenuVisible {/* For Horizontal menubar only */
        top: 100%;    /* 100% is at the bottom of parent menuItemContainer */
        left:0px; /* 'left' may need tuning depending upon borders or padding applied to menubar MenuItemContainer or MenuItem,
                        and your personal taste.
                       0px will left align the dropdown with the content area of theMenuItemContainer. Assuming you keep the margins 0
                        on MenuItemContainer and MenuItem on the parent
                        menubar, making this equal the sum of the MenuItemContainer & MenuItem padding-left will align
                        the dropdown with the left of the menu item label.*/
        z-index:10;
    #MenuBar.MenuBarVertical .SubMenuVisible {
        top: 0px;   
        left:100%;
        min-width:0px; /* Do not neeed to match width to parent MenuItemContainer - items will prevent total collapse */
    /* Submenu properties -- Second level submenu and beyond - these are visible descendents of .MenuLevel1 */
    #MenuBar .MenuLevel1 .SubMenuVisible {
        background-color: transparent;
        min-width:0px; /* Do not neeed to match width to parent MenuItemContainer - items will prevent total collapse*/
        top: 0px;    /* If desired, you can move this down a smidge to separate top item''s submenu from menubar -
                    that is really only needed for submenu on first item of MenuLevel1, or you can make it negative to make submenu more
                    vertically 'centered' on its invoking item */
        left:100%; /* If you want to shift the submenu left to partially cover its invoking item, you can add a margin-left with a
                    negative value to this rule. Alternatively, if you use fixed-width items, you can change this left value
                    to use px or ems to get the offset you want. */
    /* IE6 rules - you can delete these if you do not want to support IE6 */
    /* A note about multiple classes in IE6.
    * Some of the rules above use multiple class names on an element forselection, such as "hover" (MenuItemHover) and "has a subMenu"(MenuItemWithSubMenu),
    * giving the selector '.MenuItemWithSubMenu.MenuItemHover'.
    * Unfortunately IE6 does not support using mutiple classnames in aselector for an element. For a selector such as '.foo.bar.baz', IE6ignores
    * all but the final classname (here, '.baz'), and sets thespecificity accordingly, counting just one of those classs assignificant. To get around this
    * problem, we use the plugin in SpryMenuBarIEWorkaroundsPlugin.js to generate compound classnames for IE6, such as 'MenuItemWithSubMenuHover'.
    * Since there are a lotof these needed, the plugin does not generate the extra classes formodern browsers, and we use the CSS2 style mutltiple class
    * syntax for that. Since IE6 both applies rules where
    * it should not, and gets the specificity wrong too, we have to order rules carefully, so the rule misapplied in IE6 can be overridden.
    * So, we put the multiple class rule first. IE6 will mistakenly apply this rule.  We follow this with the single-class rule that it would
    * mistakenly override, making sure the  misinterpreted IE6 specificity is the same as the single-class selector, so the latter wins.
    * We then create a copy of the multiple class rule, adding a '.SpryIsIE6' class as context, and making sure the specificity for
    * the selector is high enough to beat the single-class rule in the "both classes match" case. We place the IE6 rule at the end of the
    * css style block to make it easy to delete if you want to drop IE6 support.
    * If you decide you do not need IE6 support, you can get rid of these,as well as the inclusion of the SpryMenuBarIEWorkaroundsPlugin.jsscript.
    * The 'SpryIsIE6' class is placed on the HTML element by the script in SpryMenuBarIEWorkaroundsPlugin.js if the browser isInternet Explorer 6. This avoids the necessity of IE conditionalcomments for these rules.
    .SpryIsIE6 #MenuBar .MenuBarView .MenuItemWithSubMenuHover .MenuItemLabel /* IE6 selector  */{
        background-color: transparent; /* consider exposing this prop separately*/
        color: #ffffff;
    .SpryIsIE6 #MenuBar .MenuBarView .SubMenu .MenuItemWithSubMenuHover .MenuItemLabel/* IE6 selector  */{
        background-color: transparent; /* consider exposing this prop separately*/
        color: #ffffff;
    .SpryIsIE6 #MenuBar .SubMenu .SubMenu  /* IE6 selector  */{
        margin-left: -0px; /* Compensates for at least part of an IE6 "double padding" version of the "double margin" bug */
    /* EndOAWidget_Instance_2141544 */
    /* Ends Spry Menu Bar Widget 2.0 (1.0) Horizontal Menu Custom styles */
    </style>

  • Follow up to recent posts regarding rendering problems

    I've read all posts to Berrett below but can't seem to get my "Flip Video" camcorder (uses MPEG-4AVI) video into FCE without the rendering problem. I've tried to convert in two ways. Using MPEG Streamclip I transferred my video to my desktop using the "export to DV" command. It appears on desktop with a .DV suffix I then imported into browser. After editing in the viewer and trying to insert edit in canvas I get the message " "..clip does not match sequence settings..." I then click yes to change sequence settings and the clip moves to timeline. The video plays but the audio has to be rendered.
    Next, I tried converting using the export to quicktime command in Streamclip with sound uncompressed and setting to DV-NTSC. When I insert into FCE and insert edit I get the sound but the picture has to be rendered. What am I doing wrong?
    I've been working on this all day and am getting very depressed. Please help. Thanks.
    Ed
    S

    Thanks but I think I tried that without success. I must have a setting somewhere wrong. My audio is fine but I still have to render my video. Using Streamclip to convert to quicktime here are the setting I used in the Movie Exporter dialog box.
    Compression: Apple Motion JPEG A
    Sound: uncompressed
    frame size 720x480 (DV-NTSC)
    In FCE my easy setup is
    Format: NTSC
    Use: DV-NTSC
    Help.

  • On 12/23/11 I update the adobe flash player and have had problems since- unexpected closing and freezing. Remove the adobe flash player and those problems resolved. How do I go back to the earlier version of adobe?

    I was prompted by Firefox to update my adobe flash player on 12/23/11, which I did. Ever since then the web site has frozen and/or crashed. I run a internet business and can't have this continue. I uninstalled the flash player and the problems have stopped. I would like to reinstall the earlier version of adobe, since that didn't seem to impact the web site.
    This is the flash player I installed on the 23rd - Flash Player 10.3 for Mac OS X 10.4-10.5 (Intel)

    Your above posted list of installed plugins doesn't show the Flash plugin for Firefox.<br />
    See [[Managing the Flash plugin]] and [[Installing the Flash plugin]]
    You can check the Adobe welcome and test page: http://www.adobe.com/software/flash/about/
    You can use this manual download link:
    *http://kb2.adobe.com/cps/191/tn_19166.html#main_ManualInstaller

  • Since numbers 3.1 rendering problem in output

    Since I upgraded to Numbers 3.1 all printed output is no more crispy, it looks like a rendering problem. My Number documents consist of normal text elements and tables, sometimes some charts. Scaling on printout is not activated. On the Mac display the problem does not exist, everything seems to be fine, also in large zoom factors. But printing the document produces some kind of unrendered, pixely output, comparable to a screenshot, by far not that crisp as in Numbers 3.0.1. Other applications such as Pages, Word, Excel are not affected, printouts are fine.
    What I did so far:
    - uninstall and reinstall numbers
    - changing, reinstalling the printer driver (HP Color LaserJet 2025 Series), I use the Postscript driver
    - converting the Number documents to Numbers '09 and opening them again
    - playing and testing with numerous zoom factors
    - changing fonts in the Numbers document
    ... all without any success.
    What helped me was:
    - Installing Numbers 3.0.1 again using TimeMachine, installed it parallel to Numbers 3.1
    - In Numbers 3.1 exporting the Numbers document to Numbers '09
    - Opening that document in Numbers 3.0.1
    - Printing the document in Numbers 3.0.1 --> Output ist fine and perfect.
    It seems to be a rendering problem, only in Numbers 3.0.1. The problem appears in all existing and new Numbers documents on Numbers 3.1.
    Here is my infrastructure:
    MacBook Air Mid 2013, OS X Mavericks 10.9.1
    Numbers 3.1 (1769)
    HP Color LaserJet CP2025dn using PostScript
    Many thanks for your help!
    speckch

    Perhaps you can see the problem in this version. This is a PRINTING problem. You cannot see it on screen in the pdf.
    This is a single Numbers document, printed directly from Numbers (3.1). The font is identical in both lines. The box color is identical (black) and the width of the line is identical (0.5 pt). It was printed on an HP Color LaserJet CP2025.
    The upper text is jagged. It may look fine on your screen, but it's not.
    This is very obvious if you look at the larger image that is linked to the image above. (Remember, a computer screen is only 72 dpi and this image is optimized for that. Printed text is much higher resolution. So, to get an accurate view on your screen of how jagged the text is when printed, you need to look at it magnified. Right-click on the image above to open the image in a new tab, and you should get the full size.)
    Also, the because the upper image is lower resolution (jaggies), the narrow line cannot print accurately. Thus, it appears blueish. When you look at the full-size image, you can see how jagged the line is and the mix of dots (red and blue, predominantly) that was output by the printer. In contrast, the lower text box is smooth and black.
    I don't know where the problem lies, but I have not experienced anything like this on any other program I currently use. It's a postscript printer, and I suspect that something's gone wrong in the postscript output associated with tables and the printer is printing the screen view, not the higher resolution printer data. But that's just a guess. And as far as I know, it's not something anyone other than Apple can fix.
    And, of course, since you can't see this problem on screen in the pdf, no matter how much you "zoom" in, you won't know if your files will print badly until you test it. Or, worse, your client does.
    Bummer.

  • h:dataTable re-rendering problem...

    hi friends,
    In my project i am using JSF and a4j .I am getting re-rendering problem with <h:dataTable> in mozilla it is working fine but in IE6 the dataTable is not re-rendering ..
    code is:
    <a4j:commandButton value="#{rb.New}" onmouseup="javascript:openModalWindow('/NGL/faces/jsp/circulation /ILLPlaceILLRequest.jsp','','dialogWidth:500px;dialogHeight:500px;status:no;scrollbars:yes;top:200;left:200')" >
    <a4j:support event="onmousedown" action="#{requestApprove.newActionPerformed}"/>
    <a4j:support event="oncomplete" reRender="illDetails"/>
    </a4j:commandButton>
    my task is:
    when i press the New button another jsp page will open in modal dialog after closing the dialog the table should re-render...
    Edited by: Venkat_quill on Oct 30, 2008 3:29 AM
    Edited by: Venkat_quill on Oct 30, 2008 3:50 AM

    thanks for your reply...
    I have already tried this case but, the datatable is not re-rendering ...
    I got below solutions..
       <a4j:commandButton value="#{rb.New}" onmouseup="javascript:openModalWindow('/NGL/faces/jsp/circulation  /ILLPlaceILLRequest.jsp','','dialogWidth:500px;dialogHeight:500px;status:no;scrollbars:yes;top:200;left:200')" >
                                    <a4j:support event="onmousedown" action="#{requestApprove.newActionPerformed}"/>
                                    <a4j:support event="oncomplete" action="#{requestApprove.clearData}" reRender="illDetails"/>
    </a4j:commandButton>Why i followed this case this i have Add,Edit ,Delete and Refresh action on datatable.In Edit case i need to set some values in the dialog this also working fine with following code..
    <a4j:commandButton value="#{rb.Edit}" onmouseup="editRequest()">
         <a4j:support event="onmousedown" action="#{requestApprove.editActionPerformed}" reRender="msg,msgmode"/>
        <a4j:support event="oncomplete" action="#{requestApprove.clearData}" reRender="illDetails,msg,msgmode"/>
    </a4j:commandButton>But this problem is oncomplete event is not working in the Internet Explorer....

Maybe you are looking for