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. Dialog events not showing

Dialog events not showing

Scheduled Pinned Locked Moved C / C++ / MFC
helpcsharpvisual-studioquestion
4 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.
  • L Offline
    L Offline
    ldaoust
    wrote on last edited by
    #1

    I really need help on this one. I have a VS6 app that I loaded in VS.NET 2003. Convertion ok, compile ok, runs ok. Now, I don't know what happend but the control IDs dont get listed in the events pane of dialog properties. Also, if I choose 'Add variable' from the context menu after right clicking a control, the add variable dialog does not allow me to add a 'control' variable. The "Control variable" check box is disabled. Looks like some link between the resoirce IDs and the dialog properties in VS is broken. Hope I explain this clearly enough. Anyone has an idea why this is happening, I been on this probleme for quite a while and really need a way to fix this. ?


    Louis * google is your friend *

    V L 2 Replies Last reply
    0
    • L ldaoust

      I really need help on this one. I have a VS6 app that I loaded in VS.NET 2003. Convertion ok, compile ok, runs ok. Now, I don't know what happend but the control IDs dont get listed in the events pane of dialog properties. Also, if I choose 'Add variable' from the context menu after right clicking a control, the add variable dialog does not allow me to add a 'control' variable. The "Control variable" check box is disabled. Looks like some link between the resoirce IDs and the dialog properties in VS is broken. Hope I explain this clearly enough. Anyone has an idea why this is happening, I been on this probleme for quite a while and really need a way to fix this. ?


      Louis * google is your friend *

      V Offline
      V Offline
      Viorel
      wrote on last edited by
      #2

      Since your problem is difficult to reproduce, I would suggest you to perform a test: make a simple new application in VS 6 (of the same type -- MDI, Dialog-based, etc.), and then convert it to VS 2003 (hope you have VS 6). Then see if the same problem appears. I think the problem can be caused by some missing special comments (like "//{{AFX_MSG", used widely by older VS wizards) accidentally deleted from source files.

      L 1 Reply Last reply
      0
      • V Viorel

        Since your problem is difficult to reproduce, I would suggest you to perform a test: make a simple new application in VS 6 (of the same type -- MDI, Dialog-based, etc.), and then convert it to VS 2003 (hope you have VS 6). Then see if the same problem appears. I think the problem can be caused by some missing special comments (like "//{{AFX_MSG", used widely by older VS wizards) accidentally deleted from source files.

        L Offline
        L Offline
        ldaoust
        wrote on last edited by
        #3

        Hi, If I remember, I think that it was working at some point. So, for sure, I must have broken something. I have other apps that I converted and I dont have this problem. I have been comparing with other projects t osee what can be different but with no avail. If I'm not mistaking, the "//{{AFX_MSG" and others similar, are not used anymore by VS.NET. So even if they are not in the source file it wont affect. In fact, new classes created for new dialogs dont have any of those special comments (tags). Heres some more info. If I click a control on a dialog form to select it, then the event pane in the properties fills with the pssible notification messages for that control. This works normally. If there is a function handler to a notification message it is also listed. I can also add a new handler to the seelcted control this way. Control Ids dont get listed only when the dialog is selected, when usually all the control IDs would appear. The biggest problem I have with this, and which is causing me a lot of delays, is that I cannot add control variables.


        Louis * google is your friend *

        1 Reply Last reply
        0
        • L ldaoust

          I really need help on this one. I have a VS6 app that I loaded in VS.NET 2003. Convertion ok, compile ok, runs ok. Now, I don't know what happend but the control IDs dont get listed in the events pane of dialog properties. Also, if I choose 'Add variable' from the context menu after right clicking a control, the add variable dialog does not allow me to add a 'control' variable. The "Control variable" check box is disabled. Looks like some link between the resoirce IDs and the dialog properties in VS is broken. Hope I explain this clearly enough. Anyone has an idea why this is happening, I been on this probleme for quite a while and really need a way to fix this. ?


          Louis * google is your friend *

          L Offline
          L Offline
          ldaoust
          wrote on last edited by
          #4

          Finally found the problem, so I post the solution here for anyone else that would stumble on this problem. My original project was a VC6 project. It was converted by VC7. At this point I think resources were ok. I was using two resource files in this project, just to split them up so it is easier to work in a team environnement. I also was including a resource file from another project which is a global library for many of our projects. I am not to sure how the problem occured, but the project lost track of which of the resource file was the main resource file. The main resource file is saved in the .vcproj file. At the end of this file there is a <Globals> then a <Global> section in which the main resource file path appears. Mine was pointing to the wrong one, after putting back the proper path, everything was back to normal. Took me a while to find this after trying several things. Case closed.


          Louis * google is your friend * -- modified at 10:51 Tuesday 11th July, 2006

          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