While I'm developing an application with the Nokia 2.0 SDK, I've found this bug in my app.
When the device is in Portrait mode, the Form's scroll works fine but when I change the orientation to Landscape I find that the scroll makes bigger than the info in the page.
How can I solve that?
Seems like a bug in the S40 port. Just detect the orientation change (by overriding Form's size changed) and call setText() again. It will trigger a recalculation of the rows in the text area.
I solved it!
I forget to put the layout to the Form and it doesn't recalculate the size.
Now it's working! Great!
Related
I am using jquery BlockUI Plugin and I'm facing an issue.
In the iOS devices when in portrait mode the overlay comes fine but when the user switches to landscape mode the overlay comes but with the same resolution of the potrait mode which looks wierd.
So is there any way I can override the CSS of the overlay without editing anything in the jQuery BlockUI plugin or is there any setting that I need to do?
The issue may be that the page is being drawn at the larger width and when you are switching resolution to the portrait view the device it is not redrawing the page but resizing it. Here is a jquery function that may fix your problem.
Just call that function when you detect a window resize.
What causes the flash of white to the right of a responsive design when changing orientation from portrait to landscape on the iPhone with iOS 6?
Try it on Safari for iOS 6:
Websites like this don't do it: http://html5boilerplate.com
But this one does: http://www.initializr.com
Something to do with re-processing (CPU lag) to fit a wider screen?
It doesn't happen in Chrome for iOS6...
For example, I just removed all img from my own testing site and set the background of <body>, <html> etc. to non-white, but it still happens. This seems to happen with a lot of different websites out there, but others are completely immune to it...
Could it be a problem with someone on the website, or an iOS Safari bug?
Thats because of the elements in the header of http://www.initializr.com/ which (dis)appear when changing orientation. It forces the header to resize and the elements below are pushed down. This causes a repaint of the DOM, that causes the short white flash on iOs.
I'm getting my app ready for the iPhone 5 using the simulator and I've found a weird issue where a couple of my buttons, in one of my views, don't work in the iPhone (Retina 4-inch) simulator, but work fine in the iPhone (Retina 3.5-inch) simulator. The buttons simply don't do anything when they're tapped. Has anyone else experienced this issue?
I having a difficult time figuring out where to start with this one. Any suggestions on where to start?
Thanks so much in advance for all your wisdom!
You need to edit your MainWindow.xib and enable "Full Screen at Launch". For a more detailed explanation, see Apple's docs:
Important: When creating your window in Interface Builder, it is
recommended that you enable the Full Screen at Launch option in the
attributes inspector. If this option is not enabled and your window is
smaller than the screen of the target device, touch events will not be
received by some of your views. This is because windows (like all
views) do not receive touch events outside of their bounds rectangle.
Because views are not clipped to the window’s bounds by default, the
views still appear visible but events do not reach them. Enabling the
Full Screen at Launch option ensures that the window is sized
appropriately for the current screen.
Complete document from Apple
For me, the solution was to set the size ("Simulated Metrics") to "Retina 4 Full Screen" for the MainWindow.xib. I did not need to alter the size of the other screens (they are still set to None). After changing the MainWindow.xib the bottom area becomes clickable again...
The problem was caused by another control overlapping my buttons due to the way the springs and struts were setup. Adjusting the z-order of the buttons fixed the issue. Thanks, all!
There are two solution to this problem :
If you are using MainWindow follow these steps :
a. Select MainWindow.xib.
b. Select Full Screen at Launch from Windows option available in Attributes Inspector.
If your application doesn't contain MainWindow then just add:
self.view.frame = [UIScreen mainScreen].bounds
in ViewDidLoad.
I solved my prob.
view .origin for 3.5 inch and 4 inch screen are different so, when writing common code for both we need to take care at giving CGRectmake(x,y,w,h);
Set temp. diff background color of diff view so you can check if any view is overlapping or not, to fetch event in 4.0 inch.
I am wondering about the on-screen keyboard (osk).
When I’m in portrait mode the osk shows up on the bottom of the screen and only covers up the lower portion of my app. This is ideal because you can still see my text box which is located in the upper portion of the app. But when the orientation is changed to landscape, the osk covers up the entire app (hiding my text box) with its own text area.
This osk text area only shows in landscape mode. Is this how the osk behaves on all Androids or is it specific to Samsung Tab 7" or something else?
Is there a way to prevent the osk from displaying its own text box in landscape mode? If not, I will have to design my own osk. If I do design my own osk can I still take advantage of Android's auto completion through B4A?
I have tried the AutoCompleteEditText but it does not work the way that the Android auto completion does which is closer to what I need.
Any suggestions?
Thank you for your help,
Bob Gately
Better answer. You can use the reflection library to disable the full screen keyboard:
Dim r As Reflector
r.Target = EditText1
r.RunMethod2("setImeOptions", 268435456, "java.lang.int") 'IME_FLAG_NO_EXTRACT_UI constant
This is the default behavior of all Androids when in landscape.
You may want to see this link for an implementation of custom keyboards:
I am making a web app for the Android and iPhone that has a div for content. I can update the div programmatically and have it scroll down but I can't scroll using just my finger.
You can see it here: http://crosswordcoach.appspot.com/poc
Type in "Cookie firs" and then select that clue (obviously there are other bugs to work out!) and it will have enough hints to fill the screen. With Chrome on a PC it works correctly and the list becomes scrollable if it is too big for the screen. On the iPhone and Android it does not.
Does anyone know what the deal is? Thanks!
iPhones cannot scroll absolute positioned divs by default, I believe.
iScroll might help.