Android Studio was working fine but when I moved my sdk to another internal drive and gave the proper path to Android Studio and restarted its gradle, it started glitching on the UI level. please find the photo attached.
I tried updating it (to the current version 1.4) but that didn't fix the problem.
Any idea?
I had same behavior, just after installing Android Studio for the first time.
In my case, the behavior becomes normal when I turn off ClearType text.
I am using Windows 7, and this is how I turned it off:
Control Panel\All Control Panel Items\Display
=> Adjust ClearType text
=> uncheck [ ] Turn on ClearType
Ok found a Solution!
Theme: Dracula
Change Font Presentation to: 8
and it will work!
Note that you can revert back to Font Size 24 and it will still work :)
Related
As you can see in my attached screenshot my windows has a issue displaying the closing button. I am thinking that a font is missing. Do you know which font i have to install?
After following a step-by-step suggestion by
http://www.withsteps.com/3483/windows-10-pro-default-fonts-download.html
I have been able to install all default windows 10 fonts.
The missing windows 10 font was also included.
Finally, to solve this problem you need to download a package with all windows 10 fonts and reinstall every one.
I have installed Xamarin under Visual Studio 2015 Community Edition, including the intel HAXM hardware acceleration, but I have a problem with the emulator:
None of the default Xamarin avd's seem to have been installed
When I create one myself and run it, it doesn't look right.
The attached image should make it clear. As you can see the top bar takes up about 1/5th of the screen height, and the bottom bar about 1/4.
Does anyone know what is wrong?
I'm also confused by the buttons on the right hand side. Are they supposed to be there?
VS can use AVDs but it's better to use emulators for Android for VS. It is using Hyper-V virtual PCs.You need to download and run Visual Studio Emulator for Android, then download VMs
Because the screen display size is too small. You should use an AVD Device Template to get a normal size:
When you launch it, make sure that the display doesn't get scaled. You can scale this, but you might accidentally make it too small
The buttons on the right are due to the Skin you have selected.
Based on your screenshot, it looks like you potentially are using the old version of emulators. Make sure to update your Android SDK tools and then re-create an emulator to benefit from the 2.0 emulators:
https://developer.android.com/studio/run/emulator.html#dependencies
After a reboot things seem to be working which weren't before, so I guess something hadn't finished installing. I still find that when I use a skin I don't see any message about hardware acceleration HAXM working, but I think it probably is. With regards to speed, it improved dramatically when I selected the option to 'Use host GPU'.
The HVGA skin still looks wrong, but I downloaded some ones for the Samsung Galaxy which work well.
I have a strange issue whit my emulate touch functionality on Google Chrome version 49.0.2623.110 m.
I'm using laptop + monitor (both Dell) and running Windows 8.
The issue is that while Chrome is on my secondary monitor and touch screen emulation is enabled I cannot see a touch screen pointer (black circle) nor any kind of pointer, but when I move my Chrome to my main laptop display it would show. I tried disabling laptop display while using external monitor and it is the same, I cannot see the pointer. This was not a problem with previous Chrome version.
Did anyone had similar issues with this version?
Thank you
EDIT:
I've change the laptop, updated to win10 and updated Chrome to 50.0.2661.87 m version and I still have the same issue (colleague of mine has the same problem as well).
A colleague of mine "solved" the problem by enabling Windows' Mouse pointer trails at minimum length. I find it too annoying to work with the setting enable, but it does work if you really need it.
Mouse settings
They did some changes in recent version of Dev Tools and some options are now gone. Ensure you have "Mobile" or "Desktop with touch" selected, as you can see on the screenshot.
Hi I got a lil problem with a mobile handheld computer (Motorola MC9200) running Windows CE 7.0.
Within the browser (Internet Explorer + software like Naurtech CETerm) there is some font-smoothing or cleartype. Problem about that is that , and font with a css style of font-weight 900 for example look exactly the same as normal font. So you can't tell the difference.
Another problem would be the panning. I'm running a fullscreen web application and the user shouldn't be able to pan the whole screen 1 cm out. Funny thing is while the user is panning the whole picture the font-smoothing/cleartype is disabled and you can tell the difference between font-weights.
Anyone no a solution to that? I already searched the registry for cleartype and font but didn't find anything helpful. I don't have other WinCE 7.0 devices so I don't know if that problem is WinCE 7.0 related or related to the device.
I don't have a device at hand, but WEC 7.0 offers the SystemParametersInfo function that sounds a bit like what you're after.
Call it with uiAction set to SPI_SETFONTSMOOTHING to disable ClearType on a system-wide basis:
SystemParametersInfo(SPI_SETFONTSMOOTHING, FALSE, NULL, SPIF_SENDCHANGE);
Earlier versions of Windows CE had a registry setting to allow OEM's to disable ClearType, but I've been unable to locate this setting in WEC 7.0, so my guess is it's no longer supported and ClearType is always enabled by default.
Edit: This is under windows 7.1 RC. (This code did work for 7.0)
Lets say we open the application up in the dark theme. A line of code to detect this would be as follows:
isDarkTheme = (Visibility.Visible == (Visibility)Application.Current.Resources[StringResource.PhoneDarkThemeVisbility]);
In this case, isDarkTheme will be true.
Now hit the windows key, change your theme to light theme. and hit the back button to go back to your application. Run the following line of code again (in your activated event)
isDarkTheme = (Visibility.Visible == (Visibility)Application.Current.Resources[StringResource.PhoneDarkThemeVisbility]);
Apparently isDarkTheme is still true even though we switched themes. Has anyone else ran into this problem or am I using an older way to check the current theme?
This is a known issue. The theme is applied to your application when it starts, so only then you are able to correctly detect whether the light or dark setting is used. Otherwise, you are stuck with the old theme until the application restarts.
That being said, it is unlikely that the user will reproduce this behavior. If he switched from your app to phone settings, chances are he is not going back via the back button.