ICal 5.0 - washed out dates unreadable

The text in Lion iCal 5.0, mainly 'Month' and 'Year' views is so washed-out grey that I can't read it. As a partially sighted Mac user I usually find a little Zoom is all that is necessary, but this text is just too weak-washedout-gray for that to help.
How do I make the date text black - or at least bold? I know I could use Universal Access to set things system wide, but it is just the ugly new-and-improved iCal that is causing me difficulties.
Getting rid of the dirty brown top to the window would also improve the look of the app.

Our office is experiencing the same symptoms. ICAL is useless  on our imac I5s due to background lines delineating days and weeks along with the labels being virtually unreadable. User input for events and to-dos are redable but useless since they simply appear on a white background. We have attempted to calibrate our displays without success. Universal access is equally without benefit. Becasue of the importance of calendaring, we are considering moving all of it to MS Office for MAC Outlook. Apple needs to either change the screen templates to black and white or provide contrast control within ical itself and/or allow the user to change the background color so that the template will be readable.
I should note that the same problem occurs on our older IMacs as well as our MacBook Pros, but not to the same degree. On these machines the ical grey lines and labels are barely readable, but still not useful.
Does anyone have any other thoughts about curing the problem. I would prefer to use ICAL but without resolution of the problem I will move to Outlook.

