I never really played with them before, now that I am trying to use them it’s not exactly clear how they work. I was expecting to be able to define internal logic to the component, but when editing the component itself, I cannot add events (at least not in a kosher way). I have also noticed that if I add the same component twice to a page, then when I add an event to that page, the triggers lists all internal controls with random names individually…
For example, let’s say I build a component with a combo box and a text box in it. I want to raise an event any time the combo box value changes to put some text in the text box next to it. The way I was expecting this to work is to add an event WITHIN the component, and that that event would fire for each individual copy of the component within the page. But it doesn’t seem to work that way, and that leaves me confused…
I think you will need to detail what you are trying to do specifically. Flesh out the what the combo box contains and what is the value you want to change. Is it like a combo of part numbers and you want the description of the part to appear in the text box?
Also, detail out what you have tried.
Kinetic is still new to all of us and I have found that the more detailed you are in what you want and what you have tried makes the people who are further along in Kinetic better able to provide answers. Right now, I know I don’t have what I need to be able to offer up a response.
I’m curious about this non-Kosher way of creating events - what is it that you have done?
Events in Kinetic are at the screen/application level, and you define the trigger that will fire off the event (no more registering event listeners to controls or control types, but you can set the trigger to watch an action on a specific control - similar result, just a different way to do it)
The menu on the left isn’t available for components, but if you choose to add an event through one of the Behavior properties, you can then change the trigger of the event before saving it.
But it doesn’t seem to work at all… I question if those components are even useful… I thought they were to make reusable user controls, but that doesn’t seem to be the case… There is not internal logic to them, you need to define the event logic in the parent page as far as I can see, so it seems pretty useless… Plus, any component you add to a page is added as a complete card, instead of just a container that you can embed in an existing card…