6D Live view sensor issue?

Taking pictures in Live view mode makes a blue/green line in the bottom of my pictures, just one or two pixels high. Some of the raw converters remove this line automatically. Darktable didn't until I noticed them. Luminance HDR doesn't remove the line. RawTherapee shows the line in preview mode before the whole image is loaded. Shotwell Photo Viewer shows the blue/green line.
I suppose all the software that I have used use dcraw, so it may be in dcraw the issue is and not in my 6D. But why then only in Live view mode?
You will be able to download the raw file in about 4 minutes from now at http://kameratrollet.se/allt/IMG_9515.CR2
Please check if the line is visible in your raw converter.
In Digital Photo Professional I can't see any line, but the height of the picture is 3647 px. In Luminance HDR I get the height of 3670 px. If I shoot an image normally not using Live view, I get the same height.
My Swedish blog
X100, 7D, 6D, 17-40/4L, 70-200/2,8L IS II, 17-55/2.8 IS, 24-105/4L, 85/1,8, 50/1,4, 24/1,4L II, Helios 58/2
Darktable, RawTherapee, Photomatix, Luminance HDR, GIMP 2.9.1.

It appears to me that some of the software you are using is adding a couple rows of pixels to the bottom of each image for some reason. Easy enough to fix, but sort of a nuisance.
Do you see the same thing happen in Canon's own softwares? Have you checked for updates and/or glitch reports for the software you are using?
Alan Myers
San Jose, Calif., USA
"Walk softly and carry a big lens."
GEAR: 5DII, 7D(x2), 50D(x3), some other cameras, various lenses & accessories
FLICKR & PRINTROOM 

