On Oct 31, 6:00 pm, Dianne Hackborn wrote:
> I'll make this a little stronger -- the Display object is LOW LEVEL access
> to the display.
> (The Display object clearly needs a lot more documentation... but this is a
> pretty low priority because, again, it really shouldn't be used by
> applic
Well the user who tested my old version and new version of the
orientation code was running a standard build of Android. I also know
at least one other user was also running standard 1.5 and not any
unofficial ROM.
Can anyone else shed any light on what may be causing this?
I cant believe this is
I wouldn't be surprised if these people are running Cyanogen mods.
People also had problems with my app when they did that. In my opinion
custom ROMS are trouble for developers.
-niko
On Nov 1, 6:31 pm, mscwd01 wrote:
> Hey Mark,
>
> I have had one user contact me by email and he had the same is
Hey Mark,
I have had one user contact me by email and he had the same issues
using the older version and the new version (using the orientation
code you supplied), so I can rule out that being the cause *I think*.
I *presume* it isn't a ROM issue as I have had 8-10 users leave
comments saying it
Phy wrote:
> I have confirmation from five users who either have a HTC G1 or HTC
> Magic who say my application works fine. However, I have had numerous
> recent comments on the Market that the orientation of my applications
> interface is rotated 90 degrees on G1/Magic devices.
Do you have any co
Okay can I just summarise my problem as I believe it is an issue which
NEEDS to be addressed...
I have confirmation from five users who either have a HTC G1 or HTC
Magic who say my application works fine. However, I have had numerous
recent comments on the Market that the orientation of my applica
Okay can I just summarise my problem as I believe it is an issue which
NEEDS to be addressed...
I have confirmation from five users who either have a HTC G1 or HTC
Magic who say my application works fine. However, I have had numerous
recent comments on the Market that the orientation of my applica
Well Niko that may be true but it doesn't change the fact that it
works fine on an HTC Hero and some G1 & Magic phones.
It should either work or not, having your application work fine on
some devices and break on other devices is rediculous and its getting
annoying now.
iPhone here I come :(
On
Wait-
YOu are remapping the coords after rotation? Well then that's where
the problem has to be, since clearly Mark has shown that the
getOrientation() works correctly
-niko
On Oct 31, 1:25 pm, mscwd01 wrote:
> Well then this is extremely confusing!
>
> Firstly, thanks Mark for taking the t
Well then this is extremely confusing!
Firstly, thanks Mark for taking the time to test it.
The only other thing which could be wrong is how the coordinate system
is represented in each device. I draw to the screen once I have
remapped the coordinate system i.e.:
if(screenOrientation == 1) { //
mscwd01 wrote:
> Okay this is getting really rather annoying now.
>
> I have used both of the following methods of getting the screen
> orientation and both do not work properly on different devices.
>
> Method 1:
> Display display = ((WindowManager) getSystemService
> (WINDOW_SERVICE)).getDefaul
mscwd01 wrote:
> Okay this is getting really rather annoying now.
>
> I have used both of the following methods of getting the screen
> orientation and both do not work properly on different devices.
>
> Method 1:
> Display display = ((WindowManager) getSystemService
> (WINDOW_SERVICE)).getDefaul
Sorry I meant "works on the HTC Hero" NOT magic ;)
On Oct 31, 6:11 pm, mscwd01 wrote:
> Dianne, I have used the configuration to try and determine orientation
> (see Method 2); however, this still fails on G1 and G2 devices. It
> works on the HTC magic though.
>
> If you could offer some other so
Dianne, I have used the configuration to try and determine orientation
(see Method 2); however, this still fails on G1 and G2 devices. It
works on the HTC magic though.
If you could offer some other solution i'd be very appreciative
indeed ;)
On Oct 31, 6:00 pm, Dianne Hackborn wrote:
> I'll ma
Okay this is getting really rather annoying now.
I have used both of the following methods of getting the screen
orientation and both do not work properly on different devices.
Method 1:
Display display = ((WindowManager) getSystemService
(WINDOW_SERVICE)).getDefaultDisplay();
int screenOrientati
I'll make this a little stronger -- the Display object is LOW LEVEL access
to the display. Trying to use this in an application is almost guaranteed
to not do what you want. The current orientation should be retrieved from
Configuration. The width and height should be retrieved from the view
hie
mscwd01 wrote:
> I added this to the activity tag in the manifest:
> android:screenOrientation="sensor"
>
> Would that make any difference?
That changes the trigger. For devices with a keyboard (e.g., G1), by
default, an orientation change is triggered by sliding the keyboard, not
the acceleromet
Hi Mark,
I added this to the activity tag in the manifest:
android:screenOrientation="sensor"
Would that make any difference?
If I get "it still doesn't work" emails, i'll try your code.
Thanks
On Oct 31, 11:54 am, Mark Murphy wrote:
> mscwd01 wrote:
> > Hi,
>
> > I have had several complaint
18 matches
Mail list logo