NASA widget doesn't display content

Does anyone know anything about this: I went to the widget download site and downloaded the NASA widget. It needed the realplayer plug-in, so I downloaded that. That needed stuffit expander, so I downloaded that. Now I find out that none of this will work on an intel based iMac:
http://real.custhelp.com/cgi-bin/real.cfg/php/enduser/stdadp.php?pfaqid=5659
So I can't get a NASA widget, created for Mac, on my Mac????
Please help me with real information.

Please, which version do you use? If it is 6, exact version number.

Similar Messages

Firefox doesn't display content, especially links.

This is my problem in a screenshot: http://d.pr/i/DjkB
The content isn't displayed and especially links. Links are always not there and sometimes text is displayed but all websites are disfunctional because of this.
Here's a link to a screenshot displaying how the same website should look like: http://d.pr/i/ZRvN

Did you manage to find out which font Firefox is using in the case when text doesn't display?
You will have to remove or update that font.<br />
You can also check that font in Fontforge.
*http://fontforge.sourceforge.net/

Finder doesn't display contents of shared NAS

I recently upgraded my NAS to the latest version and since then I cannot access the NAS in the usual way from any Mac. The Macs are Macbook Pro 2.4 duel core OSX 10.7.5 and iMac 3.2 i3 10.6.8. The NAS is a STORA 2110.
I can connect using the Stora application or using Go - Connect to server - smb://STORA then choose the partitions to mount and I can see the files on MyStora.
If I select Stora from the left hand side of the Finder window under SHARED, I says status is connected but it doesn''t show any files. It spins and spins.
I think this is something to do with how apple speaks to linux/windows...
You may wonder what the problem is as I can see it, well I have 27,000 songs on the Stora that have been added to iTunes from the old way, the shared connection, and iTunes cant see them when I connect using the Go - Connect to server... connection. I think because the path to the Stora is different for each connection.
I'm happy to have a work around if it is the path?
HELP!

As it turns out, spotlight indexing for some strange reason has been turned off for my HD.
Is it really possible, that "sudo mdutil -avE" only deletes the file, and that a new one isn't automatically created? Anyways using Spotless revealed that indexing was actually turned off for my HD, and enabling was just a click. The throbbing dot and all that came to life after e few seconds.
Actually I think it may have been turned off every since i upgraded to 10.6 - and I've just lived with it, and concluded, that Spotlight had become slow in 10.6 and instead I just used Quicksilver. No wonder it was slow when it didn't have an index!

Calling WebHelp from JS doesn't display content in frames

Hi,
We are using WebHelp on a UNIX server run from the cloud, to replace the original spartan-at-best, flat-HTML help content that was released with a web-based program, all of which was "context-sensitive" via mapping to #Name destinations within the old help web page. To make it work, we have a JavaScript that maps the old #Name destinations to the new WebHelp MapIDs and redirects the old help web page to a subdirectory that has the WebHelp output files. But, it's not working correctly. If we invoke WebHelp via
HH_DISPLAY_TOC, the new WebHelp opens within the frameset, but the context-sensitive mapping doesn't work.
The programmer says we need a way to call help using a URL. So, I sent him what it says in the RH help system for programmers:
RH_ShowHelp(0, "IQ_Help/util_en.html", HH_HELP_CONTEXT, HelpTag)
I also sent him a PDF of the RH help topics for programmers about calling WebHelp.
From what I gather reading the JavaScript (and I am NOT a programmer), he has set HelpTag as the variable for the Map ID that is provided in a .properties file.
Tried unsuccessfully using the following ways of calling it (not as sequential lines of code, but as replacement methods of the same line of code):
RoboHelp_ShowHelp(http://[servername]/IQ_Help/util_en.html, 0)
RH_ShowHelp(0, "IQ_Help/util_en.html>UUGuide%20SPi",HH_HELP_CONTEXT, HelpTag)
RH_ShowHelp(0, "IQ_Help/util_en.html>UUGuide%20SPi",HH_DISPLAY_TOC, HelpTag)
http://[servername]/robohelp/rest/robowindow?wtype=ctx&context=HelpTag <-as a call to URL
I'm sorry, I'm looking like a real idiot around here -- I really don't know much at all about Java or JavaScript, and I have never had to direct a programmer through how to get the help call to work, and I'm at the end of his patience with me... I don't know where else to turn...I need some insight from YOU.
I thought about providing the text of the JavaScript here, but I don't know for sure whether it would show up as text, or how to make it an attachment that's safe. Please tell me...?
Thanks in advance,
Rene

Hi there
If all they want is to use URLs, see if this helps...
Click here to view
Cheers... Rick
Helpful and Handy Links
RoboHelp Wish Form/Bug Reporting Form
Begin learning RoboHelp HTML 7, 8 or 9 within the day!
Adobe Certified RoboHelp HTML Training
SorcerStone Blog
RoboHelp eBooks

Chrome doesn't display content?

I'm using the TCS 3.5 version of RoboHelp, a.k.a. RoboHelp 9. Chrome looks like it's version 16? There are other versions being used, though.
We almost went crazy yesterday, because my boss followed my instructions for turning her project into WebHelp, and it came up empty. Literally. No left nav table of contents, no search, no text, nada. Just the skin. And the skin was a slightly different color, and the spacing was funky. After a few hours of hair-pulling, having others walk through the process and generate RoboHelp just fine, we found out her default browser was Chrome. So I pulled her output off our fileshare, and opened it in Chrome, Firefox, and Explorer. The last two were fine. But Chrome was empty, and the skin didn't look right. It looked fine on the other two browsers.
So, what do we do? Is there some way to make RH Chrome-friendly, the way you can add Mark of the Web? Or are we just SOL, and Chrome and RH don't play well together?

Hi there
Does Chrome display it correctly from a Web Server? For example, does the link below work in your boss' Chrome browser?
Click here to view
I seem to recall that Chrome has issues with WebHelp from any HAT because of the framesets. But only when you attempt to view locally. It's a security thing. So is Mark of the Web. But that's only applicable to Microsoft Internet Explorer.
Cheers... Rick
Helpful and Handy Links
RoboHelp Wish Form/Bug Reporting Form
Begin learning RoboHelp HTML 7, 8 or 9 within the day!
Adobe Certified RoboHelp HTML Training
SorcerStone Blog
RoboHelp eBooks

SAPUI5 Application doesn't display in Portal Content Area

Hallo Guys
We are developing a SAPUI5 application that needs to be displayed inside the portal.
The problem is that the SAPUI5 app doesn't display in in the content area, no erors, just a blank page, you have to set the iview to open in a seperate headerless window, then it works. But it needs to work in the content area.
Our findings: a possible cause is that the IE mode when inside the Portal content area is IE5 Quirks, and when it displays in a new window, the mode changes to a more recent and acceptable mode for SAPUI5, IE9.
Is there any solution to this? We get the same result with both URL iView and using the SAPUI5 iView in content provided by SAP. We are on NW 7.4
Regards
Antonette

Hi Antonette,
As Lawrence explained the reason is indeed that quirks and standards mode can't run together on the same page (not only in portal but it's a limitation by MS).
Since your framework page is in IE5 quirks mode the UI5 application doesn't run in the content area, you can run it by selecting in the iView properties "Launch in a new headerless window (strandards)", that will open the UI5 application in a new window and will work.
If you wish to run UI5 applications in the content area you can get latest SP of 7.4 and there you will have a new framework page: standards AFP, basically an AFP framework page that works in standards mode.
In that framework page you can run UI5 applications in the content area, however trying to run old applications (HTMLB, not WD) may fail, for WD you have a paramater you need to pass called sap-ie, passing it with the value of "Edge" will make sure WD applications run in standards mode as well.
When running the AFP in standards mode you will need to open your HTMLB and other old applications in a new headerless window or new window so you can see the content.
Hope this helped,
BR,
Saar

