The code, that I typed, displays color completely different from the sample code. And I have no idea how to make it displays as the sample one. This bug appears on every scheme, including Default one.
This was caused by the 'Power save mode' is turned on. We just have access to menu File > Power Save Mode to turn it off then code scheme will be displayed as normal.
Related
I have a strange issue with the android studio design screen
Whenever I enter any number in the layout -> constraint Widget (up left right down) and press ENTER
the numerical style keeps changing by itself in the attribute field (such as layout_marginTop) to Hindi style (Arabic) and of course, because of this, the Design screen keeps disappearing because that causes an error in the XML syntax.
I tried everything in the regional setting (changing the number of standard digits and native digits in the windows regional settings) but non of that made any difference. I attached a screenshot for more clarification.
can anyone help me?
Please advise on how to get rid of this issue
ScreenShot of my Android studio space with issue
Here's a snapshot of my app where you can see the running app which has missing text and you can see the text that should be displaying (which is properly displaying in design mode).
Why isn't the text displaying at runtime?
This only started happening when I updated to version 4.1 of Android Studio and rebuilt my app.
Additionally, here is how they are defined in the layout xml:
Here's a view of the layout details of the one checkbox that is not displaying the text:
Notice that it is showing text size in PT (points).
I changed it to sp after choosing from droplist and now it displays properly.
Not sure why this has always worked in the past and suddenly stopped working.
If it is a change I would expect an auto-update functionality when Android Studio upgrades the project.
Should Not Work In Design Mode Either
If it is a problem I would also expect it to display improperly in the Design Mode also. Instead it looks correct in design mode even though runtime doesn't display it. In this way I would've understood that I was using an incorrect unit.
TextView Also
I found that this was also happening in many of my TextView controls.
My VB6 application is having a layout problem on certain end user PCs, but so far we are unable to identify what is causing this.
Normal layout:
Broken layout:
The text on the left are the captions of the radio buttons. The text in the upper right is a label.
I am familiar with two different settings in Windows Control Panel which can affect text size, and initially we suspected this was the cause. In Windows 10, they are:
Control Panel >
Appearance and Personalization >
Display >
(1) "Use these display settings" > "Customize your display"
or
(2) "Set a custom scaling level"
(Terminology was different in earlier Windows versions but I think the features were the same?)
However upon testing these settings with our app neither reproduces the problem.
What else might be causing the text layout issue shown in the image?
This appears to be caused by a Windows bug.
The description & fix as mentioned in the source website are as follows:
if you have a high resolution screen at install time, Win7 will install a larger font set (125%) by default. If you then choose go back to the standard font size (100%), Windows will keep some of the large fonts even though everything else is adjusted for standard fonts, causing programs that use these fonts to break because the text will not always fit inside the GUI.
By editing the Windows registry you can get the original, intended fonts back:
Open the start menu and type regedit and then press Enter.
Locate the key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Fonts
Find the value MS Sans Serif 8,10,12,14,18,24
Change from SSERIFF.FON to SSERIFE.FON
Find MS Serif 8,10,12,14,18,24
Change from SERIFF.FON to SERIFE.FON
Finally find Courier 10,12,15
Change from COURF.FON to COURE.FON
Restart your system in order for the changes to take effect!
The exact font names may vary depending on locale settings.
I was able to create the problem scenario as described here on Windows 10, and that reproduced the problem with our VB6 app. I think that confirms this as the fix.
A Microsoft blog post seems to be the authoritative original source of this information.
While my search for a Python debugger on Emacs remains unfulfilled, I am giving PyCharm CE a test drive.
Already on my second day I'm encountering a trivial but frustrating point. Is it possible to set the background to be pitch black in just one place?
A program written by programmers for programmers should certainly have included a feature such as "change the background for Docstrings, Comments, Keywords, ... the whole shebang" to black, but I don't see it.
I understand of course that some parts of the UI will stubbornly refuse to change, and I'm OK with that, just so long as the Python code itself appears on a pure black background.
The Twilight and Mokokai themes come close, but their backgrounds still leave ample "contrast room" that could be used by darkening the background color.
(How do we get from left to right... err.. I mean.. how do we get darker than we are.. um, wait... Isn't the version on the right so much easier on the eye.. but anyway, how can we do it?)
Update
The exact same problem and solution apply to Android Studio.
In File > Settings:
Go to Editor > Colors & Fonts > General
Choose the theme you want to modify (will likely need to Save As... your own as you can't modify the default color schemes.
Go to the Text > Default Text colors and change the background to black. The only ones that won't be affected are the syntax highlighters that define their own background (usually select/highlight/errors/etc.)
In Android Studio, is there a way to change the thickness of the error validation markers in the right gutter? They are very thin and, for me, it is difficult to discern the colors. They tend to all look greyish.
the result is I'm having trouble seeing which are warnings and which are errors.
I don't know if you can "change the thickness" since it is representation of the entire file - it is more like a "heat map" than a navigation tool. Making the window taller would make them "thicker" and beyond that you have display and navigation options, so that you don't need to see individual indicators.
To change what is displayed (which warnings and errors are highlighted), go to Analyze -> Configure Current File Analysis then in the pop-up click on "Configure Inspections". Here you can select which warnings and errors are indicated. You can create profiles, etc. to your liking.
For navigation, you should be able to navigate to errors only and skip the warnings, using F2 (or shift-F2) on Mac anyway.