Agraham, I confirm your theory, the values for activity.height after rotation are incorrect, instead of expected 600 only 556 is returned. Of course this explains why the statically set 1024x600 image (or panel) is cropped by 44 pixels, or squeezed when using relative 100%xy values. Question is what is actually causing the wrong activity.width value and whether it can be fixed (by Archos I guess).
followed by code showing how I adjusted for it.' The emulator does not include the onscreen system menu of the Archos 70
' which is 40 pixels wide down the right side of the screen in landscape.
' I don't know if other 7" devices have anything like this, but here is
' an adjustment for the A70...
myButton.Initialize("")
myButton.Text = "Click Me"
Activity.AddView(myButton,0,0,-1,-2)
Basic4android doesn't use LinearLayout as the basis for its Activity ViewGroup but uses its own BALayout which will behave differently. BALayout is more like AbsoluteLayout in that it lets you specify view locations as pixel values. As far as I can see BALayout sets its own size according to values reported by the OS so if the size is wrong then it does look like an OS bug. I guess LinearLayout does things differently.add a simple button within the LinearLayout
Is there a posibility to get the real activity size excluding the softmenu size?
We use cookies and similar technologies for the following purposes:
Do you accept cookies and these technologies?
We use cookies and similar technologies for the following purposes:
Do you accept cookies and these technologies?