This is the popup I mean:
It happens to obscure the indicator margin for a couple of lines, making it impossible to drag the current statement indicator to those lines.
The "Debugging" toolbar has a button called "Show threads in source":
Turn it off to disable this pop-up, along with the messy-looking graphic underneath the current statement indicator:
(took me far too long to find this, and Googling didn't help, hence this answer... it doesn't help that this button cannot be found by searching for "thread"in the otherwise excellent Quick Launch search box)
Related
Hi, does anyone know what is it on the left?
It is unfoldable, non-draggable, useless and empty area across entire code. It appears in every opened class. If you click on it, you'll set a breakpoint. You can not collapse it. I do not remember how or why I got this, but then I didn't find any key or menu or button combination to heal this bug.
THis is the last Android Studio 3.6.3. And the same was before upgrade.
Please help, it eats my space and nerves!
UPD Gutter icons look ok.
Maybe your gutter icons are messed up. Check via the settings or the context menu on the gutter (i.e. where the line numbers are).
After 2 months of terribly inconvenient work I finally found the cause. To turn it off do
View - Appearance - Exit Distraction Free mode.
Amazingly, but this big white indent was intended to not distract me (from what? nothing else has changed).
This is hopefully pretty straight forward, but after an hour of searching online, I couldn't find anyone else complaining about this issue. Perhaps I just haven't found the right wording to describe it.
My company recently switched to Excel 2016, and I HATE the way the scrollbars work. If you drag the scrollbar with the mouse, your current view freezes in place until you 'drop' the scrollbar. Then the screen suddenly jumps to this part of the spreadsheet. It used to actively display the spreadsheet as you dragged the scrollbar around, so you could see everything as you moved around.
I constantly work with enormous spreadsheets where I need to find specific sections quickly, and now that the scrollbar has become useless, it takes me much longer to navigate.
I understand you can use the arrow keys, or different shortcuts to jump through a spreadsheet, but I found the scrollbar very useful when moving through very large files. I can't be the only person who wants this functionality turned back on, but I can't find any information on it, or any settings I can switch.
This fix works for me. In Win 10 open Control Panel. Navigate to: Control Panel\All Control Panel Items\Ease of Access Centre\Make the computer easier to see. Near the bottom in the section "Make things on the screen easier to see" is a tick-box: "Turn off all unnecessary animations (when possible)". This was ticked for me by default so I unticked it and clicked the Apply button after which the scroll bar in Excel started to work as it does in Win 7, i.e. the cells in the background move as you drag the scrollbar left/right and up/down. Perfect.
I'm using the Application.CommandBars.Add method to create a custom PopUp menu.
I'm on a Mac with OS 10.8 and using Excel for Mac 2011.
I get a Help button at the top of menu that I didn't ask for. It does work, as in it launches the Help Center. I just don't want it on this right-click menu. None of the code examples or discussion threads that I have found by searching this and other sites mention anything about this. How does it get there and what I can do to remove it?
I can't get at it with an index to the controls, or by its name:
CommandBars(MyMenu).Controls(1).Delete ........... removes my first command button ("Button 1")
CommandBars(MyMenu).Controls(0).Delete ........... fails - subscript out of range (duh)
CommandBars(MyMenu).Controls("Help").Delete ... fails - invalid argument
And likewise with trying to make it ".Enabled = False" or ".Visible = False".
Is there a way to get at it with the "Id:=30010"?
Is there some argument or property to the CommandBars.Add or ShowPopup methods that will tell it, "Don't 'Help' me so much, thanks."?
The code is exactly what you find on the MSDN site example for Creating Popup Menus so I won't add that here.
I don't have enough reputation points to post the screen snapshot of what it looks like when displayed with a Right-Click event. There is a "Help" button at the top of the menu, a separator line, then the buttons I defined on the menu.
When I'm testing my app on a mouse-driven device, I'm seeing a couple of odd highlight issues that I would like to try and resolve.
The first occurs when I call up the app bar, hover the mouse over a button (at which point the button goes grey) and then press Escape to dismiss the app bar. If I then call up the app bar again, the button has stayed grey, even if the mouse isn't over it, and remains in that state until I move the mouse over it and then away again.
I can't immediately see a property of the button that I can reset to clear that state when the app bar gets dismissed.
The other oddity I'm seeing is that sometimes the first item in the list on the page will get a box drawn around it:
This seems to happen when the app bar is being dismissed. I'm guessing that this is because the item is in a particular state that causes the box to appear but I'm not sure what state or how to clear it. The box does not appear during normal use of my app.
Thanks for any clarification or solutions you can provide.
I found a simple way to workaround this issue. In the code for Clicked/Tapped set Visibility of the button:
CreateNewDatabase.Visibility = Visibility.Collapsed;
CreateNewDatabase.Visibility = Visibility.Visible;
It will reset button state to Normal.
Hope this helps!
So, the issue is that the VisualState for the Button is being set to PointedOver, and then not being unset (because your mouse isn't leaving the bounds of the control and therefore triggering a PointerExited event). What this means is that you'll have to manually set the VisualState of the Button if you want it to change in this manner. You could do it on AppBar's Closed event. Basically, do a recursive check of all Children of the Content property of the AppBar using the VisualTreeHelper. Check to see if the Child is a Button. If it is, set its VisualState using VisualStateManager.GoToState().
I've also figured out what was causing the black box around the button - it is to indicate that the button has Focus.
The rather strange thing is that I'm not really sure why that specific button is getting focus or how a user is supposed to give focus to a button without it just randomly happening so, until I figure that out, I've decided to comment out the Focus state support from the Visual Manager XAML used in the default GridView item style.
I have an interesting (but frustraring) problem. I have an application which uses the full screen (this is meant to simulate a third-party fullscreen POS application).
My application displays a sequence of modeless dialog boxes on top of the full screen application. It shows one, hides it, then shows the next, hides it etc. After the 3rd show, the Windows taskbar appears about 1 second later. I can't figure out why.
I've stripped my code right back to see if its something I'm doing in my OnNcActivate handler (which I use to draw my skinned window) but I don't think it is as the problem appears to be timing related. I've tried running Spy++ as well as dumping messages in m WindowProc myself and I still can't see anything odd that would give me any clues.
There are some messages with ID 0x36e in my logs but I can't find out what they are supposed to be. I've checked various message ID lists and can't find them. They shouldn't be any message IDs of my own since WM_USER doesn't start until 0x400.
I know I could get around this problem by auto-hiding the taskbar but I can't ask our customers to configure their taskbars to auto-hide to get round my problem.
Any ideas why the taskbar would appear in relation to my modeless dialog boxes?
EDIT: I completely stripped out my self-drawn GUI code and I still have the same problem. I could be wrong but it would seem that when I call ShowWindow( SW_HIDE) first, Windows tries to activate "another Window" (as it says in MSDN). I think in this case its activating the taskbar rather than the POS application. If on the other hand I open my second window before calling ShowWindow( SW_HIDE ) on the second, then it seems to behave itself.
Cheers
Sparky
Following a long discussion I come to the conclusion that DestroyWindow was not the problem. I found in the end that displaying a dialog.. clicking on the POS, then clicking back on the dialog that sometimes the taskbar would appear. I have spent an entire week trying to find reasons for all of this but to no avail. I thought that assigning the POS window as the owner would solve the problem - it didn't. In the end the solution for my problem was to determine if the taskbar is obscured completely before showing my dialog. If it is, I hide the taskbar for the duration which my dialog is displayed (set its placement to SW_HIDE) and then set it to SW_SHOW when I close my dialog. The task bar doesn't pop up and annoy people anymore. Not a fantastic solution for other peoples' applications perhaps, but perfect for our customers.