NativeBase (API Reference)
Class NativeBase
- Direct Known Subclasses:
AdministrativeRulesLoader,Angle,AreaCameraBehavior,AssetsManager,Authentication,AuthenticationMode,AutomotiveCameraBehavior,CatalogUpdateTask,CatalogVersionHint,Crosswalk,DataAttributes,DataAttributesAccessor,DataAttributesBuilder,DataAttributeValue,DynamicCameraBehavior,DynamicRoutingEngine,Easing,ElectronicHorizonDataLoader,ElectronicHorizonEngine,EVChargingLocation,EVSearchEngine,ExternalMapDataSourceClient,ExternalMapDataSourceServer,FixedCameraBehavior,FlingHandler,Gestures,GPXDocument,GPXTrack,GPXTrackWriter,HereMap,IndexRange,IndoorManeuver,IndoorRouteStyle,IndoorRoutingController,IndoorRoutingEngine,IndoorWaypoint,Isoline,IsolineRoutingEngine,JsonStyleFactory,LineData,LineDataAccessor,LineDataBuilder,LineDataSource,LineDataSourceBuilder,LineTileDataSource,LocationIndicator,LocationSimulator,LockingProcess,LogControl,Maneuver,MapArrow,MapCamera,MapCameraAnimation,MapCameraAnimationFactory,MapCameraKeyframeTrack,MapCameraLimits,MapCameraUpdate,MapCameraUpdateFactory,MapContentSettings,MapContext,MapDownloader,MapDownloaderTask,MapImage,MapImageOverlay,MapItemKeyFrameTrack,MapItemRepresentation,MapLayer,MapLayerBuilder,MapLayerMapMeasureDependentStorageLevels,MapLayerPriority,MapLayerPriorityBuilder,MapMarker,MapMarker.TextStyle,MapMarker3D,MapMarker3DModel,MapMarkerAnimation,MapMarkerCluster,MapMatcher,MapObjectDescriptor,MapPickResult,MapPolygon,MapPolyline,MapPolylineAnimation,MapScene,MapScene.MapPickFilter,MapSceneLights,MapSceneLoadOptions,MapSceneLoadOptionsBuilder,MapUpdater,MapUpdateTask,MapVersionHandle,Mesh,MeshBuilder,Metadata,MyPlaces,Navigator,OfflineRoutingEngine,OfflineSearchEngine,OfflineSearchIndex,PickMapContentResult,PickMapContentResult.TrafficIncidentResult,PickMapItemsResult,Place,PlaceCategory,PointData,PointDataAccessor,PointDataBuilder,PointDataSource,PointDataSourceBuilder,PointTileDataSource,PolygonData,PolygonDataAccessor,PolygonDataBuilder,PolygonDataSource,PolygonDataSourceBuilder,PolygonPrefetcher,PolygonTileDataSource,PolylineSimplifier,Property,RasterDataSource,RefreshRouteOptions,Route,RoutePrefetcher,RoutingEngine,ScaleHandler,ScrollHandler,SDKBuildInformation,SDKCache,SDKLogger,SDKNativeEngine,SearchEngine,Section,SegmentData,SegmentDataLoader,SegmentReferenceConverter,SegmentSpanData,Span,SpatialAudioCuePanning,SpeedBasedCameraBehavior,Style,Suggestion,Threading,TileGeoBoundsCalculator,TileUrlProviderFactory,TimeRule,TrackingCameraBehavior,TrackingCameraBehavior.ZoomPolicy,TrafficBroadcast,TrafficDataProvider,TrafficEngine,TrafficFlow,TrafficIncident,TrafficIncidentOnRoute,TransitRoutingEngine,TranslucentMapLayerGroup,TransportSpecification.BicycleBuilder,TransportSpecification.BusBuilder,TransportSpecification.CarBuilder,TransportSpecification.PedestrianBuilder,TransportSpecification.PrivateBusBuilder,TransportSpecification.ScooterBuilder,TransportSpecification.TaxiBuilder,TransportSpecification.TruckBuilder,VehicleSpecification.BusBuilder,VehicleSpecification.CarBuilder,VehicleSpecification.PrivateBusBuilder,VehicleSpecification.ScooterBuilder,VehicleSpecification.TaxiBuilder,VehicleSpecification.TruckBuilder,Venue,VenueDrawing,VenueEngine,VenueGeometry,VenueGeometry.InternalAddress,VenueGeometryStyle,VenueInfo,VenueLabelStyle,VenueLevel,VenueMap,VenueModel,VenueService,VenueStyle,VenueTopology,VenueTopology.AccessCharacteristics,VisualNavigator,VisualNavigatorColors,W3WSearchEngine
Internal base class for public non-POD objects to manage the lifecycle of underlying C++ objects. While the class is public for technical reasons, but should be considered internal and not part of the public API and thus not used directly.
Java classes which wrap C++ objects inherit from NativeBase to
- reference the C++ object
- manage the lifecycle of C++ object
Cleanup of C++ objects is done automatically as long as there are new subclasses of NativeBase created. Currently there is no explicit way to destroy the underlying C++ object of a Java wrapper. This is intentional because normally no manual cleanup is necessary. Additionally the client of the Java wrapper would need additional knowledge of the underlying implementation to be able to decide whether or not cleanup is necessary. It is not clear for the client which object needs cleanup and which doesn't if all objects have auto-generated cleanup functions. So instead API designers should manually define methods if resource cleanup is necessary.
-
Method Summary