Similar Messages

  • Dialog programming, data being washed out in TAB Control

    Hi,
         i am working on dialog programming , in which i am using Table Control  for user input (data is not coming from database table) . everything is going well till assignment of data to internal table but when
    control goes to PBO by any means like pressing ENTER etc. then data being washed out.
    PROCESS BEFORE OUTPUT.
      MODULE TC_CONTROL.
      LOOP AT it_data
             INTO wa_data
             WITH CONTROL tc_control
             CURSOR tc_control-current_line.
        MODULE tc_control_get_lines.
      ENDLOOP.
    PROCESS AFTER INPUT.
    LOOP AT IT_DATA.
        CHAIN.
          FIELD WA_DATA-FREPS_N.
          FIELD wa_data-TOEPS_N.
          FIELD wa_data-PRCH_A.
          FIELD wa_data-SRVC_AMT .
          FIELD wa_data-ACCNT_C.
          FIELD wa_data-AMT_D.
          FIELD wa_data-NARR_X.
          FIELD wa_data-CRPRD_N.
          MODULE tc_control_modify ON CHAIN-REQUEST.
        ENDCHAIN.
      ENDLOOP.
    *Abap program
    MODULE TC_CONTROL OUTPUT.
    DESCRIBE TABLE it_data LINES tc_control-lines.
    ENDMODULE.                 " TC_CONTROL  OUTPUT
    CONTROLS: TC_CONTROL TYPE TABLEVIEW USING SCREEN 1000,
              TC_CONTROL1 TYPE TABLEVIEW USING SCREEN 1000.
    DATA:     G_TC_CONTROLS_LINES  LIKE SY-LOOPC,
              G_TC_CONTROLS_LINES1  LIKE SY-LOOPC.
    *&      Module  tc_control_get_lines  OUTPUT
          text
    MODULE tc_control_get_lines OUTPUT.
    g_tc_controls_lines = sy-loopc.
    move-corresponding it_data to wa_data.
    ENDMODULE.                 " tc_control_get_lines  OUTPUT
    MODULE tc_control_modify INPUT.
    move-corresponding wa_data to it_data.
    MODIFY it_data
        FROM wa_data
        INDEX tc_control-current_line.
    append it_data.
    clear it_data.
    ENDMODULE.                 " tc_control_modify  INPUT
    Please suggest me any clue.
    Thanks in advance
    vijay dwivedi

    Hi ,
    I have understood the problem.
    In your ABAP code replace all the occurrrences of wa_data  with the structurename.
    Use the TABLES keyword to declare the structure .That structure will be same as
    reference table of the table control .
    Here the structure is SPFLI.
    Check the bellow code , it will resolve the issue.
    ABAP code - -
    program  zsdn.
    tables spfli.  " Declare the structure
    data : it_data like table of spfli with header line,
    *wa_data TYPE spfli,  " commented
    w_i type i.
    *CONTROLS TC_CONTROL TYPE TABLEVIEW USING SCREEN 100.
    controls: tc_control type tableview using screen 1000,
    tc_control1 type tableview using screen 1000.
    data: g_tc_controls_lines like sy-loopc,
    g_tc_controls_lines1 like sy-loopc.
    module tc_control output.
      describe table it_data lines tc_control-lines.
    endmodule. " TC_CONTROL OUTPUT
    module tc_control_get_lines output.
      g_tc_controls_lines = sy-loopc.
      move-corresponding it_data to spfli.
    endmodule. " tc_control_get_lines OUTPUT
    module tc_control_modify input.
      move-corresponding spfli to it_data.
      modify it_data
      from spfli
      index tc_control-current_line.
      append it_data.
      clear it_data.
    endmodule. " tc_control_modify INPUT
    module status_0100 output.
      set pf-status 'STAT'.
    *  SET TITLEBAR 'xxx'.
    endmodule.                 " STATUS_0100  OUTPUT
    module user_command_0100 input.
      case sy-ucomm.
        when 'BACK' or 'EXIT' or 'CANCEL'.
          leave to screen 0.
      endcase.
    endmodule.                 " USER_COMMAND_0100  INPUT
    *&      Module  POPLATE_TABLE  OUTPUT
    *       text
    module poplate_table output.
      if it_data is initial.
        select * from spfli into table it_data.
      endif.
    endmodule.                 " POPLATE_TABLE  OUTPUT
    Screen code (Scr no 1000) - -
    PROCESS BEFORE OUTPUT.
      MODULE status_0100.
      MODULE poplate_table.
      MODULE tc_control.
      LOOP AT it_data WITH CONTROL tc_control CURSOR w_i.
        MODULE tc_control_get_lines.
      ENDLOOP.
    PROCESS AFTER INPUT.
      MODULE user_command_0100.
      LOOP AT it_data.
        MODULE tc_control_modify ON CHAIN-REQUEST.
    *    ENDCHAIN.
      ENDLOOP.
    Regards
    Pinaki

  • Lightroom's interpretation of camera raw data washes out colours

    After I import images from my Canon 5D, they look different when I go into the develop module. I read the FAQ and I understand that this is caused by the difference between the stored thumbnail on the camera and the way lightroom interprets the raw image data.
    The problem is, the tone and colour are always far superior in the camera thumbnail interpretation, and I spend considerable time on Lightroom to try and get the image back to how it originally looked on the camera thumbnail, usually unsucsessfully.
    Is there a way I can get lightroom to match exactly the look of the previews stored with the raw file on the camera?
    It is a big problem, because after lightroom interprets the data, skin tones look washed out and the colours are not as rich or natural looking.
    I don't have this problem on other raw converters, and it is making me look for another software solution if I can't resolve the problem.
    Help!

    Well, my eyes must be doing some wonky things then... because in my experience its LR that is cheating me on the colors.
    Yes... Canon many times oversaturates the colors... but I'm pretty sure that those red cherries I took a picture of were not pumpkin orange as LR shows them. ACR has some serious hue shift problems, yet not for everyone... it varies from camera model to camera model, and even within camera model from camera to camera.
    The best we can do, since ACR isn't intelligent enough, is to fiddle with the calibration settings, and save that as the new default for the camera. (There are scripts that help do this if you have a Color-checker and CS2/CS3... but are of no help if you use only LR or Elements.)
    Never expect the default settings in RAW (for ANY converter... Canon's included (with execption, perhaps of Zoombrowser)) to match the preview you see on the camera, or the out-of-camera jpeg. Adjustments will need to be made. Unfortunately in ACR, this means hours of messing the calibration sliders, much trial and error, and perhaps multiple presets to help with different lighting conditions.
    That said... I too would like to see ACR improve in this area... but for the mean-time this is the best we can do.
    edit: (I'm (slightly) exagerrating the extent of the shift above... but its VERY noticable... and can be very frustrating.
    This site: http://www.photoactivity.com/Pagine/Articoli/023%20Calibratori%20al%20sole/Calibratori%20 al%20sole_en.asp explains in more detail than I understand some of the calibration scripts... and even has some screenshots of a color-checker comparing ACR defaults and various scripts to the color-checker. I'd guess the shifts I see are comparable to some of those shifts seen on that page.)

  • Disk Utility: Differences between "Zero Out Data" and "7-Pass Erase"?

    I'm wondering if anyone knows if there's a significant difference between the "Zero Out Data" erase option in Disk Utility (specifically Disk Utility 10.5.5), and the "7-Pass Erase" and "35-Pass Erase" options in same software.
    Here's why I'm asking: I have a co-worker with an iMac G5 20" 1.8GHz with 160GB internal hard drive. As a result of the power supply overheating a week ago due to dust, some hard drive problems resulted. I'm trying to assess whether these are 'soft' formatting problems that can be recovered from, or 'hard' problems requiring replacement of the hard drive and/or power supply.
    Following the failure, I removed the dust and restored the iMac to servicable form. The power supply seems to be OK now. The next thing was to attempt to recover as much data as possible from the 160GB, as the last full backup was a week old. Carbon Copy Cloner, shell copy via 'sudo cp -p -R -v', Finder copy, and DiskWarrior recovery all met with problems. TechTool Pro identified a huge swatch of unreadable sectors during repeated surface scans. Unfortunately, these unreadable sectors were located midway in the OSX boot partition (an 80GB partition), and not in the other 80GB partition devoted to lower priority video data.
    When I was satisfied I had backed up the data to the best of my abilities, I next set out to reformat the drive and see if the bad sectors could be eliminated or remapped out of existence. I did a "Zero Out Data" erasure in Disk Utility (with no errors during the erase), but TechTool Pro showed the bad sectors persisted in equal strength at the same location. I next executed a sixteen hour "7-Pass Erase" (again no errors, and confirming that it takes about an hour per 10GB). The next day when I ran TechTool pro, all of the sector errors had disappeared. I'm a bit perplexed as to why the "7-Pass Erase" seems to have recovered the use of the drive. Is it possible that there are simply thousands of bad sectors now remapped that I'm not seeing? [If so, how do I check for this?] TechTool Pro has not reported any S.M.A.R.T. issues to date on the drive. What am I to make of that?
    There are some related threads I've checked into, but I'm not sure how to properly assess my situation based on this information:
    <http://discussions.apple.com/thread.jspa?threadID=232007>
    <http://discussions.apple.com/thread.jspa?threadID=138559>
    <http://discussions.apple.com/thread.jspa?threadID=118455>
    Since the iMac has three weeks left on it's one year warranty, and I've already moved the user to another machine temporarily, I'm thinking that the smart thing to so is to send it in to Apple to have them look at the power supply and hard drive. That way, when it returns, even if there is still a lingering hardware problem, at least it will be covered under warranty for another 90 days.
    Any thoughts?
    iMac G5 20" 1.8GHz   Mac OS X (10.4.6)   1.25GB RAM, 160GB hard disk, SuperDrive

    HI, Bret.
    The only differences between "Zero Out Data", "7-Pass Erase", and "35-Pass Erase" are the number of times a binary zero is written to every bit on the disk. "Zero Out Data" writes a binary zero once, whereas the 7- and 35-Pass options write a zero seven and 35 times, respectively.
    Technically, one pass with Zero Out Data should be sufficient to map bad sectors out of service, a process also known as sparing. If a bad sector is encountered, it is both marked as "in use" in the directory's allocation table and added to the directory's "bad blocks file."
    My understanding is that the Surface Scan of Tech Tool Pro should identify bad sectors every time it is run unless the bad sectors have been locked out by the drive controller of the ATA drive itself. This is because Surface Scan checks the entire surface of the disk.
    What may have happened is that running "Zero Out Data" spared the bad blocks from a directory standpoint, but did not result in the drive's controller locking out those sectors for reasons detailed in the "Surface Scan" section of the Tech Tool Pro manual. However, the 7-Pass Erase may have resulted in the drive's controller locking out the bad sectors and why Surface Scan did not pick them up after such.
    Given the problems you described, I concur with your plan to have Apple check the affected computer. You might also want to consider purchasing an AppleCare Protection Plan for that Mac: I recommend and buy these for all my Macs.
    For some additional information on bad sectors, see the "Bad Sectors" section of my "Resolving Disk, Permission, and Cache Corruption" FAQ.
    Good luck!
    Dr. Smoke
    Author: Troubleshooting Mac® OS X
    Note: The information provided in the link(s) above is freely available. However, because I own The X Lab™, a commercial Web site to which some of these links point, the Apple Discussions Terms of Use require I include the following disclosure statement with this post:
    I may receive some form of compensation, financial or otherwise, from my recommendation or link.

  • HP Officejet Pro 8100 - Washed out blacks in images / Dark blacks in text prints???

    Here is my system: iMac Maverics OS, HP Officejet Pro 8100, Photoshop, Pages & Genuine inks.
    I print a text page (Black and various colours) from Pages/Text Edit or any other text program and the colours are deeply saturated, blacks are black and I'm totally happy.
    I print the exact same text, recreated in Photoshop, everything is washed out. Blacks are greyish, colours are pastel & it looks like it's been printed at 50% opacity.
    I saved my Photoshop text mock up as a .Jpg .TIF .BMP and tried printing them in Pages & Mac Preview - same washed out results as when I print direct from inside Photoshop.
    All my software is genuine, drivers are up to date. It's like HP use one process to print text and a whole other process to print images, **bleep** is going on???
    Please advise on how to fix, if anyone else is having or has had similar issues.....

    Hello @pA8100 , and welcome to the HP Forums, I hope you enjoy your experience!
    I see you're experiencing Photoshop colour issues.  I would like to help.
    It is possible you need to adjust the colour settings in Photoshop from RGB to CKMY.
    I would recommend utilizing this article on How to Convert RGB to CMYK in Photoshop.
    Good luck and please let me know the results of your troubleshooting steps. Thank you for posting on the HP Forums!
    Please click “Accept as Solution " if you feel my post solved your issue, it will help others find the solution.
    Click the “Kudos, Thumbs Up" on the right to say “Thanks" for helping!
    Jamieson
    I work on behalf of HP
    "Remember, I'm pulling for you, we're all in this together!" - Red Green.

  • H.264 mp4 Export Washed Out

    I can't seem to export an H.264 video without it being washed out. Lower contrast, lower saturation, very noticeable. As if there's a hidden conversion to rec709 or some such that I can't turn off.
    PC
    Premiere Pro CC
    Exporting from Premiere Pro through Media Encoder to H.264 in an MP4 container.
    Video appears the same in VLC, QuickTime, and on Vimeo.
    I've looked and looked and all the solutions I've seen relate to H.264 within a MOV container. Nothing I've seen works.
    Other codecs play back as expected. Definitely not a driver issue.
    This is infuriating. Thoughts?

    Tried exporting a 10-bit DNxHD and taking it through DaVinci Resolve, exporting an H.264 (mov) using Data Levels, and it exports and plays correctly. As a test, I ran this file through Media Encoder reconverting to H.264 (mp4) and the result plays correctly (at data levels).
    This seems to confirm that Premiere Pro / Media Encoder by default (and without an option to change it) export H.264 with video levels. In a day when web video trumps television, it seems at the very least there would be an option to export using data and not video levels, especially when Vimeo and YouTube both request H.264 files. Am I missing something obvious, or this completely retarded?

  • Mac Mini HDMI Samsung HDTV colors washed out

    Hoping someone can point me in the right direction. Just upgraded from a 2009 Mac Mini to a new one. Using HDMI, the colors are washed out and off (greenish purplish) at the default 1360 x 1768. If I pick one of the other (like 720p) the colors are right but resolution is screwy. Any thoughts?
    And... Thank You.

    If you haven't already, make sure all firmware
    is up to date. There has been some recent updates
    that may not have made it to your machine.
    As for the 720p issue, go to the Samsung setup
    screen that deals with screen size and set the mode
    to "Fit to Screen".  Pretty sure it says that or something
    similar.

  • 4K TV not recognized correctly: MacBook Pro Mid2014 15" reports a Samsung UE40HU6900 4K TV as 8K (7680x4320). This results in an ugly, washed out image half the size it should be. Is there a fix for this? (OSX 10.10.1)

    MacBook Pro Mid2014 15" reports a Samsung UE40HU6900 4K TV as 8K (7680x4320).
    This results in an ugly, washed out image half the size it should be. If you turn off scaling everything is tiny as 8K are displayed on a 4K screen. To get the actual 4K resolution you have to turn on scaling. Still 8K is transferred to the device, but doubling the data lines makes the picture look washed out and create obscure effects for line borders.
    Did anybody encounter this problem before? Is there a fix for this? (OSX 10.10.1)

    You have the MacBookPro6,2, the Edsel of Macs. It may be covered by this program:
    MacBook Pro (15-inch, Mid 2010): Intermittent black screen or loss of video
    Make a "Genius" appointment at an Apple Store to have the machine tested.
    Print the first page of the panic report and bring it with you.
    Back up all data on the internal drive(s) before you hand over your computer to anyone. If privacy is a concern, erase the data partition(s) with the option to write zeros* (do this only if you have at least two complete, independent backups, and you know how to restore to an empty drive from any of them.) Don’t erase the recovery partition, if present.
    *An SSD doesn't need to be zeroed.

  • Photo Prints Yellow and washed out

    I am having problems printing photos on photo paper.  I have windows 7 64 bit and all my hp software and drivers are up to date.  My printer is c5180 and I have not had any trouble in the past.  I upgraded to windows 7 in Dec., and have had several printing issues since then.  By the way, I really loved the photo premiere software that came with my printer, but is no available with windows 7.  I have tried printing from several programs including picasa, and the windows photo viewer, which I also don't like as much as windows xp.  I have tried several different settings, including the default everthing on automatic, messed with the color setting in the printer settup, and tried printing on 8.5 x 11 as well as my 4 x 6 photo paper.  If I print on regular white paper the colors are just fine, it is only when I use photo paper.  My photo paper is HP Premium Photo paper.  I have attached scans of two photos and you can see the one on photo paper is yellow and washed out whereas the one on plain paper has good coloring.  Do I need to change anything in color profiles? 
    I have no idea how to get my pictures to display.  They are on picasa web albums and I also tried to just drag them in. 

    Did anyone ever solve this problem?  I have the exact situation with my C5180 and I am about replace it.

  • How to wash out an AM instance variable at the end of user session (logout)

    We have a need to create AM instance variables to hold some session level data, which is too complex to be held in a transient VO.
    What we observed is that the instance variable is not washed out at the end of the user session (i.e logout).
    I think since the AM instance is not really destroyed but only release back to the pool the instance variable content persists and is carried over to the next session that access the AM instance.
    What method in AM can be overridden to wash out this instance variable.
    At the moment we are resetting it in prepareSession(), but this means that the information is still held till the next session access the AM.
    It would be better to reset it when the AM is released back to the pool.
    Any pointers would be helpful.

    At the moment we are resetting it in prepareSession(), but this means that the information is still held till the next session access the AM.
    Note that prepareSession() is also invoked after AM activation so this can(and probaly will) reset your variable inside existing session.
    If you don't need to keep variable value between AM activations/passivations, you can use userData, for example:
    this.getSession().getUserData().put("someKey", value);
    UserData values are lost after AM passivation (by default).
    If you need to keep UserData variable value for lifetime of user session, then you can override passivateState() and activateState() as in this sample:
    Application State Management
    Dario

  • EOS T3 Pictures washed out

    I am just recently having problems with my EOS T3 camera.  The pictures will start to wash out.  The three pictures below display the problem with them middle one changing half way through.  If you know what I am doing wrong let me know.
    I generally use a photo soft cube with lighting on 3 sides and set the camera to automatic.   Never had any problems until recently.
    Thanks.

    Hi Sphudson,
    While this appears to be a flash synch issue, I recommend contacting our technical support group for further assistance.  We'll ask you for an fully unedited image (we'll need the image's EXIF data).  If you include it with your inquiry, please limit the size to 12 MB or so.  You may see contact options by clicking here.
    Did this answer your question? Please click the Accept as Solution button so that others may find the answer as well.

  • Quicktime export, colors washed out

    I think this question has been asked before but I just couldn't find a good explanation in the archives. Wondering if anyone knows why, when I export my movie out of FCP to h.264 and then playback in quicktime, the colors become much more muted and washed out. This has been happening for awhile now, and its been driving me nuts and now I have a project that is absolutely going to hurt because of it.
    I want the bright vibrant colors that I see in my canvas in FCP -- what gives? Any help would be great. Thanks.

    Yeah, sorry, this was actually a graphic created in Motion 3 then sent to FCP to sync with some audio and other sound effects. The entire workflow is HDV 1080p24, compressed to various sizes of h.264 and meant for web only. Because it is meant for the web, I have bypassed a calibrated monitor and am just doing all the work on my Apple Cinema displays.
    Like I said, I can take the exported h.264 version from FCP, open it in quicktime and hold it up right next to my FCP canvas and the luma and chroma values are noticeable muted, less vibrant, and just not as much fun to look at.
    I have played around with the general settings in Quicktime, specifically the "Enable Final Cut Studio color compatibility" option, but still no change. I have read other places about this being a gamma issue once the movie is played back in Quicktime, but I really don't know what that means.
    All of my software is about as up to date as you can get.

  • LaserJet P2015dn Washed Out Print

    The cartridege and printer is brand spanking new.
    Word, Excel documents print superbly. However, if I print something from a website it is barely readable, same for my email messages.
    I use Gadwin Print Screen software and that results also in printing almost unreadable.
    I'm slugging through the manual (sure do like those hard copies)
    I sure would appreciate any help on this. Back to the manual I go
    Thanks in advance

    Have the photos printed out in more vivid colors in the past or have the photos always been "washed out"?  You might also try the following document, just to make sure there isn't a problem with the cartridges:
    http://h10025.www1.hp.com/ewfrf/wc/document?docnam​e=c01810864&tmp_task=solveCategory&lc=en&dlc=en&cc​...
    Say Thanks by clicking the Kudos thumbs up. Please mark the post that solves your problem as an Accepted Solution so other forum users can utilize the solution.
    I am an HP employee.

  • Photos sent through ePrint are washed out - Help

    I just ran a test sending 3 photos from my ipad via email to my HP Envy 100 e-Printer and they all appeared washed out. I then sent the same 3 photos directly to the HP Envy 100 e-Printer using the HP iPrint app and they were nice and brilliant -- confirming that the HPePrint Server is degrading the quality of photos.
    Does anybody have any guidance on how to prepare photos that will be sent through the HPePrint Server so that they will be printed by the e-printer acceptably???

    Hi slimmerjim,
    Thank you for your feedback.
    There will be some degradetion print quality if you compare between ePrint and HP iPrint. ePrint is transfer the data through the Internet so the photos are printed in normal mode as compare to HP iPrint which sends the data through wireless network which are printed in best mode.
    HP is aware of this issue and we are looking to improving this.
    Thank you.
    I am an HP employee
    **** Please mark the post that solves your problem as "Accepted Solution" ****

  • Psd file wash out when add transparency to page

    HI,
    I've had a noticeable yet unknown problem, and today I figured out why, but now need help fixing it.
    Working with CS2
    When I import a grayscale psd file into ID, it gets washed out when I add a transparent element to the page. My page started out in the page Window as a solid white background, and changed to transparent when I added the transparent element next to it. At the same time, my nicely contrasted grayscale psd image (contains levels adjustment layer) became washed out and lighter. This is the first time I've actually watched it happen as I added a transparent element - probably because often transparent elements are added before my photos.(this explains the poor image quality I've had in the past - always thought it was a calibration issue on my monitor).
    So my question is, how do I get the page (icon in the pages window) to be solid white again? or at least not weaken my grayscale images?
    I had a printout before I added the transparent box, the image printed nicely. Now the image prints washed out just as on the screen. (printing using "Send All Data" for image output.
    I'm working in Doc CMYK, transparency flattener is set to Doc CMYK, turned on overprint preview, tried isolating the blending, knocking it out, re-placing the psd file, adding a solid white box behind it (a no-no, I know, but was for testing purposes) all to no avail.
    I'm sure there must be a setting somewhere, but I'm not finding it.
    I'm grateful for any help I can get!

    How are you printing? Are there any CMYK elements on the page?
    Most desktop printers are really RGB devices. You may find you get better results if you change the transparency blend space to RGB.
    Peter

Maybe you are looking for