Locator.ScrollIntoViewIfNeededAsync() is not working because of virtual scroll.
I need to use Page.Mouse.WheelAsync() to do the scroll and click on certain node.
Have you maybe encountered that situation, and/or have some (other) suggestions how to do this?
Related
I am using a plug in in order to move the whole view up to get make the entries visible when the keyboard would hide them:
Xamarin.IQKeyboardManager.SharedManager.Enable = true;
Many posts refer to this plug in and it does the job of pushing the view up very fine: however: once I close the keyboard again, the view isnt restored perfectly but instead a little bit is cut off at the bottom. Since I sometimes have buttons down there that are now cut off it is not a solution for me.
I tried multiple plug ins, they all do the same.
Does anyone here have a good solution to it?
On android everything works fin eautomatically.
I solved this issue by wrapping all entrys that were affected by a scrollview.
This is a quite strange behavior that 'persecutes' me since iOS 7.0 :) I hope someone of you can help me this time! As you probably know when you are using VoiceOver your gestures are totally different from the 'normal way'. When you need to bypass VoiceOver for a specific view you can set its accessibility traits as UIAccessibilityTraitAllowsDirectInteraction. When the view has this parameter set the user can interact with it as usual (like VoiceOver is not active in that particular view).
Quite often happens that this ability is randomly lost so VoiceOver acts in its normal way.
Did anyone of you encounter this problem in its experience? Did he solve it? Fortunately turning off and on VO seems to temporarily solve this issue (until next time it happens again)
Any idea? Thank you very much
I've seen this with other things as well. For example, notifications can be spotty, particular Screen Changed or Content Changed notifications. I believe this happens as a result of turning VoiceOver on and off. For example, if you were to turn VoiceOver on, leave it running, and open your application as a user would, you would never experience these issues.
However, if you use the VoiceOver shortcut. Or interrupt the application, re-install, and restart while using Xcode, you can disrupt the VoiceOver's connection to the application. It doesn't bond correctly. So, simple things like navigation work fine. But advanced features like notifications (and perhaps some of the more complicated traits) don't work.
Essentially, I would classify this as a bug, but a bug that only shows itself when you use VoiceOver in a way that only a developer would use it.
Having an issue with UIPickerView not spinning (iOS7/8), floating around left and right uncontrolled, being barely usable only when tapping on its values (and still horrible even then). It must be due to one of the library references, but I'm yet to figure out what exactly is causing it. The easiest way to reproduce it is by dropping a UIPickerView into one of the pages controlled by SLPagingView (https://github.com/StefanLage/SLPagingView) - screenshots included.
Just trying to see if anyone experienced this every with this trivial control?
The issue was in one of the referenced rogue libraries that overrode some of the default behavior by extending built-in controls and data types.
After excluding them one at a time from the project, cleaning it, and rebuilding, I eventually found the culprit.
Im just picking up ios development, and Im having a stupidly basic problem with xcode...
I open up a new app and open main.storyboard, and drag in a label to the center of the panel:
It just sticks to the right side, and no matter how many times I click on the darned thing, it won't move! I closed the project and started a new one, and that one worked just fine, but the problem keeps appearing just about every other time I open a new project. why does this keep happening?
That is a strange problem. You say that if you close the project and start it again, it fixes itself but keeps reappearing.
Few suggestions, try clearing up some ram by closing other, unused apps.
If that does not work, I would say delete Xcode, restart your mac, and start over. Maybe something went wrong during the install.
Storyboards are scrollable and when you scrolled out your views, you cannot make any changes to the views. Try scrolling into the storyboard and then retry moving the label.
It's AutoLayout, which is the highly recommended default for laying out components now. You need to create constraints to
position it, using the icons below the layout area.
Some components I've found I need to manipulate via the size inspector, before constraints are applied.
You will need to read up on Auto Layout sooner or later. It may seem like a hassle or drag at first, and a lot of people are cursing when they have to switch to the paradigm, but when you start to master it, it is very powerful. And it really is a sensible way to handle the layout across all the new screen sizes and orientations. It developed out of a need to manage that complexity to keep apps looking good.
Icons in IB where you set constraints for selected views:
Apple has good documentation for how to use Auto Layout as do many bloggers and sites. You will have to put some hours into getting used to it, but in a day or two you should start seeing good results.
(and don't blame me, I'm just the messenger)
In my application i have 3 scrollview, once the application is used for long time or application is in background for long time. Scrollview in my application is not scrolling properly and it is responding very slow compare to previously when the application is installed.
I tested the application using instruments but i am not able to find out the real cause of the application. Please help me in this issue?
Hy this is gues work,
without more details one could only take a look into a glas bowl,
based on my experience scrolling has no general problems so it has to be your code which causes this problem.
I could only advise you to check your state, may adding some Log statements to show the state of your scrolling brings more light into the problem?