Group: http://groups.google.com/group/android-developers/topics
- Which Intent flag should I use? [1 Update]
- Database Database Database [1 Update]
- Virtual screen size [3 Updates]
- Licensing Verification Library and Demo versions [2 Updates]
- How to do this kind of screen alignment? [1 Update]
- app security [1 Update]
- Cannot compile Desk Alarm Clock (branch eclair ver 2.1) [1 Update]
- the new eclipse UI design - absolute frustration and waste of time [1 Update]
- Issue with messages in this group? [1 Update]
- Zsolt Vasvari <zvasvari@gmail.com> Dec 31 10:26PM -0800 ^
This is part of my ongoing effort to tidy up my AppWidget code:
When a user clicks on my Widget, it goes to an Activity "deep" in my
app. When the user finishes this activity, I'd like to exit back to
the Launcher as opposed to whatever the last Activity on the stack is
for my app.
Is there an Intent flag I am not using correctly? I tried all the
ones I could see to be relevant, but nothing worked. I know I could
probably pass result codes back up the stack to wind down my app, but
that's some ugly stuff. Is there an easier way?
Happy New Year everyone!
- Abhishek Talwar <r.o.b.i.n.abhishek@gmail.com> Dec 31 10:00PM -0800 ^
Hey guys
I have simple 2 button screen which are "Create Item" and "List'
These two have been linked to other activities with intent.
Now in create.java class i have 2 fields name and description and a
save button.
So that when the user clicks save button the data must get saved but
it is giving me a force close error.
This is my error message
No command output when running: 'am start -n org.finaldatabase/
org.finaldatabase.finaldatabase -a android.intent.action.MAIN -c
android.intent.category.LAUNCHER' on device emulator-5554
Exception Stack Trace
com.android.ddmlib.ShellCommandUnresponsiveException
at com.android.ddmlib.AdbHelper.executeRemoteCommand(AdbHelper.java:
408)
at com.android.ddmlib.Device.executeShellCommand(Device.java:277)
at
com.android.ide.eclipse.adt.internal.launch.ActivityLaunchAction.doLaunchAction(Unknown
Source)
at
com.android.ide.eclipse.adt.internal.launch.AndroidLaunchController.launchApp(Unknown
Source)
at
com.android.ide.eclipse.adt.internal.launch.AndroidLaunchController.simpleLaunch(Unknown
Source)
at
com.android.ide.eclipse.adt.internal.launch.AndroidLaunchController.access
$3(Unknown Source)
at com.android.ide.eclipse.adt.internal.launch.AndroidLaunchController
$3.run(Unknown Source)
Please let me know if you want to have a look at the code also.
There must be a silly mistake which i cant catch but i want to clear
this doubt .
Happy New Year
- Pedro Duque <pmduque@gmail.com> Jan 01 02:05AM ^
When developing a live wallpaper how can I get the virtual screen size? How
can I know in which virtual screen the user is in?
Thanks,
PMD
- Pedro Duque <pmduque@gmail.com> Jan 01 05:42AM ^
Let me develop on this subject:
I've develop a Live Wallpaper that was working perfectly in Android 2.1. It
emulate the standard Android wallpaper by having a bitmap scrolling when a
user changes screen.
To achieve that effect I use the event "onOffsetsChanged" to detect screen
changes when the user swipes left and right.
I just installed Android 2.2.1 and now the values returned in onOffsetsChanged
for xPixelOffset and yPixelOffset are always 0. The value for xOffset
and yOffset
do return values from 0 to 1 but because
WallpaperManager.getInstance(myContext).getDesiredMinimumHeight() and
WallpaperManager.getInstance(myContext).getDesiredMinimumHeight() now return
the screen physical size instead of the screen virtual size, I have now way
to calculate how much that percentage represent in terms of actual
displacement.
I know it's possible to achieve the desired result because the packed
wallpaper has that behaviour.
Can somebody help? Is this a problem with Samsung Galaxy S implementation or
is this a standard behaviour?
Thanks,
Pedro Duque
- TreKing <trekingapp@gmail.com> Dec 31 11:44PM -0600 ^
> Is this a problem with Samsung Galaxy S implementation or is this a
> standard behaviour?
Did you test it on the emulator?
-------------------------------------------------------------------------------------------------
TreKing <http://sites.google.com/site/rezmobileapps/treking> - Chicago
transit tracking app for Android-powered devices
- John Lussmyer <johnlussmyer@gmail.com> Dec 31 07:01PM -0800 ^
Is there a relatively easy/good way to have an app that uses LVL, also have
a Demo version?
It appears that I have to change the Package Name to do this - which changes
the Resource file name - so nothing compiles unless I go change the import
statement in all my files.
Note that I am working from within Eclipse.
Should I make my entire app an Android Library? and just have 2 nearly
empty skeleton projects to build it? (Free and Paid versions)
- TreKing <trekingapp@gmail.com> Dec 31 11:43PM -0600 ^
> hould I make my entire app an Android Library? and just have 2 nearly
> empty skeleton projects to build it? (Free and Paid versions)
Pretty much.
-------------------------------------------------------------------------------------------------
TreKing <http://sites.google.com/site/rezmobileapps/treking> - Chicago
transit tracking app for Android-powered devices
- TreKing <trekingapp@gmail.com> Dec 31 11:38PM -0600 ^
> Happy New Year TreKing :)
An a happy one to you :)
> Right, I did try using table but the column will be stretch if the text is
> longer than the image.
> Is it suppose to work this way?
By default, yes. It will just try to expand the columns to fit it's
contents. Try using weights and the shrinkable / expandable properties to
control the column widths.
> I am now thinking whether there are ways to dynamically take the screen
> measurement and draw during run time.
There's rarely good reason to deal directly with screen measurements.
-------------------------------------------------------------------------------------------------
TreKing <http://sites.google.com/site/rezmobileapps/treking> - Chicago
transit tracking app for Android-powered devices
- Bob Kerns <rwk@acm.org> Dec 31 06:44PM -0800 ^
This isn't really an Android issue. Anyone who gives out credentials
for any purpose needs to consider that they may be compromised.
The usual ways of dealing with it are to time-limit them, and to allow
them to be revoked.
But what I think REALLY should be done, is to issue credentials with
two components, one revocable by the issuer, and one revocable by the
recipient.
So, on losing your phone, you go to a website, and invalidate all the
credentials that were associated with the phone.
This wouldn't deny you access, just force you to go through the re-
credentialing process for each affected entity, using a reissued
token.
You could see extending this to three components, so a company with
accounts with Salesforce.com and similar things, could revoke access
for a terminated employee, for example. In this case, the access token
would not be reissued.
- Bob Kerns <rwk@acm.org> Dec 31 06:34PM -0800 ^
Excellent! There's no question it's hard work, and there's no doubt it
does compete with this or that feature.
But I'm confident it will pay off in quality -- and quality, in the
end, saves you time.
- Bob Kerns <rwk@acm.org> Dec 31 06:30PM -0800 ^
Then check out the ADT 9.0 Preview 2, which has improvements to drag
and drop, and up and down arrows:
http://tools.android.com/recent
- Bob Kerns <rwk@acm.org> Dec 31 06:25PM -0800 ^
HOW do you know you're not crazy? I'm missing a step in the logic
here... :=)
Seriously, it's really a shame Google uses what I'd argue is their
worst product to support Android this way.
It's too bad this isn't a Wave, perhaps Wave would have gained some
traction. (Though I suspect it wouldn't have scaled to this sort of
usage).
But most any forum software would be superior to this.
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-developers+unsubscribe@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en