S Startup Active Member Licensed User Longtime User Feb 18, 2016 #1 I run the TabHost example from Erel's TabHost tutorial with no problem as long as I ignore the Logs' messages to 1. Add android:targetSDKVersion="14" and 2. Add SetApplicationAttribute(android:theme, "@android:style/Theme.Holo") ... to the manifest editor. When I add these lines to the manifest file and make the log messages (above) go away I find I can't run the code and instead get a message "Generating R file. Error AndroidManifest.xml:11: error: Error parsing XML: not well-formed (invalid token)." Should I just ignore the messages to change the manifest file and leave it alone or what should I do?
I run the TabHost example from Erel's TabHost tutorial with no problem as long as I ignore the Logs' messages to 1. Add android:targetSDKVersion="14" and 2. Add SetApplicationAttribute(android:theme, "@android:style/Theme.Holo") ... to the manifest editor. When I add these lines to the manifest file and make the log messages (above) go away I find I can't run the code and instead get a message "Generating R file. Error AndroidManifest.xml:11: error: Error parsing XML: not well-formed (invalid token)." Should I just ignore the messages to change the manifest file and leave it alone or what should I do?
Erel B4X founder Staff member Licensed User Longtime User Feb 19, 2016 #2 You should add the targetSdkVersion and don't add the SetApplicationAttribute. The warning will be removed in v5.80. If you get any error then please post the full error message from the logs. Upvote 0
You should add the targetSdkVersion and don't add the SetApplicationAttribute. The warning will be removed in v5.80. If you get any error then please post the full error message from the logs.
S Startup Active Member Licensed User Longtime User Feb 19, 2016 #3 Erel said: You should add the targetSdkVersion and don't add the SetApplicationAttribute. The warning will be removed in v5.80. If you get any error then please post the full error message from the logs. Click to expand... OK. That works, but it works better if I leave the manifest alone and don't make any changes. When I change the line .... <uses-sdk android:minSdkVersion="4" /> to <uses-sdk android:targetSdkVersion="14" /> the txtName label displays without the nice border and the btnNext1 gets partially covered by the soft keyboard. Would it not be best to not make either add/change to the manifest and leave it alone? Upvote 0
Erel said: You should add the targetSdkVersion and don't add the SetApplicationAttribute. The warning will be removed in v5.80. If you get any error then please post the full error message from the logs. Click to expand... OK. That works, but it works better if I leave the manifest alone and don't make any changes. When I change the line .... <uses-sdk android:minSdkVersion="4" /> to <uses-sdk android:targetSdkVersion="14" /> the txtName label displays without the nice border and the btnNext1 gets partially covered by the soft keyboard. Would it not be best to not make either add/change to the manifest and leave it alone?
Erel B4X founder Staff member Licensed User Longtime User Feb 21, 2016 #4 minSdkVersion and targetSdkVersion are not related to each other. If you don't set targetSdkVersion then your app will run with Android 2 style. Your app will look "old". Upvote 0
minSdkVersion and targetSdkVersion are not related to each other. If you don't set targetSdkVersion then your app will run with Android 2 style. Your app will look "old".
S Startup Active Member Licensed User Longtime User Feb 21, 2016 #5 Erel said: minSdkVersion and targetSdkVersion are not related to each other. If you don't set targetSdkVersion then your app will run with Android 2 style. Your app will look "old". Click to expand... OK. Thanks! Upvote 0
Erel said: minSdkVersion and targetSdkVersion are not related to each other. If you don't set targetSdkVersion then your app will run with Android 2 style. Your app will look "old". Click to expand... OK. Thanks!