So the GroupBox i am trying to place is larger than the screen real state of the designer in visual studio.
Hence i scroll to make room however after scrolling whenever i try to re-size the groupbox the designer immediately scrolls back to the center of the control making it immpossible for me to re-size the control.
Is this some sort of bug or am i doing something wrong it was working fine previously and suddenly i have this problem now tried closing and reopening VS but the problem is still there.
I Should probably add that i am using telerik's radforms.
Related
I have made several controls over the past time through Folder > Add > User Control, then dragging an ObjectListview onto the designer and setting anchor/ dock etc then implementing the code.
Since this morning when drag an Objectlistview onto a control, it shows up as a component in the bottom tray instead of on the control's design canvas.
I can't remember installing any updates on either visual studio or the ObjectListview NuGet package, it's still 2.9.5 from 2017. The behaviour is the same in Visual Studio 2017 and 2019 preview..
I did install .Net Core SDK 2.2.402 ealier this week but this project references Framework 4.6.1..
When I add a standard TreeView or ListView etc onto the form they get added normally.
I'm comparing the code with other controls I created this way, both derive from UserControl. The control that works as normal has the line near the end of InitializeComponent()
this.Controls.Add(this.objectListView1);
For some reason for new controls I create that line isn't generated by the designer for ObjectListview.
If I manually add that line to InitializeComponent() the control does show up on the design canvas but I can't select it or do anything with it.
Does anyone have any idea what could cause this changed behaviour and how to fix this? I'm working sundays b/c I'm very busy this is really messing me up.
I was able to fix by uninstalling and reinstalling the nuget package.
So I've seen a couple of questions about Visual Studio's Ctrl+Tab but none of them were referring to my problem
My Visual Studio will randomly start acting funny. Sometimes, when I hit on Ctrl+Tab to change tab, the navigation pane appears for half a second an disappears. If I hold Ctrl+Tab, it'll just appear and disappear constantly, disappearing too early to even switch one tab. When it disappears it gives the keyboard focus back to whichever document I was on (so no other program actually intercepts the focus)
Then it will randomly accept my Ctrl+Tab and stay on screen once every X tries for some reason.
I double-checked my Visual Studio parameters (which have never changed) and the shortcuts are correctly set: Ctrl+Tab to Window.NextDocumentWindowNav and Ctrl+Shift+Tab to Window.PreviousDocumentWindowNav. I try removing them and resetting them with no success.
Anyone ever had this problem? I don't know what is intercepting my Ctrl+Ctrl+Tab. When I restart Visual Studio, it'll work fine again for a while until at some point Ctrl+Tab messes up again for no reason.
Anyone ever had this bug? Any tips on how to figure out what it's from and how to fix it? I'm on Visual Studio 2013. If it's any help, I also have Resharper 8.2.1 with it
Thanks!
EDIT
A few extra details:
Disabling Resharper doesn't remove the problem, still happens
I tried setting the NextDocumentPaneNav shortcut to another combination, bug still happened
So basically it's not another running program catching Ctrl+tab for some reason, it's literally Visual Studio not willing to show the navigation pane for more than a micro second
I'm using the Visual Studio 2013 form designer to edit a form. The size of the form in the designer window is too big so I want to zoom out.
In applications like Photoshop or Blend I could (among other things) use the keyboard shortcut Ctrl-0 to fit the design to the screen.
In Visual Studio how do I zoom out in the form design window?
The Windows Forms designer doesn't zoom. The WPF one does because it's vector based, but WinForms is pixel based you don't get the zooming.
If you've got multiple monitors you can drag the designer to a second screen and work with it that way, or you can press Alt+Shift+Enter to toggle full screen and work with it that way.
in VS 2022 I've been doing some C# and had the same problem with the default grid element (the form) being zoomed way out in the Designer, so it looked extremely small, and the controls were super tiny. I found the following Microsoft page that explains how to change the zoom feature (yes, Visual Studio 2022 has a zoom feature). https://learn.microsoft.com/en-us/dotnet/desktop/winforms/controls/how-to-set-grid-options-for-all-windows-forms?view=netframeworkdesktop-4.8
So, I went into the Tools menu, down to Options, and then in the Options window I scrolled down to the XAML Designer General option. I changed the "Zoom by using" setting to "Mouse Wheel". Using "Ctrl + Mouse Wheel" didn't work for me. And I changed the "Default Zoom Setting" to "Last Used". I closed VS and opened it again. "Last Used" didn't work for me. So, I changed the "Default Zoom Setting" back to "Fit all". Closed VS again (you need to do this for the new settings to take effect). Opened VS again. And everything worked. I am able to use the mouse wheel to zoom in and out of the form. The settings I'm using are "Mouse Wheel" and "Fit All".
While position stuff in a .aspx using a Master Page, I lost the the ability to scroll horizontally using the scroll bar in design view of visual studio 2012. The bar is greyd out like if it was disabled.
Altought, I can still see the whole page in a browser.
Does anyone know of a way to fix this?
Thanks
I'm using the android designer in visual studio 2010, and I can put things on the layout without a problem. when i click to change the view from '4in WVGA (Nexus S)' to anything else, the background 'bounding box' changes size, but the content does not resize.
This happens even if I just create a brand new layout and don't put anything onto it.
Also, when I try to apply different themes, nothing changes. Anything I'm doing wrong, or is it a bug?
Found out that this is a known bug. MonoDevelop works fine. I assume they're working on it.