I'm testing my app on Windows Subsystem for Android.
When I click on a android.widget.Spinner to select an item from the list and move the mouse, the list keeps scrolling down. This behavior makes it very difficult to select items.
This does not manifest with AutoCompleteTextView
Has anyone run into the same problem?
Related
I do not want to use the mouse but only the keyboard.
I use a lot the action shortcut to do that, and I remember a number of shortcuts. But when I do a run and get some errors, I find frustrating I have to use the mouse to gain the focus of the Window Tool Build ( the one that is on default without a shortcut into the bottom bar of Android Studio. How can I without the mouse, see the runtime errors, scrolling into the Build tool window?
By the way I experience the same problem with Logcat, I gain via tab the access to the above bar functions of Logcat, but I cannot scroll Logcat
I tried a lot of commands, even giving a shortcut to Build but does not work
I have Android Studio 3.1 and for some reason I am unable to scroll using the touchpad. I have to manually scroll by dragging the scroll bar on the right, and this can get very tedious and inconvenient if im working on a large project. I used to be able to two-finger scroll on previous versions of Android Studio but for some reason its just not working anymore. I have windows 10 if thats relevant. Any idea how I can fix this?
I had the same issue and found a solution by making a small change to a registry entry:
Open regedit.exe using run
Go to HKEY_CURRENT_USER -> SOFTWARE -> Elantech -> Smartpad
Change ScrollControl_Mode from 0 to 1
I found the answer here:
https://www.reddit.com/r/techsupport/comments/3lhmhq/win10_elan_touchpad_scrolling_issues/
Just go to File>Settings or Ctrl+Alt+S. Then Select Appearance in Appearance & Behavior menu. Now Scroll down to Windows option and Select the Smooth Scrolling checkbox. Below there is an image. This worked for me.
https://i.stack.imgur.com/bXApl.png
Two-finger scrolling problem generally occurs due to malfunctioning of touchpad drivers of windows 10.
Things you can try are:
Go to File>Settings or Ctrl+Alt+S. Then Select Appearance in Appearance & Behavior menu. Now Scroll down to Windows option and select the Smooth Scrolling checkbox
as suggested by #Nikhil
You have to update your touchpad drivers:
For updating driver:
Go to the Device Manager.
Expand "Mice and other pointing devices".
Right-click on your touchpad (probably Asus Support Device)
Properties.
Driver Tab.
Roll Back Driver.
Restart computer.
If it still doesn't work now try updating your touchpad driver again after rolling back.
If it still doesn't work try to uninstall your touchpad driver and reinstall it.
Important: Always Remember to restart your computer every time you make any change.
For me, the problem is often caused by other apps that are currently running. For example cmd or OneNote. After closing those scrolling works again.
I would make sure that my application for devices Android Wear the first element of my WearableListView is selected by default when i start the application. I tried everything but without success and the many guides that I find on the web dealing with this subject for a normal ListView NOT for devices WearableListView primed for Android Wear, thanks in advance.
I have a very strange problem with Delphi Firemonkey TStringGrid on Android. It looks like that events on TStringGrid are triggered differently on windows and android platform.
For example: in windows firemonkey application I have a string grid with a few columns. TStringGrid is set as read only. OnClick event I have the following code:
TStringGrid(Sender).Cells[TStringGrid(Sender).ColumnIndex,TStringGrid(Sender).Selected] := 'result';
Android application has exactley the same code OnClick event
TStringGrid(Sender).Cells[TStringGrid(Sender).ColumnIndex, TStringGrid(Sender).Selected] := 'result';
When I run windows application and click on string grid cell it becomes selected and then ‘result’ is written in the cell.
windows before click
windows after click
When I run android application and do click (tap) what happens is that ‘result’ is written in previously selected cell, and after that cell where I did click becomes selected.
android before click
android after click
I am not sure is this a bug in Firemonkey or expected behavior. Is there a way to overcome this?
TGrid is not a supported control on mobile so you should avoid using it. The best alternative is probably a TListBox with a custom style.
It might a threading issue. But I'm not so sure you are using the best event handler. If you are trying to update the cell that is being selected, then I would advice you handle the TStringGrid.OnSelChanged event. This event is fired after cell selection has been changed.
Beware though... it is not strictly fired by mouse clicks (or finger taps). If you have some sort of keyboard attached to the Android device, or on a desktop platform, it will also fire when you use arrow keys and other means. I think you get what I mean... but then maybe that is just what you are looking for.
We have a Web application that dynamically builds elements via JS. We are testing for mobile usability and are finding that on devices that run 2.3.x versions of Android, our select element behavior is a little strange. A touch on the select element will bring up the usual radio button list of the options and touching an option will select it and return to the page view. However, the option shown in the select box does not update. It still shows the top element in the option list. When the page is reloaded, the behavior is normal. I have tried adding an additional empty element at the top of the list and setting it as selected when the element is built, which seems to clear up the issue on some devices, but our QA tester is saying that behavior remains on others.
Any ideas?
If you're fishing for areas to look into, I had a similar issue for select elements when using the fastclick library in any Android 2.3.x browser. The issue was caused by a hack in fastclick for it to work better under Android Chrome. The fix for native browsers hasn't been merged to this day (https://github.com/ftlabs/fastclick/pull/190).
On another note Android 2.x can be a nightmare in unexpected places once you start adding an assortment of everyday things - CSS animations, opacity, negative margins outside the screen etc