Maybe a Subpixel-Rendering problem ?

Hallo there,
i’ve managed successfully to programm a Lens-Distortion Plugin, using the Skeleton Template as a base.
So far, every function from this Plugin is functioning like it should be. The single problem that I have, is that the Image is like “Pixelated“ on the edges maybe a Subpixel-rendering or antialiasing problem.
This can be seen at example foto down here. 1 is the original image and the 2 foto is the distorted image with my plugin. The subpixeling is really on each corner of the box.
I thought first, that i was rounding the variables, but i’ve checked my algorithmus and am using doubles for the parameters, so it can’t be round.
Do you have any Idea, what i am missing ?
Thanks in advanced,
Boban
The main function looks like this:
static PF_Err
MySimpleGainFunc16(
void    *refcon,
A_long    xL,
A_long    yL,
PF_Pixel16  *inP,
PF_Pixel16  *outP)
  PF_Err        err = PF_Err_NONE;
  DistInfo      *giP = reinterpret_cast<DistInfo*>(refcon);
  AEGP_SuiteHandler  suites(giP->in_data.pica_basicP);
  PF_FpLong      tempF = 0;
  PFBarrelCommon    *barrel = NULL;
  PF_Fixed      new_xFi = 0, new_yFi = 0;
  double        offset_x_ = 0, offset_y_ = 0;
  double        //GUI PARAMETERN
    c3_ = giP->low,    // Low Order par
    c5_ = giP->high,  // High Order par
    xp_ = (double)((giP->centerX)),  // Lens center X
    yp_ = (double)((giP->centerY)),  // Lens center Y
    in_width_ = giP->orig_width,      // Undistored x giP->footage_width;
    in_height_ = giP->orig_height,      // Undistored y giP->footage_height;
    orig_width_ = giP->orig_width + giP->footage_width,      // Undistored x giP->footage_width;
    orig_height_ = giP->orig_height + giP->footage_height,
    squeeze_ = giP->anaS,  // Ana... Squezze
    invSqueeze_ = 1 / squeeze_,
    f1 = orig_width_ / in_width_,
    f2 = orig_height_ / in_height_;
  Point2
    DistortPoint = Point2(1, 1),
    UnDistortPoint = Point2(1, 1),
    C3C5_ = Point2(c3_, c5_),
    outputAbsCent = barrel->calcAbsCent((float)xp_, (int)orig_width_, (float)yp_, (int)orig_height_),
    absCent_ = barrel->calcAbsCent((float)xp_, (int)in_width_, (float)yp_, (int)in_height_);
    offset_x_ = absCent_.x - outputAbsCent.x,
    offset_y_ = absCent_.y - outputAbsCent.y;
  Point2
    pt_ = Point2(((double)xL_*f1 + offset_x_), ((double)yL_*f2 + offset_y_)),
    norm_ = barrel->calcNorm((int)in_width_, (int)in_height_);
      switch (giP->distortion_mode)
        case DM_DISTORT:
          DistortPoint = barrel->PFBarrelCommon::solveDistort(C3C5_, absCent_, squeeze_, invSqueeze_, norm_, pt_);
          break;
        case DM_UNDISTORT:
          DistortPoint = barrel->PFBarrelCommon::solveUndistort(C3C5_, absCent_, squeeze_, invSqueeze_, norm_, pt_);
          break;
        default:
          break;
  new_xFi = (A_long)(DistortPoint.x) << 16;
  new_yFi = (A_long)(DistortPoint.y) << 16;
  ERR(suites.Sampling16Suite1()->subpixel_sample16(giP->in_data.effect_ref,
    new_xFi,
    new_yFi,
    &giP->samp_pb,
    outP));
  return err;

I would try connecting an external monitor, if the problem doesn't appear on the external monitor then you possibly have a failing internal LCD display panel or cable.
If the problem appears on the external monitor as well, then that would indicate to me its a graphics chip / logic board issue, this fault may qualify for Apple's free repair offer.
http://support.apple.com/kb/ts2377
What ever the outcome with the external monitor, it's worth taking it to an Apple store anyway, as they'll check it for free.

