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. Visual Studio
  4. Major bug in VS - Menus not displaying

Major bug in VS - Menus not displaying

Scheduled Pinned Locked Moved Visual Studio
helpvisual-studiotutorialquestionlounge
2 Posts 2 Posters 13 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.
  • S Offline
    S Offline
    SawmillTurtle
    wrote on last edited by
    #1

    There's a major bug that seems to affect projects at random, and I don't know how to fix it. I don't know if there's even a way to fix it. See, there's this weird thing that VS2019 does where it will suddenly, and without explanation, stop letting me access any kind of menu strips in the Designer. This includes Context Menu strips. With the Context Menus, they show up when I click the icon at the bottom of the Designer, but they're cut off, as if they're being drawn behind everything else. So I can only see the top half of the text of the first item in the menu. Trying to click on it results in the menu immediately disappearing. Regular Menu Strips that are a staple of GUI programs bring problems of their own. They don't vanish, but clicking on them does nothing. It's like they're just pictures of menus that are supposed to be there. They all operate as they should when the program is run, but there's another problem: without the ability to click on or interact with the menus, I can't set the click events using the functionality built into the editor to do so. When I want to add menu items, I have to go into the properties panel, find Collection, and manually set each item. Then, if there are sub menus for any of them, I have to go into the Collection for each of those and repeat the process. Getting them to work with mouse clicks is not impossible. I just go into the .Designer.cs file and hook into the events manually. It's not ideal. It's actually a pain in the REAR PELVIC SPLIT. What makes it worse is that closing VS and restarting does nothing. When I load the project again, the problem remains. Starting new projects does not present this problem, at least for awhile. Menus work... until VS breaks them again. It appears to be something that VS is doing to projects specifically, since it isn't a universal problem. There's some setting or some switch that gets flipped along the way that breaks certain functionality in the loaded project forevermore. Unless there's a way to fix it. That's what I'm really hoping for. I'm hoping someone has encountered this and found a way to repair the problem. Internet search results have suggested running a Clean on the code, which yielded no results at all. Other comments seem to suggest that Microsoft is quite aware that the problem exists and has for some time, but just don't care enough to fix it. I dunno. Please help? This bug is driving me insane. It slows down my workflow and annoys the living daylights out of me. Yes, there ar

    V 1 Reply Last reply
    0
    • S SawmillTurtle

      There's a major bug that seems to affect projects at random, and I don't know how to fix it. I don't know if there's even a way to fix it. See, there's this weird thing that VS2019 does where it will suddenly, and without explanation, stop letting me access any kind of menu strips in the Designer. This includes Context Menu strips. With the Context Menus, they show up when I click the icon at the bottom of the Designer, but they're cut off, as if they're being drawn behind everything else. So I can only see the top half of the text of the first item in the menu. Trying to click on it results in the menu immediately disappearing. Regular Menu Strips that are a staple of GUI programs bring problems of their own. They don't vanish, but clicking on them does nothing. It's like they're just pictures of menus that are supposed to be there. They all operate as they should when the program is run, but there's another problem: without the ability to click on or interact with the menus, I can't set the click events using the functionality built into the editor to do so. When I want to add menu items, I have to go into the properties panel, find Collection, and manually set each item. Then, if there are sub menus for any of them, I have to go into the Collection for each of those and repeat the process. Getting them to work with mouse clicks is not impossible. I just go into the .Designer.cs file and hook into the events manually. It's not ideal. It's actually a pain in the REAR PELVIC SPLIT. What makes it worse is that closing VS and restarting does nothing. When I load the project again, the problem remains. Starting new projects does not present this problem, at least for awhile. Menus work... until VS breaks them again. It appears to be something that VS is doing to projects specifically, since it isn't a universal problem. There's some setting or some switch that gets flipped along the way that breaks certain functionality in the loaded project forevermore. Unless there's a way to fix it. That's what I'm really hoping for. I'm hoping someone has encountered this and found a way to repair the problem. Internet search results have suggested running a Clean on the code, which yielded no results at all. Other comments seem to suggest that Microsoft is quite aware that the problem exists and has for some time, but just don't care enough to fix it. I dunno. Please help? This bug is driving me insane. It slows down my workflow and annoys the living daylights out of me. Yes, there ar

      V Offline
      V Offline
      Victor Nijegorodov
      wrote on last edited by
      #2

      Have you reported this "bug" to Microsoft?

      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