Right...
Having just finished up the code to make it a little more cross
platform friendly here's what I needed to do to make it work nice:
1) Make the assumption that the keyboard isn't shown when the
application starts (which seems to be generally true)
2) Look for size change notifications (f
Or to put it real simply, how come we can easily toggle the showing of
the keyboard, but not query or set it?
I do see the benefit in allowing flexibility for localization, etc,
via open-ended keyboard capabilities, but at the same time some
applications that "just barely fit" in the display real
I think that putting the flexibility onto keyboard developers takes
actually imposes a burden on the application developers. I would say
that the number of people developing applications for Android are
going to far outnumber the number of people who are developing
keyboards and IMEs. Furthermor
On Tue, Sep 22, 2009 at 9:20 PM, Chris Stratton wrote:
> Expecting applications to be arbitrarily resizable strikes me as
> seriously unworkable in the general case, especially as you include
> the ime taking over the full screen in your list of possibilities.
>
In full screen mode the IME compl
Expecting applications to be arbitrarily resizable strikes me as
seriously unworkable in the general case, especially as you include
the ime taking over the full screen in your list of possibilities.
This really only works for apps where the necessary context can be
limited to a single text entry
We don't have any plan on adding that. An IME being visible can mean
anything from a small bar along the bottom to it covering the full screen of
your UI. An API telling whether it is visible or not is just not sufficient
for this. The intended way for this to work is for the underlying
applicat
Thanks
A recommendation that I'd make for a future rev of the API is that it
be possible to register a callback interface to indicate when an IME
is activated or deactivated.
I've read various statements that it's not good practice to trigger
off an IME transition but for our app it's a pretty e
You find out about the IME impacting your application by your application
window getting resized. That is the -only- way. Different IMEs may have
radically different approaches to interacting with the user. You certainly
can't assume they are doing anything solely or at all with the back key.
Th
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-develo
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-develo
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-develo
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-develo
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-develo
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-develo
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-develo
Bear in mind that if you develop and test your app on a device w/o a
sliding kb, it may not run as expected on a device with one, and vice
versa.
Yusuf Saib
Android
·T· · ·Mobile· stick together
The views, opinions and statements in this email are those of the
author solely in their individual c
dashman wrote:
> i'd like to buy the HTC Magic for my dev phone - i don't want the
> physical sliding keyboard.
>
> with the HTC magic work as the dev phone.
You can test SDK applications using an HTC Magic.
> does HTC provide updated android updates for it.
Please contact your mobile provider
Hi,
I was facing the same problem. I am not an expert but what all I can
gather from various posts it seems our SPL cannot be rooted.
Please see http://forum.xda-developers.com/showthread.php?t=529019
Haykuro quote : "T-Mobile myTouch : 1.33.0006 and 1.33.0010 is the
dreaded "perfected" SPL".
Maybe you can run the benchmark and post your test results
http://forum.xda-developers.com/showthread.php?t=532668
those results at XDA certainly shows the Magic to be
slowerdespite Magic having more ram and rom over G1...
Maybe also post the results using
CaffeineMark
I know G1 have over
Please help to unlock the device.
On Jul 12, 5:46 am, Mike Wolfson wrote:
> You will need to root your device, before you can flash a new ROM.
>
> So, yes, it appears your device is locked.
>
> On Jul 11, 1:58 am, Nima wrote:
>
>
>
> > Hi,
>
> > I have followed the instructions in
> > link:
Unless you can confirm that they're using the same firmware, have the
same apps installed which are working with the same data sets and
background tasks are firing off at the same time on both devices it's
extremely difficult to say one it's the hardware that's causing the
performance difference.
You will need to root your device, before you can flash a new ROM.
So, yes, it appears your device is locked.
On Jul 11, 1:58 am, Nima wrote:
> Hi,
>
> I have followed the instructions in
> link:http://android-dls.com/wiki/index.php?title=Magic_Rooting
>
> but the following error is reported
Hi,
I have followed the instructions in link:
http://android-dls.com/wiki/index.php?title=Magic_Rooting
but the following error is reported
fastboot boot recovery-RAv1.0H.img
downloading 'boot.img'... FAILED (remote: not allow)
Whether any locking is there in the device
Please advice
Thanks&
Hi,
Thanks a lot for your quick response.
We are not able to see the option "settings->applications->development-
>"USB Debugging" in device
Please advice.
Thanks & Regards,
On Jul 10, 10:33 pm, "Yusuf T. Mobile"
wrote:
> As a T-Mobile employee, I discourage you in the strongest possible
> ter
As a T-Mobile employee, I discourage you in the strongest possible
terms from rooting your Magic and upgrading it to 1.5 at the same time
using this link: http://android-dls.com/wiki/index.php?title=Magic_Rooting
Yusuf Saib
Android
·T· · ·Mobile· stick together
The views, opinions and statements
The Rogers HTC Magic phone is using the 'p' as a pause, but it seems
they haven't changed the PhoneNumberUtils.PAUSE to reflect this. This
is rather unfortunate, because it makes the Rogers build non-standard
and my app breaks. I would hope in the future there are no more
deviations of the standar
You didn't say what actually goes wrong. Are you not getting the DPAD_CENTER
event at all, is it not repeating the same as on a G1, or something else?
One thing that looks a little suspicious is that in onKeyDown when it
receives DPAD_CENTER, you set 'inited' to false, which would then prevent
you
--- On *Sun, 6/7/09 numan * wrote:
hello my friends have a nice day
sexy summer fashion & more fashion show videos
visit us http://www.fashioninfokit.com/
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google
Groups "Android Develo
HTC Magic is already been rooted at XDA.
Eric
On Jun 7, 5:40 am, JP wrote:
> It's a device given to developers, but out of the box it's not a
> development device, so if you need it rooted for development you'll
> have to yourself.
>
> On Jun 5, 3:54 pm, NTDYLF
> wrote:
>
> > Hello all. I rece
It's a device given to developers, but out of the box it's not a
development device, so if you need it rooted for development you'll
have to yourself.
On Jun 5, 3:54 pm, NTDYLF
wrote:
> Hello all. I received an HTC Magic at the Google IO conference, and
> had heard that it is a dev phone, but w
At this point there is no "HTC Magic." I would assume that these people are
using one of the leaked builds of 1.5, which is from some random pre-final
build of 1.5 with some random set of changes HTC as done on it. I would not
spend my time trying to support it at this point, as it is not a real
31 matches
Mail list logo
