I am trying to understand why Mac terminal font is not sharp.
Mac terminal most of the time shows up like this:
Rarely it shows up like this:
Much sharper. I want to make it so it is always like the second image here, the sharper version.
What could be causing the fond to be not as sharp like shown in the first image?
I am running macOS 12.0 Monterey.
And this is my General and Profiles tabs:
That's the Antialias text option in Terminal's Preference->Profiles. My guess is that you sometimes switch between the predefined Basic profile, which has the option enabled, and the Homebrew profile, which has it disabled.
In the Preferences General tab, you can setup the Terminal to use a non-default profile on startup. If you do so, but at the same time have new windows open with the default profile, you get a different profile for every Terminal window but the first, which may be why you see these differences.
Related
I have XQuartz 1.20.11 (xorg-server 1.20.11) on an M1 MacBook Pro (installed via MacPorts) and am trying to display IntelliJ running on a Linux box via ssh/X11.
The IntelliJ windows appear with oddly rendered text that's unreadable—the white background turns black, and there are white outlines around the black text. If I click outside of an X11 window and start typing, then the IntelliJ window looks normal. But as soon as I touch the trackpad, IntelliJ becomes unreadable.
I tried taking a screen shot, but it comes out looking normal even though the window is nearly unreadable. So I've attached photo of the screen.
X11 windows from other applications display fine.
As mentioned in an XQuartz thread, setting
export _JAVA_OPTIONS='-Dsun.java2d.xrender=false' clears up the text but results in extremely slow display.
Anyone have suggestions for troubleshooting or a solution?
There is a ticket for this issue in IDEA tracker, please upvote it and follow for updates.
Do the latest recommendations from the thread that you mentioned help?
If not, then please try switching IDE boot JDK to e.g. OpenJDK 17 and inform if the issue persists after that.
I'm experiencing a really weird and frustrating issue with the Android Emulator on macOS Monterey.
I have "tap to click" enabled on my Macbook Pro (Mid 2015 15"), and it works fine in all other apps. But somehow, when the emulator window is active it seems to miss almost every other tap. If I click hard instead of tapping, it catches every click. The tap sensitivity in the Trackpad settings is set to "light".
So, it seems that the emulator window is somehow less sensitive to tapping than all other apps. I don't even know how this is possible, is there even such a thing as app-specific tap-sensitivity??
What's more, it's not only the emulator window itself that has this issue, but the emulator settings window as well. If I tap the "Enable clipboard sharing" toggle, it misses about 50% of the taps. If I click hard, it catches them 100%. If I try the same in some other app (tested with the "System Preferences" window), it catches 100% of the taps.
I have tested and tested this again to make sure I'm not biasing the results, but there really is a difference, and it's driving me nuts. I think it appeared after updating to Monterey, but not 100% sure of the exact timing correlation.
Any ideas??
My problem was really similar, I am using MAC with apple mouse, so I could fix it by disabling the mouse wheel on Android Emulator Extended Controls.
Hope that help
I've noticed the same issue some time ago. Unfortunately, I didn't find any solutions.
However, there are a couple of good enough workarounds:
Launch the emulator in a tool window. Anyway, this is a default approach for modern versions of Android Studio. To enable/disable it check Preferences -> Tools -> Emulator -> Launch in a tool window.
Use alt emulators. For instance, Genymotion doesn't have such an issue.
I ran into a simmiliar issue for me and the solution that i found was enabling "tap on click" to in the "system preferences" -> "trackpad".
I am new to the Android Emulator, but am experiencing the same issue in Ubuntu, even though I have tap-to-click disabled in the OS. I hate tap-to-click, so having an ultra-sensitive-to-touch Android screen emulated on my laptop is beyond frustrating.
Looking at the documentation, I came across the SOURCE_CLASS_POINTER method, which states:
The input source is a pointing device associated with a display. Examples: SOURCE_TOUCHSCREEN, SOURCE_MOUSE. A MotionEvent should be interpreted as absolute coordinates in display units according to the View hierarchy. Pointer down/up indicated when the finger touches the display or when the selection button is pressed/released. Use getMotionRange(int) to query the range of the pointing device. Some devices permit touches outside the display area so the effective range may be somewhat smaller or larger than the actual display size.
In reading that, I've come to believe this may actually be the default behavior due to touchpad events being interpreted through the SOURCE_TOUCHSCREEN method, rather than SOURCE_TOUCHPAD or SOURCE_MOUSE.
Unfortunately, I don't have a solution as much as a workaround:
I plugged in a mouse and tested the pointer up/down movements over the screen, which this part of the document suggests should register as a press. However, with the mouse it only responds to clicks. So it suggests to me that it is indeed properly interpreted as a SOURCE_MOUSE controlled pointer and not a SOURCE_TOUCHSCREEN controlled pointer.
So unless we can find out how to make the AVD properly interpret a touchpad as a touchpad, and not a touchscreen, using a mouse seems like the best solution.
For reference, I'm including this link to the AVD manual: https://developer.android.com/studio/run/emulator
UPDATE: Somehow over the period of about 18 hours and several restarts, my AVD no longer does tap-to-click on its virtual screen. It would be very hard to pinpoint exactly what changed because I've been updating packages frequently since I'm running a pre-alpha release of Ubuntu, but I think it's from using X11 instead of Wayland.
Which got me thinking, you could try changing your display server from Cocoa to X11. Thankfully, MacPorts, the MacOS version of the FreeBSD Ports Tree, makes it fairly easy to cross-compile software. It contains build recipes for multi-platform unix-like software, much like HomeBrew but often allowing for more customization.
That tap issue was annoying enough it's probably worth giving a shot.
(from macports website) The X11 windowing environment, for ports that depend on the functionality it provides to run. You have multiple choices for an X11 server: https://www.macports.org/install.php
I would build them in this order:
MacPorts: X11 - If you build it, you'll have a bunch of libraries already
MacPorts: QEMU - use make configure menu to select GTK3+, if there's no option for X11, try this build flag with make after you install X11 (pointing it at your X11's lib dir):
make -L/opt/X11/lib -lX11
Lastly, MacPorts: Android Platform tools
Related StackOverflow Q/As:
Compiling a C program that uses OpenGl in Mac OS X
Running x11 on Mac OS
In windows terminal (latest version) I am trying to open an Azure Cloud Shell. Functionality is working, however I am unable to read the display as when I set focus to the window, it becomes obscured (foreground shading is applied). When I select a different window, the terminal returns to normal.
Does anyone know how to change the theme to something useful or to turn off this foreground shading?
Regards
In writing out the bug as mentioned above I found I needed to delete my old settings file. Once I did this, and restarted terminal it started working.
I note when the azure shell is started, it briefly becomes transparent before updating itself.
I have established an ssh connection from Win10 to RedHat machine via MobaXTerm. I have also enabled X11 forwarding, but when I launch eclipse or gedit or anything else the application window looks blurry, i.e. not really crystal sharp as it would look be it run natively. Below is how it looks like when forwarded from a linux machine. Any clue how to make it look more sharp?
right click mobaxterm executable or shortcut
go to compatibility tab
go to high dpi settings
check the box override dpi table
leave dropdown to application
apply
restart mobaxterm
launch the app
I found a similar issue when working with VcXsrv and the solution for that one worked for me in MobaXTerm as well.
I'm going to guess that your screen is a high DPI one as it seems like that's where most people seem to have this issue.
Try going to the MobaXTerm executable, right-click it and go to properties.
Inside properties, click on the Compatibility tab and then mark the check to disable display scaling on high DPI.
I had the same problem with blurry Mobaxterm windows on Win10. Try to change scale and layout of the monitor in Windows to 100% like in
this image, and it worked for me.
I have 125% display scale and the same issue. In MobaXTerm (21.4) I've changed the following setting to make applications look sharper:
MobaXTerm / Settings / X11 / DPI: auto
I toggled into full screen mode on QGIS 2.2 on my Mac, and now the menu bar won't show and I can't toggle out of it. From the documentation, it looks like it should toggle with F11, but it's not working. I've seen people having similar trouble on Ubuntu and Windows 7, but nothing for OSX. Any ideas? I appreciate it.
Just spent close to an hour with this problem- QGIS 2.2 on mavericks. Really vexing! I tried reinstalling (after trashing the previous version as instructed in the install notes), tried removing the hidden .qgis2 folder in the home directory, tried disabling all spaces on the machine (I started with 8 desktops), tried all permutations of Apple-F, ctrl-F, apple-shift-F, etc...
Finally, and simply, the answer was this:
F11 is documented as the toggle key, but in my mostly stock setup this was bound in MissionControl to 'display the desktop'. I rebound that function to F1, and then with QGIS up, hit F11 (on my MBP I need to also hold the fn key otherwise it's 'volume down') and I was out of Full screen mode.
Hope it works for you!