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
I have the MacOS application developped using UNO Platform whitch i would like to test using appium. Application was is fully fucntional for manual usage.
Then i encountered an issue with accessibility inspector that default MacOS window buttons like "close application", "maximalize", and "minimalize" can be accessed wia UIElementInspector but almost all of the application connetnt cannot be accessed(they are not listed at all) as a children of the main window. Only images are accessible but none of the buttons neither texts.
I checked other applications like calculator, visual studio etc and hadn't simillar problems - every element was listed, so in my opinion problem is not coming form system but the application or uno platrorm itself. Remark - on windows this application hadn't such inssue with contetnt acessibility.
Also found example application developed in uno platform and this applicacion also does not share the elements in inspector.
https://github.com/unoplatform/Uno.Ch9
Have anyone had faced similar problem and was able to solve it?
So we've recently had our dev machines replaced with 4k laptops and windows 10. I've got visual studio set up, the DPI scaling has worked for the most part to make things usable. The only problem is errors / dialog boxes.
I can't find a way to make them scale up to something readable. Instead I'm getting unintelligable errors written for ants.
Has anyone had any experience of this issue on high DPI screens? And if so did you find a way to fix the problem?
As an example of what I'm talking about, content is scaled, but the options to the left are not. If I get an error popup (exceptions, build failed etc) then everything is in that tiny text, making it unreadable.
I'm the author of a Windows application that's been around for years. The app uses the wxWidgets UI library. For the newest version, we upgraded to the Microsoft c++ compiler in Studio 10 and to the latest Windows SDK library. We did not change much else in the app. Now, several users have reported that after a period of time running the app, the menus go crazy. All of the users reporting the problem are running on Windows XP. The menus either get huge, filling the screen, and have a giant italic font with strikethroughs. Or they get really small, so that the only thing shown are up and down arrows, suggesting the rendering code thinks the screen real estate is too small to display anything else.
You can find example screen shots here:
Once the menus go crazy, all menus are affected, except the standard Windows and MDI menus. The only way to recover is to restart the app.
The code in the app and wxWidgits is a thin layer on top of the standard Windows API. Once the menus are created, afaik Windows manages the rendering.
Any ideas what's going wrong?
Problem
Qt Designer is locking up when selecting a image from Resource, stops responding, just
makes Windows bing sound.
Does anyone know what might be causing this problem with Qt Designer, or a decent work-around?
I've only tried Label.pixmap and PushButton.icon so far.
Every time I select this option the entire Designer locks up. It seems like it's trying to display a modal selection dialog box, but I can't see it anywhere.
"Choose File..." option works fine but isn't a convenient option.
I have had Designer working properly in the past.
My project was paused for a couple of months, during this time I lost my Qt build due a complete HDD failure, and have restored from a zip-backup I'd made. I can still build against Qt libs.
Since then hasn't worked.
I also built for Linux and the same .ui files can be editing properly with Ubuntu 10.10.
Environment
Qt v4.7.1
VS2008 SP1, I built my own build of Qt
VS addin (same symptoms for v1.1.7 and v1.1.9)
Win7-x64 Pro
Tried (without success):
rebuilding Qt from source
manually editing .ui file as suggested here: http://discussion.forum.nokia.com/forum/…crashes-Creator
running Designer from installed folder
watched designer.exe in procmon (seems to be doing a lot registry lookups for HKLM\System\CurrentControlSet\Services\Tcpip\Parameters\Interfaces, but nothing that looks significant)
This is really hurting me, help very much appreciated.
The 'lockup' was caused by Designer opening a modal resource dialog. However, since last using Designer, I had moved my second screen to the other side of my primary screen, the modal dialog was open in the old screen (no longer connected) so I couldn't see it.
Resolution: Windows-key + Left-key moved the missing dialog back onto a connected screen.