Questions about B4A V2.50

klaus

Expert
Licensed User
Longtime User
A few questions about B4A V2.50 :

1) Application Label is now in the code. But the Package Name is still in the menu. Is there a rason to leave it in the menu ?

2) The header of a new project looks like this:
B4X:
#Region  Project Attributes 
    #ApplicationLabel: B4A Example
    #VersionCode: 1
    #VersionName: 
    #SupportedOrientations: unspecified
    #CanInstallToExternalStorage: False
#End Region

#Region  Activity Attributes 
    #FullScreen: False
    #IncludeTitle: True
#End Region
Loading an 'old' project it looks like this:
B4X:
#Region Module Attributes
    #FullScreen: False
    #IncludeTitle: True
    #ApplicationLabel: MyFirstProgram
    #VersionCode: 1
    #VersionName: 
    #SupportedOrientations: unspecified
    #CanInstallToExternalStorage: False
#End Region
Module Attributes for the Main module and not Project Attributes and Activity Attributes?

3) I suggest to add a comment with the possible values for
B4X:
#SupportedOrientations: unspecified 'possible values: unspecified, landscape, portrait
In the menu we saw the possible choices.

Best regards.
 

Erel

B4X founder
Staff member
Licensed User
Longtime User
1) The reason is technical. The package name is required by several tasks that run in the background of the IDE (optimized dexer, designer scripts and others). Moving the package name to the code editor makes it more difficult to handle package name changes.

2) The regions are not really important. It was simpler to implement it this way.

3) The possible values are listed in the attributes list internal help (the list that pops-up when you enter '#'). I will add a comment above this attribute.
 
Upvote 0
Top