LiveCode Forums.

I've discovered that changing the Standalone App Settings > Android > Android Minimum Version settings changes the way that my app displays graphics, on both the emulator & a single real device. See the attached PNG file.

The top row in the PNG file is a screen shot of my app with Android Minimum Version = 2.3. I get the same when I use Android Minimum Version = 3.0

The 2nd row in the PNG file is a screen shot of my app with Android Minimum Version = 4.0. I get the same when I use Android Minimum Version = 4.4.

Note the square halo that surrounds the disks in the 2nd row version, but not in the top row. I've worked out that this halo is coming from the graphic type oval, with a radial gradient, and a level 25 blendoverlay, that I use to provide shading to the blue oval graphic that is in the layer underneath it.

And is it my imagination or is the 2nd row lighter that the top row?

The only thing that I changed between taking these two screen shots was the Android Minimum Version in the stand alone settings.

1) Is this a bug or a feature Seriously - I don't know if Android v4 changed the way that Livecode needed to display graphics.

2) I want my graphics to appear as they do in the top row; without a square halo. Is there any disadvantage to me specifying Android Minimum Version = 2.3? If there is no disadvantage then this is my easiest "solution".

Thanks in advance

Livecode 7.1 Indy on Windows 7

@KimD: Could you file a bug with your test stack at http://quality.livecode.com... The min android version should not be making a difference to rendering! Thanks in advance.

Thanks Mark. I will file the bug report in the middle of next week (I just need to get my beta up onto the play store first).

Is there any disadvantage in me specifying Android Minimum Version 2.3 instead of 4.0? For example - does specifying 2.3 make things run slower?

@KimD: Not to my knowledge - the majority of the engine is compiled C++ which shouldn't be affected by the min android SDK version. This is why I'm intrigued to see a sample stack reproducing the problem as it is distinctly odd!

Hi Mark

Sorry about the delay. I've managed to reproduce the issue on a very simple stack, which I attach.
- When I save this as a standalone Android app, with Minimum Android Version = 2.3, it looks fine on both my physical test device and the Android emulator.
- When I save this as a standalone Android app, with Minimum Android Version = 4.0, I get a square halo effect around the graphics on both my physical test device and the Android emulator.

Do you get the same result?

My impression is that this is something to do with Accelerated Rendering AND Minimum Android Version >= 4.0

Regards

Kim