Other B4A v5.80 BETA is released!

Status
Not open for further replies.

Erel

B4X founder
Staff member
Licensed User
Longtime User
I'm happy to release B4A v5.80 BETA version.

This update includes important new features, including better support for custom views:



Improvements:

  • Custom views: [B4X] Custom Views with Enhanced Designer Support
    With this feature it is much easier to add and configure custom views.
  • #ExcludeClasses: https://www.b4x.com/android/forum/threads/new-feature-three-birds-with-one-stone.63127/
    This attribute makes it simple to exclude classes not required from libraries such as google play services.
  • CreateResource manifest editor keyword: https://www.b4x.com/android/forum/threads/new-feature-three-birds-with-one-stone.63127/#post-398974
    Allows creating XML resource files from the manifest editor.
    For example with this code we can use the native light theme based on the Android version:
    B4X:
    SetApplicationAttribute(android:theme, "@style/LightTheme")
    CreateResource(values-v20, theme.xml,
    <resources>
      <style
      name="LightTheme" parent="@android:style/Theme.Material.Light">
      </style>
    </resources>
    )
    CreateResource(values-v14, theme.xml,
    <resources>
      <style
      name="LightTheme" parent="@android:style/Theme.Holo.Light">
      </style>
    </resources>
    )

  • Debugger improvements and fixes. Mostly related to larger projects.
  • Coarse location permission added to BluetoothAdmin. Required for discovery in Android 6.
  • The default setting of the holo theme in the manifest editor was removed.
    It is recommended to use a custom theme or the device default theme.
    The compiler will issue a warning about explicit usage of the holo.theme.
  • The WYSIWYG designer defaults to material theme on Android 5+.
  • The READ_LOGS permission was removed from LogCat object. It is not useful since Android 4.1.
  • The compiler will issue a warning if the targetSdkVersion is missing or if the value is not between 14 to 22.
  • ViewsEx library - Includes two views implemented as custom views (Switch and RatingBar). The source code of this library is available in the custom views tutorial.
  • Other minor IDE improvements and bug fixes.
Developers who are eligible for a free upgrade will receive an email with upgrade instructions.
 
Last edited:

DonManfred

Expert
Licensed User
Longtime User
The Customview is only enabled when you
- have a library in use in your project which contains at least one customview
- have a Customview-Class in your project (see this example)



First activate the Libs and THEN go to the Designer. Activate for example the new ToggleSwitch library in v5.8ß

 
Upvote 0

Claudio Oliveira

Active Member
Licensed User
Longtime User
Hey guys!
@DonManfred @Erel

I'm getting this error message from designer script when 'autoscaling' a ACSwitch custom view.

An error occurred.
Error running designer script:
Property: 'textsize' not supported by this view

As there's a bunch of ACSwitch views in my layout, the AutoScaleAll statement fails as well.
Workaround so far is using AutoScale for each view but ACSwitches.
It's happening only in B4A 5.80
Works fine in B4A 5.50

Regards,
Claudio
 
Upvote 0

marcel

Active Member
Licensed User
Longtime User

Same here!
 

Attachments

  • 2016-02-13 20_06_04-Photos.png
    9.1 KB · Views: 510
Upvote 0

rproberto

Member
Licensed User
Longtime User
Hello

Confirm for Error running script designers AutoScaleAll
release a small demo
congratulations for the products
 

Attachments

  • error.zip
    59.3 KB · Views: 553
Upvote 0

Claudio Oliveira

Active Member
Licensed User
Longtime User
@Erel
I was up to send a little test project, but @rproberto did it first. Thanks, rproberto!
Well, I thought a compatibility issue between the designer and AppCompat library could raise this error, but it looks like designer scripts can't deal with any custom view, not only AppCompat's ones, as we can see from rproberto's project which uses no AppCompat views at all...
 
Upvote 0
Status
Not open for further replies.
Cookies are required to use this site. You must accept them to continue using the site. Learn more…