Mpreviews

My guide on how to figure out what Latin American Country you are in

2022.03.19 17:46 slipperysoup My guide on how to figure out what Latin American Country you are in

Im not a pro player but I’m decent enough and can be able to differentiate Latin American countries pretty good but I still make some very dumb guesses often.
This is just for South America + Mexico + Guatemala
For Latin America the sun, road signs, Electric meters, electric poles and googles cars are typically what can help you differentiate. Google cars probably being the most useful
Sun in the South = Northern Hemispehere and vice versa
Note that Mexico and Brazil can sometimes have an inaccurate compass for some reason
South America has PARE stop signs, Mexico and Guatemala has ALTO
Mountains: Remember for South America, the western side is the most mountainous, so that is Chile, Bolivia, Peru, Colombia, Ecuador, and the Western half of Argentina. Mexico also has some very mountainous regions
I will bold what I think are the most useful tips for countries:
COLOMBIA:

has yellow license plates
is very tropical and mountainous
there is a cross on the back of road signs, I believe I have seen a cross on the back of Brazilian signs, however you shouldn’t get confused as Brazilian signs are always black on the back.

ECUADOR:

is also very tropical/mountainous and looks similar to Colombia
They have white bollards with 2 red rings like this
They have unique electric poles where it has steps up the pole. Brazil has similar but Ecuador there is more steps. Brazilian looks like this. Ecuador looks like this

PERU:

has a White or Black google car with no antenna
Can be Tropical but often times can also be sandy, dry and mountainous
Very common to see sign poles with a black and white pattern like this
Peru also super unique electric meters (skip to 2:17) outside buildings/homes. Electric meters in Peru have unique horizontal double/triple slits that doesn’t exist anywhere else. This is most helpful when you are on a street with lots of buildings. This clue i will say is not as easy to find as others. Only use when you have unlimited time not on timed rounds

CHILE:

will only ever have white car. They look like this. Peru and Bolivia can also have a white google car. However Chile’s car can sometimes be white with a black outline on the bottom and the white is more pronounced like this. This will only ever be in Chile so definitely look out for this
typically very dry and mountainous everywhere, can also be grassy/flat/tropical occasionally. (I’m not as good with Chile’s biome still very often throws me off)
Can find white bollards with a single black stripe that has a yellow or white rectangle inside the black stripe (one side the rectangle is yellow other is white). It looks like this
Can find unique electric poles with a narrow indentation on the lower part and has small holes on the top like this. This is similar to Brazil/Ecuador but there are no “steps” for Chile
Taxis in Chile can have an orange license plate like this

BOLIVIA:

dry and mountainous, sometimes tropical . Similar to Peru
Only White car
I don’t really know any solid ways of differentiating Bolivia, typically I go off the feel or process of elimination

Argentina:

black or blue car
very flat on the eastern side, the western side can be more dry and similar to Chile. Argentina most often though you will be on a flat road on a grassy biome, it’s probably one of the easiest country to guess with how often you see this. Uruguay can also be flat and look like Argentina however Argentina comes up more for me personally
License plates in Argentina when blurred look grey/white with a black dot in the middle like this

URUGUAY

will only have black car
pretty much will always be flat and grassy, looks very similar to Argentina

BRAZIL:

Can have white car with antenna or blue car
Very diverse biomes, can be decievjng and look like other countries
Very common to see red dirt roads. Not guaranteed, but Brazil is most common in Latin America to have red soil. Note red soil can be common in other continents like places like Cambodia and Ghana, but Brazil is the safest guess in Latin America.
Have steps in their electric poles, can also see in Ecuador but in Brazil they are spread out and Ecuador is more condensed. See Ecuador to look at the poles
Brazilian road signs are very often black on the backside, other countries can be black occasionally but it’s a safe assumption to think Brazil

MEXICO:

one of the most diverse countries, probably has like every biome possible
being in North America, Sun is in the south (occasionally compass can be wrong)
stop signs say ALTO.
Have circular electric meters on buildings like this. This can be found in other North American countries, should only look for this when differentiating Mexico vs South America
I really don’t know any super reliable clue for Mexico when the above is not helpful. I’m terrible at Mexico in general and mostly use process of elimination of it doesn’t make sense for other countries

