how to use custom components

Mon Jul 08, 2013 5:20 pm

This may just need some clarification of how custom components are meant to be used...

When I made a custom component from an on-page grid (call this the source component) the source component itself became a custom component which I had to break up to do further work on. This lost all my mappings and javascript in those mappings. (not in the custom component itself, but in the source component)

I've tried this twice to make sure, and it happens every time - the source component becomes an instance of the custom component, and to edit it you need to break it up and lose mappings and code.

Is this working as designed? It would seem to me that the source component should remain unchanged, the custom component itself being a snapshot of the source component.

To put it another way, I think the source of a custom component should not itself become an instance of that custom component.

The way it works now means custom components aren't useful as they effectively freeze their source components.

Have I missed something?

John

Mon Jul 08, 2013 7:19 pm

Hello! This is how custom components work. After you save component as custom it becomes an instance component for just created custom component. So you can specify events for custom component, but not mapping. First you have to create component you want to be custom (without mapping), then save it as custom.

Tue Jul 09, 2013 8:14 am

Thanks Marina

This comment is only about how to treat the source component.

I'm pretty new to Appery, so I may be less disciplined than most, but I think if the source component didn't automatically become an instance of the custom component it would be more useful - you'd effectively have copy and paste for components, which I would find really useful, plus the components you copy get snapshotted into the custom component panel for future use.

That would suit me, but I'm new here
John

Tue Jul 09, 2013 9:06 am

Hi John,

Thanks for the idea, I will pass it on to the developers, but can not guarantee its implementation.