The blocks area did not load properly

[Taifun]

@ChrisWard

Edit: Even if the extension is deleted, the Project is now corrupted.

The author if the extension @iamwsumit might want to check...

Probably it is not a good idea to use the same name for an extension to avoid conflicts like this?

Taifun

[ChrisWard]

That's a good point, though the AI2 LV was "ListView1" and the Extension arrives as "ListView2". You should be able to have a standard LV and a Custom LV on the same Screen IMO.

[Taifun]

@ChrisWard

You should be able to have a standard LV and a Custom LV on the same Screen IMO

Yes, but most probably different component/extension names are necessary...

My guess is, if @iamwsumit renames the extension to something else, for example Sumit1334Listview, then the issue is gone... magically...

Taifun

[ChrisWard]

@Elson_Am

I tried to use the following extension for listview and then I changed it back to the original ListView component in App Inventor and that's when this error may have occurred.

I was able to reproduce that scenario, see post #20.

It may be only a small issue from the extension perspective, the developer may not have expected a Standard ListView to be on the same Screen. It seems to be that deleting the extension is not 100% successful - not sure about that though.

[ChrisWard]

@Taifun

My guess is, if @Sumit1334 renames the extension to something else, for example Sumit1334Listview, then the issue is gone... magically...

I think you are right!

[ChrisWard]

@Elson_Am

If there is any update to the original components in AppInventor, do I have to do it manually from my end?

Not sure what you mean Elson. The AI2 ListView is a built-in component. Example:
ListViewAdd.aia (4.6 KB)

[Elson_Am]

I understand that AI2 ListView is built-in.

The blocks area did not load properly

..... that may have been for the 'original' ListView component, it has recently had a huge update.

This statement of yours raised the confusion about the downloadable extension and update in the original component. I thought I will have to manually update the built-in components when you said that "that may have been the original ListView component", when I never have to download a built-in component.

But, thanks for the example.

Extension having the same name as a built-in component could be the prime cause of this glitch.@iamwsumit

[ChrisWard]

@Elson_Am

This statement of yours raised the confusion

Often, extensions enhance existing components rather than delivering a complete replacement - hence my comment. At that time, I had not seen the extension (indeed, I had never heard of it until now, probably because it is not in the AI2 list of extensions but on Kodular's site).

I hope the error can be fixed easily - the basis of the extension is similar to the AI2 built-in component, but with a lot of more advanced features.

[iamwsumit]

@Taifun

Probably it is not a good idea to use the same name for an extension to avoid conflicts like this

Yes, surely it is not. I already updated it a very long time ago in V2.

• Extension has renamed to CustomListView from ListView as it was causing error while dragging the list view component. It may break your whole blocks. So kindly make a backup of the older project please. It was necesary to change the extension name.

Unfortunately, this extension is not fully compatible with AI2.
Read here:

https://community.kodular.io/t/free-custom-list-view-an-extension-for-making-image-and-text-list-view-with-a-lot-of-customization/142175/49?u=sumit1334

You can give V3 a try:

https://community.kodular.io/t/free-custom-list-view-an-extension-for-making-image-and-text-list-view-with-a-lot-of-customization/142175/45?u=sumit1334

[ewpatton]

@ChrisWard

You should be able to have a standard LV and a Custom LV on the same Screen IMO.

Sure, you just need to call the class name something different. An example is the WebViewer component and the CustomWebViewer extension. The original extension development instructions encouraged this by having people build the extension alongside the App Inventor components so there was never any question that the name had to be different (you couldn't have two ListView.java files in the same folder...).

Internally, App Inventor keys off of the class name so creating extensions that collide with built-in App Inventor components with different signatures is a recipe for disaster.