Looks pretty well intact, loads without complaint - I think it must be pretty close to the original state before the issue began. In particular, when I tried to rescue the file (copy-paste incrementally to a new file) I had to remake the zero4D and initGPS procedures - however, after save, logout, login, load - those procedures had disappeared.
That's a good spot. How on earth that could happen is a bit of a mystery - perhaps a 'Click' extension that was subsequently removed. I think a lot of the more recent extensions could be more robust.
Thank you very much Boban. You guys have been a solid help.
Chris, 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.
Neither the built-in list view nor this extension reference the existence of a Click event. I wonder if some interplay between either the backpack or copy/paste functionality, in combination with a Button or other component with a Click handler had a name collision and the failure mode is the result we see here.
I'm currently at a loss for how to come up with a good sequence of events that would result in a project in this state.
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.
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.
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
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.
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:
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.