[mobile:Android] mobileSetAllowedOrientations gives error

Roger Eller roger.e.eller at sealedair.com
Mon Jun 6 20:30:36 EDT 2011


On Mon, Jun 6, 2011 at 12:17 PM, J. Landman Gay wrote:

> On 6/5/11 5:00 PM, Roger Eller wrote:
>
>  Have you heard anything on how the iOS/Android alignment is coming along
>> at
>> RunRev?
>>
>
> Not really. The only info I have is that the team is swamped and working
> like mad. Presumably they are focusing mainly on all the bugs that affect
> *me*, but I'm not sure. :)
>
>
Lucky you!  ;-)


>
>  No such luck.  Both portrait orientations and their menus are still
>> opposite
>> of what they should be.  My Android version is 2.3.3 and the Kernel
>> version
>> is 2.6.32.39, in-case that info is useful.
>>
>
> I'm on 2.2 so I only get two working orientations, but they both display
> correctly. If yours don't, I'd say that's a bug. Upside down is a unique
> approach, but probably not what users expect. ;)
>

I noticed the Androide release note saying that 2.3 is required 'due to a
limitation of the OS'.  I have to call bs on this statement because other
apps on a 2.2 device can rotate fully.


>
> QCC time, I think.
>
>
It was previously reported on May 13, 2011, and flagged as 'Fixed' on June
1, 2011.
http://quality.runrev.com/show_bug.cgi?id=9540

I added my comment that it is STILL upside-down, but the QCC record is still
closed.


>
> --
> Jacqueline Landman Gay         |     jacque at hyperactivesw.com
> HyperActive Software           |     http://www.hyperactivesw.com
>

˜Roger



More information about the use-livecode mailing list