GUATEMALA:

Have unique roof rack google car like this Do not confuse this with Dominican Republic that has a thicker black colour and Guatemala has mirrors on the car
Not much hints are needed, the google car typically is enough
typically very green and tropical

Cars summary:
blurry white car + sometimes antenna: Mexico, Brazil, Colombia, Ecuador

Sometimes the antenna is not visible, however you should make sure to not get the white cars when there is no antenna for these countries with Peru/Chile/Bolivia. The car for these countries often look smudged/blurry, while Peru/Chile/Bolivia, the white car is not blurred and very visible

blurry black car + sometimes antenna: Colombia

as far as I know this is only in Colombia. once again like the blurry white car, the black car in Colombia is blurred unlike Argentina/Uruguay which have a clear black car and may not always have an antenna.

clear white car + never has antenna : Peru, Bolivia, Chile, Brazil
clear black car and never has antenna:Argentina, Uruguay
Blue Car: Mexico, Brazil, and Argentina
Roof rack: Guatemala, Dominican Republic
Use geotips.com for more but what I wrote is the tips that I use that will help way more on a regular basis
Even with all this, South America is still very tricky, Mexico and Brazil are one of the most frustrating countries to figure out for me and I often still make dumb guesses
If anybody has common reliable clues that work for differentiating one specific Latin American country feel free to comment what I have missed

submitted by slipperysoup to geoguessr [link] [comments]

2022.03.08 10:29 HDGTurkey LibGDX Demo Game Application With ML Kit Hand Gesture Detection and Ashley System Library Part 1

https://preview.redd.it/vl9h7ph5p4m81.jpg?width=1400&format=pjpg&auto=webp&s=6629feb6c63f7fa3a0233b5beb041b552b484936

Introduction

In this demo application, we will build LibGDXDemo Game Application with ML Kit Hand Gesture Detection and Ashley Entity System Library. If you didn’t know anything about LibGDX you can read my first article about LibGDX at this link. Firstly, I will explain the LibGDX Ashley Entity System Library and how to use and implement this Library in LibGDX. After that, I will explain the ML Kit Hand Gesture Detection and how to implement it. Finally, we will create a custom camera view to use hand gesture detection while playing the game.

Integrating Applications to HMS Core

To start developing an app with Huawei mobile services, you need to integrate your application to the HMS core. Check the link below to integrate your application, also don’t forget to enable the ML Kit from AppGallery Connect.
https://medium.com/huawei-developers/android-integrating-your-apps-with-huawei-hms-core-1f1e2a090e98

Ashley Entity System Library

Ashley Entity System is an Entity System library that’s managed under the LibGDX organization and is well-suited for game development. It depends on LibGDX utility classes. Entity systems provide a different way to manage data and functionality towards large sets of objects without having to make the object classes rich with inheritance. Utilizing Ashley might be a helpful approach for those looking for an object modeling approach like Unity provides, but with the scope of a framework instead of the game engine.
Ashley Library is formed by the combination of Entity, System, Component, and Engine.
Entity: Entities are game object it exists in our game world used with a list of components
Component: Components are game data, it is used with entities and systems
System: Systems are game logic used with the Family to use specific entities. There are three systems in Ashley Library. These are Interval System, Entity System, Iterating System.
Family: Families are groups of components. it defines which components should be used in a specific System. Systems only work with those components
Engine: The engine class is the core class and center of our Ashley Library. We can add systems and entities using the Engine Class.

ML Kit Hand Gesture Detection

This service provides two capabilities: hand keypoint detection and hand gesture recognition. The hand keypoint detection capability can detect 21 hand keypoints (including fingertips, knuckles, and wrists) and return positions of the key points. The hand gesture recognition capability can detect and return the positions of all rectangle areas of the hand from images and videos, and the type and confidence of a gesture. This capability can recognize 14 gestures, including the thumbs-up/down, OK sign, fist, finger heart, and number gestures from 1 to 9. Both capabilities support detection from static images and real-time camera streams. I use hand gesture detection and choose the number one sign to move the player in this project.