Similar Messages

  • Incorrect subpixel rendering iin FF 19.0.2

    In many situations FF does not correctly display subpixel rendering. It appears as if the color one one side of a leg is assigned also assigned to the adjacent pixel of the leg. For a font leg only one pixel wide, there is no black portion of the leg, only the color which should be on the side. See http://tinypic.com/r/2rx6zax/6 or for a screen capture showing the problem. In the screenshot notice that the "l" in "baseline" is completely yellow.
    The problem occurs frequently, on a seemingly random basis. Each line of text is affected individually. In the screenshot, the top three lines are affected; the bottom line is not affected. Selecting any text within an affected line will clear the problem for the entire line. As I scroll through a long page, lines that approach the top of the window will often become affected.
    No other browser has this problem on the displayed pages. No other application has this problem. The problem is reproduced on a variety of sites. This site, support.mozilla.org shows the problem, but just for the text in the text entry boxes, though. The NewYork Times and slashdot are frequent problem sites. Other sites seem immune. I suspect it has something to do with how the text is packaged within the HTML for the page.
    I am running Windows 7 (64 bit), and to the best of my knowledge, I have the latest version of all video drivers. My monitor is a Dell U2410. Turning off clear type or turning off font smoothing obviously eliminates the problem, but only by eliminating sub pixel rendering, making the fonts are more difficult to read. Interestingly, just activating the "ClearType Text Tuner" window, clears up the problem for the currently displayed text. Other actions besides selecting text in the line will also clear the problem.
    I am able to reproduce the problem on a nearly a daily basis. I will be happy to provide further information if requested.
    Question: Is there a solution to this situation short of disabling subpixel rendering?

    Try to disable hardware acceleration in Firefox.
    *Tools > Options > Advanced > General > Browsing: "Use hardware acceleration when available"
    *https://support.mozilla.org/kb/Troubleshooting+extensions+and+themes
    *https://hacks.mozilla.org/2010/09/hardware-acceleration/

  • Graphics rendering problem in web dynpro

    Hi all,
    I have a problem using BusinessGraphics in my web dynpro application. I got the "Graphics Rendering Problem". Reading some foruns, Ive read in some thread that I have to have 5 files under my igs/conf folder of SAP installation, but I have only 2 (gwfchart.tpl and xmlchart.tpl).
    One proposed solution is to apply one patch to my igs server.
    My question is....
    - How do I dowload the patches ? From where ? I couldnt find a download link.
    Thanks in advance,

    Hi,
    the corresponding note for the IgsUrl paramter mentioned by Rich is <a href="http://service.sap.com/sap/support/notes/704604">704604</a>.
    I think you should check this first before you upgrade your IGS installation. Note <a href="http://service.sap.com/sap/support/notes/931900">931900</a> shows you how to find out the IGS patchlevel. Then you see if your IGS is running (correct) and maybe an upgrade is needed also.
    Regards
    Matthias

  • 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.

  • 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.

  • Is Adobe Premiere Elements 10 compatible with Windows 8? Or maybe it will have problems?

    Is Adobe Premiere Elements 10 compatible with Windows 8? Or maybe it will have problems?

    Riccardo Pesare
    I have Premiere Elements 10 on Windows 8.1 64 bit, and it runs well there.
    But, I must disagree with SG when he writes
    It will likely run. But it will not be able to take advantage of Windows 8's advanced architecture (including the 64-bit operating system and ability to access more than 4 gigs of RAM).
    You can prove to yourself that Premiere Elements 10 is a 64 bit application running on Windows 8 64 bit. To do this use the Process Explorer Sysinternals and add a Image Type Column readout. When you do this for Premiere Elements 10, 11, or 12 on Windows 7, 8, or 8.1 64 bit, the readout tells you that you are working with a 64 bit version.
    http://technet.microsoft.com/en-us/sysinternals/bb896653.aspx
    And, as a 64 bit application, Premiere Elements 10, 11, or 12 Windows should be able to take full advantage of the 64 bit system when Windows 7, 8, or 8.1 64 bit.
    I suspect SG is thinking Mac not Windows in his comment. It is my recollection that Premiere Elements 10 Mac is still a 32 bit application on 64 bit system. And, you are using Windows, not Mac.
    We will watch for his clarification on this point or for support for what he posted as is.
    ATR

  • 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....

  • Uninstall FCP for rendering problem? Then re-install?

    I keep loosing my render files. I think the problem started when I installed an update for FCP. Now, the render files disappear. I'll render, but then they go away.
    I've seen posts with others having this same problem. Would un-installing FCP work? Of course, I'll back up my video on an external drive - just in case. Then I'll re-install my FCP, hoping that this will solve my disappearing render files.
    If you'd like more details to my rendering problem, here's the post I put up a few days ago that describes in greater detail what's happening...
    http://discussions.apple.com/thread.jspa?threadID=1394901&stqc=true
    Do you think un-installing would work?

    Hi JGD 500, and a warm welcome to the forums!
    I noticed there is no mention of hardware space - should there be? This information doesn't show up anywhere in the disc utility diagnostics/profile - leading me to the thing the harddrive is busted - but the hardware test found no problems.
    Yes, I believe if it can't see the HD, it won't test it or even mention it.
    I've seen several Notebook HDs die within a years time, they've always been the worst HDs, but I think the pressures of today's world are making them even worse.

  • ADF 12c Rendering Problems at design time

    Hi all,
    I am experimenting the following unexpected rendering problems at Design time with JDEV 12c:
    -  Sometimes a complete page is showed empty or blank but the components exists on the page (you can see them in the structure panel) and the page has no warnings.
    -  Sometimes I cannot click a component because it is behind the container.
    -  Sometimes the containers are rendered in other place on the page.
    -  Sometimes the containers not stretching
    I remember some posts about this problem in 11.1.2.x but I think it was not fixed in 12c. For this reason, I have some questions:
    What is the "real" memory requirement  of Jdev 12c to avoid render problems?
    What is the best configuration in jdev.conf?
    Is it only a memory issue or Is it also a dependency reference problem? According to a blog post of Frank Nimphius:
    Though with Oracle JDeveloper 11g the problem of the IDE not rendering JSF pages properly in the visual editor has become rare, there always is a way for the creative to break IDE functionality. A possible reason for the visual editor in JDeveloper to break is a failed dependency reference, which often is in a custom JSF PhaseListener configured in the faces-config.xml file. To avoid this from happening, surround the code in your PhaseListener class with the following statement (for example in the afterPhase method)
    public void afterPhase(PhaseEvent phaseEvent) {   if(!ADFContext.getCurrent().isDesigntime()){ ... listener code here ... } }
    The reason why the visual editor in Oracle JDeveloper fails rendering the WYSIWYG view has to do with how the live preview is created. To produce the visual display of a view, JDeveloper actually runs the ADF Faces view in JSF, which then also invokes defined PhaseListeners. With the code above, you check whether the PhaseListener code is executed at runtime or design time.If it is executed in design time, you ignore all calls to external resources that are not available at design time.
    source:
    https://blogs.oracle.com/jdevotnharvest/entry/when_jdeveloper_ide_doesn_t
    if it is a known problem, then Why is not fixed in 12c?
    Jhon
    Jdev 12c

    Jhon, what Frank mentioned can't be fixed from the outside. You or the developers who use phase listens without thinking about the design view are the ones to fix this. Frank provided you with the solution for this.
    However, we don't know if you use any self written phase listener. If you don't do this you have another problem. I do see some of your symptoms but can't reproduce them at the moment. As long as we can't reproduce the problem somehow it's difficult to to get a solution.
    My advise is to keep your eyes open (add I do) and whenever you can reproduce this behaviour come back and tell us about it. It's hard or impossible to give the 'best' settings for Jdev.conf as they depend on other factors e.g. operating system, memory, other applications running at the same time and many more.
    Personally I don't change the parameters as long as I can't put the problems to low memory (which I can't at the moment).
    Timo

  • JTreeTable rendering problems

    Hi all!
    I have used some clesses to create a JTable containing a JTree, basing on the example in the sun's site. The costructor is:
    JFrame frame = new JFrame("TITLE");
    JTreeTable table = createTable(); //Creates the treetable
    JScrollPane scrollPane = new JScrollPane(table); //it puts the newly created table in a scrollPane
    frame.getContentPane().add(scrollPane,BorderLayout.CENTER);
    frame.pack();
    frame.show();
    I have the following problems:
    1. If I have not many nodes in the tree, I have a bad renderer effect: the table doesn't fit the whole window but just the upper part of that, at the bottom it's all gray (the JFrame color, I think).Even if I set the JFrame background color to white, I still have that problem.
    2. If I don't add the table to the scrollbar, I can't see the headers, but I don't have the problem of the gray panel.
    Does anyone know how I can work out this? Has anybody examples of JTreeTables that don't have this rendering problem (with the table fitting the whole window even though they don't have many nodes)?
    Feedbacks are welcome, this is really showstopper for me...
    Thanks a lot!

    Hi there.
    Try setting the viewport color of your scrollpane. I don't have my API's on hand but you go something like myScrollPane.getViewport().setBackgroundColor(Color.white);
    How does that go for you?
    Cheers,
    Rachel

  • Separate subpixel rendering for each monitor

    Hi,
    is it possible to configure separate subpixel rendering for each monitor? I use a multi monitor setup with 2 additional inverted screens (via xrandr). Each screen has a RGB subpixel mapping. The font rendering on the inverted screens looks odd, because they would need BGR mappings. Thats my guess at least, tested it via http://www.lagom.nl/lcd-test/subpixel.php

    Unfortunately there is no way to have separte subpixel rendering for each monitor.  The library doing the rendering (freetype), would have to know which screen you are on and adjust dynamically.  Plus, suppose you have half of a window on one screen and half on another - it wouldn't know which to choose.
    I would like to be able to do this, too, for my rotated monitor.
    I am sure it is technically possible, but not without a major redesign of how the applications render the fonts.

  • Business Graphics Tutorial: graphics rendering problem

    Hello,
    I did the tutorial "business graphics". Deploying the project I get the error: graphics rendering problem
    Is there anything first to set up, I forgot?
    Thank You, Regards Mario

    Hi Mario,
    Go to this link .It contains steps for installing igs
    http://help.sap.com/saphelp_nw04/helpdata/en/4b/72d43ac66e1f08e10000000a114084/frameset.htm
    After installing igs see whether you can see it on the services in mmc
    Hive the listener port as 8030
    After the installation go to the default page as given below
    http://<server name>:8030
    If the igs service is running you will get a default page
    After that go to this link and do the sample application
    Regards
    Rohit

  • Geo Maps - Graphics rendering problem

    Hi Experts,
    I got this error while running an Application with Geo Map.- " Graphics rendering problem"
    In my application there are two UI elements ,
    Geo Map and Business Graphics, i can see business graphics properly but problem is only with GeoMap.
    I checked the SAP Note : 704604.
    And the entry in my Visual Admin is : http://localhost :40180
    When i go to the URL http://<server>:4<instance>80 , i get the message displayed as "SAP IGS is running"
    I am unable to figure out the problem can you guys help?
    regards,
    Ashish Shah

    Hello Ashish,
                     There must be some problem with IGS server. So check whether your IGS server is configure properly or not.
    Follow these steps:
    1. Check the path first
      Local Drive : \ usr \ SAP \ J2E \ JC01 \ J2EE \ admin
    2. Connect to SAP J2EE Engine
    3.Open the Visual Administrator Window, In Global Configuration page ,go to
           CONFIGURATION ADAPTER  -> WEBDYNPRO -> sap.com - > tcwddispwda -> propertysheet.default
    4. Switch to edit mode
    5.Change property entry , http://<server name: port number>
    6.Exit the visual Administrator window
    7.Restart J2EE Engine.
    Best Regards,
    Sheetal.
    Edited by: Shital Patil on May 1, 2008 3:11 PM

Maybe you are looking for

  • Won't add more than 3 video files at a time

    I had 22 episodes or a TV show in mp4 format, average size 124MB, to add to my iTunes. When I go "Add file to library" and select all 22 episodes, nothing happens. I search for the files in iTunes and they are not added. If I add 3, not MORE than 3,

  • Transferring from old imac to new

    I currently am using a Firewire drive for my Time Machine backup.  How can I get that data to the new iMac which does not have a Firewire port?

  • First Website Attempt

    This is my first attempt at building a website. I have many questions, but I will start with a basic one. I have one image that I want to cover the entire page. How can I do that and then set the table up after the image is placed? Please remember th

  • Getting my partners MacBook onto our wireless home LAN using WPNT834

    I don't have much experience with Macs but know a bit about basic networking, well enough to set up a home network based on a cable modem, cable router with both wired and wireless PC clients. My partner has a MacBook which used to be on the wireless

  • Photoshop will not save file extension, how do I fix?

    When saving any file, Photoshop saves only the filename without the extension- i must manually add the extension in finder- nightmare! Help Chat sucks so here I am. I have uninstalled and reinstalled but it still doesn't work- any ideas??