Android Question B4A Upgrade Path - Advice Needed

[Highwinder]

Hi everyone.

The last projects I wrote was in B4A v2 and v3, before some major changes had taken place to B4A in following versions. These changes are a bit confusing to someone coming back in the door a few versions later. Particularly, I am confused about several issues as I try to bring my projects from v2/3 into v5.5 (skipping right over v4).

My questions:

1. What's the deal with manifest file editing and how has it changed since v2 or v3? I seem to remember something about a major upgrade or change on this issue.
2. Does the manifest editor edit the whole manifest file? Or is it just an editor for things that will be added to a larger manifest file? I find this confusing.
2. Do I still have to manually edit the manifest file on top of having to fill in the new "Region" code sections and also on top of still needing to use the manifest editor? This seems like a big mess to me.
3. What's the deal with the new "Region" code that replaces the old pulldown menu options, and how do I make sure I'm doing it right? Does it override manifest editor/file? More confusion.
4. B4A v5.5 told me that my v2/3 project's files (additional graphics and sound files) could not be found. I was told that my projects should open just fine, but I'm finding that not to be the case.
5. What else should I be aware of as far as upgrade path issues?

Thanks so much,

Bob

 

[eurojam]

Hi Bob,
did you check the change log history: https://www.b4x.com/android/forum/threads/b4a-change-log-versions-history.19332/

 

[Highwinder]

Hi Bob,
did you check the change log history: https://www.b4x.com/android/forum/threads/b4a-change-log-versions-history.19332/

I will certainly start by reading through that entire thread, it looks like it might be very helpful, thank you. I'll still need some advice about B4A's manifest file handling however, as a description of new features doesn't always explain how to properly use them or answer the questions.

 

[DonManfred]

I try to give some light on it (maybe wrong or missing something )

You dont need to edit a manifest-file by hand (outside b4a) at all.

b4a is, while compiling, generating a new one each time. Some parts of the new manifest file comes from the region (app name, version)
some comes out of the content of the ide manifest editor.

I think a general rule can be; all changes to the manifest will be put in the manifesteditor in the ide. You just need/use this editor. Nothing else

 

[Highwinder]

I try to give some light on it (maybe wrong or missing something )

You dont need to edit a manifest-file by hand (outside b4a) at all.

b4a is, while compiling, generating a new one each time. Some parts of the new manifest file comes from the region (app name, version)
some comes out of the content of the ide manifest editor.

I think a general rule can be; all changes to the manifest will be put in the manifesteditor in the ide. You just need/use this editor. Nothing else

Good to know, thank you. I am used to the old way of manually editing the manifest file and telling B4A to leave it alone so it doesn't screw it up at compile.