Juhu,
I had the same problem this weekend. My DB has a size of 11 MB and I got a
Java.IO.IOException,
when I have tried to use AssesManager to transport the DB to my device. There
seems to be that the Asset Manager has a problem with greater files (I don't
figure out the exact size. sorry!)
Hi,
Android has a restriction on Asset Files which are compressed
above 1MB. All asset files
get compressed except the below file extension list
Android aapt will not compress the following file extension, namely
static const char* kNoCompressExt[] = {
".jpg", ".jp
On Aug 23, 2011, at 4:51 AM, Andreas Bräsen wrote:
> I had the same problem this weekend. My DB has a size of 11 MB and I got a
> Java.IO.IOException, when I have tried to useAssesManager to transport the DB
> to my device. There seems to be that the Asset Manager has a problem with
> greater fi
On Aug 23, 2011, at 6:14 AM, SRI wrote:
> I have renamed the sqlite db extension to mp4 to avoid the
> compression and hence able to handle big asset files.
An alternative solution is to use the mandroid -0 (zero) option [0] in the
$(MandroidExtraArgs) MSBuild property [1]. The -0 option
U can use this...
class MyAnimationListener : Java.Lang.Object,
Android.Views.Animations.Animation.IAnimationListener
{
private Activity1 activity;
public MyAnimationListener(Activity1 activity)
{
// TODO: Complete member initialization
On Aug 22, 2011, at 1:56 PM, was wrote:
> I wonder if this relates to the problems I'm having using Resco's
> AdvancedList and DetailView (DV)components when scrolling records/items. My
> recent Resco forum message on this subject:
>
> /'Further info: With 6 ComboBoxes containing nearly 1500 recor
When will be the update released. My app does not start any longer. It is
still the same message:
I am using Mono for Android as part of my master thesis. So please release
as fast as you can!
Best
andi
--
View this message in context:
http://mono-for-android.1047100.n5.nabble.com/App-crashes
I'm experiencing the crashes on both the emulator and on various hardware too
- an Acer tablet and a San Francisco mobile phone. So, hopefully, this will
be fixed by the next update.
Regards...Andrew
--
View this message in context:
http://mono-for-android.1047100.n5.nabble.com/App-crashes-tp464
Mono for Android VS 2010 tells me that the deployment was successful, but the
app is never installed in the emulator. I've searched around and tried
several "work arounds" and none of them have resolved it yet. This app has
never been installed to the emulator so it's not an uninstall/reinstall
thi
Hi
I want to change the color of a shape dynamically but I am unsure how.
http://schemas.android.com/apk/res/android";
android:shape="rectangle">
// this seems to be how do it in android
ShapeDrawable bgShape = (ShapeDrawable )btn.getBackground();
bgShape.getPaint().setColor
Hey Everyone!
We are happy to announce a new version of Mono for Android is available!
Some changes included in 1.0.3:
- Several big bugs fixed in Garbage Collection.
- Faster stepping and variable inspection when debugging in VS.
Full release notes:
http://android.xamarin.com/Releases/Mono_fo
I'm wondering if anybody has written a Polygon Tessellation utility for use
with OpenGL(TK) ES 1.1?
I mucked about, and did not find anything that would handle complex (and
self crossing) polygons.
So, before I sit down and build one, I wanted to check with the list.
smime.p7s
Description: S/
Woohoo, can't wait to get home and try this tonight and see if it solves my
GC woes.
By the way, that link is linking to the 1.0.2 release notes :)
- Greg
On Tue, Aug 23, 2011 at 4:27 PM, Jonathan Pobst wrote:
> Hey Everyone!
>
> We are happy to announce a new version of Mono for Android is
Hey Everyone!
We are happy to announce a new version of Mono for Android is available!
Some changes included in 1.0.3:
- Several big bugs fixed in Garbage Collection.
- Faster stepping and variable inspection when debugging in VS.
Full release notes:
http://android.xamarin.com/Releases/Mono_fo
Jonathan,
That's great, I've really been looking forward to this.
>From my initial tests I think most of the GC problems I was seeing have been
resolved - random crashes where the app just dies don't seem to be happening
nearly as much.
I say "as much"... to begin with I re-compiled against the
Hello.
I´ve experienced the same behaviour. It is much more stable but in some
cases it hangs or it is really slow.
Kind regards,
Carlo
-Original Message-
From: "Andrew Sinclair"
To: "'Discussions related to Mono for Android'"
Date: Wed, 24 Aug 2011 00:43:56 +0100
Subject:
On Aug 23, 2011, at 7:43 PM, Andrew Sinclair wrote:
>> From my initial tests I think most of the GC problems I was seeing have been
> resolved - random crashes where the app just dies don't seem to be happening
> nearly as much.
...
> One thing I have noticed is that the GC now seems to hang the ap
On Aug 21, 2011, at 2:36 PM, SplendidCRM wrote:
> The problem is frustrating because I don't have any more information on the
> problem. Is there any other logging information that can be enabled?
First, try Mono for Android 1.0.3. That will hopefully fix your problem.
If that fails, you can ena
On Aug 16, 2011, at 11:03 PM, emalamisura wrote:
> I added a reference to that assembly you are mentioning and it did not seem
> to fix it, the only thing I can think of is that I was calling the DB in my
> onCreate method for the launcher activity, which may be too early in the app
> lifecycle.
T
On Aug 23, 2011, at 3:50 PM, chobo2 wrote:
> // this seems to be how do it in android
> ShapeDrawable bgShape = (ShapeDrawable )btn.getBackground();
> bgShape.getPaint().setColor(Color.BLACK);
>
>
> I tried
>
>ShapeDrawable bgShape = (ShapeDrawable)
> Resources.GetDrawable(Resource.Drawable.
On Aug 23, 2011, at 3:24 PM, derikj wrote:
> *My setup*
> *OS*: Windows 7 Ultimate x64
> *IDE*: Visual Studio 2010 Premium
> *JDK*: 1.7.0 (x86 & x64)
That's your problem. You need to use JDK 1.6. JDK 1.7 is responsible for the
INSTALL_PARSE_FAILED_NO_CERTIFICATES error you're seeing.
You also ne
I'm having all kinds of problems trying to get the debugging to work in 1.0.3.
When I run my app outside of the debugger, everything seems to be fine. When I
run in the debugger and set a breakpoint, the debugger goes to lala land when
I attempt to get the value of a variable.
Is the version
To add to this, I am running on Windows7 32 bit with Visual Studio.
Wally
From: theevilprogram...@hotmail.com
To: monodroid@lists.ximian.com
Date: Tue, 23 Aug 2011 23:20:18 -0400
Subject: [mono-android] 1.0.3
I'm having all kinds of problems trying to get the debugging to work in 1.0.3.
When running on my Mac OSX with Lion and Monodevelop 2.6 RC2, I'm finding that
the new update works fine and allows me to hit breakpoints, list variable
values in watch windows, and see variable values in the immediate window. this
is working for a simple int being displayed. This only works
at least on my mac and in the emulator, the "hello world" app does seem to
startup a wee bit quicker and run just a little faster. Non-of this is earth
shatteringly faster, but it does feel just a tick better.
Wally
From: theevilprogram...@hotmail.com
To: monodroid@lists.ximian.com
Date: Tue,
Russell McVeagh
OFFICIAL LAW FIRM OF RUGBY WORLD CUP 2011
Winner - ALB Awards 2011: New Zealand Deal of the Year, Australasian Debt
Markets Deal of the Year.
Please think of the environment before printing this email.
This email contains confidential
On 8/23/2011 10:39 PM, Wally McClure wrote:
> at least on my mac and in the emulator, the "hello world" app does seem
> to startup a wee bit quicker and run just a little faster. Non-of this
> is earth shatteringly faster, but it does feel just a tick better.
The debugger changes only affect Visua
27 matches
Mail list logo