Assigning Permissions in the Manifest File

The ML Kit SDK Hand Gesture Services requires some permissions. We should declare the permissions in the AndroidManifest.xml file as follows:

 ... Camera permission  Write permission  ...

Preparations for the Code

After adding permission to AndroidManifest.xml we need to add dependency of ML Kit Hand Gesture Service to Project/build.gradle file.

We should define our android specific services under Project/ build.gradle in the android header for Libgdx Application.

project(":android") { apply plugin: "android" apply plugin: "kotlin-android" apply plugin: 'com.huawei.agconnect' apply plugin: 'com.android.application' //dagger hilt apply plugin: 'kotlin-kapt' configurations { natives } configurations { natives } dependencies { implementation project(":core") api "com.badlogicgames.gdx:gdx-backend-android:$gdxVersion" annotationProcessor "com.squareup.dagger:dagger-compiler:1.2.2" natives "com.badlogicgames.gdx:gdx-platform:$gdxVersion:natives-armeabi-v7a" natives "com.badlogicgames.gdx:gdx-platform:$gdxVersion:natives-arm64-v8a" natives "com.badlogicgames.gdx:gdx-platform:$gdxVersion:natives-x86" natives "com.badlogicgames.gdx:gdx-platform:$gdxVersion:natives-x86_64" api "com.badlogicgames.gdx:gdx-box2d:$gdxVersion" natives "com.badlogicgames.gdx:gdx-box2d-platform:$gdxVersion:natives-armeabi-v7a" natives "com.badlogicgames.gdx:gdx-box2d-platform:$gdxVersion:natives-arm64-v8a" natives "com.badlogicgames.gdx:gdx-box2d-platform:$gdxVersion:natives-x86" natives "com.badlogicgames.gdx:gdx-box2d-platform:$gdxVersion:natives-x86_64" api "com.badlogicgames.ashley:ashley:$ashleyVersion" api "com.badlogicgames.gdx-controllers:gdx-controllers-android:$gdxControllersVersion" api "org.jetbrains.kotlin:kotlin-stdlib:$kotlinVersion" api 'com.huawei.agconnect:agconnect-core:1.4.1.300' api 'com.huawei.hms:hianalytics:6.2.0.301' api 'com.huawei.hms:hwid:6.1.0.302' api 'com.huawei.hms:game:5.0.4.303' //ML Kit Hand Gesture Service implementation 'com.huawei.hms:ml-computer-vision-handkeypoint:3.2.0.300' // Import the hand keypoint detection model package. implementation 'com.huawei.hms:ml-computer-vision-handkeypoint-model:3.2.0.300' // Import the hand gesture recognition model package. implementation 'com.huawei.hms:ml-computer-vision-gesture-model:3.2.0.300'

We can define the ML Kit Hand Gesture Service dependency in the project(“: android”) dependencies.

Lens Engine Preview Class

We use this preview class to control the Lens Engine and Graphic Overlay. We can use start and stop functions to start or stop the Lens Engine.

Lens Engine: Lens Engine a class with the camera initialization, frame obtaining, and logic control functions encapsulated.

class LensEnginePreview(private val mContext: Context) : ViewGroup(mContext) { private val mSurfaceView: SurfaceView private var mStartRequested = false private var mSurfaceAvailable = false private var mLensEngine: LensEngine? = null private var mOverlay: GraphicOverlay? = null @Throws(IOException::class) fun start(lensEngine: LensEngine?) { if (lensEngine == null) { stop() } mLensEngine = lensEngine if (mLensEngine != null) { mStartRequested = true startIfReady() } } @Throws(IOException::class) fun start(lensEngine: LensEngine?, overlay: GraphicOverlay?) { mOverlay = overlay this.start(lensEngine) } fun stop() { if (mLensEngine != null) { mLensEngine!!.close() } } fun release() { if (mLensEngine != null) { mLensEngine!!.release() mLensEngine = null } } @Throws(IOException::class) private fun startIfReady() { if (mStartRequested && mSurfaceAvailable) { mLensEngine!!.run(mSurfaceView.holder) if (mOverlay != null) { val size = mLensEngine!!.displayDimension val min = Math.min(size.width, size.height) val max = Math.max(size.width, size.height) if (isPortraitMode) { mOverlay!!.setCameraInfo(min, max, mLensEngine!!.lensType) } else { mOverlay!!.setCameraInfo(max, min, mLensEngine!!.lensType) } mOverlay!!.clear() } mStartRequested = false } } private inner class SurfaceCallback : SurfaceHolder.Callback { override fun surfaceCreated(surface: SurfaceHolder) { mSurfaceAvailable = true try { startIfReady() } catch (e: IOException) { Log.e(TAG, "Could not start camera source.", e) } } override fun surfaceDestroyed(surface: SurfaceHolder) { mSurfaceAvailable = false } override fun surfaceChanged(holder: SurfaceHolder, format: Int, width: Int, height: Int) {} } override fun onLayout(changed: Boolean, left: Int, top: Int, right: Int, bottom: Int) { var previewWidth = 480 var previewHeight = 360 if (mLensEngine != null) { val size = mLensEngine!!.displayDimension if (size != null) { previewWidth = size.width previewHeight = size.height } } if (isPortraitMode) { val tmp = previewWidth previewWidth = previewHeight previewHeight = tmp } val viewWidth = right - left val viewHeight = bottom - top val childWidth: Int val childHeight: Int var childXOffset = 0 var childYOffset = 0 val widthRatio = viewWidth.toFloat() / previewWidth.toFloat() val heightRatio = viewHeight.toFloat() / previewHeight.toFloat() if (widthRatio > heightRatio) { childWidth = viewWidth childHeight = (previewHeight.toFloat() * widthRatio).toInt() childYOffset = (childHeight - viewHeight) / 2 } else { childWidth = (previewWidth.toFloat() * heightRatio).toInt() childHeight = viewHeight childXOffset = (childWidth - viewWidth) / 2 } for (i in 0 until this.childCount) { getChildAt(i).layout(-1 * childXOffset, -1 * childYOffset, childWidth - childXOffset, childHeight - childYOffset) } try { startIfReady() } catch (e: IOException) { Log.e(TAG, "Could not start camera source.", e) } } private val isPortraitMode: Boolean private get() { val orientation = mContext.resources.configuration.orientation if (orientation == Configuration.ORIENTATION_LANDSCAPE) { return false } if (orientation == Configuration.ORIENTATION_PORTRAIT) { return true } Log.d(TAG, "isPortraitMode returning false by default") return false } companion object { private val TAG = LensEnginePreview::class.java.simpleName } init { mSurfaceView = SurfaceView(mContext) mSurfaceView.holder.addCallback(SurfaceCallback()) this.addView(mSurfaceView) } }

Graphic Overlay Class

I use this class to render a series of custom graphics to be overlayed on top of an associated preview (i.e., the camera preview). The creator can add graphics objects, update the objects, and remove them, triggering the appropriate drawing and invalidation within the view. Supports scaling and mirroring of the graphics relative to the camera’s preview properties. The idea is that detection items are expressed in terms of a preview size but need to be scaled up to the full view size, and also mirrored in the case of the front-facing camera.

class GraphicOverlay(context: Context?) : View(context) { private val mLock = Any() private var mPreviewWidth = 0 private var mWidthScaleFactor = 1.0f private var mPreviewHeight = 0 private var mHeightScaleFactor = 1.0f private var mFacing = LensEngine.BACK_LENS private val mGraphics: MutableSet = HashSet() abstract class Graphic(private val mOverlay: GraphicOverlay) { /** * Draw the graphic on the supplied canvas. Drawing should use the following methods to * convert to view coordinates for the graphics that are drawn: * * 1. [Graphic.scaleX] and [Graphic.scaleY] adjust the size of * the supplied value from the preview scale to the view scale. * 1. [Graphic.translateX] and [Graphic.translateY] adjust the * coordinate from the preview's coordinate system to the view coordinate system. * * * @param canvas drawing canvas */ abstract fun draw(canvas: Canvas?) /** * Adjusts a horizontal value of the supplied value from the preview scale to the view * scale. */ fun scaleX(horizontal: Float): Float { return horizontal * mOverlay.mWidthScaleFactor } fun unScaleX(horizontal: Float): Float { return horizontal / mOverlay.mWidthScaleFactor } /** * Adjusts a vertical value of the supplied value from the preview scale to the view scale. */ fun scaleY(vertical: Float): Float { return vertical * mOverlay.mHeightScaleFactor } fun unScaleY(vertical: Float): Float { return vertical / mOverlay.mHeightScaleFactor } /** * Adjusts the x coordinate from the preview's coordinate system to the view coordinate * system. */ fun translateX(x: Float): Float { return if (mOverlay.mFacing == LensEngine.FRONT_LENS) { mOverlay.width - scaleX(x) } else { scaleX(x) } } /** * Adjusts the y coordinate from the preview's coordinate system to the view coordinate * system. */ fun translateY(y: Float): Float { return scaleY(y) } fun postInvalidate() { mOverlay.postInvalidate() } } /** * Removes all graphics from the overlay. */ fun clear() { synchronized(mLock) { mGraphics.clear() } postInvalidate() } /** * Adds a graphic to the overlay. */ fun add(graphic: Graphic) { synchronized(mLock) { mGraphics.add(graphic) } postInvalidate() } /** * Removes a graphic from the overlay. */ fun remove(graphic: Graphic) { synchronized(mLock) { mGraphics.remove(graphic) } postInvalidate() } /** * Sets the camera attributes for size and facing direction, which informs how to transform * image coordinates later. */ fun setCameraInfo(previewWidth: Int, previewHeight: Int, facing: Int) { synchronized(mLock) { mPreviewWidth = previewWidth mPreviewHeight = previewHeight mFacing = facing } postInvalidate() } /** * Draws the overlay with its associated graphic objects. */ override fun onDraw(canvas: Canvas) { super.onDraw(canvas) synchronized(mLock) { if (mPreviewWidth != 0 && mPreviewHeight != 0) { mWidthScaleFactor = canvas.width.toFloat() / mPreviewWidth.toFloat() mHeightScaleFactor = canvas.height.toFloat() / mPreviewHeight.toFloat() } for (graphic in mGraphics) { graphic.draw(canvas) } } } }

Associated [Graphic] items should use the following methods to convert to view coordinates for the graphics that are drawn: [Graphic.scaleX] and [Graphic.scaleY] adjust the size of the supplied value from the preview scale to the view scale. [Graphic.translateX] and [Graphic.translateY] adjust the coordinate from the preview’s coordinate system to the view coordinate system.

Custom Camera View Class

I create this class by using the device camera to recognize hand gestures and movement rectangles on the game screen.

object CustomCameraView { fun initView (context: Context,gameView:View,mPreview:LensEnginePreview,mOverlay:GraphicOverlay):View { val mainLayout= RelativeLayout(context) mainLayout.id=R.id.adLensId val lensLayout= RelativeLayout(context) val overlayParams= RelativeLayout.LayoutParams(ViewGroup.LayoutParams.WRAP_CONTENT, ViewGroup.LayoutParams.WRAP_CONTENT) val previewParams= RelativeLayout.LayoutParams(200,140) val lensParams= RelativeLayout.LayoutParams(ViewGroup.LayoutParams.MATCH_PARENT,140) overlayParams.addRule(RelativeLayout.ALIGN_PARENT_TOP, RelativeLayout.CENTER_IN_PARENT) previewParams.addRule(RelativeLayout.ALIGN_PARENT_TOP, RelativeLayout.CENTER_IN_PARENT) lensLayout.addView(mPreview,previewParams) lensLayout.addView(mOverlay,overlayParams) val gameParams= RelativeLayout.LayoutParams(ViewGroup.LayoutParams.MATCH_PARENT, ActionBar.LayoutParams.MATCH_PARENT) gameParams.addRule(RelativeLayout.BELOW,mainLayout.id) mainLayout.addView(gameView,gameParams) mainLayout.addView(lensLayout,lensParams) return mainLayout } }

I create two dynamic Relative Layouts to show the camera on the game screen. For creating the dynamic layouts we should define Layout params and Rules. I use Layout params for defining the width and height of the layouts. Also, I use rules for defining the location of the relative layouts on the screen.

Hand Analyzer Transactor

I create the HandAnalyzerTransactor class for processing recognition results. This class implements the MLTransactor API and uses the transactResult method in this class to obtain the recognition results and implement specific services.

class HandAnalyzerTransactor(private val mGraphicOverlay: GraphicOverlay) : MLTransactor { /** * Process the results returned by the analyzer. */ override fun transactResult(result: MLAnalyzer.Result) { mGraphicOverlay.clear() val handGestureSparseArray = result.analyseList val list: MutableList = ArrayList() for (i in 0 until handGestureSparseArray.size()) { list.add(handGestureSparseArray.valueAt(i)) } val graphic = HandGestureGraphic(mGraphicOverlay, list) mGraphicOverlay.add(graphic) } override fun destroy() { mGraphicOverlay.clear() } }

(in line 12) I call HandGestureGraphic class with mGraphicOverlay parameter and list parameter to get the real coordinate of the result points.

Hand Gesture Graphic

I use this class for getting results points and adjusting coordinates from the preview’s coordinates system to the view coordinates system.

class HandGestureGraphic(overlay: GraphicOverlay?, private val results: MutableList) : Graphic(overlay!!) { override fun draw(canvas: Canvas?) { for (i in results.indices) { val mlGesture = results[i] val rect = translateRect(mlGesture!!.rect) if(mlGesture.category==MLGesture.ONE){ GameConfig.TOUCH_LEFT_RIGHT= (rect.centerX()-200f)/100f if(GameConfig.TOUCH_LEFT_RIGHT>=6f){ GameConfig.TOUCH_LEFT_RIGHT= 6f } } } } private fun translateRect(rect: Rect): Rect { var left = translateX(rect.left.toFloat()) var right = translateX(rect.right.toFloat()) var bottom = translateY(rect.bottom.toFloat()) var top = translateY(rect.top.toFloat()) if (left > right) { val size = left left = right right = size } if (bottom < top) { val size = bottom bottom = top top = size } return Rect(left.toInt(), top.toInt(), right.toInt(), bottom.toInt()) } }

(In lines 5–6) I get the result lists every member and translate this rectangle to real view coordinates with the help of translateRect method. (In lines 8–13). I get the mlGesture.category and use the rect.centerX() method to get hand-moving coordinates and give that coordinates to my constant value to move the player.

ML Kit Class

We should create that class under the android folder.

class MLKit(private val context: Context) { private var tag: String = "MLKit" private var mPreview: LensEnginePreview? = null private var mOverlay: GraphicOverlay? = null private var mAnalyzer: MLGestureAnalyzer? = null private var mLensEngine: LensEngine? = null private var mLensType = LensEngine.BACK_LENS // Create Hand analyzer fun createHandAnalyzer() { val setting = MLGestureAnalyzerSetting.Factory() .create() mAnalyzer = MLGestureAnalyzerFactory.getInstance().getGestureAnalyzer(setting) mAnalyzer!!.setTransactor(HandAnalyzerTransactor(mOverlay!!)) } // Initialize the custom view fun initView(gameView: View): View { return CustomCameraView.initView(context, gameView, mPreview!!, mOverlay!!) } //initialize LensEnginePreview and Graphic Overlay fun initPreviewAndOverlay(context: Context) { mPreview = LensEnginePreview(context) mOverlay = GraphicOverlay(context) } // Create LensEngine. fun createLensEngine() { mLensEngine = LensEngine.Creator(context, mAnalyzer) .setLensType(mLensType) .applyDisplayDimension(640, 480) .applyFps(25.0f) .enableAutomaticFocus(true) .create() } // Start the lens engine with preview start fun startLensEngine() { if (mLensEngine != null) { try { mPreview!!.start(mLensEngine, mOverlay) } catch (e: IOException) { Log.e(tag, "Failed to start lens engine.", e) mLensEngine!!.release() mLensEngine = null } } } fun previewStop() { mPreview!!.stop() } fun destroyLensEngineAndAnalyzer() { if (mLensEngine != null) { mLensEngine!!.release() } if (mAnalyzer != null) { mAnalyzer!!.stop() } } }

(in lines 16–20) I create a hand gesture recognition analyzer using a gesture analyzer setting. Also, I set the transactor with help of the analyzer setTransactor method. (in lines 24–26) I initialize the custom camera view. (In lines 29–32) I initialize the Lens engine preview and graphic overlay. (in line 35–41) I create Lens Engine with the help of Lens Engine creator. (in lines 45–55) I control the lens engine if it is not null then I start the lens engine preview with lens engine and graphic overlay parameter. (in lines 61–68) I destroy the lens engine and ML Gesture Analyzer.

Kit Module Object

@Module @InstallIn(ActivityComponent::class) object KitModule { // Account Kit scope @ActivityScoped @Provides fun accountKitProvider(@ApplicationContext context: Context): AccountKit { return AccountKit(context) } // ML kit scope @ActivityScoped @Provides fun mlKitProvider(@ApplicationContext context: Context): MLKit { return MLKit(context) } }

We create that module object for the Dagger Hilt dependency injection using our MLKit class.

Android Launcher Class

I use this class to check camera permission and trigger the ml kit functions. This class is the main class of the Android for playing the game on the android device.

class AndroidLauncher : AndroidApplication(), KitInterface { private var isPermissionRequested = false private val CAMERA_PERMISSION_CODE = 0 private var TAG: String = "AndroidLauncherXxxx" private var isUserLoggedIn = false @Inject lateinit var accountKit: AccountKit @Inject lateinit var mlKit: MLKit override fun onCreate(savedInstanceState: Bundle?) { super.onCreate(savedInstanceState) accountKit = AccountKit(this) mlKit = MLKit(this) //init ml kit preview and overlay mlKit.initPreviewAndOverlay(this) //ml kit create analyzer mlKit.createHandAnalyzer() // Checking Camera Permissions, create and start Lens Engine if (ActivityCompat.checkSelfPermission(this, Manifest.permission.CAMERA) == PackageManager.PERMISSION_GRANTED) { mlKit.createLensEngine() mlKit.startLensEngine() } else { checkPermission() } } // Init view private fun initView() { val config = AndroidApplicationConfiguration() val gameView = initializeForView(DarkSpaceGame(this), config) setContentView(mlKit.initView(gameView)) } // get permission private fun getAllPermission(): List { return Collections.unmodifiableList(listOf(Manifest.permission.CAMERA)) } private fun checkPermission() { if (Build.VERSION.SDK_INT >= 23 && !isPermissionRequested) { isPermissionRequested = true val permissionsList: ArrayList = ArrayList() for (perm in getAllPermission()) { if (PackageManager.PERMISSION_GRANTED != checkSelfPermission(perm)) { permissionsList.add(perm) } } if (permissionsList.isNotEmpty()) { requestPermissions(permissionsList.toArray(arrayOfNulls(0)), 0) } } } override fun onRequestPermissionsResult(requestCode: Int, permissions: Array, grantResults: IntArray) { if (requestCode == CAMERA_PERMISSION_CODE) { if (grantResults[0] == PackageManager.PERMISSION_GRANTED) { mlKit.createLensEngine() } else if (grantResults[0] == PackageManager.PERMISSION_DENIED) { if (!ActivityCompat.shouldShowRequestPermissionRationale(this, permissions[0]!!)) { Toast.makeText(this, "BAD", Toast.LENGTH_SHORT).show() } else { Toast.makeText(this, "GOOD", Toast.LENGTH_SHORT).show() finish() } } return } super.onRequestPermissionsResult(requestCode, permissions, grantResults) } override fun onActivityResult(requestCode: Int, resultCode: Int, intent: Intent?) { super.onActivityResult(requestCode, resultCode, intent) accountKit.loginWithHuaweiId(requestCode, intent, onSuccess = { this.isUserLoggedIn = true Log.d(TAG, "$this onActivityResult onSuccess") }, onFail = { this.isUserLoggedIn = false Log.d(TAG, "$this onActivityResult onFail $it") }) } override fun onSignInButtonClicked(onSuccess: (() -> Unit)?, onFail: ((e: Exception) -> Unit)?) { startSignInIntent(onSuccess = { Log.d(TAG, "$this onSuccess onSignInButtonClicked") }, onFail = { onFail?.invoke(it) }) } override fun onSignOutButtonClicked() { accountKit.signOut(context) } override fun signInSilently(onSuccess: (() -> Unit)?, onFail: ((e: Exception) -> Unit)?) { accountKit.silentSignIn(this, onSuccess = { Log.d(TAG, "$this onSuccessSilent") onSuccess?.invoke() }, onFail = { Log.d(TAG, "$this onFailSilent") onFail?.invoke(it) } ) } override fun isUserLoggedIn(): Boolean { return isUserLoggedIn } override fun onResume() { super.onResume() if (ActivityCompat.checkSelfPermission(this, Manifest.permission.CAMERA) == PackageManager.PERMISSION_GRANTED) { mlKit.createLensEngine() mlKit.startLensEngine() } else { checkPermission() } } override fun onPause() { super.onPause() mlKit.previewStop() } override fun onDestroy() { super.onDestroy() mlKit.destroyLensEngineAndAnalyzer() } }

(In line 15) I use the injection for the ML Kit class with u/Inject annotation. (In line 23) I use the MLKit class initPreviewAndOverlay method to initialize the LensEnginePreview and GraphicOverlay. (In lines 28–34) Firstly, I check the camera permission after that I create and start the LensEngine with the help of MLKit class. (In lines 37–41) I create the game view using the initializeForView method. After that, I use MLKit class to initialize the custom view with a parameter of the game view. (in lines 133–136) I stop the LensEnginePreview in the onPause method and (in line 140) I release the Lens engine and stop the analyzer in the onDestroy method.

Conclusion

Now we learned how to implement and use the ML Kit Hand Gesture Services with the LibGDX application. Also, we learned how to create a custom camera view with the LibGDX game. If you want to learn more about LibGDX and its services, you can check this link. We will continue the LibGDX demo application in the next part of this article by creating our Libgdx Game screen and understanding LibGDX Ashley Entity System Library. Also, we will create our player object with entity factory class, we will learn and use components, systems, engines in the LibGDX game demo application and etc.

https://i.redd.it/sofvnltwo4m81.gif
Take Care until next time …

References

https://libgdx.com/dev/
https://github.com/libgdx/ashley
https://github.com/HMS-MLKit/HUAWEI-HMS-MLKit-Sample/tree/masteMLKit-Sample
https://developer.huawei.com/consumeen/doc/development/hiai-Guides/service-introduction-0000001050040017

submitted by HDGTurkey to u/HDGTurkey [link] [comments]

2021.02.12 17:40 ManSore Need a recommendation. Moving from my MM1000

Hey MPReviewers,
I've been using a model d- with a corsair mm1000.
After finding the right mouse for me, I'm learning that this is not the mouse pad for me. It's too fast and I seem to lack control.
I could lower sens to combat my lack of aim in both tracking and flicking but then I have to move my arms too much. As of right now, I play with a sensitivity of a 3/4 circle turn from one side to the other of the mousepad in all my FPShooters. It works well until close combat shooting.
What's a good alternative to pair with the model d-? I've been looking at the mp510.
It seems like the mp510 adds control while not adding too much friction.
Using my experience in finding the right mouse, I know I probably have to try at least 2 or 3 mousepads to find what's right for me. I know for sure I don't need a mousepad with even less friction :)

submitted by ManSore to MousepadReview [link] [comments]

2020.06.06 19:42 DenjeRL Reposting here as MPreview is quite small sub so i know not everyone have tested everything. If you have any input , i'd be highly appreciated. Thank you.

submitted by DenjeRL to MouseReview [link] [comments]

2015.09.10 04:08 North_Korean_Spy_ Shillplus user attempts to port M'Preview 1 to Onepleb, DuARTe smites his filthy hard drive.

submitted by North_Korean_Spy_ to androidcirclejerk [link] [comments]