Running Android Firemonkey application on the Intel-based devices. You can try the steps from the link below, but so far we tested this only on an emulator.
The result of this test showed it is possible to run the application, but there is a problem with debugging. http://blog.marcocantu.com/blog/2015-october-running-android-intel.html
To display a layer from the folder with TatukGIS Samples data, please add GisAllLayers unit or GisAllBasicLayers unit. Otherwise only very few standard formats, like SHP, GML, JPG, WMS, and WMTS, are supported.
To run the Android/iOS/OSX application properly, please remember about correct Deployment configuration: do not use absolute path in the project:
Note: After a local change of file content/name, it is recommended to uninstall the application manually.
TGIS_ObjectList is based on generics and, due to bugs in C++Builder, such an object cannot be deleted on the C++Builder side. A source of the problem is that generics destructors in Delphi are inlined and therefore cannot be properly called/expanded from C++ code. A workaround is to free such object using DK helper function FreeObjectNotNil See C++ version of the SplitByArc sample
TGIS_ObjectList can not be instantiated on C++ sites due to limitation described in RAD Studio documentation: How to Handle Delphi Generics in C++. Therefore the use of TGIS_ObjectList is limited to list returned by DK API.
If you encounter any of these problems on Windows:
The most common cause is a buggy DirectX 11 driver. In such a case, just force a no DX11 driver by placing this line at the end of your main form:
initialization FMX.Types.GlobalUseDX := False ;
If the problem still persists, try also to switch to software rendering by disabling DirectX entirely:
initialization FMX.Types.GlobaluseDirect2d := False ;
Those problems are not a bug in terms of the Developer Kernel. The bug(s) is located elsewhere and we have no influence on resolving it.
only VCL affected
Some PNG images (also fetched from web services like WMS & WMTS) look somehow bad having a dark hollow around features and texts. The problem is related to a bug in Delphi TPngImage class which improperly handles transparent palette. So only PNG 8, 4 bits per color are affected. A workaround for web services is to ask for “image/png24' or image/png; mode=24bit;”. You can also apply this fix: RSP-16446 and vote.
We made an effort to support HiDPI even on an older version of RAD Studio. However, due to some internal limitations, reliable support is available on RAD Studio 10.1 Berlin or newer. In older version way how forms are presented depends if HiDpi monitor is a main monitor or not. As a result, we strongly recommend disabling HiDPI, if you do not run at least RAD Studio 10.1 Berlin.
RAD Studio 10.2 Tokyo fixes a few more issues like the improper size of forms captions and therefore it is a recommended minimum version.
Generally, it works as expected. However, if you encounter endless form flashing upon moving a form between monitors with different DPI - do not blame us, instead please vote forRSP-18270.
When connecting to web services, we try to use the Embarcadero native and cross-platform THTTPClient class instead of WinInet API. Therefore a basic access authentication by prepending username:password@ to the hostname in the URL may not work correctly. Instead, USER and PASS authentication parameters should be added to the url after ? as key-value pairs.
Using THTTPClient can cause problems with connecting to some HTTPS services and handling the security certificates. Therefore to use legacy WinInet API, a user can disable the USE_NEW_HTTP_CLIENT define in GisInclude.inc source.
Starting with Android 9 (API level 28), cleartext support is disabled by default and network requests to http web services will not work. The solution is to modify the AndroidManifest.xml and enable usesCleartextTraffic by adding :
either to <application> section or as a separate network security config file.
@System@Classes@TFieldsCache@$bcctr$qqrv. There is nothing we can do - we migrated all our RAD Studios to 10.3.2. If you must stay with the previous version of RIO then you should be patient - we must wait for an official fix.