Similar Messages

  • How do I use Dreamweaver CC 2014.1 Live View to copy complex formatted text into web page?

    Since Design View has been removed from Fluid Grid Layouts, and could be removed completely in next upgrade, I cannot use Live View to place complex text into my web pages.
    Our business requires the listing of complex job descriptions on our web pages.  Design View worked fine, Live View does not. Both examples are noted below.
    Using Design View the web page rendered this way:
    Research & Analytics Director
    Position# 2469
    Location:  Midwest
    Education Requirements:  MS degree in Mathematics, Statistics, Economics, Engineering, Actuarial Science or related field or equivalent designation, such as FCAS.
    Other Requirements:  Include:
    Job Competencies:
    Achieve Results.
    Be Accountable.
    Lead Change.
    Lead Corp Vision & Strategy.
    Lead People.
    Maximize Customer Experience.
    Specialized Knowledge and Skills Requirements:
    Demonstrated ability to develop strategic partnerships.
    Demonstrated ability to identify potential issues, and to proactively work to the mitigation of those issues.
    Demonstrated experience communicating business implications of complex data relationships and results of statistical models to multiple business partners.
    Demonstrated experience formulating, approaching, and solving problems in massive, complex datasets.
    Demonstrated experience in public speaking and use of appropriate presentation skills.
    Demonstrated experience interfacing with business clients and driving solution discussions with both IT and business stakeholders.
    Demonstrated experience performing advanced statistical analysis, including generalized linear models, decision trees, neural networks, etc., to discover business insights and develop predictive models.
    Demonstrated experience with statistical and modeling software tools, such as SAS or R.
    Demonstrated management or leadership experience.
    Solid knowledge and understanding of mathematical modeling and research.
    Salary Range:  $146,300 to $243,800+
    Description:  This position is responsible for oversight and strategic direction of advanced analytics, including predictive modeling, that drive business performance consistent with company goals and objectives.  Works with internal business partners to understand and validate scope of advanced analytics projects and directs projects teams to support those projects.  Collaborates within the division and cross-divisionally to develop and integrate statistical models into various processes. Oversees research of new and innovative analytic tools and techniques.  Monitors industry trends in analytics and investigates new concepts, ideas, and data sources.  Primary accountabilities include:
    Advanced Analytics Oversight (40%):
    Provides oversight and direction for the design, development, and evaluation of predictive models and advanced algorithms that lead to business solutions.
    Directs the most complex and vital analytics work critical to the organization.
    Oversees advanced exploratory analytics that produce a variety of business solutions.
    Conducts peer review on technical aspects of projects.
    Partners with business areas (Commercial Lab, EDM, IS, etc.) on data innovation.
    Portfolio Strategy and Management (25%):
    Collaborates with Strategic Data & Analytics Vice President as well as business partners internal and external to the division to develop and execute advanced analytics strategy and project portfolio.
    Leverages business acumen and domain expertise in directing advanced analytics strategy and application.
    Aligns plans to divisional and corporate objectives/goals and integrates within the corporate planning cycle.
    Monitors and analyzes advanced analytics resources. Assesses needs and appropriately allocates resources to priorities and initiatives.
    Works with divisional management to improve work processes that impact work environment and divisional resources.
    Provides overall portfolio/project management oversight and direction for a variety of advanced analytics project.  Oversees measurement, monitoring and reporting of project progress and resource utilization.  Manages project resources to ensure timely delivery of projects consistent with divisional goals and objectives.
    Coordinates with business partners (Analytics Strategy, etc.) on knowledge management and participates in business area meetings. Maintains holistic view of the business.  Ensures rapid delivery and execution of insights derived from data analytics into the organization.
    Analytic Tools and Techniques Research Oversight (15%):
    Sets the vision for the use of new and innovative tools and technology.
    Maintains and fosters an industry awareness of new developments in analytics techniques and tools, and ensures quick execution in their use within the department.
    Interfaces with Enterprise Data Management (EDM) and Information Services (IS) on evolving technological and data needs and requirements.
    Strategies Linked to the Division's Business Goals/Results (10%):
    Establishes, communicates, and implements departmental plans, objectives, and strategies.
    Participates as a member of the Management Team.
    Maintains an active awareness of our Client's business environments, corporate culture, and structure to support key decision-making.
    Management/Leadership for Department or Unit (10%):
    Manages direct reports, systems, and projects to achieve department/unit goals in accordance with Company policies and practices.
    Prepares and analyzes department/unit plans and reports.
    Provides leadership by exhibiting influence and expertise, thus affecting the results of the operating area.
    Creates an effective work environment by developing a common vision, setting clear objectives, expecting teamwork, recognizing outstanding performance, and maintaining open communications.
    Develops staff through coaching, providing performance feedback, providing effective performance assessments, and establishing performance & development plans.
    Using Live View the web page rendered this way:
    Research & Analytics Director Position# 2469 Location: Midwest Education Requirements: MS degree in Mathematics, Statistics, Economics, Engineering, Actuarial Science or related field or equivalent designation, such as FCAS. Other Requirements: Include: • Job Competencies: o Achieve Results. o Be Accountable. o Lead Change. o Lead Corp Vision & Strategy. o Lead People. o Maximize Customer Experience. • Specialized Knowledge and Skills Requirements: o Demonstrated ability to develop strategic partnerships. o Demonstrated ability to identify potential issues, and to proactively work to the mitigation of those issues. o Demonstrated experience communicating business implications of complex data relationships and results of statistical models to multiple business partners. o Demonstrated experience formulating, approaching, and solving problems in massive, complex datasets. o Demonstrated experience in public speaking and use of appropriate presentation skills. o Demonstrated experience interfacing with business clients and driving solution discussions with both IT and business stakeholders. o Demonstrated experience performing advanced statistical analysis, including generalized linear models, decision trees, neural networks, etc., to discover business insights and develop predictive models. o Demonstrated experience with statistical and modeling software tools, such as SAS or R. o Demonstrated management or leadership experience. o Solid knowledge and understanding of mathematical modeling and research. Salary Range: $146,300 to $243,800+ Description: This position is responsible for oversight and strategic direction of advanced analytics, including predictive modeling, that drive business performance consistent with company goals and objectives. Works with internal business partners to understand and validate scope of advanced analytics projects and directs projects teams to support those projects. Collaborates within the division and cross-divisionally to develop and integrate statistical models into various processes. Oversees research of new and innovative analytic tools and techniques. Monitors industry trends in analytics and investigates new concepts, ideas, and data sources. Primary accountabilities include: • Advanced Analytics Oversight (40%): o Provides oversight and direction for the design, development, and evaluation of predictive models and advanced algorithms that lead to business solutions. o Directs the most complex and vital analytics work critical to the organization. o Oversees advanced exploratory analytics that produce a variety of business solutions. o Conducts peer review on technical aspects of projects. o Partners with business areas (Commercial Lab, EDM, IS, etc.) on data innovation. • Portfolio Strategy and Management (25%): o Collaborates with Strategic Data & Analytics Vice President as well as business partners internal and external to the division to develop and execute advanced analytics strategy and project portfolio. o Leverages business acumen and domain expertise in directing advanced analytics strategy and application. o Aligns plans to divisional and corporate objectives/goals and integrates within the corporate planning cycle. o Monitors and analyzes advanced analytics resources. Assesses needs and appropriately allocates resources to priorities and initiatives. o Works with divisional management to improve work processes that impact work environment and divisional resources. o Provides overall portfolio/project management oversight and direction for a variety of advanced analytics project. Oversees measurement, monitoring and reporting of project progress and resource utilization. Manages project resources to ensure timely delivery of projects consistent with divisional goals and objectives. o Coordinates with business partners (Analytics Strategy, etc.) on knowledge management and participates in business area meetings. Maintains holistic view of the business. Ensures rapid delivery and execution of insights derived from data analytics into the organization. • Analytic Tools and Techniques Research Oversight (15%): o Sets the vision for the use of new and innovative tools and technology. o Maintains and fosters an industry awareness of new developments in analytics techniques and tools, and ensures quick execution in their use within the department. o Interfaces with Enterprise Data Management (EDM) and Information Services (IS) on evolving technological and data needs and requirements. • Strategies Linked to the Division's Business Goals/Results (10%): o Establishes, communicates, and implements departmental plans, objectives, and strategies. o Participates as a member of the Management Team. o Maintains an active awareness of our Client's business environments, corporate culture, and structure to support key decision-making. • Management/Leadership for Department or Unit (10%): o Manages direct reports, systems, and projects to achieve department/unit goals in accordance with Company policies and practices. o Prepares and analyzes department/unit plans and reports. o Provides leadership by exhibiting influence and expertise, thus affecting the results of the operating area. o Creates an effective work environment by developing a common vision, setting clear objectives, expecting teamwork, recognizing outstanding performance, and maintaining open communications. o Develops staff through coaching, providing performance feedback, providing effective performance assessments, and establishing performance & development plans.
    Obviously, as seen above, I'm doing something wrong or Live View does not do all the functions that Design View use to do.  I realize I can still access Design View in non-Fluid Grid Layout documents and that is my current work-around.  I copy from my Word file into Design View available in non-Fluid, then copy that code into my Fluid Grid Layout document, not real efficient use of my time.  And, even that work-around may not be available after the next upgrade.

    Hans thank you for your reply and attention to this matter.  Moreover, with your steeped expertise I do not, in any fashion, intend to be flippant or capricious. 
    However, I do not believe the reply is on point since I'm not discussing the insertion of an HTML tag/element; but rather, the placing of complex formatted text into my various web pages.
    Design View and  2014.1 Live View seem to serve different functions.  That is, Design View, for us, serves as a highly sophisticated HTML5 code generator that allows us to properly display complex formatted text that originally is created as a Word docx file.  As I noted in my original post, the complex formatted text from the Word file is then pasted into Design View and thus properly renders on the web page.  I invite you to try this yourself.  Simply copy my properly formatted text in my original post (that can be found at "Using Design View the web page rendered this way:") to a Word file, and it will retain the complex formatting, then copy that Word file text to both Design View and  2014.1 Live View files.  Please apprise me of your results.
    Discussion has been had in at least two separate threads on the Design View disappearance in Fluid Grid.  In https://forums.adobe.com/thread/1597260 staff member Lalita wrote "It would be helpful for us if you list the issues you are seeing with fluid grid live view editing."  And in https://forums.adobe.com/message/6807088#6807088 staff member Subhadeep wrote "If you can list down the workflows you are trying while editing in Live View & the issues you are facing in doing so, it will help us understand what is amiss & suggest alternative workflows to do the same."  I believe I've pointed out issues when attempting to use Live View for functions or work flow that customarily had been done in Design View.
    Being a CC subscriber, if someone can provide me with a workflow using other additional Adobe products to get my complex formatted text from Word ultimately to my Dreamweaver web page, be it an image insert or whatever, I would take the suggestions.
    The difference in the coding of my example in my original post is as follows.
    Code when using Design View is:
    <p><strong>Research &amp; Analytics Director</strong><br>
      <strong>Position# 2469</strong><br>
      <strong>Location:</strong>  Midwest<br>
      <strong>Education Requirements:</strong>  MS degree in Mathematics, Statistics,  Economics, Engineering, Actuarial Science or related field or equivalent  designation, such as FCAS.<br>
      <strong>Other Requirements:</strong>  Include:</p>
    <ul type="disc">
      <li>Job       Competencies:</li>
      <ul type="circle">
        <li>Achieve        Results.</li>
        <li>Be        Accountable.</li>
        <li>Lead        Change.</li>
        <li>Lead Corp        Vision &amp; Strategy.</li>
        <li>Lead        People.</li>
        <li>Maximize        Customer Experience.</li>
      </ul>
      <li>Specialized       Knowledge and Skills Requirements:</li>
      <ul type="circle">
        <li>Demonstrated        ability to develop strategic partnerships.</li>
        <li>Demonstrated        ability to identify potential issues, and to proactively work to the        mitigation of those issues.</li>
        <li>Demonstrated        experience communicating business implications of complex data        relationships and results of statistical models to multiple business        partners.</li>
        <li>Demonstrated        experience formulating, approaching, and solving problems in massive,        complex datasets.</li>
        <li>Demonstrated        experience in public speaking and use of appropriate presentation skills.</li>
        <li>Demonstrated        experience interfacing with business clients and driving solution        discussions with both IT and business stakeholders.</li>
        <li>Demonstrated        experience performing advanced statistical analysis, including        generalized linear models, decision trees, neural networks, etc., to        discover business insights and develop predictive models.</li>
        <li>Demonstrated        experience with statistical and modeling software tools, such as SAS or        R.</li>
        <li>Demonstrated        management or leadership experience.</li>
        <li>Solid        knowledge and understanding of mathematical modeling and research.</li>
      </ul>
    </ul>
    <p><strong>Salary Range:</strong>  $146,300 to  $243,800+<br>
      <strong>Description:</strong>  This position is  responsible for oversight and strategic direction of advanced analytics,  including predictive modeling, that drive business performance consistent with  company goals and objectives.  Works with internal business partners to  understand and validate scope of advanced analytics projects and directs  projects teams to support those projects.  Collaborates within the  division and cross-divisionally to develop and integrate statistical models into  various processes. Oversees research of new and innovative analytic tools and  techniques.  Monitors industry trends in analytics and investigates new  concepts, ideas, and data sources.  Primary accountabilities include:</p>
    <ul type="disc">
      <li>Advanced       Analytics Oversight (40%):</li>
      <ul type="circle">
        <li>Provides        oversight and direction for the design, development, and evaluation of        predictive models and advanced algorithms that lead to business        solutions.</li>
        <li>Directs        the most complex and vital analytics work critical to the organization.</li>
        <li>Oversees        advanced exploratory analytics that produce a variety of business        solutions.</li>
        <li>Conducts        peer review on technical aspects of projects.</li>
        <li>Partners        with business areas (Commercial Lab, EDM, IS, etc.) on data innovation.</li>
      </ul>
      <li>Portfolio       Strategy and Management (25%):</li>
      <ul type="circle">
        <li>Collaborates        with Strategic Data &amp; Analytics Vice President as well as business        partners internal and external to the division to develop and execute        advanced analytics strategy and project portfolio.</li>
        <li>Leverages        business acumen and domain expertise in directing advanced analytics        strategy and application.</li>
        <li>Aligns        plans to divisional and corporate objectives/goals and integrates within        the corporate planning cycle.</li>
        <li>Monitors        and analyzes advanced analytics resources. Assesses needs and        appropriately allocates resources to priorities and initiatives.</li>
        <li>Works        with divisional management to improve work processes that impact work        environment and divisional resources.</li>
        <li>Provides        overall portfolio/project management oversight and direction for a        variety of advanced analytics project.  Oversees measurement,        monitoring and reporting of project progress and resource        utilization.  Manages project resources to ensure timely delivery of        projects consistent with divisional goals and objectives.</li>
        <li>Coordinates        with business partners (Analytics Strategy, etc.) on knowledge management        and participates in business area meetings. Maintains holistic view of        the business.  Ensures rapid delivery and execution of insights        derived from data analytics into the organization.</li>
      </ul>
      <li>Analytic       Tools and Techniques Research Oversight (15%):</li>
      <ul type="circle">
        <li>Sets the        vision for the use of new and innovative tools and technology.</li>
        <li>Maintains        and fosters an industry awareness of new developments in analytics        techniques and tools, and ensures quick execution in their use within the        department.</li>
        <li>Interfaces        with Enterprise Data Management (EDM) and Information Services (IS) on        evolving technological and data needs and requirements.</li>
      </ul>
      <li>Strategies       Linked to the Division's Business Goals/Results (10%):</li>
      <ul type="circle">
        <li>Establishes,        communicates, and implements departmental plans, objectives, and        strategies.</li>
        <li>Participates        as a member of the Management Team.</li>
        <li>Maintains        an active awareness of our Client's business environments, corporate        culture, and structure to support key decision-making.</li>
      </ul>
      <li>Management/Leadership       for Department or Unit (10%):</li>
      <ul type="circle">
        <li>Manages        direct reports, systems, and projects to achieve department/unit goals in        accordance with Company policies and practices.</li>
        <li>Prepares        and analyzes department/unit plans and reports.</li>
        <li>Provides        leadership by exhibiting influence and expertise, thus affecting the        results of the operating area.</li>
        <li>Creates        an effective work environment by developing a common vision, setting        clear objectives, expecting teamwork, recognizing outstanding performance,        and maintaining open communications.</li>
        <li>Develops        staff through coaching, providing performance feedback, providing        effective performance assessments, and establishing performance &amp;        development plans.</li>
      </ul>
    </ul>
    Code when using Live View is:
      <div id="liveview" class="fluid">Research &amp; Analytics Director Position# 2469 Location: Midwest Education Requirements: MS degree in Mathematics, Statistics, Economics, Engineering, Actuarial Science or related field or equivalent designation, such as FCAS. Other Requirements: Include: • Job Competencies: o Achieve Results. o Be Accountable. o Lead Change. o Lead Corp Vision &amp; Strategy. o Lead People. o Maximize Customer Experience. • Specialized Knowledge and Skills Requirements: o Demonstrated ability to develop strategic partnerships. o Demonstrated ability to identify potential issues, and to proactively work to the mitigation of those issues. o Demonstrated experience communicating business implications of complex data relationships and results of statistical models to multiple business partners. o Demonstrated experience formulating, approaching, and solving problems in massive, complex datasets. o Demonstrated experience in public speaking and use of appropriate presentation skills. o Demonstrated experience interfacing with business clients and driving solution discussions with both IT and business stakeholders. o Demonstrated experience performing advanced statistical analysis, including generalized linear models, decision trees, neural networks, etc., to discover business insights and develop predictive models. o Demonstrated experience with statistical and modeling software tools, such as SAS or R. o Demonstrated management or leadership experience. o Solid knowledge and understanding of mathematical modeling and research. Salary Range: $146,300 to $243,800+ Description: This position is responsible for oversight and strategic direction of advanced analytics, including predictive modeling, that drive business performance consistent with company goals and objectives. Works with internal business partners to understand and validate scope of advanced analytics projects and directs projects teams to support those projects. Collaborates within the division and cross-divisionally to develop and integrate statistical models into various processes. Oversees research of new and innovative analytic tools and techniques. Monitors industry trends in analytics and investigates new concepts, ideas, and data sources. Primary accountabilities include: • Advanced Analytics Oversight (40%): o Provides oversight and direction for the design, development, and evaluation of predictive models and advanced algorithms that lead to business solutions. o Directs the most complex and vital analytics work critical to the organization. o Oversees advanced exploratory analytics that produce a variety of business solutions. o Conducts peer review on technical aspects of projects. o Partners with business areas (Commercial Lab, EDM, IS, etc.) on data innovation. • Portfolio Strategy and Management (25%): o Collaborates with Strategic Data &amp; Analytics Vice President as well as business partners internal and external to the division to develop and execute advanced analytics strategy and project portfolio. o Leverages business acumen and domain expertise in directing advanced analytics strategy and application. o Aligns plans to divisional and corporate objectives/goals and integrates within the corporate planning cycle. o Monitors and analyzes advanced analytics resources. Assesses needs and appropriately allocates resources to priorities and initiatives. o Works with divisional management to improve work processes that impact work environment and divisional resources. o Provides overall portfolio/project management oversight and direction for a variety of advanced analytics project. Oversees measurement, monitoring and reporting of project progress and resource utilization. Manages project resources to ensure timely delivery of projects consistent with divisional goals and objectives. o Coordinates with business partners (Analytics Strategy, etc.) on knowledge management and participates in business area meetings. Maintains holistic view of the business. Ensures rapid delivery and execution of insights derived from data analytics into the organization. • Analytic Tools and Techniques Research Oversight (15%): o Sets the vision for the use of new and innovative tools and technology. o Maintains and fosters an industry awareness of new developments in analytics techniques and tools, and ensures quick execution in their use within the department. o Interfaces with Enterprise Data Management (EDM) and Information Services (IS) on evolving technological and data needs and requirements. • Strategies Linked to the Division's Business Goals/Results (10%): o Establishes, communicates, and implements departmental plans, objectives, and strategies. o Participates as a member of the Management Team. o Maintains an active awareness of our Client's business environments, corporate culture, and structure to support key decision-making. • Management/Leadership for Department or Unit (10%): o Manages direct reports, systems, and projects to achieve department/unit goals in accordance with Company policies and practices. o Prepares and analyzes department/unit plans and reports. o Provides leadership by exhibiting influence and expertise, thus affecting the results of the operating area. o Creates an effective work environment by developing a common vision, setting clear objectives, expecting teamwork, recognizing outstanding performance, and maintaining open communications. o Develops staff through coaching, providing performance feedback, providing effective performance assessments, and establishing performance &amp; development plans.  </div>
    It is readily apparent that Design View is a much needed code generator in the Dreamweaver product.  Live View serves completely other, and needed, purposes.  Therefore, I still, after all the forum discussions, do not understand why Design View has been removed from Fluid Grid.
    Again Hans thank you for your reply.  But unless I'm missing something, citation to the links you provided does not solve my problem.  And that problem is this: If Design View is on its way out and thus will be completely removed from Dreamweaver at some point, then how do I provide my information (i.e. complex executive job descriptions) on my website?
    Apparently a vote is taking place https://forums.adobe.com/ideas/3922 on the issue of placing Design View back into Fluid Grid.  I do not understand why the need for two rather disjunctive functionalities are at the mercy of the democratic process.  These are matters of engineering principles not "town hall gatherings".

  • Well Documented Live View Exposure Simulation Issue

    I'm including a number of links which document this issue across multiple canon cameras. After doing a search on the canon forum, I can't find this particular issue, so I thought I'd post and see if we can get an official solution. (New to the Canon forums, so if I'm not looking in the right place, please let me know.)
    In my opinion, the vimeo link illustrates this best. (and while the 2nd link says "solved" ... perhaps the solution could be described as "janky" at best.)
    Basically, from what I can gather: The Live View (*in photo mode) uses the lens's aperture data to update the exposure simulation parameters. This effects the way the LCD and the Histogram interpret exposure settings. If you are using a lens without these digital chips, the Exp. Sim. parameters don't get updated and the liveview/histogram will sometimes appear under exposed when compared to the actual photograph (anywhere from -1 to -4 stops from what I've seen).
    What's strange is that this problem disapears in video mode. Perhaps I don't understand the real issue, but it sounds like a firmware update is needed. Is there an update available(or will there be) that fixes this problem?
    https://vimeo.com/43633270
    http://www.dvxuser.com/V6/showthread.php?246032-dark-live-view-on-T2i-550D-when-using-vintage-manual...
    http://www.dvxuser.com/V6/archive/index.php/t-247001.html

    If I understand you correctly... you're referring to a 3rd party lens designed to fit on a Canon EOS body as an "EF" lens -- not actually suggesting that Canon themselves make a lens that has the problem.  
    Niether Canon nor Nikon (nor anybody else that I am aware of) release the specs to 3rd party lens makers.  Those 3rd parties reverse-engineer the cameras in an attempt to build compatible lenses.  Again, I'd stress that to my knowledge, ALL camera makers are the same in this respect.  It is not a differentiator.  
    Rokinon (and the same lenses are sold under a variety of names) is known for their very cheap lenses.  It's a bit of a case of "you get what you paid for."  
    I don't work for Canon so I'm not trying to argue that you should only consider Canon products.  (I do like their products and am happy with all of my Canon gear.)  But I would probably not reduce my camera buying decisions be decided by just this one feature alone.  There are are so many aspects to consider when buying a camera.  Is this really that important to you?  
    The guy in this video is using a Canon 5D III.  That's a $3500 camera body.  Realistically, no photographer who can afford a $3500 camera body is going to shoot with a Rokinon 14mm lens -- and then have the audacity to expect that it's Canon's fault when the cheap lens isn't fully compatible with the high end $3500 body.   :-/
    There are a number of 3rd party lens makers... Sigma, Tokina, Tamron... and then there are some very high end lens makers... Schneider, Ziess, etc.   But when these lens makers build lenses for the cameras, they actually do tend to work correctly (not always... and sometimes a lens that worked with one body might not continue to work years later when Canon comes out with newer bodies... but Canon's own lenses DO work EVEN when you upgrade camera bodies.  Canon makes certain of that.)
    Rokinon, however (and the same lenses are sold under multiple names... Samyang, Bower, Pro-Optic, etc.) are known for their especially cheap, basic, low-end lenses.  If you are going to buy an exceptionally cheap, basic, low-end lens... you should probably not be at all surprised to learn that there are limitations.   Notice, for example, that the lens has an aperture ring on the lens... modern lenses don't do that anymore.  
    Tim Campbell
    5D II, 5D III, 60Da

  • T4i Strobe Refiring issues after using Live View to preview the shot just taken.

    I have a Canon t4i and am using it in Live View, and have attached a Paul Buff transmitter to my hotshoe to fire the Strobe, but if I go and review my shot, the strobe will not refire, I must first turn of my camera. IF I don't review my shot, the strobe will refire, no issues. Any ideas why this is occuring?

    I have no idea... You should get in touch with the folks at Paul Buff to see if there is a known issue.
    Alan Myers
    San Jose, Calif., USA
    "Walk softly and carry a big lens."
    GEAR: 5DII, 7D(x2), 50D(x3), some other cameras, various lenses & accessories
    FLICKR & PRINTROOM 

  • Live view hardware or software issues have I been cheated

    Hi I have recently bough a Live View unit. I am deaf  and I got this gadget because I needed something that would help med notice new text message. My local reseller recommended this device. I had a normal sonyericsson bluetooth watch in mind but the reseller told med that these watches was not surly supported to my phone (Xperia X10 mini pro). The Live View unit would have the vibration function that I needed. I know that the phone in it self has a similar function but unless you strap the phone on you self these vibration are easy to miss.
    I have used the live view unit about 2 weeks now. It constantly disconnect. Even if I keep the phone in my pocket and the live view unit strapped to my wrist it looses connection and is not reminding me about incoming text messages. I have used bluetooth headsets in past time. And I remember that if I got to fare away from the phone it would disconnect. But than as I got close it would reconnect.
    In the bluetooth settings it says that the live view unit is paired but not connected?. Once the live view unit locked it self .. in start mode the sonyericsson logo was showed on the display until the battery was drained, not responding to any buttons. The facebook functions has never worked. I have followed other users advise to check all the boxes on activities.
    My question should I go back to my reseller and ask him to replace it with another one ? Have I misunderstood the function of the live view unit ? It there possible a software issue ? What can I do to fix it ?

    It should work as you describe/it's advertised. It is a shame, but it's a product not ready for release. Personally, I told my retailer it doesn't work as advertised so returned it and got a refund.

  • Color issues w/ .png and .gif files in CS5.5 Live view

    Hi All,
    I am having a bunch of trouble with my .png and .gif image files in Dreamweaver CS5.5. In Dreamweaver's design view everything looks fine but when I preview my pages in Live View or in a browser the colors in my .png and .gif files are way off. All my images are designed in RGB.
    Any info anyone has to offer will be greatly appreciated. Thanks!

    GIFS contain a maximum of 216 colors (web safe palette)
    PNG and JPG can contain 16 million colors (true color palette),
    When you say the colors are  "way off"  we don't know what you mean.
    Can you post a link to your web page?
    Nancy O.
    Alt-Web Design & Publishing
    Web | Graphics | Print | Media  Specialists 
    http://alt-web.com/
    http://twitter.com/altweb

  • Text Fields Not Showing in Design or Live View

    Hello Everyone,
    I have run into a problem trying to create a simple contact form through Dreamweaver CS6.  I have two text fields for Name & Email, and 1 text area for Comments.  The issue I am running into is that the text fields are not showing in Design or Live view.  I have set-up all variables required for the server for the form to work... but that should not have any effect on the text field showing...  I tried uploading my contact page with the same result of no text fields showing...
    What is really laughable is that the "text area" I placed in my form for Comments shows up in Design & Live view just fine.  I am thinking that I am missing something, but just do not know what exactly.  The form is styled through CSS.
    Here is the form code:
         <div id="CRDForm">
           <form action="http://www.sweetformimi.com/formmail/formmail.php" method="post" enctype="application/x-www-form-urlencoded" name="contact" target="_self" id="contact">
        <input type="hidden" name="env_report" value="REMOTE_HOST,REMOTE_ADDR,HTTP_USER_AGENT,AUTH_TYPE,REMOTE_USER">
        <input type="hidden" name="recipients" value="[email protected]" />
        <input type="hidden" name="subject" value="Contact Form" />
             <label><p>Your Full Name
               <input name="Name" type="text" id="Name" size="40" /></p>
             </label>
             <label><p>Email
             <input name="email" type="text" accesskey="2" tabindex="2" title="Email" value="Email"></p>
             </label>
             <label>Comments<br />
             <textarea name="comments" cols="40" rows="10" accesskey="3" tabindex="3" title="Comments"></textarea>
             </label>
             <input name="submit" type="submit" accesskey="4" tabindex="4" title="submit" value="submit">
           </form>
        </div>
    Are there other variables I should be thinking about in the rest of my site?  I am using a fluid grid layout.  I have CSS for desktop, tablet, and phone devices.  I also have a primary CSS file that imports all three.  The sites structure was done by using <header>, <article>, <footer>, and of course <div> tags. 
    Has anyone ever experienced the "text fields" not showing up before? Is it a simple fix as reinstalling Dreamweaver CS6?  Finally, another thing I should mention is that I did have a previous version of Dreamweaver on my comp, which was CS3.  I did not uninstall that before installing the newer version.  I assumed (and I could be wrong here) that it would automatically replace the older version.
    I apoligize for it being long winded, but I am looking for some help on this issue...
    Thank You

    Hey thank you osgood for the reply!
    When I look at code for long hours it sort of blurs together, and I miss things... I think that happens to the most of us
    Ya I found what was blocking my text fields in my desktop.css
    I primarily work through code view, and currently working on quite a few projects kind of makes your eyes miss the small errors.
    Thanks again!

  • Div Image not showing in Live View

    Why can't I see my image placed within a Div tag in Live View? Makes no sense. I've changed the z-index to 1000, also tried 1 nothing changes. Please advise if anyone can help. Thank you!

    I've applied BOLD to the Div tag in question
    HTML Code:
    <!doctype html>
    <html><!-- InstanceBegin template="/Templates/pavemend_website1.dwt" codeOutsideHTMLIsLocked="false" -->
    <head>
    <meta charset="UTF-8">
    <!-- InstanceBeginEditable name="doctitle" -->
    <title>Permanent Concrete and Asphalt Repair Home Page</title>
    <meta name="description" content="CeraTech's Pavemend family of high performance concrete repair products have become the choice of professionals across the country for their rapid return to service, versatility, ease of use, and superior durability.">
    <style type="text/css">
    #apDiv8 {
        position: absolute;
        width: 200px;
        height: 115px;
        z-index: 2;
    </style>
    <!-- InstanceEndEditable -->
    <link href="pavmend_styles.css" rel="stylesheet" type="text/css">
    <style type="text/css">
    #pavemendlogo {
        background-image: url(_images/NEW%202012%20PAVEMEND%20LOGO%20WHITE.png);
        background-repeat: no-repeat;
        height: 78px;
        width: 196px;
    #prochoicetype {
        background-image: url(_images/pro_choice_concrete_type.png);
        background-repeat: no-repeat;
        height: 25px;
        width: 521px;
        margin-left: 200px;
        margin-top: -40px;
    #prochoicetype {
        background-image: url(_images/pro_choice_concrete_type.png);
        background-repeat: no-repeat;
        height: 25px;
        width: 521px;
        margin-left: 200px;
        margin-top: -40px;
    </style>
    <!-- InstanceBeginEditable name="head" -->
    <!-- InstanceEndEditable -->
    </head>
    <body>
    <div id="wrapper">
    <div class="container">
      <div id="apDiv1"><!-- InstanceBeginEditable name="HeaderLogo" --><a href="pavemend_home_page.html"><img src="_images/NEW 2012 PAVEMEND LOGO WHITE.png" width="197" height="79" class="fltlft" /></a>
        <div id="resources"></div>
      <!-- InstanceBeginEditable name="Header" -->
      <div class="headerResources"></div>
      <!-- InstanceEndEditable -->
    <nav>
      <ul id="menu">
        <li><a href="pavemend_home_page.html">OUR PRODUCTS &#9660;</a>
          <ul>
            <li><a href="slq_product_page.html">SLQ<sup>®</sup></a></li>
            <li><a href="sl_product_page.html">SL<sup>®</sup></a></li>
            <li><a href="dotline_product_page.html">DOTLine™</a></li>
            <li><a href="15.0_product_page.html">Pavemend 15.0<sup>®</sup></a></li>
            <li><a href="TR_product_page.html">Pavemend TR<sup>®</sup></a></li>
            <li><a href="VR_product_page.html">Pavemend VR<sup>®</sup></a></li>
            <li><a href="IA_product_page.html">Instant Asphalt™</a></li>
            <li><a href="kemrok_product_page.html">KEMROK™</a></li>
            <li><a href="kemrokVR_product_page.html">KEMROK VR™</a></li>
            <li><a href="firerok_product_page.html">FIREROK™</a></li>
            <li><a href="antiwear_product_page.html">Anti-Wear™</a></li>
            <li><a href="antiscale_product_page.html">Anti-Scale™</a></li>
          </ul>
        </li>
        <li><a href="resources_page.html">RESOURCES</a></li>
        <li><a href="technical_support.html">TECHNICAL SUPPORT</a></li>
        <li><a href="contact_page.html">CONTACT US</a></li>
      </ul>
    </nav>
        </section>
      <!-- InstanceBeginEditable name="Sidebar" -->
      <div class="sidebarleftlong">
      <nav>
        <ul>
          <li><a href="#">PAVEMEND PRODUCT <br>    BROCHURE</a></li>
          <p><li><a href="#">KEEP TRAFFIC MOVING <br>    BROCHURE</a></li></p>
          <p><li><a href="#">CASE STUDIES</a></li></p>
          <p><li><a href="#">INSTANT ASPHALT REPAIR</a></li></p>
          <p><li><a href="#">SL PRODUCT VIDEO</a></li></p>
          <p><li><a href="#">SLQ PRODUCT VIDEO</a></li></p>
          <p><li><a href="#">DOTLINE FIELD <br>    APPICATION VIDEO</a></li></p>
        </ul>
        </nav>
       <div id=""></div>
       <!-- end .sidebar1 --> </div>
      <!-- InstanceEndEditable -->
      <!-- InstanceBeginEditable name="Content" -->
      <div class="content">
    <p> </p>
    <img src="_images/resources_header.png" alt="slheader" width="553" height="31" class="productlogos" />
    </section>
    <p> </p>
          <section>
            <p><strong>Pavemend</strong><sup>®</sup> Rapid, Permanent Concrete and Asphalt repair products are quickly becoming the choice for Turnpike, State DOT Bridge Crews and discriminating engineers who value superior, permanent repairs and reduced traffic disruptions.</p>
    <p>Typical repair applications include full and partial depth bridge deck repairs, bridge header joints, approach slabs, form & pour repairs, dowel bar retrofits, joint nosings and more. <strong>Pavemend</strong><sup>®</sup> products require only the addition of water, with no bonding agents or curing requirements and offer all season rapid repair capability.</p>
    <p>Featuring technology developed here in the USA, <strong>Pavemend</strong><sup>®</sup> (by CeraTech Inc) products are easier to use, offer greater durability, provide superior return on investment, and are by far the most sustainable repair products available today.</p> 
            <p><img src="_images/Done Smart Logo.png" width="150" height="17" alt="donesmartlogo" />               
          </section>
    <!-- end .content --></div>
            <!-- InstanceEndEditable -->
      <div class="footer"><!-- InstanceBeginEditable name="Footer Logo" --><img src="_images/NEW 2012 PAVEMEND LOGO WHITE.png" width="160" height="64" class="flt_rgt" /><!-- InstanceEndEditable -->
        <table width="510" summary="footer material">
      <tr>
        <td width="210"><strong><em>Manufactured by</em></strong></td>
      <tr>
        <td><img src="_images/CTI_logo_white.png" width="200" height="47"  alt=""/>
        <td width="50" align="center"><a href="#../twitter.com/Pavemend">Twitter</a>
    <div id="apDiv7"></div>
      <td><strong><em>Planet Friendly Technology</em></strong></td>
       </tr>
    </table>
        <div id="apDivPFT1"></div>
        <!-- end .footer --></div>
      <!-- end .container --></div>
    </body>
    <!-- InstanceEnd --></html>
    CSS:
    @charset "UTF-8";
    /* BEGIN HORIZONTAL DROP-MENU */
    #menu {
        clear: left;
        position: relative;
        width: 100%; /**adjust width as needed**/
        margin: 0;
        padding: 0;
        background-image: url(_images/topnavpanel.png);
        color: #FFFFFF;
    #menu ul {
        margin: 0;
        padding: 0
    #menu li {
        list-style: none;
        float: left;
        text-align: center;
        font-family: "Gill Sans", "Gill Sans MT", "Myriad Pro", "DejaVu Sans Condensed", Helvetica, Arial, sans-serif;
        color: #000000;
    /**top level menu**/
    #menu li a {
        display: inline-block;
        text-decoration: none;
        /* adjust width as needed or use auto */
        width: 13em;
        padding: 8px;
        font-weight: bold;
        line-height: 12px;
        color: #000;
        border-top-style: none;
        font-size: 90%;
        margin-bottom: 0;
        margin-left: 2%;
        margin-right: 2%;
        margin-top: 0;
        border-bottom-style: none;
    /**top menu style on mouse over**/
    #menu li:hover > a {
        color: #FFF;
        width: 13em;
    /**sub-menu**/
    #menu li ul {
        display: none;
        text-align: center;
        padding: 0;
        margin-bottom: 0;
        margin-left: 40px;
        margin-right: 0;
        margin-top: 0;
        border-bottom-style: none;
    /**sub-menu, help for older IE**/
    #menu li:hover ul, #menu li.hover ul {
        display: block;
        position: absolute;
        z-index:1000;
        padding: 0;
    #menu li:hover li, #menu li.hover li {
        float: none;
        background-color: #E1D5BB;
    /**drop-menu style**/
    #menu li:hover li a, nav li.hover li a {
        width: 14em; /* adjust width as needed or use auto */
        margin-top: 0;
    /**drop-menu style on mouse over**/
    #menu li li a:hover {
        color: #FFF;
        background-color: #03C;
    /* Clear floated elements at the end*/
    #menu:after {
        visibility: hidden;
        display: block;
        font-size: 0;
        content: " ";
        clear: both;
        height: 0;
    /**END HORIZONTAL DROP-MENUS STYLES**/
    #apDiv11 {
        position: absolute;
        width: 190px;
        height: 180px;
        z-index: 2;
        background-image: url(_images/WomanPhone.png);
        background-position: 10px;
        background-repeat: no-repeat;
        margin-top: 240px;
    #apDivSustainability {
        position: absolute;
        width: 200px;
        height: 420px;
        z-index: 3;
        background-image: url(_images/sustainabilitySB2.png);
        background-repeat: no-repeat;
    #apDiv10 {
        position: absolute;
        width: 75px;
        height: 73px;
        z-index: 2;
        background-image: url(_images/PFTLogo.png);
        float: right;
        margin-left: 650px;
        margin-top: -110px;
    #apDiv9 {
        position: absolute;
        width: 200px;
        height: 207px;
        z-index: 3;
        background-image: url(_images/slphoto1.png);
        background-repeat: no-repeat;
        margin-top: 30px;
        margin-left: -5px;
    #apDivslqphoto {
        position: absolute;
        width: 200px;
        height: 267px;
        z-index: 3;
        background-image: url(_images/slqphoto.jpg);
        background-repeat: no-repeat;
        margin-top: 30px;
        margin-left: -5px;
    #apDivdotlinephoto {
        position: absolute;
        width: 200px;
        height: 267px;
        z-index: 3;
        background-image: url(_images/dotlinephoto.png);
        background-repeat: no-repeat;
        margin-top: 30px;
        margin-left: -5px;
    #apDiv15photo {
        position: absolute;
        width: 200px;
        height: 179px;
        z-index: 3;
        background-image: url(_images/15.0_photo.png);
        background-repeat: no-repeat;
        margin-top: 30px;
        margin-left: -5px;
    #apDivTRphoto {
        position: absolute;
        width: 200px;
        height: 267px;
        z-index: 3;
        background-image: url(_images/TR_photo.png);
        background-repeat: no-repeat;
        margin-top: 30px;
        margin-left: -5px;
    #apDivAWphoto {
        position: absolute;
        width: 200px;
        height: 150px;
        z-index: 3;
        background-image: url(_images/AWPhoto.png);
        background-repeat: no-repeat;
        margin-top: 30px;
        margin-left: -5px;
    #apDivASphoto {
        position: absolute;
        width: 200px;
        height: 134px;
        z-index: 3;
        background-image: url(_images/ASphoto.png);
        background-repeat: no-repeat;
        margin-top: 30px;
        margin-left: -5px;
    #apDivVRphoto {
        position: absolute;
        width: 200px;
        height: 150px;
        z-index: 3;
        background-image: url(_images/VR_photo.png);
        background-repeat: no-repeat;
        margin-top: 30px;
        margin-left: -5px;
    #apDivIAphoto {
        position: absolute;
        width: 200px;
        height: 162px;
        z-index: 3;
        background-image: url(_images/IA_photo.png);
        background-repeat: no-repeat;
        margin-top: 30px;
        margin-left: -5px;
    #apDivKemrokphoto {
        position: absolute;
        width: 200px;
        height: 207px;
        z-index: 3;
        background-image: url(_images/KEMROK%20pic.jpg);
        background-repeat: no-repeat;
        margin-top: 30px;
        margin-left: -5px;
    #apDivFirerokphoto {
        position: absolute;
        width: 200px;
        height: 248px;
        z-index: 3;
        background-image: url(_images/Firerok_photo.png);
        background-repeat: no-repeat;
        margin-top: 30px;
        margin-left: -5px;
    #apDivtechsupportphoto {
        position: absolute;
        width: 200px;
        height: 248px;
        z-index: 3;
        background-image: url(_images/techsupport_photo.png);
        background-repeat: no-repeat;
        margin-top: 30px;
        margin-left: -5px;
    #apDivKemrokVRphoto {
        position: absolute;
        width: 200px;
        height: 207px;
        z-index: 3;
        background-image: url(_images/Kemrok%20VR%20pic.jpg);
        background-repeat: no-repeat;
        margin-top: 30px;
        margin-left: -5px;
    #apDiv8 {
        position: absolute;
        width: 180px;
        height: 167px;
        z-index: 2;
        background-image: url(_images/SLbktandbag.png);
        background-repeat: no-repeat;
        float: right;
        margin-top: -160px;
        margin-left: 520px;
    #apDivslq {
        position: absolute;
        width: 80px;
        height: 105px;
        z-index: 2;
        background-image: url(_images/SLQbucket.png);
        background-repeat: no-repeat;
        float: right;
        margin-top: -125px;
        margin-left: 515px;
    #apDivdotlinebag {
        position: absolute;
        width: 88px;
        height: 167px;
        z-index: 2;
        background-image: url(_images/dotlinebag.png);
        background-repeat: no-repeat;
        float: right;
        margin-top: -165px;
        margin-left: 280px;
    #apDivkemrokbag {
        position: absolute;
        width: 121px;
        height: 167px;
        z-index: 2;
        background-image: url(_images/kemrok_bag.png);
        background-repeat: no-repeat;
        float: right;
        margin-top: -165px;
        margin-left: 570px;
    #apDivPFT1 {
        position: absolute;
        width: 121px;
        height: 167px;
        z-index: 2;
        background-image: url(_images/PFTLogo.png);
        background-repeat: no-repeat;
        float: right;
        margin-top: -75px;
        margin-left: 470px;
    #apDivkemrokVRbag {
        position: absolute;
        width: 121px;
        height: 167px;
        z-index: 2;
        background-image: url(_images/kemrokvr_bag.png);
        background-repeat: no-repeat;
        float: right;
        margin-top: -160px;
        margin-left: 590px;
    #apDivFirerokbag {
        position: absolute;
        width: 90px;
        height: 167px;
        z-index: 2;
        background-image: url(_images/firerok_bag.png);
        background-repeat: no-repeat;
        float: right;
        margin-top: -160px;
        margin-left: 570px;
    #apDivAWbucket {
        position: absolute;
        width: 90px;
        height: 167px;
        z-index: 2;
        background-image: url(_images/firerok_bag.png);
        background-repeat: no-repeat;
        float: right;
        margin-top: -160px;
        margin-left: 590px;
    #apDivAWbucket {
        position: absolute;
        width: 90px;
        height: 167px;
        z-index: 2;
        background-image: url(_images/firerok_bag.png);
        background-repeat: no-repeat;
        float: right;
        margin-top: -160px;
        margin-left: 590px;
    #apDivAWbucket {
        position: absolute;
        width: 80px;
        height: 96px;
        z-index: 2;
        background-image: url(_images/AWbucket.png);
        background-repeat: no-repeat;
        float: right;
        margin-top: -160px;
        margin-left: 590px;
    #apDiv15bag {
        position: absolute;
        width: 88px;
        height: 111px;
        z-index: 2;
        background-image: url(_images/15.0bucket.png);
        background-repeat: no-repeat;
        float: right;
        margin-top: -115px;
        margin-left: 260px;
    #apDivTRbucket {
        position: absolute;
        width: 80px;
        height: 106px;
        z-index: 2;
        background-image: url(_images/TRbucket.png);
        background-repeat: no-repeat;
        float: right;
        margin-top: -120px;
        margin-left: 370px;
    #apDivAWbucket {
        position: absolute;
        width: 205px;
        height: 150px;
        z-index: 2;
        background-image: url(_images/AWArt.png);
        background-repeat: no-repeat;
        float: right;
        margin-top: -140px;
        margin-left: 420px;
        font-size: 120%;
        -webkit-box-shadow: 0px 0px;
        box-shadow: 0px 0px;
    #apDivASArt {
        position: absolute;
        width: 205px;
        height: 150px;
        z-index: 2;
        background-image: url(_images/ASArt.png);
        background-repeat: no-repeat;
        float: right;
        margin-top: -140px;
        margin-left: 420px;
        font-size: 120%;
        -webkit-box-shadow: 0px 0px;
        box-shadow: 0px 0px;
    #apDivVRbucket {
        position: absolute;
        width: 80px;
        height: 87px;
        z-index: 2;
        background-image: url(_images/VRbucket.png);
        background-repeat: no-repeat;
        float: right;
        margin-top: -105px;
        margin-left: 470px;
    #apDivIAbucket {
        position: absolute;
        width: 251px;
        height: 106px;
        z-index: 2;
        background-image: url(_images/IAbuckets.png);
        background-repeat: no-repeat;
        float: right;
        margin-top: -120px;
        margin-left: 400px;
    body {
        background-color: #666;
        color: #000;
        text-align: center;
        background-image: url(_images/roadblurred.png);
        background-repeat: no-repeat;
        background-attachment: fixed;
        background-position: center;
        padding-top: 60px;
        font-family: Verdana, Arial, Helvetica, sans-serif;
        font-size: 100%;
        line-height: 1.4;
    .formtext {
        font-size: 100%;
        text-align: left;
    .bodyfootnote {
        font-size: 70%;
        margin-left: 20px;
        font-family: Verdana, Arial, Helvetica, sans-serif;
    .red {
        font-size: 70%;
        color: #F00;
    .popups {
    /* ~~ Element/tag selectors ~~ */
    ul, ol, dl { /* Due to variations between browsers, it's best practices to zero padding and margin on lists. For consistency, you can either specify the amounts you want here, or on the list items (LI, DT, DD) they contain. Remember that what you do here will cascade to the .nav list unless you write a more specific selector. */
        padding: 0;
        margin: 0;
        text-transform: capitalize;
        text-decoration: none;
        list-style: none;
    h1, h2, h3, h4, h5, h6, p {
        /* [disabled]margin-top: 0; */     /* removing the top margin gets around an issue where margins can escape from their containing div. The remaining bottom margin will hold it away from any elements that follow. */
        padding-right: 15px;
        padding-left: 23px;
        line-height: 25px;
    a img { /* this selector removes the default blue border displayed in some browsers around an image when it is surrounded by a link */
        border: none;
    /* ~~ Styling for your site's links must remain in this order - including the group of selectors that create the hover effect. ~~ */
    a:link {
        color: #FFFFFF;
        text-decoration: none;
        font-size: 100%;
        padding: 5px;
    a:visited {
        color: #FFFFFF;
        text-decoration: underline;
    a:hover, a:active, a:focus { /* this group of selectors will give a keyboard navigator the same hover experience as the person using a mouse. */
        text-decoration: none;
        background-color: #03C;
        color: #FFF;
        height: 12px;
        alignment-baseline: text-after-edge;
    /* ~~this fixed width container surrounds the other divs~~ */
    .container {
        width: 960px;
        background-color: #FFF; /* the auto value on the sides, coupled with the width, centers the layout */
        background-image: url(_images/Bridge4WebScreened.png);
        background-repeat: no-repeat;
        margin-bottom: 0;
        margin-left: 0px;
        margin-right: 0px;
        margin-top: 0;
        text-align: left;
    .containerTS {
        width: 960px;
        background-color: #FFF;
        margin: 0 0px; /* the auto value on the sides, coupled with the width, centers the layout */
        background-image: url(_images/US_Map.png);
        background-repeat: no-repeat;
        text-align: left;
    /* ~~ the header is not given a width. It will extend the full width of your layout. It contains an image placeholder that should be replaced with your own linked logo ~~ */
    .header {
        background-color: #000;
        background-image: url(_images/BannerBlured960.png);
        height: 229px;
        background-repeat: no-repeat;
        width: 960px;
    .headerSL {
        background-color: #000;
        background-image: url(_images/PMND%20SL%20Header.png);
        height: 229px;
        background-repeat: no-repeat;
        width: 960px;
    .headerPurchase {
        background-color: #000;
        background-image: url(_images/contact%20us%20pavemend%20header.png);
        height: 229px;
        background-repeat: no-repeat;
        width: 960px;
    .headerSLQ {
        background-color: #000;
        background-image: url(_images/PMND%20SLQ%20Header.png);
        height: 229px;
        background-repeat: no-repeat;
        width: 960px;
    .headerDOTline {
        background-color: #000;
        background-image: url(_images/DOTLINE%20Header.png);
        height: 229px;
        background-repeat: no-repeat;
        width: 960px;
    .header15 {
        background-color: #000;
        background-image: url(_images/PMND%2015.0%20Header.png);
        height: 229px;
        background-repeat: no-repeat;
        width: 960px;
    .headerTR {
        background-color: #000;
        background-image: url(_images/PMND%20TR%20Header.png);
        height: 229px;
        background-repeat: no-repeat;
        width: 960px;
    .headerAW {
        background-color: #000;
        background-image: url(_images/anti_wear_pavemend_header.png);
        height: 229px;
        background-repeat: no-repeat;
        width: 960px;
    .headerAS {
        background-color: #000;
        background-image: url(_images/anti%20scale%20pavemend%20header.png);
        height: 229px;
        background-repeat: no-repeat;
        width: 960px;
    .headerVR {
        background-color: #000;
        background-image: url(_images/PMND%20VR%20Header.png);
        height: 229px;
        background-repeat: no-repeat;
        width: 960px;
    .headerIA {
        background-color: #000;
        background-image: url(_images/Instant%20asphalt%20packaged%20Header.png);
        height: 229px;
        background-repeat: no-repeat;
        width: 960px;
    .headerKemrok {
        background-color: #000;
        background-image: url(_images/KEMROK%20packaged%20Header.png);
        height: 229px;
        background-repeat: no-repeat;
        width: 960px;
    .headerKemrokVR {
        background-color: #000;
        background-image: url(_images/KEMROK%20VR%20packaged%20Header.png);
        height: 229px;
        background-repeat: no-repeat;
        width: 960px;
    .headerFirerok {
        background-color: #000;
        background-image: url(_images/FIREROK%20packaged%20Header.png);
        height: 229px;
        background-repeat: no-repeat;
        width: 960px;
    .headerAntiWear {
        background-color: #000;
        background-image: url(_images/anti_wear_pavemend_header.png);
        height: 229px;
        background-repeat: no-repeat;
        width: 960px;
    .headerTechSupport {
        background-color: #000;
        background-image: url(_images/FEBlurred.png);
        height: 229px;
        background-repeat: no-repeat;
        width: 960px;
    .headerResources {
        background-color: #000;
        background-image: url(_images/ResourceBanner.png);
        height: 229px;
        background-repeat: no-repeat;
        width: 960px;
    .header h1 {
        font-family: Gotham, "Helvetica Neue", Helvetica, Arial, sans-serif;
        font-size: 20pt;
        font-style: normal;
        font-weight: bolder;
        color: #FFF;
        padding-top: 150px;
        padding-left: 30px;
    /* ~~ These are the columns for the layout. ~~
    1) Padding is only placed on the top and/or bottom of the divs. The elements within these divs have padding on their sides. This saves you from any "box model math". Keep in mind, if you add any side padding or border to the div itself, it will be added to the width you define to create the *total* width. You may also choose to remove the padding on the element in the div and place a second div within it with no width and the padding necessary for your design.
    2) No margin has been given to the columns since they are all floated. If you must add margin, avoid placing it on the side you're floating toward (for example: a right margin on a div set to float right). Many times, padding can be used instead. For divs where this rule must be broken, you should add a "display:inline" declaration to the div's rule to tame a bug where some versions of Internet Explorer double the margin.
    3) Since classes can be used multiple times in a document (and an element can also have multiple classes applied), the columns have been assigned class names instead of IDs. For example, two sidebar divs could be stacked if necessary. These can very easily be changed to IDs if that's your preference, as long as you'll only be using them once per document.
    4) If you prefer your nav on the left instead of the right, simply float these columns the opposite direction (all left instead of all right) and they'll render in reverse order. There's no need to move the divs around in the HTML source.
    .sidebar1 {
        float: right;
        width: 180px;
        margin-left: 0px;
        margin-right: 30px;
        clear: none;
        font-family: Gotham, "Helvetica Neue", Helvetica, Arial, sans-serif;
        font-size: 100%;
        font-style: italic;
        background-image: url(_images/Testimonialb.gif);
        background-repeat: no-repeat;
        height: 456px;
        text-decoration: none;
        z-index: 1000;
    .sidebarPurchase {
        float: right;
        width: 200px;
        margin-left: 0px;
        margin-right: 20px;
        clear: none;
        font-family: Gotham, "Helvetica Neue", Helvetica, Arial, sans-serif;
        font-size: 100%;
        font-style: italic;
        background-image: url(_images/purchaseSB.png);
        background-repeat: no-repeat;
        height: 420px;
        margin-top: 0px;
        text-decoration: none;
        background-color: #217CC0;
        background-position: 10px 10px;
    .sidebarleft {
        float: left;
        width: 195px;
        font-family: Gotham, "Helvetica Neue", Helvetica, Arial, sans-serif;
        font-size: 85%;
        font-style: oblique;
        height: 200px;
        text-decoration: none;
        padding-top: 8px;
        padding-left: 10px;
        margin-right: 5px;
        background-color: #217CC0;
        vertical-align: bottom;
        line-height: 30px;
        font-weight: bold;
        border-bottom-style: groove;
        border-bottom-width: 10px;
        margin-top: -4px;
    .sidebarleftlong {
        float: left;
        width: 195px;
        font-family: "Gill Sans", "Gill Sans MT", "Myriad Pro", "DejaVu Sans Condensed", Helvetica, Arial, sans-serif;
        font-style: oblique;
        height: 280px;
        text-decoration: none;
        padding-top: 20px;
        margin-right: 5px;
        background-color: #217CC0;
        vertical-align: bottom;
        line-height: 17px;
        font-weight: bold;
        border-bottom-style: groove;
        border-bottom-width: 10px;
        margin-top: -4px;
        color: #FFF;
        font-size: 85%;
        text-align: left;
        padding-left: 10px;
    .sidebargreen {
        float: left;
        width: 195px;
        height: 410px;
        text-decoration: none;
        padding-top: 20px;
        margin-right: 5px;
        background-color: #8CC63F;
        border-bottom-style: groove;
        border-bottom-width: 10px;
        margin-top: -4px;
        padding-left: 10px;
    .nav2 {
        font-family: bebas-neue;
        font-style: normal;
        font-weight: 400;
        color: #FFF;
    .sidebarleft nav ul li a {
        text-decoration: none;
        color: #FFF;
    .sidebarleftlong nav ul li a {
        text-decoration: none;
        color: #FFF;
        font-family: "Gill Sans", "Gill Sans MT", "Myriad Pro", "DejaVu Sans Condensed", Helvetica, Arial, sans-serif;
        font-weight: bold;
    .content {
        width: 730px;
        float: left;
        background-image: none;
        background-repeat: no-repeat;
        background-position: left;
        font-family: "Gill Sans", "Gill Sans MT", "Myriad Pro", "DejaVu Sans Condensed", Helvetica, Arial, sans-serif;
        padding: 10px 0;
        text-align: left;
        font-size: 100%;
    /* ~~ This grouped selector gives the lists in the .content area space ~~ */
    .content ul, .content ol {
        padding: 0 15px 15px 40px;
        text-decoration: none;
    /* ~~ The navigation list styles (can be removed if you choose to use a premade flyout menu like Spry) ~~ */
    ul.nav {
        list-style: none; /* this removes the list marker */
        border-top: 1px solid #666; /* this creates the top border for the links - all others are placed using a bottom border on the LI */
        margin-bottom: 15px; /* this creates the space between the navigation on the content below */
        text-decoration: none;
    ul.nav li {
        border-bottom: 1px solid #666;
    ul.nav a, ul.nav a:visited { /* grouping these selectors makes sure that your links retain their button look even after being visited */
        padding: 5px 5px 5px 15px;
        display: block; /* this gives the link block properties causing it to fill the whole LI containing it. This causes the entire area to react to a mouse click. */
        width: 160px;  /*this width makes the entire button clickable for IE6. If you don't need to support IE6, it can be removed. Calculate the proper width by subtracting the padding on this link from the width of your sidebar container. */
        text-decoration: none;
        background-color: #C6D580;
    ul.nav a:hover, ul.nav a:active, ul.nav a:focus { /* this changes the background and text color for both mouse and keyboard navigators */
        background-color: #DFEBF3;
        color: #FFF;
        text-decoration: none;
    /* ~~ The footer ~~ */
    .footer {
        padding: 10px 0;
        position: relative;/* this gives IE6 hasLayout to properly clear */
        clear: both;
        background-color: #000000;
    /* ~~ miscellaneous float/clear classes ~~ */
    .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: left;
        margin-left: 760px;
    .fltlft { /* this class can be used to float an element left in your page. The floated element must precede the element it should be next to on the page. */
        float: left;
        margin-right: 8px;
    .clearfloat { /* this class can be placed on a <br /> or empty div as the final element following the last floated div (within the #container) if the #footer is removed or taken out of the #container */
        clear:both;
        height:0;
        font-size: 1px;
        line-height: 0px;
    #apDiv1 {
        position: absolute;
        width: 900px;
        height: 94px;
        z-index: 1;
        margin-top: 80px;
        margin-left: 30px;
        white-space: 3;
        font-size: 100%;
        text-align: left;
    sllogo {
        background-image: url(_images/SLwhitelogo.png);
        background-repeat: no-repeat;
    .slLogo {
        background-image: url(_images/SLwhitelogo.png);
        background-repeat: no-repeat;
        height: 100px;
        width: 240px;
    .productlogos {
        margin-left: 23px;
        margin-top: 10px;
    .Bold {
        font-weight: bold;
    .inherent {
        font-style: inherit;
    sup {
        position: relative;
        top: -1ex;
        vertical-align:baseline;
        font-size: 75%;
    #apDiv2 {
        position: absolute;
        width: 650px;
        height: 31px;
        z-index: 2;
        background-repeat: no-repeat;
        padding-right: 15px;
        padding-left: 15px;
        margin-right: 15px;
        margin-left: 15px;
        top: 369px;
        background-image: url(_images/homeheader.png);
    .footer table tr td {
        font-family: Gotham, "Helvetica Neue", Helvetica, Arial, sans-serif;
        font-size: 75%;
        color: #FFF;
        height: 8px;
        width: 160px;
        margin-left: 10px;
        padding-left: 15px;
        border-collapse: collapse;
        padding-top: 0px;
        padding-right: 0px;
        padding-bottom: 5px;
    .footer p {
        font-family: Gotham, "Helvetica Neue", Helvetica, Arial, sans-serif;
        font-size: 80%;
        color: #FFF;
        margin-top: 20px;
        margin-bottom: 20px;
        margin-right: 30px;
    .footer table tr th h4 {
        font-family: Gotham, "Helvetica Neue", Helvetica, Arial, sans-serif;
        font-size: 75%;
        color: #FFF;
        float: left;
        padding-left: 15px;
        height: 0px;
    .footer table tbody tr td a {
        color: #FFF;
    #wrapper {
         width:970px; /**adjust as needed**/
         margin:0 auto; /**centers page on screen**/              
    .flt_rgt {
        float: right;
        margin-top: 15px;
        margin-right: 30px;
        background-image: ;
        background-repeat: no-repeat;
    .title {
        /* [disabled]margin-right: 30px; */
        margin-top: 35px;
        margin-left: 10px;
        background-image: ;
        background-repeat: no-repeat;
        /* [disabled]margin-left: 20px; */
        top: 30px;
        /* [disabled]margin-top: 30px; */
        left: 30px;
    .flt_products {
        float: right;
        margin-right: 30px;
        background-image: ;
        background-repeat: no-repeat;
    .container section nav {
        background-image: url(_images/topnavpanel.png);
        background-repeat: no-repeat;
        height: 30px;
        width: 960px;
        padding-top: 3px;
    #apDiv3 {
        position: absolute;
        width: 468px;
        height: 41px;
        z-index: 2;
        background-image: url(_images/savetimetext.png);
        background-repeat: no-repeat;
        margin-left: 15px;
    #apDiv4 {
        position: absolute;
        width: 400px;
        height: 41px;
        z-index: 3;
        background-image: url(_images/ULTRAFLOR.png);
        background-repeat: no-repeat;
        margin-left: 10px;
        margin-top: 45px;
    #apDiv5 {
        position: absolute;
        width: 250px;
        height: 103px;
        z-index: 4;
        background-image: url(_images/HI%20RES%20PRODUCT%20FAMILY%20w%20IA.png);
        background-repeat: no-repeat;
        float: right;
        right: auto;
        margin-left: 675px;
        margin-top: -22px;
    #apDiv6 {
        position: absolute;
        width: 40px;
        height: 38px;
        z-index: 5;
        background-image: url(_images/PFT%20No%20Text%20No%20Flip.png);
        margin-top: -25px;
        margin-left: 83px;
    #apDiv7 {
        position: absolute;
        width: 20px;
        height: 17px;
        z-index: 5;
        background-image: url(_images/twitter-bird-dark-bgs.png);
        margin-top: -15px;
        margin-left: 85px;
    nav ul {
        list-style: none; /* this removes the list marker */
        border-top: 1px solid #666; /* this creates the space between the navigation on the content below */
        font-size: 90%;
    nav ul li {
        text-decoration: none;
        color: #FFF;
    nav ul a:link , nav ul a:visited { /* grouping these selectors makes sure that your links retain their button look even after being visited */
        padding: 5px 5px 5px 15px;
        display: block; /* this gives the link block properties causing it to fill the whole LI containing it. This causes the entire area to react to a mouse click. */
        width: 160px;  /*this width makes the entire button clickable for IE6. If you don't need to support IE6, it can be removed. Calculate the proper width by subtracting the padding on this link from the width of your sidebar container. */
        text-decoration: none;
        text-align: left;
        color: #FFF;
    nav ul a:hover, nav ul a:active, nav ul a:focus { /* this changes the background and text color for both mouse and keyboard navigators */
        color: #FFF;
        text-decoration: none;
    .orange {
        color: #FAA634;
    .white {
        color: #FFFFFF;
    .red {
        color: #F00;
    .red1 {
        color: #F00;
    .toppanel {
        background-image: url(_images/topnavpanel.png);
        background-repeat: no-repeat;
        height: 30px;
        width: 960px;
    #apDiv12 {
        position: fixed;
        width: 960px;
        height: 30px;
        z-index: 5;
        background-image: url(_images/topnavpanel.png);
        background-repeat: no-repeat;
        float: left;
        top: 229px;
    .white {
    .CeraTechLogo {
        background-image: url(_images/CTI_logo_white.png);
        background-repeat: no-repeat;
        width: 200px;
        height: 60px;
    .apDivPFT {
        background-repeat: no-repeat;
        padding-left: px;
        padding-top: 0px;
    #prochoicetype {
        background-image: url(_images/pro_choice_concrete_type.png);
        background-repeat: no-repeat;
        height: 25px;
        width: 521px;
        margin-left: 200px;
        margin-top: -40px;
    #resources {
        background-image: url(_images/ResourcesType.png);
        background-repeat: no-repeat;
        height: 25px;
        width: 521px;
        margin-left: 200px;
        margin-top: -40px;

  • Canon 6D will not focus or flash in "Live View" mode.

    My Canon 6D will not focus or flash in "Live View" mode.  I have a canon 430ex II  and a E-ttl flash connected with a sync cord for E-ttl function.  The camera does simulate shutter action, but no photo is taken.  How can I over-come this problem. 
    Once in a while, after trying to take several photos it will start working, but usually not.
    Solved!
    Go to Solution.

    Hi Shadowcat!
    Thanks for posting.
    It sounds like the AF Method is set to Quick Mode.  When the camera is set for Live View Shooting, there are different AF Methods that can be set.  In Quick Mode, the camera uses its dedicated AF sensor to focus when you press the shutter button down halfway. 
    The image on the LCD will be interrupted while the camera tries to focus because the shutter closes and the mirror drops back over the image sensor.  This may look as though the camera is taking a picture, but it is not, it is only focusing.  No flash is fired during this process either.  Continue to hold the shutter button halfway until focus is achieved, at which point the image will return to the LCD.  Then you can press the shutter button the rest of the way down to take the picture.  The flash will fire and an image will be recorded.
    This didn't answer your question? Find more help at Contact Us.
    Did this answer your question? Please click the Accept as Solution button so that others may find the answer as well.

  • Webpage looks good with tranparent boxes and photo background in live view but not in browsers

    If anyone has time to help I would be very grateful.   I am new to dreamweaver and am trying to make a webpage with transparent colums and boxed text using styles.  It looks perfect in "live view" but when I look at it in any browser all formatting is gone.  It looks like the background with text on top layed out wrapped across the entire page.   I have not been able to figure out what is wrong in days of searching.  Does anyone know the answer?
    This first the format I want and is what it looks like in Live View, the second is what it looks like in most browsers.
    Here is the code I used:
    </style>
    <link href="../styles/tcastyles.css" rel="stylesheet" type="text/css">
    <style type="text/css">
    body {
              background-image: url(bamboo.JPG);
              margin-left: 150px;
    a:link {
              color: #600;
              text-decoration: none;
    a:visited {
              text-decoration: none;
    a:hover {
              text-decoration: none;
    a:active {
              text-decoration: none;
              font-family: Verdana, Geneva, sans-serif;
              font-size: 12px;
              font-weight: bold;
    a {
              font-size: 12px;
    body,td,th {
              font-family: Verdana, Geneva, sans-serif;
    .container .faqs h2 {
              line-height: 40px;
    .container .faqs ul li {
              text-align: left;
    .footer {
              padding: 5;
              position: relative;
              clear: both;
    </style>
    <div class="container">
      <div class="header"><span class="menutable"></span><img border="0" src="navigate_projects.jpg" width="307" height="167" usemap="#FPMap0" alt="The Conservation Agency - Project Menu" align="absmiddle" />
        <map name="FPMap0">
          <area shape="rect" coords="132, 112, 172, 127" href="asia.htm" alt="Asia" />
          <area shape="rect" coords="138, 92, 286, 110" href="west.htm" alt="Western Hemisphere" />
          <area shape="rect" coords="138, 73, 279, 89" href="flamingos.htm" alt="British Virgin Islands" />
          <area shape="rect" coords="131, 55, 249, 72" href="turkscaicos.htm" alt="Turks and Caicos" />
          <area shape="rect" coords="121, 35, 244, 52" href="newengland.htm" alt="Narragansett Bay" />
          <area shape="rect" coords="103, 17, 306, 32" href="coyote.htm" alt="Narragansett Bay Coyote Study " />
          <area shape="rect" coords="121, 128, 173, 144" href="pacific.htm" alt="Pacific" />
        </map>
      </div>
      <div class="menu">
        <table width="100%" border="0" align="center" id="menutable">
          <tr>
            <td height="30" align="center" valign="middle"><p><strong><a href="mission.htm">Mission</a></strong></p></td>
            <td height="30" align="center" valign="middle"><p><strong><a href="pubs.htm">Publications</a></strong></p></td>
            <td height="30" align="center" valign="middle"><p><strong><a href="projects.htm">Projects</a></strong></p></td>
            <td height="30" align="center" valign="middle"><p><strong><a href="opps.htm">Opportunities</a></strong></p></td>
            <td height="30" align="center" valign="middle"><p><strong><a href="sponsors.htm">Sponsors</a></strong></p></td>
            <td height="30" align="center" valign="middle"><p><strong><a href="coyote.htm">NBCS</a></strong></p></td>
            <td height="30" align="center" valign="middle"><p><strong><a href="guana.htm">Guana</a></strong></p></td>
            <td height="30" align="center" valign="middle"><p><strong><a href="tca.htm">Contact us</a></strong></p></td>
            <td height="30" align="center" valign="middle"><p><strong><a href="index.htm">Home</a></strong></p></td>
          </tr>
        </table>
      </div>
      <div class="banner">Narragansett Bay Coyote Study</div>
      <d/div>
          <div class="box739">
            <h3>What does NBCS Do?</h3>
            <p>Since 2004 The Narragansett Bay Coyote Study (NBCS) has been developing science-based coexistence and management strategies for our newest top predator.  Coyotes, originally a prairie species, have successfully colonized all parts of the continental and nearshore us in the past 100 years. They reached the islands of Narragansett Bay in the mid-1990s. Since then coyotes have become increasingly abundant and problematic in some island communities.</p>
            <p>In our history of cohabitation with coyotes people consistently  tried to eliminate them by hunting, trapping, and poisoning. Lethal removal  worked for individual problem animals but did not work as a population control strategy. Why? Coyotes have intrinsic physiological and behavioral abilities to control their own numbers. If coyotes are removed they increase reproduction and numbers rapidly rebound. The critical population regulation trigger is competition for food. As long as coyotes are well fed (with few coyotes competing for food) their populations will grow. </p>
            <p>It is also known that opposite effect occurs if coyotes if coyotes are stressed by competition for food. If there are too many coyotes competing for the food available coyotes will drop the the level sustainable by those resources.</p>
            <p>Understanding this relationship, NBCS scientists decided to study the resource use of coyotes on two islands in Narragansett Bay, Rhode Island. We used GPS tracking collars to find out where the coyotes were spending thier time. We theorized that if we could identify important coyote food resources - and control them - the coyotes would bring their own numbers down. NBCS calls this &quot;passive coyote management.&quot;</p>
            <p> Since 2005 when we trapped and collared our first island coyotes we have continually found that the most important food resources to our study are provided by people. That means they are within our control That means we can control coyotes. If we remove anthropogenic resources (human subsidies) coyote numbers will drop to the level sustainable by natural resources. When coyotes are sustained only by natural prey (mice, woodchucks, rabbits, geese, and deer) coyotes numbers will be lower and they will provide helpful pest control services. </p>
            <p>Based our scientific data NBCS generated a set of <a href="coyotes/Best Management Practices for Coexistence with Coyotes - Nov 8 2010.pdf" target="_new">Best Management Practices for Coexistence with Coyotes</a>- basically a toolbox for safe, sustainable, community coyote management. We are working with the towns in our study area to adopt the CBMPs and be the first community in the nation to successfully and sustainably manage coyotes. We also believe other cities and towns might be able to use our results as a template if they are experiencing coyote problems. We have only just begun to implement the CBMPs on our islands. We hope in the near future to have all our towns implementing the CBMPs - only then will we see the full impacts they make on coyote numbers and behavioral problems. You can follow our progress on this website.</p>
          </div>
          <div class="footer">
            <table width="100%" border="0" cellspacing="5">
              <tr>
                <td>Return to top</td>
                <td><a href="mailto:[email protected]">[email protected]</a></td>
              </tr>
            </table>
          </div>
        </div>
      </div>
      <p> </p>
    </div>iv class="faqs">
        <h2>FAQs</h2>
        <ul>
          <li>How do coyotes control their own population numbers?</li>
          <li>bla bla bla</li>
        </ul>
      </div>
      <div class="content">
        <div class="clearbox">
          <div class="col1">
            <h3>Middletown Adopts the CBMPs and passes a No-Feeding Ordinance!</h3>
          </div>
          <div class="col2">
            <h3>Pilot, Java, and the Valley Pack</h3>
          <
    And here are the styles:
    .container {
              height: 1500px;
              width: 975px;
              border: 8px solid #660000;
              float: left;
    .header {
              float: left;
              height: 170px;
              width: 975px;
              background-color: #033000;
    .menu {
              background-color: #FFC;
              float: left;
              height: 30px;
              width: 975px;
              font-family: Verdana, Geneva, sans-serif;
              font-size: 9px;
              color: #660000;
              font-weight: bold;
              margin-bottom: 5px;
    .table {
              font-family: Verdana, Geneva, sans-serif;
              font-size: 8px;
              font-weight: bold;
    .banner {
              float: left;
              height: 100px;
              width: 739px;
              font-family: Verdana, Geneva, sans-serif;
              font-size: 37px;
              font-weight: bold;
              color: rgba(0,51,0,1);
              background-color: rgba(255,255,204,.7);
              text-align: center;
              line-height: 75px;
              border-radius: 5px;
              padding: 5px;
              margin: 5px;
    .clearbox {
              float: left;
              height: auto;
              width: 760px;
    .box739 {
              width: 739px;
              float: left;
              height: auto;
              background-color: rgba(255,255,204,.7);
              font-size: 12px;
              color: rgba(0,51,0,1);
              border-radius: 5px;
              padding: 5px;
              margin: 5px;
    .faqs {
              float: right;
              height: 620px;
              width: 205px;
              font-family: Verdana, Geneva, sans-serif;
              font-size: 12px;
              font-style: normal;
              line-height: normal;
              overflow: scroll;
              background-color: rgba(255,255,204,.7);
              margin: 5px;
              border-radius: 5px;
              font-weight: bold;
              color: rgba(0,51,0,1);
              text-align: center;
    .col1 {
              float: left;
              height: 500px;
              width: 359px;
              background-color: rgba(255,255,204,.7);
              font-size: 12px;
              border-radius: 5px;
              color: rgba(0,51,0,1);
              margin: 5px;
              padding: 5px;
    .col2 {
              float: left;
              height: 500px;
              width: 359px;
              background-color: rgba(255,255,204,.7);
              font-size: 12px;
              border-radius: 5px 5px 5px 5px;
              color: rgba(0,0,0,1);
              padding: 5px;
              margin: 5px;
    .footer {
              position:relative;
              clear: both;
              background-color: rgba(255,255,204,1);
              font-size: 12px;
              color: rgba(0,51,0,1);

    Helo thanks for responding .  I think it uploads...  It says it does as an assocaiated file when I put to the website.  But that sounds like it is the issue. Those format commands seem to be the one it is ignoring.  I am not familiar with html but I see that the href command is what identifies the path to the file I call TCAStyles.  I notice that dw puts all my files in a local public file and the structure is different - with no public file - at the site.
    I am not sure what the 2 dots in the href command mean - there is not a full path.  Is this command valid?  I will try to look into the directory structure on local and remote site and will check for files.

  • When using Live View, site looks great, browser testing goes crazy

    I am creating a new website (and I am really unexperienced with Dreamwaver CS5).  But when I check my site using "Live View" everything looks great, the way it is supposed to.  Then when I go to test it in my browswer (Primary browser is Chrome) it goes crazy:  I at first noticed that I had saved one copy as an .asp but then resaved it to .xhtml  I did delete the first line of code already that the .asp file created as it kept giving me an error on line 1.
    Then I tried to do a spry drop-down menu bar, which I have deleted since I thought I was doing something wrong with that and I should just stick to what I half-way know.
    If I were to preview the template page it gives me this error:
    This page contains the following errors:
    error on line 150 at column 76: error parsing attribute name
    Below is a rendering of the page up to the first error.
    Here is line 150:
        if (a[i].indexOf("#")!=0){ d.MM_p[j]=new Image; d.MM_p[j++].src=a[i];}}
    If I were to test the index.xhtml page in the browser, it ignores most images (all but one), and the first nav-bar (an editable region) appears to the left instead of under the header.  The layout is totally ignored and everything is on the left-hand side of the screen instead of in a two column layout.
    I am not testing this on a server just off of my computer.
    I am assuming that the error has something to do with the .asp file I first did and when I resaved it, since I don't know what I would be looking for, is still in there screwing it up.
    Here is the code from the template page:
    <!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" />
    <!-- TemplateBeginEditable name="doctitle" -->
    <title>Midwest Window Brokers | Page</title>
    <!-- TemplateEndEditable -->
    <!-- TemplateBeginEditable name="head" -->
    <!-- TemplateEndEditable -->
    <style type="text/css">
    <!--
    body {
              font: 100%/1.4 Verdana, Arial, Helvetica, sans-serif;
              margin: 0;
              padding: 0;
              color: #000;
              background-image: url(/images/bkg.jpg);
              background-repeat: repeat;
    /* ~~ Element/tag selectors ~~ */
    ul, ol, dl { /* Due to variations between browsers, it's best practices to zero padding and margin on lists. For consistency, you can either specify the amounts you want here, or on the list items (LI, DT, DD) they contain. Remember that what you do here will cascade to the .nav list unless you write a more specific selector. */
              padding: 0;
              margin: 0;
    h1, h2, h3, h4, h5, h6, p {
              margin-top: 0;           /* removing the top margin gets around an issue where margins can escape from their containing div. The remaining bottom margin will hold it away from any elements that follow. */
              padding-right: 15px;
              padding-left: 15px; /* adding the padding to the sides of the elements within the divs, instead of the divs themselves, gets rid of any box model math. A nested div with side padding can also be used as an alternate method. */
              text-align: left;
    a img { /* this selector removes the default blue border displayed in some browsers around an image when it is surrounded by a link */
              border: none;
    /* ~~ Styling for your site's links must remain in this order - including the group of selectors that create the hover effect. ~~ */
    a:link {
              color: #060;
              text-decoration: none; /* unless you style your links to look extremely unique, it's best to provide underlines for quick visual identification */
    a:visited {
              color: #666;
              text-decoration: underline;
    a:hover, a:active, a:focus { /* this group of selectors will give a keyboard navigator the same hover experience as the person using a mouse. */
              text-decoration: none;
    /* ~~this fixed width container surrounds the other divs~~ */
    .container {
              width: 960px;
              background: #FFF;
              margin: 0 auto; /* the auto value on the sides, coupled with the width, centers the layout */
    /* ~~ the header is not given a width. It will extend the full width of your layout. It contains an image placeholder that should be replaced with your own linked logo ~~ */
    .header {
              background-color: #FFF;
    /* ~~ These are the columns for the layout. ~~
    1) Padding is only placed on the top and/or bottom of the divs. The elements within these divs have padding on their sides. This saves you from any "box model math". Keep in mind, if you add any side padding or border to the div itself, it will be added to the width you define to create the *total* width. You may also choose to remove the padding on the element in the div and place a second div within it with no width and the padding necessary for your design.
    2) No margin has been given to the columns since they are all floated. If you must add margin, avoid placing it on the side you're floating toward (for example: a right margin on a div set to float right). Many times, padding can be used instead. For divs where this rule must be broken, you should add a "display:inline" declaration to the div's rule to tame a bug where some versions of Internet Explorer double the margin.
    3) Since classes can be used multiple times in a document (and an element can also have multiple classes applied), the columns have been assigned class names instead of IDs. For example, two sidebar divs could be stacked if necessary. These can very easily be changed to IDs if that's your preference, as long as you'll only be using them once per document.
    4) If you prefer your nav on the left instead of the right, simply float these columns the opposite direction (all left instead of all right) and they'll render in reverse order. There's no need to move the divs around in the HTML source.
    .sidebar1 {
              float: right;
              width: 300px;
              background: #ffffff;
              padding-bottom: 10px;
    .content {
              padding: 10px 0;
              width: 650px;
              float: right;
    /* ~~ This grouped selector gives the lists in the .content area space ~~ */
    .content ul, .content ol {
              padding: 0 15px 15px 40px; /* this padding mirrors the right padding in the headings and paragraph rule above. Padding was placed on the bottom for space between other elements on the lists and on the left to create the indention. These may be adjusted as you wish. */
    /* ~~ The navigation list styles (can be removed if you choose to use a premade flyout menu like Spry) ~~ */
    ul.nav {
              list-style: none; /* this creates the space between the navigation on the content below */
    ul.nav li {
              border-bottom: 1px solid #666; /* this creates the button separation */
    ul.nav a, ul.nav a:visited { /* grouping these selectors makes sure that your links retain their button look even after being visited */
              padding: 5px 5px 5px 15px;
              display: block; /* this gives the link block properties causing it to fill the whole LI containing it. This causes the entire area to react to a mouse click. */
              width: 160px;  /*this width makes the entire button clickable for IE6. If you don't need to support IE6, it can be removed. Calculate the proper width by subtracting the padding on this link from the width of your sidebar container. */
              text-decoration: none;
              background-color: #DDDECB;
    ul.nav a:hover, ul.nav a:active, ul.nav a:focus { /* this changes the background and text color for both mouse and keyboard navigators */
              background: #ADB96E;
              color: #FFF;
    /* ~~ The footer ~~ */
    .footer {
              padding: 10px 0;
              position: relative;/* this gives IE6 hasLayout to properly clear */
              clear: both; /* this clear property forces the .container to understand where the columns end and contain them */
              background-color: #DDDECB;
              font-size: small;
    /* ~~ miscellaneous float/clear classes ~~ */
    .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. The floated element must precede the element it should be next to on the page. */
              float: left;
              margin-right: 8px;
    .clearfloat { /* this class can be placed on a <br /> or empty div as the final element following the last floated div (within the #container) if the #footer is removed or taken out of the #container */
              clear:both;
              height:0;
              font-size: 1px;
              line-height: 0px;
    #h-navbar {
              font-weight: bold;
              height: auto;
              font-size: 18px;
              line-height: 50px;
              background-image: url(/images/navbar2.jpg);
    #h-navbar1 {
              background-image: none;
              background-repeat: repeat-x;
    -->
    </style>
    <script type="text/javascript">
    function MM_preloadImages() { //v3.0
      var d=document; if(d.images){ if(!d.MM_p) d.MM_p=new Array();
        var i,j=d.MM_p.length,a=MM_preloadImages.arguments; for(i=0; i<a.length; i++)
        if (a[i].indexOf("#")!=0){ d.MM_p[j]=new Image; d.MM_p[j++].src=a[i];}}
    function MM_swapImgRestore() { //v3.0
      var i,x,a=document.MM_sr; for(i=0;a&&i<a.length&&(x=a[i])&&x.oSrc;i++) x.src=x.oSrc;
    function MM_findObj(n, d) { //v4.01
      var p,i,x;  if(!d) d=document; if((p=n.indexOf("?"))>0&&parent.frames.length) {
        d=parent.frames[n.substring(p+1)].document; n=n.substring(0,p);}
      if(!(x=d[n])&&d.all) x=d.all[n]; for (i=0;!x&&i<d.forms.length;i++) x=d.forms[i][n];
      for(i=0;!x&&d.layers&&i<d.layers.length;i++) x=MM_findObj(n,d.layers[i].document);
      if(!x && d.getElementById) x=d.getElementById(n); return x;
    function MM_swapImage() { //v3.0
      var i,j=0,x,a=MM_swapImage.arguments; document.MM_sr=new Array; for(i=0;i<(a.length-2);i+=3)
       if ((x=MM_findObj(a[i]))!=null){document.MM_sr[j++]=x; if(!x.oSrc) x.oSrc=x.src; x.src=a[i+2];}
    </script>
    </head>
    <body onload="MM_preloadImages('/images/home2.jpg')">
    <div class="container">
      <div class="header"><a href="/index.xhtml"><img src="../images/heading.jpg" alt="Midwest Window Brokers, Windows, Siding, Roofing, 605-791-5352" name="Insert_logo" width="950" height="200" align="right" id="Insert_logo" style="background: #FFFFFF; display:block;" /></a>
        <div id="h-navbar1"><a href="/index.xhtml"><img src="/images/home.jpg" alt="home" width="159" height="51" id="Image1" onmouseover="MM_swapImage('Image1','','/images/home2.jpg',1)" onmouseout="MM_swapImgRestore()" /></a><a href="/windows.html"><img src="/images/services.jpg" width="151" height="51" alt="services" /></a><a href="/freebay.xhtml"><img src="/images/specials.jpg" width="153" height="51" alt="specials" /></a><a href="/gallery.html"><img src="/images/gallery.jpg" width="152" height="51" alt="gallery" /></a><a href="/roofing.xhtml"><img src="/images/order.jpg" width="152" height="51" alt="order" /></a><img src="/images/blank.jpg" width="75" height="51" /><img src="/images/facebook.jpg" width="38" height="51" alt="facebook" longdesc="http://facebook.com/midwestwindowbrokers" /><img src="/images/twitter.jpg" width="37" height="51" alt="twitter" longdesc="http://twitter.com/midwestwindow" /><img src="/images/google.jpg" width="42" height="51" alt="google+" longdesc="http://https://plus.google.com/u/0/b/108071947231835835141/108071947231835835141/posts" /></div>
      <!-- end .header --></div>
      <!-- TemplateBeginEditable name="navbar" -->
      <div id="h-navbar">
        <div id="h-navbar2">  Content for  id "h-navbar2" Goes Here</div>
      </div>
      <!-- TemplateEndEditable -->
      <div class="sidebar1">
        <ul class="nav">
        </ul>
        <p> <div id="wufoo-z7x3k1">
    Fill out my <a href="http://midwestwindow.wufoo.com/forms/z7x3k1">online form</a>.
    </div>
    <script type="text/javascript">var z7x3k1;(function(d, t) {
    var s = d.createElement(t), options = {
    'userName':'midwestwindow',
    'formHash':'z7x3k1',
    'autoResize':true,
    'height':'601',
    'async':true,
    'header':'show'};
    s.src = ('https:' == d.location.protocol ? 'https://' : 'http://') + 'wufoo.com/scripts/embed/form.js';
    s.onload = s.onreadystatechange = function() {
    var rs = this.readyState; if (rs) if (rs != 'complete') if (rs != 'loaded') return;
    try { z7x3k1 = new WufooForm();z7x3k1.initialize(options);z7x3k1.display(); } catch (e) {}};
    var scr = d.getElementsByTagName(t)[0], par = scr.parentNode; par.insertBefore(s, scr);
    })(document, 'script');</script></p>
        <!-- end .sidebar1 --></div>
      <!-- TemplateBeginEditable name="Body" -->
      <div class="content">
        <h1>Instructions</h1>
        <p>Be aware that the CSS for these layouts is heavily commented. If you do most of your work in Design view, have a peek at the code to get tips on working with the CSS for the fixed layouts. You can remove these comments before you launch your site. To learn more about the techniques used in these CSS Layouts, read this article at Adobe's Developer Center - <a href="http://www.adobe.com/go/adc_css_layouts">http://www.adobe.com/go/adc_css_layouts</a>.</p>
        <h2>Clearing Method</h2>
        <p>Because all the columns are floated, this layout uses a clear:both declaration in the .footer rule.  This clearing technique forces the .container to understand where the columns end in order to show any borders or background colors you place on the .container. If your design requires you to remove the .footer from the .container, you'll need to use a different clearing method. The most reliable will be to add a &lt;br class=&quot;clearfloat&quot; /&gt; or &lt;div  class=&quot;clearfloat&quot;&gt;&lt;/div&gt; after your final floated column (but before the .container closes). This will have the same clearing effect.</p>
        <h3>Logo Replacement</h3>
        <p>An image placeholder was used in this layout in the .header where you'll likely want to place  a logo. It is recommended that you remove the placeholder and replace it with your own linked logo. </p>
        <p><span style="font-size: 18px; color: #C00; font-weight: bold; font-style: italic;">Logo Replacement</span></p>
        <p> Be aware that if you use the Property inspector to navigate to your logo image using the SRC field (instead of removing and replacing the placeholder), you should remove the inline background and display properties. These inline styles are only used to make the logo placeholder show up in browsers for demonstration purposes. </p>
        <p>To remove the inline styles, make sure your CSS Styles panel is set to Current. Select the image, and in the Properties pane of the CSS Styles panel, right click and delete the display and background properties. (Of course, you can always go directly into the code and delete the inline styles from the image or placeholder there.)</p>
        <h4>Backgrounds</h4>
        <p>By nature, the background color on any div will only show for the length of the content. This means if you're using a background color or border to create the look of a side column, it won't extend all the way to the footer but will stop when the content ends. If the .content div will always contain more content, you can place a border on the .content div to divide it from the column.</p>
        <!-- end .content -->
      </div>
      <!-- TemplateEndEditable -->
      <div class="footer">
        <p class="footer"><strong>  <em>References Available!</em>     We accept cash, check, Visa, Discover, MasterCard</strong></p>
          Copyright 2012 Midwest Window Brokers Inc. All Rights Reserved.
        <!-- end .footer --></div>
      <!-- end .container --></div>
    </body>
    </html>

    I had saved one copy as an .asp but then resaved it to .xhtml 
    I'm assuming this is a static web site.  Rename (F2) all your pages with .html or .htm extension. 
    .xhtml is not a valid extension.
    Nancy O.

  • Live View not working in Dreamweaver CC 2014

    I just installed the new 2014 version and opened the index file of an existing website design. When I click on the live view all I get is blank white screen. I thought it was a time issue and waited for a long time but nothing. I opened other files as well and still just a blank white screen. The installation was done through Creative Cloud as I have a subscription. Is there anything  that can fix this? there seems to be some know issues but I didn't find this one among them and perhaps this needs t be added to it if there are others with the same problem.
    I am using an iMac with Maverick OS latest version.
    Thank you

    Hi iraji,
    Can you try the solution in this post and let us know if it helped?
    Just upgraded to CC 2014. In Live View the window is blank. Was fine in previous CC.
    See Restore preferences | Dreamweaver CS4, CS5, CS5.5, CS6 for information on restoring preferences.
    Thanks,
    Preran

  • Help with Wordpress in Live View

    I have recently started attempting to use Dreamweaver to customise Wordpress themes, following the guidance given in this article:
    http://www.adobe.com/devnet/dreamweaver/articles/dw_wordpress_pt1.html
    However, despite following the advice precisely, I've encountered a problem. When I add an image to the header (following the method described on page 3 of the article), it does not display in Live View, nor does it appear in my web browser. Instead, as you can see (circled in red) it simply displays the icon for a missing image. In my browser, the alternate text is shown instead. So, in short, the image is missing.
    The open file is index.php, opened from the root (htdocs) as specified in the article. I note from the comments on page 3 of the article that several people have experienced the same thing. One user reports solving it by placing the image in the images folder in the root directory, instead of within the theme directory. However, this seems odd for two reasons - one, as I understand it, it's not how Wordpress themes generally work (though I can understand having another 'images' folder in the root for working purposes), and two there is no images folder in my root directory. So, I have a few questions - the general one of what's going on and how do I fix, plus the specific question of whether or not there should be an images folder in my root directory? If so, why isn't it there? Any help greatly appreciated.
    Regards,
    Matt

    I'm sure it is a path issue - the code in the header file supplies a path of images/banner_logo.gif as you can see. This is obviously causing the problem in some way because the set-up with Dreamweaver demands I open the index.php file from the root, but my quandary is that the path as it stands is sort of 'correct' in terms of how Wordpress should usually work, is it not? I obviously don't want to be creating absolute links for the sake of Dreamweaver that create additional problems (or simple redundancy) when I upload the theme.
    The image is where it should be, relative to header.php:
    Here's the Live Code - will supply CSS if needed but not sure it's the issue:
    <!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>
    blog</title>
    <link rel="Shortcut Icon" href="http://localhost/wp-content/themes/MyTheme/favicon.ico" type="image/x-icon">
    <link rel="stylesheet" href="http://localhost/wp-content/themes/MyTheme/style.css" type="text/css" media="screen">
    <link rel="pingback" href="http://localhost/xmlrpc.php">
    <meta name="robots" content="noindex,nofollow">
    <link rel="EditURI" type="application/rsd+xml" title="RSD" href="http://localhost/xmlrpc.php?rsd">
    <link rel="wlwmanifest" type="application/wlwmanifest+xml" href="http://localhost/wp-includes/wlwmanifest.xml">
    <link rel="index" title="blog" href="http://localhost">
    <meta name="generator" content="WordPress 3.2.1">
        <style type="text/css">.recentcomments a{display:inline !important;padding:0 !important;margin:0 !important;}</style>
    </head><body>
    <div class="bannerArea">
      <div class="container">
        <div class="bannernav"><a href="#">Privacy Policy</a> • <a href="#">Contact Us</a> • <a href="#">Site Map</a></div>
        <!--Title and description start-->   
        <img src="images/banner_logo.gif" width="223" height="51">   
        <!--Title and description end-->   
        <div style="clear:both;"></div>
      </div>
    </div>
    <!--Navbar start-->
    <div class="topnavigationArea">
      <div class="container">
        <div class="topnavigationgroup">
          navigation goes here
        </div>
        <div style="clear:both;"></div>
      </div>
    </div>
    <!--Navbar end-->
    <div class="contentArea">
      <div class="container">
        <div class="contentleft">
          <!--Here's where the loop starts-->
          <!--Post box begin-->
          <div class="box">
            <h2 class="posttitle"><a href="http://localhost/?p=1">
              Hello world!          </a></h2>
            <p class="metablock"><span class="meta">Posted on
              October 11, 2011          by
              <a href="http://localhost/?author=1" title="Posts by Matt Keefe" rel="author">Matt Keefe</a>          </span><span class="postcomments">
              <a href="http://localhost/?p=1#comments" title="Comment on Hello world!">1 Comment</a>          </span></p>
            <div class="entry">
              <p>Welcome to WordPress. This is your first post. Edit or delete it, then start blogging!</p>
                      </div>
            <!--<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
                xmlns:dc="http://purl.org/dc/elements/1.1/"
                xmlns:trackback="http://madskills.com/public/xml/rss/module/trackback/">
            <rdf:Description rdf:about="http://localhost/?p=1"
        dc:identifier="http://localhost/?p=1"
        dc:title="Hello world!"
        trackback:ping="http://localhost/wp-trackback.php?p=1" />
    </rdf:RDF>-->
          </div>
          <!--Post box end-->
          <!--Next is what happens if no posts are found-->
                <p>
                  </p>
        </div>
        <!--sidebar start-->
    <div class="contentright">
        <div id="search">
        <!-- Search form in sidebar. Alternatively you can save the search form code as search.php and use a PHP include. -->
        <form method="get" id="searchform" action="http://localhost/">
          <input type="text" value="Search our site..." name="s" id="searchbox" onfocus="if (this.value == 'Search our site...') {this.value = '';}" onblur="if (this.value == '') {this.value = 'Search our site...';}" size="15">
          <input type="submit" value="search" id="searchbutton">
        </form>
        <!-- Close search form -->
      </div>
      <h2>About My Blog</h2>
      <p>This is a sample region where you can tell your blog visitors a little about you.</p>
      <h2>Archives</h2>
          <li><a href="http://localhost/?m=201110" title="October 2011">October 2011</a></li>
      <h2>Categories</h2>
          <li class="cat-item cat-item-1"><a href="http://localhost/?cat=1" title="View all posts filed under Uncategorized">Uncategorized</a>
    </li>
        <div class="clearer"><!-- Clear floats--></div>
    </div>
    <!--sidebar end-->
        <div style="clear:both;"></div>
      </div>
    </div>
    <!--Footer start-->
    <div class="footerArea">
    <div class="container">
    <div class="copyright">
    Copyright © 2010 <a href="http://localhost/">
      blog  </a> <a href="#">Terms of Use</a> | <a href="#">Privacy</a> | <a href="#">Contact</a></div></div></div>
    <!--Footer end-->
    </body></html>

  • Testing Server / 'Live View' not working

    Hey guys, I'm trying to create my first e-Commerce site in Business Catalyst and having a bit of an issue with setting up testing. I've downloaded multiple basic templates from 'BC' and they all seem to be giving me the same issue.
    Issue:
    When using Dreamweaver CC's 'Live View' (which seems to be a one stop shop for testing changes without them pusing to the live site) the encompassing template in a page is displayed correctly, but the content area always displays 'Page not Found'. Take a look at the attached image to see exactly what I mean.
    I've contacted support and browsed the form, but it seems I am the only one with this issue. Again I've tried it with multiple templates on multiple computers. Am I missing something simple? What does everyone else use for testing? Please help.

    Hi,
    When you press the "Live" button in Dw, it asks you if you want to save the file before putting. If you select No, and there's also NO such file on the server, then you'll have the "Page not found" message displayed.
    Hope this helps.
    Kind Regards,
    Alex

  • Live View Updates Extremely Slow in DW 5.5

    I'm having a problem with the Live view update. I'm using the localhost as my testing server.  So, network speed shouldn't be an issue.  I'm on a Windows 64 bit, 2.2 gHz, Quad Core, 8 GB ram..so it should run relatively well.  But, I sometimes have to wait 2 minutes for the screen to update when I change something, turn off LiveView, then turn it back on.  You can imagine how this slows down development.  Every change takes 2 minutes to see?  Yikes!  It makes the product almost unusable. 
    Is there any fix for this?

    Last night, I got the solution to this from Adobe tech support -- at least for me.  The technician suggested that I update my video card driver.
    And also make sure that I had the latest version of Flash  player.  Apparently, CS5.5 has adopted a new way of previewing files that relys heavily on the video cache and the player, and old drivers are usually the problem. 
    I did this, and things work much better.  Still a bit doggy at times, but I can work with it.
    He also suggested that I upgrade to Windows 7.  (I'm still using Vista)  ANd that I would see a "100% improvement".  I like the sound of that.  Haven't tried it yet....If anybody does, let me know how it goes.
    :<)McFrisco

Maybe you are looking for