[F/OS] - Dynamic Components Extension (for every component) 2.3.0

Extensions
,
#393

I don’t think this works because the Ball component doesn’t have it’s own X property, it inherits it from the Sprite component.

2 Likes
#394

This is the only configuration that doesn’t generate an error.
The ball is created, it is placed in random x and y but it remain static even though the speed is not 0.

image
image906×689 41.4 KB

#395

If I used the ImageSprite speed instead of Ball speed setter, it returns the expected error.

image
image966×677 48.3 KB

#396

I don’t think so, I use getMethods() method to get the methods for the component.

According to Java docs:

Returns an array containing Method objects reflecting all the public methods of the class or interface represented by this Class object, including those declared by the class or interface and those inherited from superclasses and superinterfaces.

Can you try if this happens for the static component too?

#397

Yes, doing this, the ball created in the designer starts moving.
I tried with dynamic ImageSprite too and they don’t move when speed is > 0 but Heading works fine.

image
image788×277 18.3 KB

The blocks SetProperty from your extension do not seem to work with elements inside the canvas. Thanks for checking this.

#398

So, to make it short:

  1. Balls and ImageSprites created with the extension do not move even when speed is > 0.

  2. The blocks SetProperty return an error when trying to set Ball or ImageSprite properties.

#399

That’s so weird. I will check what is going wrong. Thanks :slightly_smiling_face:

I already changed the behavior of SetProperty for v1.2, can you try with the new version which I will sent it from DM?

1 Like
#400

Version 1.2

Looks like a month (or maybe more) has been passed from the previous release. So sorry for waiting long for a new release because I had other jobs to do first :sweat_smile:, so here is the new release!

  • New Block UsedIDs
    Returns all used IDs that you used in Create block. As Boban suggested! :raised_hands:

    component_method(1)

  • New Block ChangeId
    Changes the used ID to a new one. After changing the ID, old ID will be invalid forever. As yoni_mic suggested! :raised_hands:

    component_method(2)

  • Removed Block RemoveAll
    Sadly, this block was causing a weird error that I can’t solve, and it would be better to use this method instead of having a buggy block:

    You need to use a for each loop together with the UsedIDs block to remove all components.

  • Bug Fix SetProperty block is much stable anymore!
    Because it supports numbers too! And I made some tweaks to it, so it doesn’t cause any casting errors anymore (until someone reports it :crazy_face:).
    And thanks to Italo for helps me for testing it! :raised_hands:

  • Enhancement Implemented ProGuard to decrease extension size
    I know it won’t have any effect on it as extension is open source, I just built with it to decrease the extension size. :sweat_smile:

  • Enhancement Create block now supports creating from existing component!
    Now you don’t need to learn the internal name of the component anymore! Just add a current static component block to the componentName parameter and extension will create another instance of it! Don’t worry you can still use the old method!

    resim
    resim730×208 14.6 KB

:warning: Migration Warning

As these things have been changed, you may need to change the blocks that you used.

  • SetProperty block’s parameter names have been changed.
  • As RemoveAll block has been removed, you won’t able to use it again.

I updated the first post. You can go to the top of the page for download links.

14 Likes
#401

After The Update I can’t set the get component block in any component block to change properties.

image
image704×165 10.6 KB

2 Likes
#402

Yes, that block now doesn’t accept the extension one.

And the SetProperty blocks are still returning an error when trying to use them:

image
image1287×322 30.1 KB

#403

You can put the component in a variable and then use the variable as a workaround for now.

Anyways, the speed is still accepted this way but the created ball doesn’t move. Only the ones created with the designer.

image
image808×302 20.5 KB

2 Likes
#404

NYC update but problem in setting the property by any component

#405

Sorry, that was because I changed the parameter types to Component instead of Object. I will release a fix today.

#406

You can now use Speed in SetProperty block. But X and Y needs to be set from Any Component blocks. I will check what is going wrong.

Edit: It works like this.

image
image1106×327 25.9 KB

Edit 2: It also works like this.

image
image1452×620 69.8 KB

2 Likes
#407

Hi in this new version can I delete the image sprites or not yet?

#408

Did you used Remove block?

#409

Version 1.2.1

I released a small fix for GetComponent's return type and updated the first post, thanks and sorry about it!

You can go to the top of the page for download links.

9 Likes
#410

longKlick
longKlick1038×512 113 KB
.
Long click doesn’t work. Does it make sense to look for a solution, or does it really not work?
Sorry for the automatic translation.

#411

@paska_ig
Try to tick Clickable in Designer screen.

click1
click1796×430 53.4 KB

#414

Clickability is assigned when the component is created.

clicable
clicable1566×333 138 KB

Only a long click doesn’t work. Short works well