[FREE] Component tools extension

Extensions
#177

For sliding ACTION_MOVE is useful.For fling I think it can be done using the pointer count variable, you can find all of the actions here:

1 Like
#178

On Component put x put y did not use duration of moving ā€¦i need that

#179

I didnā€™t understand you :sweat: Do you mean to have a parameter to set the duration of the component movement when using SetX and SetY blocks?

2 Likes
#180

#off-topic
i just send you a PM. :relaxed:

#181

with This extension Can make Slider

#182

My extension Repositioning Tools would be more helpful, but it would need an update to limit the dragging area :grin: , another good solution :slightly_smiling_face:

2 Likes
#183

Yes like thatā€¦ because move x y in component tool its relative and put x put y it absolute i iwant absolute but have property duration movement

#184

Since you want a new block like this:

So itā€™s already available in the next update :grinning:

2 Likes
#185

Thank you :pray::pray:

1 Like
#186

Is it possible to support absolute x,y position? X and Y coords are dependent on position in arrangement instead of whole screen.

1 Like
#187

For which block exactly you would like the absolute X,Y support ( i.e: the getX, getY block, the touched event X and Y parameters) :blush:

1 Like
#188

Get X and Y block. It would help me to get work with custom floating movable buttons and place them correctly according to my template :slight_smile:

Itā€™s hard to calculate it with CardViews, cause the CardView elevation is unpredictible and i lose some pixels in ā€œmanualā€ calculations.

Thanks for the fast answer!

#189

Thanks for your suggestion ! I will be adding a new GetAbsoluteX and GetAbsoluteY for the next update.

1 Like
#190

:heart_eyes: :heart_eyes: I have some question? Can I pm you? I would like to know if it is possible to create a movable component without placing it in specific place or arrangement on the screen. FAB is a great example. But it canā€™t be make movable. FAB doesnā€™t need any location to be created.
The problem is: to make a movable component it has to be placed in any arrangement on the screen. Dragging the component doesnā€™t delete the area to which the component belongs. Empty useless space is created. It takes a lot of combinations to make components like these outside the visible screen area and to make the screen fixed with the possibility to auto size.

Your extension work great with dynamic components, cause it allow to manipulate overlaying easily with the help of ā€œmove componentā€ in dynamic comp. extension. Could you also add overlaying settings?

1 Like
#191

When next update lounce?

1 Like
#192

Can you add onTouchdown and onTouchup , onLongclick ,set fullclickable ,onLongclick,set Longclick

#193

The touched event do that, the action would be ACTION_DOWN or ACTION_MOVE when touching down and ACTION_UP on touch up.

Thanks for your suggestion, I added them in the next update :smile:

1 Like
#194

Thanks :+1: :+1: :+1: :+1:

1 Like
#195

Amazing extension. Very powerful. Together with your second extension, it offers great opportunities.

I had a little fun with the extension. It is a pity that you cannot unregister a registered component.

1 Like
#196

The CustomPath method isnā€™t working as I thought. It just lets the component jump to the new position instead of moving to it. No matter what value you set as duration.
From your aia:

Unbenannt
Unbenannt813Ɨ743 79.9 KB

So this method seems useless as you can also archieve this position-jump via your SetX,Y methods.
Is this a bug? I am using v3.
on Android 7.0.

1 Like