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. Weird problem - UI related

Weird problem - UI related

Scheduled Pinned Locked Moved C / C++ / MFC
c++helpquestionbeta-testingdesign
3 Posts 2 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.
  • D Offline
    D Offline
    Don Miguel
    wrote on last edited by
    #1

    Needles to say, not a directly Visual C++ question, but a weird one, clearly related to intimately Win32 API. To make a long story short: - I developed a desktop application, using MFC and having, among other controls a list control. - During development ant testing, everything looked OK. - As a must, when the application is installed on a real user machine, it must register itself in "run at startup applications" (Registry locale machine key), and start a dialog, where some data is displayed (loaded in the list control) And now come the WEIRD thing: on one of the machines, used for testing, the application failed to instantiate... because the List control was not instantiate. In other words, the application UI started before common controls being available!!! Is such a thing possible??? Did anybody encounter such situation before? Does anybody heard about such a weird problem in his experience?? Did exist a remedy?? Of course, I did not take in consideration a hack, like a "sleep" in my application startup... what make me worry is the situation itself. What is particular on machine I experienced the situation is that at machine starup, a service start and took most of machine resources for a while. In this time, I was able to log on (a Windows 2000 machine), and my application started immediately, with the error. Did anybody hear somethiing like that?? For me, it sounds like Windows OS is not able to fully load its UI libraries, before application start... and this is weird, could be such a flaw? This lead a door to serious problems in how UI is designed... I will search myself further, but I also want your feedback, if such situation was encountered by someone. I mention of course that, if the apllication is started late enough, it work normally on that machine. So, I'm not intrested in advices, but just in situation I mentioned: is possible that UI resources, needed by a desktop application, don't be available, at a certain moment?? :wtf: - is a windows system!!!!!! Any information with such a issue is greatly apreciated. I can reformulate the problem, to avoid false hints: when is user32.dll loaded by OS, during the boot process?? Regards.

    D 1 Reply Last reply
    0
    • D Don Miguel

      Needles to say, not a directly Visual C++ question, but a weird one, clearly related to intimately Win32 API. To make a long story short: - I developed a desktop application, using MFC and having, among other controls a list control. - During development ant testing, everything looked OK. - As a must, when the application is installed on a real user machine, it must register itself in "run at startup applications" (Registry locale machine key), and start a dialog, where some data is displayed (loaded in the list control) And now come the WEIRD thing: on one of the machines, used for testing, the application failed to instantiate... because the List control was not instantiate. In other words, the application UI started before common controls being available!!! Is such a thing possible??? Did anybody encounter such situation before? Does anybody heard about such a weird problem in his experience?? Did exist a remedy?? Of course, I did not take in consideration a hack, like a "sleep" in my application startup... what make me worry is the situation itself. What is particular on machine I experienced the situation is that at machine starup, a service start and took most of machine resources for a while. In this time, I was able to log on (a Windows 2000 machine), and my application started immediately, with the error. Did anybody hear somethiing like that?? For me, it sounds like Windows OS is not able to fully load its UI libraries, before application start... and this is weird, could be such a flaw? This lead a door to serious problems in how UI is designed... I will search myself further, but I also want your feedback, if such situation was encountered by someone. I mention of course that, if the apllication is started late enough, it work normally on that machine. So, I'm not intrested in advices, but just in situation I mentioned: is possible that UI resources, needed by a desktop application, don't be available, at a certain moment?? :wtf: - is a windows system!!!!!! Any information with such a issue is greatly apreciated. I can reformulate the problem, to avoid false hints: when is user32.dll loaded by OS, during the boot process?? Regards.

      D Offline
      D Offline
      Daniel Turini
      wrote on last edited by
      #2

      Did you link MFC statically or dynamically? It looks like it could not find the MFC DLLs, but it's just a guess. Try the Dependency Walker tool to check your executable for runtime dependencies, and verify if the machine has all the appropriates DLLs, or link everything statically. I see dead pixels Yes, even I am blogging now!

      D 1 Reply Last reply
      0
      • D Daniel Turini

        Did you link MFC statically or dynamically? It looks like it could not find the MFC DLLs, but it's just a guess. Try the Dependency Walker tool to check your executable for runtime dependencies, and verify if the machine has all the appropriates DLLs, or link everything statically. I see dead pixels Yes, even I am blogging now!

        D Offline
        D Offline
        Don Miguel
        wrote on last edited by
        #3

        My application use MFC linked dinamically. Dependency walker did not report problems, and as I said, the application run normally, if I move it from startup programs. The problem, as you point, could be that MFC is not available (loaded) at the particular time when application start. But for me this is really weird. Thanks.

        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