Basic4android v2.71 is released!

[Erel]

Basic4android v2.71 is now available. I would first like to thank the beta testers for their help and feedback :icon_clap:.

This version includes many improvements including several major new features:

• Compiler warnings - A new warning engine that helps finding common errors as soon as possible:
  
  
  
  
  
• Custom views with designer support - Developers can create custom views (with classes or libraries) that can be added with the visual designer. This feature makes it possible to build the complete layout with the designer and designer scripts.
  
• Classes properties - a long-awaited feature.
  
• Bitmaps handling improved - LoadBitmap / LoadBitmapSample internally handle out of memory errors by down-scaling the image. The visual designer loads images based on the target size to preserve memory.
  
• DateTime.ListenToExternalTimeChanges - raises an event when the device time is set or when the time zone changes (and updates the internal time zone used).
  
• CallSub keyword improvements:
  
  Returns Object instead of String.​
  Sender is set when calling from a class. This is useful for events implementation.​
  Significant performance improvements when calling subs in classes.​
  No error is raised if the target sub is not found when calling from a class. This is useful for events implementation.​
• #LibraryName attribute. Sets the compiled library name.
• Libraries dependencies resolver was improved and it can now handle cases such as described here.
• Logs are colored based on the message type.
• LogColor keyword - Similar to Log. The message will be displayed in the IDE with the specified color.
• Screenshot tool improved.
• HttpUtils2 and DateUtils are now included as libraries in the IDE.
• Bug fixes and other minor improvements (including "run last deployment" feature).

Version 2.71 is now available for download from the same link as v2.70. This update fixes the following issues:

• Low quality images when adding images with the designer
• CallSub casing fails with some numeric types
• Support for the new location of aapt.exe
• Other minor improvements

 

[JanMucha]

very, very helpful!
thanks

 

[JCO]

I downloaded it this afternoon and find that it is indeed a great update.
Can't wait for tomorrow and see if the new bitmap handling solves some issues I was having with OOM errors in the app I'm developing at work.

However, there is a new behaviour in the IDE that I find quite annoying. It now scrolls the visible text up or down to the place where the cursor is. I often like to scroll up and down to see other pieces of code without changing the place the "text cursor" is.

I guess it comes from the new complier warning engine. Is there a way to turn it (momentarily) off?

Thanks to Erel for this great (as all) new version,

Julio

 

[sioconcept]

Thanks Erel !!!

 

[miguelconde]

Excelente trabajo el que estas haciendo, muy agradecido.
Excellent work that you are doing. I am very grateful.

 

[gulliver]

B4A the best purchase I have made.
Thanks Erel. :sign0060:

 

[abdulla]

Thanks Erel

 

[mangojack]

Well done once again Erel .. A brilliant product that just continues to get better.

Congrats

Cheers mj

 

[giga]

:icon_clap: BIG THANKS. Appreciate the new library access link in the program.

 

[virpalacios]

Congratulations Erel !!!

:icon_clap:

B4A is the Best!

 

[b4AMarkO]

:wav:

Im loving it ... Thanx Erel!!!!

 

[Sonny]

Occasional IDE problem

Erel,

Firstly, kudos for the update to version 2.70. You always do great work and my many thanks to you.

Now for my issue; after the update to 2.70, it appears that I occasionally get IDE issues where the creation of new methods, within a class, don't get recognized in the IDE. The code compiles properly, but I don't seem to be able to "see" the methods that I have created. When I shut down the IDE and restart, the problem goes away, and everything works properly.

This did not happen in version 2.5.2, nor did it appear to happen in version 2.70 beta - only with this latest 2.70 production release.

Sorry I can't be any more specific about this, or give you any way to reliably recreate this problem for further investigation.

Thanks.

>> Sonny <<

 

[irda]

Many thanks, great job.

 

[idong]

Great work Erel!

 

[nitinb4a]

Congrats for new b4a version

Hello Erel,

Thanks for new B4A version.

:sign0142:

 

[aalekizoglou]

Thanks Erel,

Class properties and custom views are a great plus. I don't know if this is the right place to post feedback on the new version, but anyway...

- Compiler warnings list should have a selected bar as it is for other such as log, so that we can see where the selection is.

 

[Erel]

Class properties and custom views are a great plus. I don't know if this is the right place to post feedback on the new version, but anyway..

Actually better to post it in the wishlist forum.

Compiler warnings list should have a selected bar as it is for other such as log, so that we can see where the selection is.

Not sure that I understand. You can click on any item to jump to the relevant code line.

 

[abhishek007p]

Bug?

i think i found a bug in version 2.70, please see the screenshot. it is related to the warning system, it says it unused variable but that variable was used on Sub Initialize.

here is screenshot.

http://imageshack.us/photo/my-images/855/sshot276.png

 

[bidibulle]

Thanks Erel for this release :sign0060:

 

[Erel]

it says it unused variable but that variable was used on Sub Initialize.

Are you sure that the variable is actually used and not only assigned a value?

 

[softbug]

thanks admin! thank your hard work.