Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • World
  • Users
  • Groups
Skins
  • Light
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Code Project
  1. Home
  2. General Programming
  3. C / C++ / MFC
  4. ShellExecute/Browser problem

ShellExecute/Browser problem

Scheduled Pinned Locked Moved C / C++ / MFC
comhelpquestiondiscussion
3 Posts 3 Posters 0 Views 1 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • L Offline
    L Offline
    Leslie Sanford
    wrote on last edited by
    #1

    I have an application with an About Dialog Box. The dialog displays an image, and when you click part of the image, a browser opens that takes you to a website. So far, so good. But what I'm finding is that if I close the browser immediately after it opens, it locks up for a few seconds with a blank, white screen. Eventually the browser closes. If I wait, say, ten seconds or so after the browser opens to close it, it will close immediately with no problems.. Here's my code for opening the browser:

    ::ShellExecute(NULL, "open", "http://www.lesliesanford.com", NULL, NULL, SW_SHOWNORMAL);

    Nothing really special there. Any thoughts or clues? EDIT: Interesting. I just noticed that this problem occurs when I open IE outside of my application. This seems to be a problem that's independent of my app, i.e. my app's not causing it.

    R B 2 Replies Last reply
    0
    • L Leslie Sanford

      I have an application with an About Dialog Box. The dialog displays an image, and when you click part of the image, a browser opens that takes you to a website. So far, so good. But what I'm finding is that if I close the browser immediately after it opens, it locks up for a few seconds with a blank, white screen. Eventually the browser closes. If I wait, say, ten seconds or so after the browser opens to close it, it will close immediately with no problems.. Here's my code for opening the browser:

      ::ShellExecute(NULL, "open", "http://www.lesliesanford.com", NULL, NULL, SW_SHOWNORMAL);

      Nothing really special there. Any thoughts or clues? EDIT: Interesting. I just noticed that this problem occurs when I open IE outside of my application. This seems to be a problem that's independent of my app, i.e. my app's not causing it.

      R Offline
      R Offline
      Renjith Ramachandran
      wrote on last edited by
      #2

      yeah! it puzzled me first, because the same thing has been done by a dozen times by me, nothing went wrong then. so please update if you find a solution of that ( even if its nothing to do with your app )

      Never Work Hard! - Work Smart!!! www.indianITforum.com

      1 Reply Last reply
      0
      • L Leslie Sanford

        I have an application with an About Dialog Box. The dialog displays an image, and when you click part of the image, a browser opens that takes you to a website. So far, so good. But what I'm finding is that if I close the browser immediately after it opens, it locks up for a few seconds with a blank, white screen. Eventually the browser closes. If I wait, say, ten seconds or so after the browser opens to close it, it will close immediately with no problems.. Here's my code for opening the browser:

        ::ShellExecute(NULL, "open", "http://www.lesliesanford.com", NULL, NULL, SW_SHOWNORMAL);

        Nothing really special there. Any thoughts or clues? EDIT: Interesting. I just noticed that this problem occurs when I open IE outside of my application. This seems to be a problem that's independent of my app, i.e. my app's not causing it.

        B Offline
        B Offline
        Bram van Kampen
        wrote on last edited by
        #3

        Seen this problem many a time. Nothing to do with your Programming skills, apart from, why did you call this Browser App in the first place. This has to do with different threads having to do many things on a finite computer. Calling a Website is 'Expensive'. It typically involves downloading scripts, which gives you the next script title to download. These things take time to do, and things to dismantle! This won't be sorted untill we have: -1500 GB Drives as Standard -1500 MB Memory as Standard -1500 MB/S Network Connections -At the Same time, Everyody in Microsoft thinks that we are working with 10GB drives and 10GB Memory.and 1GB Connections. :rolleyes:

        Bram van Kampen

        1 Reply Last reply
        0
        Reply
        • Reply as topic
        Log in to reply
        • Oldest to Newest
        • Newest to Oldest
        • Most Votes


        • Login

        • Don't have an account? Register

        • Login or register to search.
        • First post
          Last post
        0
        • Categories
        • Recent
        • Tags
        • Popular
        • World
        • Users
        • Groups