-
Similar Content
-
By Yaroslav Brovin
Download:
The distributive is available by request only.
Release date:
14 December 2020
New ✨
The new component TfgBottomSheetLayout was added for IDE and Android and 2 demo-samples "Components" -> "TfgBottomSheetLayout" -> "Modal mode", "Interesting places on map". Improvements ?
All headers for android.telephony were added into Android.Api.Telephony. We marked all methods of Android Api, which were introduced after Android 5.0. We restructured the grouping of header files alittle. All animation related classes were moved in new unit Android.Api.Animations. Basic text classes were moved to Android.Api.Text. Before all loaded TfgBitmap from file or stream were immutable. It meant that you were not able to use Canvas of this bitmap. So if you wanted to render on this bitmap, you had to make copy of this bitmap. Now all bitmaps are mutable by default. Bug Fixes ?
If you are using automatically opening last opened forms in FGX Native project group, sometimes forms couldn't find the assets. When you closed form, project or IDE, sometimes it could lead to raising exception. The iOS Application with Button with Icon could be crashed. When user opens TfgDrawer first time by button, panel is opened without animation. -
By Yaroslav Brovin
Download:
The distributive is available by request only.
Release date:
14 December 2020
Bug Fixes 🐛
Release 1.7.0.0 threw away several methods from Android.Api.ActivityAndView, which are used Parcelable. -
By Yaroslav Brovin
Download:
The distributive is available by request only.
Release d ate:
9 May 2020
Changelog:
* Project building: - In some cases apk android application didn't have classes.dex. Fixed. * Deployment: - Fixed deployment issue with non generating special xml files (strings.xml, colors.xml, provider_paths.xml) related to Push-notification and security file sharing. * TfgListMenu: - Added new properties: "Tag" and "TagObject" to TfgListMenuItem for storing user's data. * TfgNavigationBar: - Added new properties: "Tag" and "TagObject" to TfgNavigationBarButton for storing user's data * Assets designer: - Sometimes when saving assets, the image of the mask was lost. Fixed. -
By Yaroslav Brovin
Download:
The distributive is available by request only.
Release d ate:
16 May 2020
Changelog:
~ Loss of backward compatibility: - Assets: Renamed TfgBitmapInfo.BitmapSource -> Source. - Assets: Renamed TfgBitmapInfo.TfgBitmapSource -> TfgSource. - Assets: The public constructor is moved from TfgAsset to protected section. - Assets: GetAssetsNames returns TArray<TfgAssetName>, not a TArray<string> - Assets: Now the method of theme name normalization is a part of record helper of TfgThemeName. * Assets manager: - Dynamical saving operative memory: - Added a new method TfgAsset.ReleaseFromMemory. It is responsible for unloading from memory, heavy data associated with the resource. For example, if you no longer use an image resource, then this method will allow you to unload the bitmap from memory, thereby freeing up RAM for the system. - Now the Assets Manager can automatically unload resources from memory that are no longer used. This is the responsibility of setting TfgAssetsManager.AutoreleaseOptions.Enabled, which is disabled by default. - If you want to prevent a asset from being unloaded from memory, you can do this via the new OnShouldReleaseFromMemoryEvent event. - Now the asset takes into account the number of active clients - those who directly use the resource. All components automatically work in the "Acquire-Release" resource paradigm via the new TfgAsset.Acquire and TfgAsset.Release methods. - For dynamically added graphics assets in the runtime provided for the discharge of such resources on disk. This is the responsibility of the following settings: TfgAssetsManager.AutoreleaseOptions.DumpTarget. - Added new demo sample: "Assets" -> "Images" -> "Releasing image from memory" - Fixed memory leaks, which may have occurred when the BitmapSet resource was physically deleted. - Added more xml-documentations. - General improvements in internal implementation that are not visible to the eye. * New project wizard: - Added page for selecting a template for the new project. Two templates are currently available. Further the list will be expanded.. * TfgPageControl: - Added a new method TfgPageControl.GoToPage for animated tab selection based on the index. -
By Yaroslav Brovin
Download :
The distributive is available by request only.
Release d ate:
30 May 2020
Changelog:
* Support for Android services: - The IDE has a new wizard for managing connected Android services. It's available via main menu "Project" -> "FGX Android Services" - You can add followed service kinds via Android service manager: 1. Android Service with native part in so-library written on Delphi. 2. Classical Android service without native part. - The Manager automatically writes all the necessary information about the service in the Android manifest. - Now you can use service projects written for FMX in FGX Native. However, only if they don't use FMX. - You can user Android API from RTL or from FGX Native. Both bridges are supported. - Android service can be created by the same way as for FMX: http://docwiki.embarcadero.com/RADStudio/Sydney/en/Creating_Android_Services - General information about Android services is available in official Android documentation: https://developer.android.com/guide/topics/fundamentals/services?hl=ru - Android services supports FGX Native core. So you can use Toasts, timers and other FGX Native features. * Improvement in Java-Delphi bridge: - The work of Java listeners has been slightly accelerated. - Full support for working in Android services. - Internal improvements. * Other general improvements: - Removed the dependency of the timer implementation on the FGX Native ctivity. Now the timer can be used in Android services. - Now the registration of platform core services in Android is based on whether it is an Android activity or an Android service. - The dependency on Android activity is removed from the implementation of timers. Timers can now be used in Android services. However, you need to keep in mind that in the services of the timers should not be used for long-term operation. Since Android is slow down timers, which leads to them falling asleep after a certain period of time.
-
-
Recently Browsing 0 members
No registered users viewing this page.
Recommended Posts