Flash content doesn't display in browsers

I recently updated Dreamweaver to 8.0.2. I updated an .swf
file, updated the link on my DreamWeaver page and uploaded
everything. When I saved the DreamWeaver page a window popped up
that said it was modifying the html to work with the updated
Internet Explorer. The new .swf file doesn't display on any browers
(Safari, FireFox, IE)
Does anyone know what's going on?

Did you upload the Scripts folder that DW places into your
local site when
you do this?
Murray --- ICQ 71997575
Adobe Community Expert
(If you *MUST* email me, don't LAUGH when you do so!)
==================
http://www.dreamweavermx-templates.com
- Template Triage!
http://www.projectseven.com/go
- DW FAQs, Tutorials & Resources
http://www.dwfaq.com - DW FAQs,
Tutorials & Resources
http://www.macromedia.com/support/search/
- Macromedia (MM) Technotes
==================
"dlipscombe" <[email protected]> wrote in
message
news:ecv25g$i9v$[email protected]..
>I recently updated Dreamweaver to 8.0.2. I updated an
.swf file, updated
>the
> link on my DreamWeaver page and uploaded everything.
When I saved the
> DreamWeaver page a window popped up that said it was
modifying the html to
> work
> with the updated Internet Explorer. The new .swf file
doesn't display on
> any
> browers (Safari, FireFox, IE)
> Does anyone know what's going on?
>

Weather Widget bug: doesn't display full city name initially

I have a brand-new Mac Mini.
The weather widget is configured incorrectly if you go through the default set-up process for Philadelphia.
I went through the standard Mac OS X first-time setup, telling it my location (Philadelphia, USA). This pre-configured my time zone correctly for east coast, but for some reason pre-configured my weather widget for Philadelphia, NY (instead of the MUCH more likely Philadelphia, PA).
BUT it just said "Philadelphia" on the widget, and in the widget settings, so it looked correct... it took me a week to figure out why the weather data was always so wrong. It was just on a whim that I tried re-entering the location in the settings (even though it appeared to be correct.)
Really, it should be smart enough to assume the larger city, but at the very least the widget should have displayed "Philadelphia, NY" in the settings instead of just "Philadelphia".

I can't help with a fix but I can confirm seeing the same behavior, not only with the 'snow' image but with others. It is very erratic: sometimes the city name underlines & I get the hand pointer on mouse overs, sometimes no underline but the hand pointer, sometimes nothing but a flicker of the hand that reverts to the arrow as soon as the pointer comes to a stop over the name.
Worse, this seems to have little to do with the ability to click through to the web page. Sometimes there is no visual pointer change or underline cue but the link is live; other times it isn't.
Try this: Cmd-option-clicking on the weather graphic icon cycles through all the graphics & changes the location to "Nowhere." Cute, but sometimes "Nowhere" sticks as the location the next time Dashboard is displayed, sometimes not. Other anomolies have been noted in other threads, too.
Bottom line is I think the weather widget isn't very sophistocated & is easy to confuse.

Content doesn't display

Recently, my home versin of Framemaker 10 refuse to display content. I have opened several files that I created in FM 10 but I get a blank page display. when i close the file, I will often get a flicker on the screen showing the that the content is indeed there, just not displayed for editing.
Any one have a similar experience and hopefully some advice on solving this?

I have opened several files that I created in FM 10 but I get a blank page display. when i close the file, I will often get a flicker on the screen showing the that the content is indeed there, just not displayed for editing.
If you create a new document, can you see the text?
When you open an old, and click-drag the text select cursor where text should be, does it look like anything is being selected?
There are a number of ways the text could be there, but be invisible or hidden. Some snap guesses:
a Condition Code got applied and is set to Hide
text color got set to white
text color isn't white, but whatever it is is set to Invisible in Color Views
Master Page layouts got trashed, shoving text out of view
black got redefined

Logo doesn't display in IE7

Hi, New to Dreamweaver. Followed basic design example from a CS5 class by James Williamson on Lynda.com. All layout and standard features including images and background images are fine except my logo. It is positioned absolutely in upper left corner within the body, wrapper and header div. When previewing in browser lab the logo doesn't display in IE7. Works fine in other browsers and IE8. On browser compatibility check I get mention of float drop on my footer, but I don't think that would be my problem. Please help me. I want to make a template, but not with an image problem.

Thank you Richard. I used both validations and only received error & warning for ampersand in line 94. No problems with my main.css I'll try the fix later. I guess I have to copy and paste the code, I don't know how to get you a link since the file is still local. I'll start with htm page. Excuse my novice skills. I also put extra code in to try and fix float drop error, to no avail. Thank you.
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />

<title>base template</title>
<link href="_css/main.css" rel="stylesheet" type="text/css" />
<script src="SpryAssets/SpryMenuBar.js" type="text/javascript"></script>
<link href="_css/newspry.css" rel="stylesheet" type="text/css" />
</head>
<body id="body">
<div id="wrapper">
<div id="header"></div>
<div id="mainNav">
    <ul id="MenuBar1" class="MenuBarVertical">
      <li><a href="#">Home</a></li>
      <li><a href="#" class="MenuBarItemSubmenu">Services</a>
        <ul>
          <li><a href="#" class="MenuBarItemSubmenu">Wellness Care</a>
            <ul>
              <li><a href="#">Puppies & Kittens</a></li>
              <li><a href="#">Vaccinations</a></li>
              <li><a href="#">Parasite Prevention</a></li>
              <li><a href="#">Senior Pet Care</a></li>
            </ul>
          </li>
          <li><a href="#">Exotics</a></li>
          <li><a href="#">General Surgery</a></li>
          <li><a href="#">Dental Care</a></li>
          <li><a href="#">Spay & Neuter</a></li>
          <li><a href="#">Pain Management</a></li>
          <li><a href="#">Boarding</a></li>
          <li><a href="#">Microchipping</a></li>
          <li><a href="#">End of Life Care</a></li>
        </ul>
      </li>
      <li><a class="MenuBarItemSubmenu" href="#">About Us</a>
        <ul>
          <li><a href="#">Doctors</a></li>
          <li><a href="#">Staff</a></li>
          <li><a href="#">Tour</a></li>
        </ul>
      </li>
      <li><a href="#" class="MenuBarItemSubmenu">Admissions</a>
        <ul>
          <li><a href="#">Appointments</a></li>
          <li><a href="#">Boarding Reservations</a></li>
          <li><a href="#">New Clients</a></li>
          <li><a href="#">Accepted Payment</a></li>
        </ul>
      </li>
      <li><a href="#">Rx Refills</a></li>
      <li><a href="#">Pet Gallery</a></li>
      <li><a href="#">Pet Resources</a></li>
      <li><a href="#">Community Involvement</a></li>
      <li><a href="#">News</a></li>
      <li><a href="#" class="MenuBarItemSubmenu">Contact Us</a>
        <ul>
          <li><a href="#">Map</a></li>
          <li><a href="#">Hours</a></li>
          <li><a href="#">Email</a></li>
          <li><a href="#">Comments</a></li>
        </ul>
      </li>
    </ul>
</div>
<div id="mainContent">
    <div id="target">
      <div id="bullseye"></div>
      <div id="afterhours">After Hours Emergencies</div>
    </div>
    <h1 id="pageID">Our Mission</h1>
    <p>Our mission is to provide your pets with quality veterinary care in a compassionate and caring environment and to provide our pet owners with the information they need to enjoy life with their pets to the fullest.<br />
      A veterinary hospital serving the Lakeland, Florida community since 1993.</p>
    <img src="_images/hospfrontcynthia_edited-1-3.jpg" width="320" height="213" alt="hospital" />
    <h2>h2 sample</h2>
    <h3 id="mainarticle">h3 sample</h3>
    <p> </p>
    <p>this is a paragraph. This paragraph 2 in the main article in main content. Descendent selectors make up 90% of CSS styles. </p>
</div>
<div id="sidebar"></div>
<div id="footer">
    <div class="footer" id="footerNav">
      <h1 >Thompson Animal Hospital</h1>
      <p>6615 S. Florida Ave</p>
      <p> Lakeland, Florida 33813 </p>
      <p>(863)648-4886</p>
      <h1>Map & Directions    ׀     Email Us </h1>
      <h2><strong> Monday – Friday </strong></h2>
      <p>8 am – 5 pm </p>
      <h2><strong>Saturday </strong></h2>
      <p>8:30 – 12 noon </p>
      <h2><strong>Sunday </strong></h2>
      <p>Closed </p>
      <p></p>
    </div>
    <div id="footerNav2">Content for id "footerNav2" Goes Here</div>
</div>
<script type="text/javascript">
var MenuBar1 = new Spry.Widget.MenuBar("MenuBar1", {imgRight:"SpryAssets/SpryMenuBarRightHover.gif"});
</script>
</div>
</body>
</html>
my main.css
a {
color: #3366CC;
text-decoration: none
/*^1-----------------global constants-----------*/
html, body {
margin: 0px;
padding: 0px;
h1, h2, h3, h4, h5, p, address, blockquote, div, ul, li {
margin: 0;
padding: 0;
p {
color: #333;
line-height: 1.8;
margin-bottom: 1em;
a:link, a:visited {
color: #FFC559;
text-decoration: none;
a:hover, a:active {
color: #F60;
border-bottom: 1px dashed #F60;
body {
background: #FC6 url(../_images/grad3.gif) repeat-x;
text-align: center;
margin-top: 25px;
font-family: Georgia,
             Palatino,
             "Palatino Linotype",
             Times,
             "Times New Roman",
             serif;
font-size: 100%;
line-height: 2em;
h1,h2,h3 {
clear: both;
#wrapper {
background: #fff;
width: 930px;
text-align: left;
margin-top: 0px;
margin-right: auto;
margin-left: auto;
position: relative;
#target {
height: 40px;
width: 200px;
left: 5px;
float: right;
padding-right: 10px;
padding-left: 5px;
font-family: Georgia, "Palatino Linotype", "Times New Roman", serif;
font-size: 0.8em;
font-weight: normal;
color: #C03;
#header {
background: url(../_images/TAH_logo_web200x126.jpg);
height: 132px;
width: 206px;
position: absolute;
left: 3px;
top: 3px;
#bullseye {
background: #FFF url(../_images/target.gif) no-repeat;
float: left;
height: 26px;
width: 26px;
margin-top: 5px;
padding: 3px;
overflow:hidden
#afterhours {
margin-left: 38px;
padding: 3px;
/*----- color guide -----
#FFC559   BUBBLES ORANGE
#9CC2E2 LESTER BLUE
#BCBFC2 GRAY
#C00           RED
#69C            darker than lester blue                */
h1 {
font-family: Georgia,
             Palatino,
             "Palatino Linotype",
             Times,
             "Times New Roman",
             serif;
font-size: 1.2em;
line-height: 1.8em;
font-weight: bold;
color: #69C;
margin-bottom: 0.4em
h2 {font-family: Georgia,
             Palatino,
             "Palatino Linotype",
             Times,
             "Times New Roman",
             serif;
font-size: 1.6em;
color: #BCBFC2;
font-weight: normal;
margin: 1.2em 0 1em;
h3 {
font-family: Georgia,
             Palatino,
             "Palatino Linotype",
             Times,
             "Times New Roman",
             serif;
font-size: 1.3em;
color: #666;
font-weight: normal;
margin: 1.2em 0 0.5em;
h4 {
color: #000000
#mainNav {
background: #fff;
float: left;
margin-top: 150px;
width: 200px;
#mainContent {
background: #fff;
width: 670px;
float: right;
margin-bottom: 45px;
padding-right: 25px;
margin-top: 0px;
#mainContent h1 {
font-family: Georgia,
             Palatino,
             "Palatino Linotype",
             Times,
             "Times New Roman",
             serif;
font-size: 1.8em;
margin-bottom: 0.4em;
font-weight: bold;
clear: both;
#mainContent h1#pageID {
font-size: 1.4em;
font-weight: bold;
margin-top: 46px;
padding-bottom: 0.25em;
border-bottom: 2px solid #69C;
#mainContent p {
font-family: Georgia, "Palatino Linotype", "Times New Roman", serif;
font-size: 1em;
margin-bottom: 1em;
#mainContent h2 {
font-family: Georgia, "Palatino Linotype", "Times New Roman", serif;
font-size: 1.6em;
line-height: 1.4;
color: #999;
margin-bottom: 1em;
margin-top: 1.2em;
#mainContent h3 {
font-family: Georgia, "Palatino Linotype", "Times New Roman", serif;
font-size: 1.3em;
line-height: 1.2;
color: #999;
margin: 1.25em 0 0.5em;
table {
color: #FFFFFF
td, th {
font-family: Georgia,
             Palatino,
             "Palatino Linotype",
             Times,
             "Times New Roman",
             serif;
font-size: 1em;
line-height: 2em;
color: #333333
textarea {
font-family: Georgia,
             Palatino,
             "Palatino Linotype",
             Times,
             "Times New Roman",
             serif;
font-size: 1em
ul {
font-family: Georgia,
             Palatino,
             "Palatino Linotype",
             Times,
             "Times New Roman",
             serif;
font-size: 1em;
list-style-type: square;
list-style-position: outside
.BulletBackgroundColor {
color: #FFFFFF
.DataColor {
color: #DEDECA
.footer {
font-family: Georgia,
             Palatino,
             "Palatino Linotype",
             Times,
             "Times New Roman",
             serif;
font-size: 1.167em;
font-weight: bold;
line-height: 1.83em;
color: #333333;
background-color: #CCCCCC;
overflow: hidden;
.FormBackgroundColor {
color: #CCCCCC
.ImageTitleColor {
color: #CCCCCC
.LabelColor {
color: #CCCCCC
.ListColorEven {
color: #CCCCCC
.ListFooterColor {
color: #333333
.ListHeaderColor {
color: #333333
.ListColorOdd {
color: #DEDECA
.ListTitleColor {
color: #CCCCCC
.NavigationBackgroundColor {
color: #666666
.NavigationColor {
color: #CCCCCC
.NewsDataColor {
color: #DEDECA
#sidebar {
background: #FCC;
width: 200px;
clear: left;
float: left;
font-size: 0.9em;
line-height: 1.2;
#footer {
background: url(../_images/tahext.gif) no-repeat;
height: 525px;
width: 870px;
padding: 45px 30px 30px;
clear: both;
margin-top: 45px;
font-size: 0.7em;
overflow:hidden;
.StoryTitle {
color: #000000;
font-weight: bold
.StoryContentColor {
color: #000000
.TitleColor {
color: #000000
a:hover {
text-decoration: underline
tr.ListHeaderColor th {
text-align: left;
}.small {
font-size: 85%;
#pageID {
#footerNav {
margin: 0px;
width: 210px;
background: #FC6;
float: left;
#footer #footerNav p {
text-align: left;
line-height: 0.5px;
color: #666;
font-weight: normal;
#footer #footerNav h1 {
font-size: 1em;
line-height: 1.8em;
font-weight: bold;
color: #369;
font-variant: normal;
overflow: hidden;
#footer #footerNav h2 {
color: #666;
font-size: 1em;
line-height: 0.5em;
font-weight: normal;
#footerNav2 {
margin: 0px;
float: right;
height: 300px;
width: 200px;
clear: right;
top: auto;
right: auto;
a {
color: #3366CC;
text-decoration: none
/*^1-----------------global constants-----------*/
html, body {
margin: 0px;
padding: 0px;
h1, h2, h3, h4, h5, p, address, blockquote, div, ul, li {
margin: 0;
padding: 0;
p {
color: #333;
line-height: 1.8;
margin-bottom: 1em;
a:link, a:visited {
color: #FFC559;
text-decoration: none;
a:hover, a:active {
color: #F60;
border-bottom: 1px dashed #F60;
body {
background: #FC6 url(../_images/grad3.gif) repeat-x;
text-align: center;
margin-top: 25px;
font-family: Georgia,
             Palatino,
             "Palatino Linotype",
             Times,
             "Times New Roman",
             serif;
font-size: 100%;
line-height: 2em;
h1,h2,h3 {
clear: both;
#wrapper {
background: #fff;
width: 930px;
text-align: left;
margin-top: 0px;
margin-right: auto;
margin-left: auto;
position: relative;
#target {
height: 40px;
width: 200px;
left: 5px;
float: right;
padding-right: 10px;
padding-left: 5px;
font-family: Georgia, "Palatino Linotype", "Times New Roman", serif;
font-size: 0.8em;
font-weight: normal;
color: #C03;
#header {
background: url(../_images/TAH_logo_web200x126.jpg);
height: 132px;
width: 206px;
position: absolute;
left: 3px;
top: 3px;
#bullseye {
background: #FFF url(../_images/target.gif) no-repeat;
float: left;
height: 26px;
width: 26px;
margin-top: 5px;
padding: 3px;
overflow:hidden
#afterhours {
margin-left: 38px;
padding: 3px;
/*----- color guide -----
#FFC559   BUBBLES ORANGE
#9CC2E2 LESTER BLUE
#BCBFC2 GRAY
#C00           RED
#69C            darker than lester blue                */
h1 {
font-family: Georgia,
             Palatino,
             "Palatino Linotype",
             Times,
             "Times New Roman",
             serif;
font-size: 1.2em;
line-height: 1.8em;
font-weight: bold;
color: #69C;
margin-bottom: 0.4em
h2 {font-family: Georgia,
             Palatino,
             "Palatino Linotype",
             Times,
             "Times New Roman",
             serif;
font-size: 1.6em;
color: #BCBFC2;
font-weight: normal;
margin: 1.2em 0 1em;
h3 {
font-family: Georgia,
             Palatino,
             "Palatino Linotype",
             Times,
             "Times New Roman",
             serif;
font-size: 1.3em;
color: #666;
font-weight: normal;
margin: 1.2em 0 0.5em;
h4 {
color: #000000
#mainNav {
background: #fff;
float: left;
margin-top: 150px;
width: 200px;
#mainContent {
background: #fff;
width: 670px;
float: right;
margin-bottom: 45px;
padding-right: 25px;
margin-top: 0px;
#mainContent h1 {
font-family: Georgia,
             Palatino,
             "Palatino Linotype",
             Times,
             "Times New Roman",
             serif;
font-size: 1.8em;
margin-bottom: 0.4em;
font-weight: bold;
clear: both;
#mainContent h1#pageID {
font-size: 1.4em;
font-weight: bold;
margin-top: 46px;
padding-bottom: 0.25em;
border-bottom: 2px solid #69C;
#mainContent p {
font-family: Georgia, "Palatino Linotype", "Times New Roman", serif;
font-size: 1em;
margin-bottom: 1em;
#mainContent h2 {
font-family: Georgia, "Palatino Linotype", "Times New Roman", serif;
font-size: 1.6em;
line-height: 1.4;
color: #999;
margin-bottom: 1em;
margin-top: 1.2em;
#mainContent h3 {
font-family: Georgia, "Palatino Linotype", "Times New Roman", serif;
font-size: 1.3em;
line-height: 1.2;
color: #999;
margin: 1.25em 0 0.5em;
table {
color: #FFFFFF
td, th {
font-family: Georgia,
             Palatino,
             "Palatino Linotype",
             Times,
             "Times New Roman",
             serif;
font-size: 1em;
line-height: 2em;
color: #333333
textarea {
font-family: Georgia,
             Palatino,
             "Palatino Linotype",
             Times,
             "Times New Roman",
             serif;
font-size: 1em
ul {
font-family: Georgia,
             Palatino,
             "Palatino Linotype",
             Times,
             "Times New Roman",
             serif;
font-size: 1em;
list-style-type: square;
list-style-position: outside
.BulletBackgroundColor {
color: #FFFFFF
.DataColor {
color: #DEDECA
.footer {
font-family: Georgia,
             Palatino,
             "Palatino Linotype",
             Times,
             "Times New Roman",
             serif;
font-size: 1.167em;
font-weight: bold;
line-height: 1.83em;
color: #333333;
background-color: #CCCCCC;
overflow: hidden;
.FormBackgroundColor {
color: #CCCCCC
.ImageTitleColor {
color: #CCCCCC
.LabelColor {
color: #CCCCCC
.ListColorEven {
color: #CCCCCC
.ListFooterColor {
color: #333333
.ListHeaderColor {
color: #333333
.ListColorOdd {
color: #DEDECA
.ListTitleColor {
color: #CCCCCC
.NavigationBackgroundColor {
color: #666666
.NavigationColor {
color: #CCCCCC
.NewsDataColor {
color: #DEDECA
#sidebar {
background: #FCC;
width: 200px;
clear: left;
float: left;
font-size: 0.9em;
line-height: 1.2;
#footer {
background: url(../_images/tahext.gif) no-repeat;
height: 525px;
width: 870px;
padding: 45px 30px 30px;
clear: both;
margin-top: 45px;
font-size: 0.7em;
overflow:hidden;
.StoryTitle {
color: #000000;
font-weight: bold
.StoryContentColor {
color: #000000
.TitleColor {
color: #000000
a:hover {
text-decoration: underline
tr.ListHeaderColor th {
text-align: left;
}.small {
font-size: 85%;
#pageID {
#footerNav {
margin: 0px;
width: 210px;
background: #FC6;
float: left;
#footer #footerNav p {
text-align: left;
line-height: 0.5px;
color: #666;
font-weight: normal;
#footer #footerNav h1 {
font-size: 1em;
line-height: 1.8em;
font-weight: bold;
color: #369;
font-variant: normal;
overflow: hidden;
#footer #footerNav h2 {
color: #666;
font-size: 1em;
line-height: 0.5em;
font-weight: normal;
#footerNav2 {
margin: 0px;
float: right;
height: 300px;
width: 200px;
clear: right;
top: auto;
right: auto;
a {
color: #3366CC;
text-decoration: none
/*^1-----------------global constants-----------*/
html, body {
margin: 0px;
padding: 0px;
h1, h2, h3, h4, h5, p, address, blockquote, div, ul, li {
margin: 0;
padding: 0;
p {
color: #333;
line-height: 1.8;
margin-bottom: 1em;
a:link, a:visited {
color: #FFC559;
text-decoration: none;
a:hover, a:active {
color: #F60;
border-bottom: 1px dashed #F60;
body {
background: #FC6 url(../_images/grad3.gif) repeat-x;
text-align: center;
margin-top: 25px;
font-family: Georgia,
             Palatino,
             "Palatino Linotype",
             Times,
             "Times New Roman",
             serif;
font-size: 100%;
line-height: 2em;
h1,h2,h3 {
clear: both;
#wrapper {
background: #fff;
width: 930px;
text-align: left;
margin-top: 0px;
margin-right: auto;
margin-left: auto;
position: relative;
#target {
height: 40px;
width: 200px;
left: 5px;
float: right;
padding-right: 10px;
padding-left: 5px;
font-family: Georgia, "Palatino Linotype", "Times New Roman", serif;
font-size: 0.8em;
font-weight: normal;
color: #C03;
#header {
background: url(../_images/TAH_logo_web200x126.jpg);
height: 132px;
width: 206px;
position: absolute;
left: 3px;
top: 3px;
#bullseye {
background: #FFF url(../_images/target.gif) no-repeat;
float: left;
height: 26px;
width: 26px;
margin-top: 5px;
padding: 3px;
overflow:hidden
#afterhours {
margin-left: 38px;
padding: 3px;
/*----- color guide -----
#FFC559   BUBBLES ORANGE
#9CC2E2 LESTER BLUE
#BCBFC2 GRAY
#C00           RED
#69C            darker than lester blue                */
h1 {
font-family: Georgia,
             Palatino,
             "Palatino Linotype",
             Times,
             "Times New Roman",
             serif;
font-size: 1.2em;
line-height: 1.8em;
font-weight: bold;
color: #69C;
margin-bottom: 0.4em
h2 {font-family: Georgia,
             Palatino,
             "Palatino Linotype",
             Times,
             "Times New Roman",
             serif;
font-size: 1.6em;
color: #BCBFC2;
font-weight: normal;
margin: 1.2em 0 1em;
h3 {
font-family: Georgia,
             Palatino,
             "Palatino Linotype",
             Times,
             "Times New Roman",
             serif;
font-size: 1.3em;
color: #666;
font-weight: normal;
margin: 1.2em 0 0.5em;
h4 {
color: #000000
#mainNav {
background: #fff;
float: left;
margin-top: 150px;
width: 200px;
#mainContent {
background: #fff;
width: 670px;
float: right;
margin-bottom: 45px;
padding-right: 25px;
margin-top: 0px;
#mainContent h1 {
font-family: Georgia,
             Palatino,
             "Palatino Linotype",
             Times,
             "Times New Roman",
             serif;
font-size: 1.8em;
margin-bottom: 0.4em;
font-weight: bold;
clear: both;
#mainContent h1#pageID {
font-size: 1.4em;
font-weight: bold;
margin-top: 46px;
padding-bottom: 0.25em;
border-bottom: 2px solid #69C;
#mainContent p {
font-family: Georgia, "Palatino Linotype", "Times New Roman", serif;
font-size: 1em;
margin-bottom: 1em;
#mainContent h2 {
font-family: Georgia, "Palatino Linotype", "Times New Roman", serif;
font-size: 1.6em;
line-height: 1.4;
color: #999;
margin-bottom: 1em;
margin-top: 1.2em;
#mainContent h3 {
font-family: Georgia, "Palatino Linotype", "Times New Roman", serif;
font-size: 1.3em;
line-height: 1.2;
color: #999;
margin: 1.25em 0 0.5em;
table {
color: #FFFFFF
td, th {
font-family: Georgia,
             Palatino,
             "Palatino Linotype",
             Times,
             "Times New Roman",
             serif;
font-size: 1em;
line-height: 2em;
color: #333333
textarea {
font-family: Georgia,
             Palatino,
             "Palatino Linotype",
             Times,
             "Times New Roman",
             serif;
font-size: 1em
ul {
font-family: Georgia,
             Palatino,
             "Palatino Linotype",
             Times,
             "Times New Roman",
             serif;
font-size: 1em;
list-style-type: square;
list-style-position: outside
.BulletBackgroundColor {
color: #FFFFFF
.DataColor {
color: #DEDECA
.footer {
font-family: Georgia,
             Palatino,
             "Palatino Linotype",
             Times,
             "Times New Roman",
             serif;
font-size: 1.167em;
font-weight: bold;
line-height: 1.83em;
color: #333333;
background-color: #CCCCCC;
overflow: hidden;
.FormBackgroundColor {
color: #CCCCCC
.ImageTitleColor {
color: #CCCCCC
.LabelColor {
color: #CCCCCC
.ListColorEven {
color: #CCCCCC
.ListFooterColor {
color: #333333
.ListHeaderColor {
color: #333333
.ListColorOdd {
color: #DEDECA
.ListTitleColor {
color: #CCCCCC
.NavigationBackgroundColor {
color: #666666
.NavigationColor {
color: #CCCCCC
.NewsDataColor {
color: #DEDECA
#sidebar {
background: #FCC;
width: 200px;
clear: left;
float: left;
font-size: 0.9em;
line-height: 1.2;
#footer {
background: url(../_images/tahext.gif) no-repeat;
height: 525px;
width: 870px;
padding: 45px 30px 30px;
clear: both;
margin-top: 45px;
font-size: 0.7em;
overflow:hidden;
.StoryTitle {
color: #000000;
font-weight: bold
.StoryContentColor {
color: #000000
.TitleColor {
color: #000000
a:hover {
text-decoration: underline
tr.ListHeaderColor th {
text-align: left;
}.small {
font-size: 85%;
#pageID {
#footerNav {
margin: 0px;
width: 210px;
background: #FC6;
float: left;
#footer #footerNav p {
text-align: left;
line-height: 0.5px;
color: #666;
font-weight: normal;
#footer #footerNav h1 {
font-size: 1em;
line-height: 1.8em;
font-weight: bold;
color: #369;
font-variant: normal;
overflow: hidden;
#footer #footerNav h2 {
color: #666;
font-size: 1em;
line-height: 0.5em;
font-weight: normal;
#footerNav2 {
margin: 0px;
float: right;
height: 300px;
width: 200px;
clear: right;
top: auto;
right: auto;

Widget menu not displaying correctly

Hi,
I've created a web site and uploaded it to the FTP server to check it works OK and I've found the home page menu doesn't display correctly, but every other page is OK.
The drop down 'sub-menu' is getting clogged up in it's layout.
See here:
all the other pages display correctly and look like this:
Because the menu is generated by Muse as a widget, (I've just edited colours etc) why should 1 page display differently to the others?
I have this in the Master file, so I'm not making duplicate menus on each seperate page... the one widget serves all the pages.
Any ideas?
Thanks a lot.

If you have inserted the menu on the Master page, then ideally it should appear even and remain unselectable/uneditable on all of the content pages.
Does the menu appear distorted in Design mode for the homepage too or only when you preview in browser/after publish?
I believe you're using the "All Pages" menu type and by looking at the screenshots, it appears that the Products menu item is overlapping the Education menu item. Did you try making a copy or delete the menu and re-insert in Master page? Can you do a Select All on the Home page and check if you don't have an identical but mis-aligned manual menu overlapping the original menu?
If the problem persists, can you share a link to the website for us to have a look?
Thanks,
Vinayak

XMP doesn't display proper info in Photoshop CS2 for Mac.

Dear List members:
I have just recently installed Creative Suite CS2 and begun to explore the functionality of XMP. After purchasing Bruce Fraser's book on Camera Raw for CS2, I downloaded Metalab (Pound Hill Software) and created my first custom XMP panel that can be seen under the file info in Photoshop when an image (digital photo) is open.
The problem is that I noticed a few odd things and began to question myself if there is some kind of bug or a problem with my installation of CS2.
1. The window that opens under the file info command has several categories of information on the left to be chosen from, in the following order:
(1)Description, (2)Camera Data 1, (3)Camera Data 2, (4)Categories, (5)History, (6)IPTC Contact, (7)IPTC Content, (8)IPTC Image, (9)IPTC Status, (10)Adobe Stock Photos, (11)Origin, (12)Advanced
The Camera Data 1 option when selected opens a panel in the file info window that seems to contain all the information it is supposed to contain. The Camera Data 2 panel, on the other hand, doesn't display any information at all. Although the fields are there, they are empty. The fields are:
(1)Pixel Dimension X and Y, (2)Orientation, (3)Resolution X and Y, (4)Resolution Unit, (5)Compressed Bits per Pixel, (6)Color Space, (7)Light Source, (8)File Source.
All these fields are empty but when looking at the same file under Bridge the information is there, displayed under the metadata menu.
This is something I noticed "before" installing Metalab so I know it is not a compatibility issue generated by the installation of the software.
After installing CS2 I noticed that CS1 remained installed in my system. The version I purchased of CS2 is the upgrade one. Since I have no use for CS1 as I am now totally converted to CS2, I would like to uninstall CS1. The following are some of the questions I have:
1. How can I uninstall CS1 without causing any problems to my installation of CS1 ? Is there an uninstall utility with the software or will I have to uninstall the entire package manually ?
2. My G5 came with only one internal 160 GB drive where I originally installed CS1. I then purchased another internal 400 GB HD and copied the original drive onto it. This week I am going to replace the original 160 GB drive with a second 400 GB drive so that I can do regular "mirror image" back-ups between the two drives. Shold I expect any problems as I remove the drive where I originally installed CS1 ? Since I used disk utility to "copy" the 160 GB drive onto the 400 GB drive, my understanding it that any Adobe software key or authorization was also transferred to the drive. Is this right ? In case it hasn't, how can I transfer this information so that after I remove the 160 GB drive I will not experience any problems when trying to run CS2 ?
3. How can I fix the problem with the Camera Data 2 panel under the file info window and command ? I noticed that the folder that is supposed to hold the Custom File Info Panels (HD>Library>Application Support>Adobe>XMP>Custom File Info Panels) has files for CS1 and CS2. Could this be a problem ? There many more files with .dat extenson than there are with the .txt extension. Bruce Fraser specifically says that the ones with the .txt extension are the ones that hold the XMP templates for information related to the image files. The files I have in this folder with the .txt are:
(1)Camera1_CS2.txt , (2)Camera1.txt , (3)Camera2_CS2.txt , (4)Camera2.txt , (5)Categories.txt , (6)History.txt , (7)IPTC_Contact.txt , (8)IPTC_Content.txt , (9)IPTC_Image.txt , (10)IPTC_Status.txt , (11)StockPhotoInfo.txt
The only ones that have two separate files one each for CS1 ad CS2 are Camera 1 and Camera 2. Camera 2 seems to be the only that is now non-functional. What should I expect to happen if I were to manually uninstall the ones that relate to CS1 ? Could that cause any problems ?
My apologies for the long post but I didn't really know how to make it shorter.

The Photoshop and/or Bridge forums would be more likely places to get answers to your questions. This forum is inhabited more by programmer types interested in implementing the XMP specification in applications we write.
I'd expect CS2 to ignore CS1 panels so I doubt that's the issue. Panels don't interfere with each other--they just offer different views of the data. In any case, move the extra panels to your desktop and see what happens.
As far as I know, all you need to do on the Mac is drag the CS1 application folder to the trash to uninstall it.

IE doesn't display navigation menus or slideshows correctly

I'm fairly new to Muse and was pretty excited for it as an alternative to using Dreamweaver all of the time but now I wish it would come with a disclaimer that the sites created with it are not compatible across all browsers.
I have a simple horizontal navigation menu that won't work in IE but appears fine in Firefox and Chrome. The slideshows on the homepage as well as the project pages doesn't display correctly either. As you can imagine, the client is none too happy. Also, the Google map widget does not work correctly in IE either.
Are there known issues with IE? Are there any fixes short of redoing the site in another program?
The URL is: www.ethosthree.com
Any help or input would be greatly appreciated. Thanks.

We are experiencing similar issues. We have used the slideshow widget in Muse on several pages and it fails to work under IE 10 or IE 11, but works fine on all current versions of Firefox, Chrome, and Safari.

FCP X doesn't display iMovie clips correctly in Event Library

I have 10 years of clips that are setup by year/date in iMovie. Although I had imported most of the media in 2009, iMovie seems smart enough to read the actual file metadata and find the media recording date, which is prior to the import date. As a result, the clips are diplayed correctly in iMovie Event by Year/Month of actual recording.
However, the Event Library in FCP X doesn't do that at all and lists the events by "Content Creation" date, which is simply reads from the system file date, and NOT the recording date that is embedded into the file.
Bottom line is that Event Library is semi-useless as it doesn't all at display my clisp in the correct order, unlike iMovie that was doing it correctly.
Any ideas?

I went into Finder and discovered that FCP X created a directory structure where the files are in the correct Year/Month directory structure (as an exact mirror directory structure as the iMovie one), so it's even more weird that the Event Library doesn't display the events correctly???

Updated to 10.4.9 and now weather widget doesn't work-what to do?

Hello-
Just updated to 10.4.9 tonight and for the first time since I bought this computer in August, the weather widget doesn't work.
Would anyone happen to know what I could do to get this to work. I am connected to the internet, I can access the accuweather.com that I think this widget connects to, I restarted and reset PRAM (not even sure if that has anything to do with it).
I just don't even know where to go from here to troubleshoot. Any suggestions would be appreciated... Thanks.

Just for the record... There is quite a bit of discussion about widgets. I only use the dictionary and iStat. I use WeatherPop in the taskbar, which resides in the taskbar...
It did it again this morning. I let it boot all the way, and then I went into system preferences to find the resolution that the display was using. It was 1400x1050. But there was a second display preferences window open. Basically... The computer was "mirroring" to a second non-existent monitor. I ran through the "detect displays" and it got rid of the second setting.
I've never had a second monitor hooked to the machine, and I've never messed with the display settings, other than to change wallpaper. I'm not sure how or why it turned on, but I think it's off now... Weird that it only did it every now and then.
Steve

NASA widget doesn't display content

Similar Messages

Maybe you are looking for