Hi,

im trying to implement the library, but i cant put target as a view to method setPoint(textview1);

the round is not fit to the view..

any advice would help much.

thanks

Thanks for awesome library, but I am little disappointed that there is no round rectangle option. anyone who forked and made changes for this feature?

 val firstRoot = LinearLayout(this)
        val first = layoutInflater.inflate(R.layout.spotlight_tour, firstRoot)
        val firstTarget = com.takusemba.spotlight.Target.Builder()
            .setAnchor(btnLoginWithEmail)
            .setEffect(RippleEffect(100f, 200f, argb(30, 124, 255, 90)))
            .setShape(RoundedRectangle(200f,400f,100f))
            .setOverlay(first)
            .build()
        val spotlight = Spotlight.Builder(this)
            .setTargets(firstTarget)
            .setBackgroundColor(R.color.spotlight_bg_color)
            .setDuration(1000L)
            .setAnimation(DecelerateInterpolator(2f))
            .build()

        btnLoginWithEmail.doOnPreDraw {
            spotlight.start()
        }
// Even tried btnLoginWithEmail.post({}) but did not help

By the way I am using Material design UI elements the button class is com.google.android.material.button.MaterialButton. Though I checked with regular Button class but it didn't work. In the corner again...

Hello,

is there a method or some workaround to show the previous target? For moving to the next one we have spotlight.closeCurrentTarget(), anything similar for going back would be useful.

In this way for example in a tutorial you can have all kind of buttons, skip, next but also back.

i had a issues. please help me.

"Manifest merger failed : Attribute application@appComponentFactory value=(android.support.v4.app.CoreComponentFactory) from [com.android.support:support-compat:28.0.0] AndroidManifest.xml:22:18-91 is also present at [androidx.core:core:1.0.1] AndroidManifest.xml:22:18-86 value=(androidx.core.app.CoreComponentFactory). Suggestion: add 'tools:replace="android:appComponentFactory"' to element at AndroidManifest.xml:6:5-24:19 to override."

The spotlight position is different between two phone. A Pixel 2 XL emulator looks like this:

https://i.imgur.com/G7Lcrmq.png

but on a Pixel 3 XL phone (no emulator) it's here:

https://i.imgur.com/7qddSSE.png

I'm thinking the notch might be effecting the positioning.

I'm also using 1.5.0 because 1.8.0 is throwing some manifest merge compiling error.

I created a customtarget.

CustomTarget customtarget = new CustomTarget.Builder(activity)
                .setPoint(viewToFocus)
                .setRadius(50f)
                .setView(R.layout.fab_filter_coachmark)
                .build();

Start spotlight:

Spotlight.with(activity)
                    .setOverlayColor(ContextCompat.getColor(activity, R.color.transparent))
                    .setTargets(customtarget)
                    .setClosedOnTouchedOutside(true)
                    .start();

layout : fab_filter_coachmark

<?xml version="1.0" encoding="utf-8"?>
<LinearLayout xmlns:android="http://schemas.android.com/apk/res/android"
    android:orientation="vertical" android:layout_width="match_parent"
    android:background="@color/coachMarkBg"
    android:layout_height="match_parent">
    <TextView
        android:id="@+id/textViewDescription"
        android:layout_width="match_parent"
        android:text="Description"
        android:textColor="@color/white"
        android:layout_height="wrap_content" />
    <TextView
        android:layout_width="match_parent"
        android:text="got it"
        android:textColor="@color/blue_priceinsight"
        android:layout_height="wrap_content" />
</LinearLayout>

There are two issues

1. Custom view is not inflated near to the target, It inflated on the top left of screen.
2. Spotlight is not started on target.

Hello, I got trouble when put data in tag view before put in setPoint method and get data in OnTargetStateChangedListener in method onStarted and onEnded, and always got null value.

I think this is a bug.

Sorry, my english is bad.

Thank you

Hi, the library was cool and working fine in activities and fragments. But whenever i want to display the overlay on top of dialog it was displaying below the dialog. Please suggest any possible solution..

Its an awesome library but I have a query how do I show the coachmark over the dialog. Its always coming behind the dialog. I am using the DialogFragment with animation in android.

Can you make spotlightview or the target clickable? I know we can make a custom view and set clickable there but it would be great to make the target itself clickable to make the user tap on the target to move forward

Since most of the new UI development is moving toward Jetpack Compose, which is way better than XML, it would be great to have such a library for Compose.

Hello,

Is there a way to set the background of the spotlight to a blur? Meaning that you cannot see the layout underneath the spotlight, due to the blur? I currently tried to but a view that matched parent on width and height but then it blocks the target being shown. Does anyone know a work around for this?

Thanks!

Consider a situation when there are some configuration changes. In the current spotlight, I don't think there is any way we can persist the targeted index. In my experience, if the screen is rotated, then the spotlight restart from the beginning.

Also, consider if the user is using a different UI for different orientations, then in that case we will have to use a different layout for each target. But the thing is, the spotlight takes predefined layout targets. How can we conditionally or with some other method can change the target layout during runtime?

Problem

I've seen issue https://github.com/TakuSemba/Spotlight/issues/123 (from @aryandii) and decided to help you make Spotlight more functional ✨

Solution

So I added a new flag to make it possible to finish spotlight on touch outside of current target. Let's see how it looks like:

• Circle shape showcase (gif)
• Round rectangle shape showcase (gif)

There is a listener to catch on touch outside of current target event. Finishing on touch outside is the only one usage of listener. If you want to add new Shape just create a child class and implement contains function. It can be quite complex if your shape is not primitive. So it can be not perfectly precise (and there is nothing horrible, IMHO). Round rectangle is an example of complex shape:

• Round rectangle contains calculation imprecision (gif)

@TakuSemba , thanks a lot for your work. I hope this feature will improve your project and engage new developers 🤝