Compiling code. 0.06
Generating R file. 0.03
Compiling generated Java code. 1.33
Convert byte code - optimized dex. Error
Unable to access jarfile C:\Android\android-sdk-windows\tools\lib\dx.jar
Standard dexer.
sp.Initialize("sp")
activity.AddView(sp,100%x/2-100dip,100%y-200dip,100dip,100dip)
sp.Add("one")
sp.Add("two")
sp.Add("two") ' Duplicating the entry kicks off the standard dexer!
When the optimized dexer fails and the standard dexer is started. It's the same path problem as before with the old structure SDK with tools under each platform.When do you get the first error? When the optimized dexer fails and the standard dexer is started? Or do you get it every time?
The optimized dexer wasn't modified in this version. It waits a few seconds before starting another background compilation. I guess that you have tried running it before the background compilation was ready.It's odd that the same code sometimes errors in the optimised dexer and some times goes through OK. Once it's worked once it seems to carry on working until you edit the code again. I've not noticed this before, but then I only noticed now because of the SDK path problem. Has anything changed in the optimised dexer? Initialisation problem somewhere?
Will check it...It's the same path problem as before with the old structure SDK with tools under each platform.
...The phone object in Phone library was changed. As most of its methods do not require any permission, the methods that do require the READ_STATE permission were moved to PhoneId and the vibrate method that requires the VIBRATE permission was moved to PhoneVibrate. This change helps with minimizing the required permissions.
The Intent object has also moved from the phone library to the core library.
Looks great!
You are passing an image, right?
I have an app that uses the Phone library to get the battery level to display (PE_BatteryChanged). I expected that when I recompiled with 1.6 and installed the new APK, it wouldn't ask for Phone permission, but it still does. What am I missing?
This is a short beta cycle. The beta version is not publicly available. The full version should be released in a few days. Currently planned for next Sunday. You will get an email once it is released.
Currently planned for next Sunday. You will get an email once it is released.
We use cookies and similar technologies for the following purposes:
Do you accept cookies and these technologies?
We use cookies and similar technologies for the following purposes:
Do you accept cookies and these technologies?