I've been using chrome for about a year steady. About a month back two weird behaviors happened. When I right click anywhere I get a black box. If I remember what the choices are in the box, I can use the arrow keys to select and it works.
The second problem is that when I mouse over anything, I don't get the tool tip text, I get some graphic display that looks like a very tiny version of some distorted text or graphics
Version 44.0.2403.125,
lubuntu
Menu> Settings> Show Advanced Settings > System menu >
Use hardware acceleration when available: turn it off
Related
I downloaded octave and accidentally pressed some buttons which changed the design of the software to be more specific it doesn't look like how my professor at university was working with it . Could you please help me to fix it in order to look like how it did in the beginning?
I upload a picture of how it looks like now
OK, it appears you are only looking at the Editor window, which is normally docked with other windows like the command window, documentation, etc. It also appears to be maximized, hiding everything else.
In the upper right you see two icons, one that looms like an x, and one that looks like two overlapping squares (two windows). If you click the x, that should close the editor and you should be able to see the rest of your desktop including the rest of the octave GUI. If you cannot see octave anywhere, of you are in Windows try using ALT-Tab or clicking on Octave in the task bar to make the window visible.
In the main octave window there should be a "Reset Default Window Layout" menu item under the Window menu. That should restore everything to the default layout without having to go to the trouble of a full reinstall.
The following YouTube video doesn't exactly match your problem, but it does show how to change and restore the GUI layout:
https://youtu.be/0USOvYHLqSU
So I'm trying to develop a webapplication and I'm trying to check it out on mobile.
I'm currently using Cordova and JQuery Mobile together with ripple.js to view my application in my browser.
The first issue (as far as I know) is that ripple.js will work best in Google Chrome, so this is my only test platform.
The second issue is that when I toggle Device Mode on, it doesn't show me the black dot (cursor) when I enter the rendered version.
I'll explain my situation or a scenario:
As an example I'll go to http://google.com
I press F12 to enter developer mode
I click the Toggle Device Mode button
I will see my cursor, until I enter the generated mobile canvas. While I would normally see a black transparant dot, I now see nothing.
I can however click and drag like I would normally do, but I can't see what I'm doing.
The things I already tried:
Reset all the flags back to default
Reset all developer tool settings to default
(edit) Installed a previous version of Chrome AND Chromium
So question is, how do I get my cursor back?
Extra: I'm using version 49.0.2623.87 m, but that's not related since my co-worker, has the same version and he sees the cursor.
(edit) currently I'm using the mouse option where I press Ctrl to see the circle which indicates where my cursor is, but this really has to be a temp solution.
(edit) I fixed it by doing a combination of things. So I'm not sure which exact thing fixed it. I removed a few programs that I installed after it still worked. I uninstalled about 4 of them. Also I did an update of my graphics card and then did a reboot. So it could be either the graphics card update, the software uninstall and/or the reboot.
I had the same issue. (note this question might be a duplicate of this one)
Following the advice on the Chrome forum here I changed the Quantization Range in my Intel HD Graphics Control Panel from "Default Range" to "Full Range". The touch pointer (grey circle) appeared immediately.
If that doesn't help you may have to change refresh rate too. Changing from 59p Hz to 60p Hz or some other refresh rate might help.
This should also help.
Open the mouse control panel.
Select the Pointer Options tab in the Mouse Properties window.
Then enable Display pointer trails option.
In case you don't like or are getting annoyed, like me, due to the trailer. Move the slider to the Short position and the trailer becomes near to non-existent or invisible.
I fixed it myself, yet I'm not exactly sure how I did it. I edited my original post and added the solution in the last paragraph.
Had the same on my Asus laptop with Chrome 66
Resolution that worked for me
Graphics Control Panel > Display > General Settings > Scaling > Change to Scale full screen.
OFF your Asus Eye Care Switcher.
I am posting this as answer because above mentioned answer didn't work for me but I had this issue when I had a monitor attached to my laptop, for development work. I played around with my display settings and discovered that IF the scale on my second monitor did not match the scale on my laptop, the mobile development mode cursor would disappear. (windows 10)
If this is an issue for anyone just go into Display settings -> Display -> Scale and Layout --> make sure that both your laptop/desktop matches the display scale of your second monitor.
Hope this will help.
Google Chrome shows a gray circle cursor when dev tools is active. Why is this happening and how do I make this stop?
Nov 29th, 2017 Update:
Quick Update brought to you by #Howdy_McGee.
Chrome 62 you have to Add Device Type, there's no longer an option for Show Device Type.
Why is this happening?
As Randy Hall points out below "This cursor indicates a "touch", such as your finger, for emulating touch events in (the) Chrome browser."
July 20th, 2017 Update: (version 59.0.3071.115) Just checking in again, looks like the below is still valid even through a bunch of Chrome updates. They have changed the wording of Show device type to Add device type. I've changed the wording below, but the image does not reflect the change.
They have also changed the way the device type settings work, explained below.
Once in responsive mode (via F12, then ctrl + shift + m) you will need to select the settings section indicated by the 3 grey circles, then select Add device type. Once you do this, a new drop down will appear next to the dimensions area, select Mobile (no touch). I imagine they did this so that you don't have to keep it on desktop and adjust the user agent type to a mobile device as I've described below.
What do the Device Types mean?
As of today (July 20th, 2017), the same settings for device type exist (as shown in the image above), but they work a bit differently than previously before:
Mobile: Now scales the content on the page when resizing the window (to accurately simulate pixel density on a mobile device). The circle that replaces your mouse, simulates a screen touch action when clicking (full fledged mobile development / testing).
Mobile (no touch): Also scales the content on the page when resizing the window, but continues to use your regular mouse cursor for your click actions.
Desktop: Does not scale content, uses regular mouse cursor (full fledged desktop development / testing).
Desktop (touch): Also does not scale content, but replaces your regular mouse cursor with a circle that will simulate screen touches on click.
But I still want to emulate a specific mobile device...
There is still a way to override the user-agent with this Mobile (no touch) setting set. When you're looking at your console (brought up via F12), you'll see the 3 vertical circles there next to the console tab, click them and bring up Network Conditions. Within this section you'll see that User agent is set to Select Automatically, just turn this off and use the drop-down to change to the user-agent you want to emulate as. This will allow you to emulate as a specific mobile device.
This cursor indicates a "touch", such as your finger, for emulating touch events in Chrome browser.
In the dev tools window, click the settings (gear) button in the bottom right. Go to the Overrides tab and disable Emulate touch events.
I'm posting this here because it took me a LONG while to find it via searches, and I know others have been having the same issue.
Update via Paulo Manuel Santos' comment:
From Chrome 32 the Emulation is configured in a different place. This is how I get to it: Elements, press Esc, Emulation, Sensors, Emulate touch screen
At july 2017 this option calls Add device type:
On Chrome 50 it seems the Emulation option is not available..
My workaround was to add a custom device with the 'Mobile (no touch)' option..
When you click this ICON to activate (change to blue); The Grey Circle CURSOR will appear as representing finger touch for devices, and Deactivating this will simulate desktop version and Showing POINTER Cursor.
None of the above answers worked for me... So after clicking the aforementioned 3 dots in the bottom right corner, I selected Settings and then Restore defaults and reload
It's not a clean solution, but I had just to choose a new dock side position and then I was back to work
Just deselect the Toggle device toolbar
https://i.stack.imgur.com/3lcFl.png
Once installing Fedora 19 Desktop Edition, I run the systray of Qt Example. But I could not look for the system tray icon.
There is no Notification area in the Activities overview.
Please let me know to display the notification area or the tray icon.
Moving your mouse quickly to the bottom right should display the Message Tray. If it doesn't work, use Super+M (windows key+M).
If you're running Synergy, the pressure sensitivity isn't working and you won't be able to use the mouse, because of this known bug. You must use Super+M.
Today I installed Ubuntu Gnome 13.10 and I couldn't find the Message Tray.
Moving the mouse down I made it appear some times. Finally I realized that it opened every time I moved my finger down on the touchpad two times.
I don't know if this interaction is intended or it is just a bug.
Super+M works too, thanks!
If you're willing to install the Frippery Bottom Panel.
The little exclamation point icon on the bar can be clicked to bring up the Message Tray too.
Clicking an item from the tray area or pressing Esc to cancel it, will remove the focus on the tray.
I don't know what I've switched on (by accident) but every time I have the Inspect Element area open and then try to click anything on the webpage not within the Inspect Element area (especially something jQuery related like a slideshow for example) it greys the page, shows a message saying 'Paused in debugger' and then opens a jQuery file within the Sources section of Inspect Element.
Within the 'Call Stack' area, it shows a message saying 'Paused on a "click" Event Listener'.
I don't remember switching this feature on but I'm keen for it to be switched off.
I know this question has been asked before - I thought I'd found the answer when everyone suggested we look to see if the 'Pause' option is switched on (blue). However, it's not switched on, it's grey not blue or any other colour and when I hover over it, it says "Don't pause on exceptions. Click to Pause on all exceptions".
You might also check the Source tab, check under the Event Listener Breakpoints panel if you've set any breakpoints under 'Mouse'.
This can also cause the issue
Break Point icon at top left should be blue like this(For Deactivate BreakPoints)
Should not grey like this
Found solution here, if the little octagonal stop/pause sign (at lower left of Chrome "Sources") is colored (blue or purple), you need to click on it until it's black again.
It did drive me nuts for a short while.....scroll all the way to the bottom of breakpoint window and you'll find XHR Breakpoints & under it there is the Any XHR checkbox...
Goto the sources tab and check all breakpoints.
Go to Elements tab and remove all breakpoints from right pane under DOM Breakpoints
One possible cause, it that you've enabled the "pause on exceptions" (the little stop-sign shaped icon with the pause (||) symbol with in in the lower left of the window). Try clicking that back to the off/grey state (not red nor blue states) and reload the page.
For me, I resolved it by temporarily disabling the Chrome Bitwarden extension.
You could check to see in the Sources tab in the devtools panel to see what is causing this error, it could be an extension.
To open the devtools panel on Chrome, press the F12 key.
For Visual Studio Users, just go Tools>Options>Debugging and make disabled it