For some time I have been struggling with this glitch in MFC.
It can be easily observed.
In Visual Studio 2012 Update 1 create a new MFC application,
in wizard settings set Multiple documents/Tabbed documents, Office 2007 Black style
run the application on Windows 7:
Application launched while Windows 7 Aero theme is on:
Theme in Windows control panel set to Windows 7 Basic:
Theme in Windows control panel set back to Windows 7 Aero:
Notice the unpainted gaps when aero off, and black title with missing close button when aero back on.
This problem has always been around,
in Visual Studio 2010 wizard generated application used to work ok with themes switching through Windows control panel, but still showed black title after aero was disabled/reenabled with DwmEnableComposition() API call.
I hoped that in Visual Studio 2012 the problem was sorted out, but seems it was not.
So what can I do to workaround the bug?
I suppose that Windows Aero Glass background is broken after hibernate. How can I solve this? is basically the same problem.
Hence the answer to that question should be what you are looking for.
Related
After reinstalling win10 and vs2017 in my old HP255G, the vs design window exhibits weird behavior.
Empty property, tools with usercontrol disabled.
Unmanageable controls.
Same problem with my new Lenovo IdeaPad 3 hdpi plus blurry font in the code window.
Identical problems with Vs2019.
Try pressing F4 key the property tab will auto populate.
I have to maintain a legacy codebase which for a variety of reasons, can only be worked on in Visual Studio 2008.
I noticed the Tool Windows' buttons for Menu, Pin, and Close have their icons replaced with the letters "H D A" or "H B A".
Whereas on Windows Server 2008 R2 (Windows 8.1) it looks like this:
My guess is that the font it uses for the buttons is either missing or being overridden. Does anyone know what font it is (so I can see if it's missing) or some other fix?
After running Windows 10 for a few weeks I noticed the Visual Studio 2008 tool window caption buttons have been restored to their correct appearance without me having to do anything specifically, weird. No bug then, I guess :)
I have something really weird going on and don't know where the problem lies..
I recently started working on a Lenovo X1 Carbon with touchscreen. When working with the touchpad or external mouse there seems to be some kind of a bad offset when clicking inside my visual studio working pane.
I have to click on the row above to get my cursor to be set on the row below. This ONLY happens in Visual Studio's working pane.
I need to click on the red square to get my cursor on the place it is in the picture and I have NO idea how to fix this :-( I couldn't find any problem like this on the web.
I'm working in Visual Studio Enterprise 2015 on a brand new system with all drivers up to date. Running Windows 10 enterprise on a UHD display, so my DPI is set at 200% and perhaps the problem lies here...
Visual Studio 2012 crashes when open a form that contains a Visio 2013 Preview Drawing control. (Microsoft Visio 15.0 Drawing Control - Com Component).
Steps to reproduce this issue.
Open Visual Studio 2012
Create a new Windows Forms Application (C#)
Add COM Component Microsoft Visio 15.0 Drawing control to toolbox.
Place Visio Drawing Control on Form2.cs[Design].
Save all files, project and solution.
Close Form1.cs [Design] in the Visual Studio 2012 IDE.
Double click Form1.cs in the Solution explorer to edit form [Design] view.
Visual Studio Application Crashes at this point.
Is this a known bug in Visio 2013 Preview.
Using the Visio 2013 Drawing Control in VB6 applications also produces a similar result with &H80004005 (-2147467259) error message shown.
Our product makes use of the Visio 2013 control in a VB6 application. It is also an issue in Visual Studio 2012.
Any ideas of what is going on?
This is indeed a known bug: See http://connect.microsoft.com/VisualStudio/feedback/details/766229/visio-2013-preview-drawing-control-on-a-windows-forms-application-crashes
The best workaround I could come up with so far was to instantiate the drawing control in code only. In other words. Don't drag it onto your form (etc.) from the toolbox in the IDE but only create and instantiate the control from within the code. That way the control does not appear in the GUI form editor and it will not freeze your Visual Studio instance.
If you are not sure how to do that you can always drag it temporarily to your form and lift the relevant code for the control from your FormName.Designer.cs (or .vb) file.
Mind you my experience is with VS2012 only. I am not sure if you can even use the control in VB6 (don't have it installed to test).
Option Explicit
Private WithEvents moo As Visocxctl.DrawingControl
Private Sub Command1_Click()
Set moo = Form1.Controls.Add("VisOcx.DrawingControl.1", "VisioRuntime")
moo.Left = 0
moo.Top = 0
moo.Visible = True
End Sub
Try this workaround:
Visio Drawing Control Fails in Visual Studio 2012.
Replace Office14 with Office15 for Visio 2013. I could successfully drop the control in design-time and run a sample windows form application. This is a known bug in VS2012 when working with any version of Visio drawing control.
I tried it with two different mice- both of which work perfectly fine in all other applications. The mouse is MS Intellimouse Optical. I even tried to speed up the vertical scroll through the mouse utility and still nothing.
It barely moves the code a tiny bit and then it stops. I had no problems at all with VS 2008 which is concurrently installed in the same machine.
Am I the only one having this?
You can also make the IntelliPoint application (ipoint.exe) to run as administrator on Windows 7.
I tried this on Windows 7 Machine and it worked for me. Go to Contol Panel -> Mouse -> heel Tab -> Select the radio button "Use Microsoft Office 97 Scrolling Emulation Only" -> Click Ok
I had this issue on my machine and I tried a lot but got nothing. Then I also tried installing VS SP1 also but the problem persisted. Then I tried above method and I am happy that it worked for me.
Just disable the "smooth scrolling" in mouse configuration (control panel). Worked fine to me.
Same issue here in Windows 7 with Visual Studio 2010 and 2012. I have Lenovo Mouse Suite 6.45
1.Control Panel - View by : Large Icon
2.Mouse
3.Lenovo - Adavnce Properties
4.Select Wheel Tab
5.change settings to "Use Microsoft Office 97 Scrolling Emulation Only"