Other B4A v10.50 is available for download

[Erel]

Download link: https://www.b4x.com/b4a.html

Improvements:

1. New libraries tab:
   
   
   
   
   
   
   
2. Find all references feature was rewritten. Previously it couldn't handle more complex cases, where a sub or field are called indirectly:
   For example:
   
   
   
   
   
   
3. The various IDE notifications also appear in the logs:
   
   
   
   
   
   
   
4. #CustomBuildAction - direct support for jar files, including Java 11+ UI jars.
5. Default manifest updated. This allows resetting the manifest by removing the manifest text and saving.
6. Dexer optimization can be disabled through the ini file.
7. Updated or new internal libraries: XUI, XUI Views, B4XDrawer, BCTextEngine, OkHttpUtils2, GooglePlayBilling, KeyValueStore, B4XPages template, GooglePlayBIlling and FileProvider.
8. Bug fixes and other minor improvements. This includes a long-standing bug where the wrong context was used after a resumed sleep in some edge cases (fix is relevant to B4XPages).

I wish you all a great 2021!

 

[lbaiz]

Thanks @Erel for the new version!

 

[Fredy Rodriguez]

Thanks @Erel, for you support to this great software

 

[PABLO2013]

tks

 

[NGUYEN TUAN ANH]

Thank Erel group very much and Happy new year !

 

[Pravee7094]

Nice Update! Thanks @Erel

 

[KIM jihoon]

thank you so much

 

[tuhatinhvn]

Thank you , hope soon support AttributeSet when build view library for b4a too

 

[Hamied Abou Hulaikah]

Thank you @Erel
I see this change in this release:

Dim a as string="1234"
Dim b as object="1234"
'a=b >> False in this version
'a=b >> True in old version

Is this bug? or I'm wrong in coding!

 

[gabriels]

Thank you!!

I think same way ----

I have suspected for a while you might not be completely Human - perhaps an Interstellar Genius Organism who landed on Earth

 

[LucaMs]

Thank you @Erel
I see this change in this release:

Dim a as string="1234"
Dim b as object="1234"
'a=b >> False in this version
'a=b >> True in old version

Is this bug? or I'm wrong in coding!

    Dim a As String="1234"
    Dim b As Object="1234"
    If b = a Then
        Log("True")
    Else
        Log("False")
   End If

Write the object first

 

[Hamied Abou Hulaikah]

Write the object first

But I have many projects written & worked fine without taking care of object first !!
I don't want to re-write all previous codes of projects !!!

 

[LucaMs]

But I have many projects written & worked fine without taking care of object first !!
I don't want to re-write all previous codes of projects !!!

I think it has always been like this; it certainly hasn't changed in this new version.

 

[LucaMs]

But I have many projects written & worked fine without taking care of object first !!
I don't want to re-write all previous codes of projects !!!

https://www.b4x.com/android/forum/threads/b4a-v9-90-has-been-released.119043/post-744586

 

[LucaMs]

I think it has always been like this;

Wrong; with B4A 8.80 your code works.

EDIT:
This is wrong, not the previuous one, sorry.

 

[Hamied Abou Hulaikah]

I test now again ..
I see if project created with this version all things are right, but old projects with old versions raise this behavior in current version!

https://www.b4x.com/android/forum/threads/b4a-v9-90-has-been-released.119043/post-744586

Yes, post says warning only raise, not non-equal values.

 

[agraham]

Conditional comparison is done by casting the second item to the type of the first first, so to get a String comparison it should be if a = b then. In general when using an Object type in a comparison then it should be on the right as what is probably intended is a comparison of the type of the other (first parameter). This can also be important if you are comparing numeric values and String types, to get a numeric comparison the numeric type needs to be on the left or you may get unexpected results as String values may have leading or trailing zeroes.

 

[Hamied Abou Hulaikah]

Conditional comparison is done by casting the second item to the type of the first first, so to get a String comparison it should be if a = b then. In general when using an Object type in a comparison then it should be on the right as what is probably intended is a comparison of the type of the other (first parameter). This can also be important if you are comparing numeric values and String types, to get a numeric comparison the numeric type needs to be on the left or you may get unexpected results as String values may have leading or trailing zeroes.

That is means no hope with new version to compile my old projects containing this comparison in object=string manner!
So only solution is downgrade B4A to previous one! or revise all old projects code and change *impossible, I have large codes"
I hope this problem solved asap.

 

[agraham]

I don't think anything has changed with the compiler, I think it was always like that but a new warning was added as some people were getting puzzling comparison results.

B4J v8.30 BETA is available for download

Improvements: Support for Java 14. As with Java 11, B4J expects a specific structure. You should download this package (OpenJDK 14 + OpenJFX 14): https://b4xfiles-4c17.kxcdn.com/jdk-14.0.1.zip Build standalone package - B4JPackager11 is now integrated in the IDE. This makes it simpler to build...

www.b4x.com

If it was working before I would expect it to keep working now.

 

[LucaMs]

I don't think anything has changed with the compiler,

I think it has always been like this; it certainly hasn't changed in this new version.

Wrong; with B4A 8.80 your code works.

 

[Jeffrey Cameron]

That is means no hope with new version to compile my old projects containing this comparison in object=string manner!
So only solution is downgrade B4A to previous one! or revise all old projects code and change *impossible, I have large codes"
I hope this problem solved asap.

You are missing the point. All the IDE is doing new is warning you your code has the potential to fail, it is not doing anything differently that it always has. If it was working in prior versions properly it will continue to work properly in the new version. The order of comparison may not be significant if you are sure your object variable is of the same type you are comparing.

If it makes you feel better, just add

    #IgnoreWarnings: 35

to your Activity Attributes section and/or modules.