I am currently using the perspective equipment schedule component. There are several other forum posts regarding the click events to update/modify/delete schedule events that already exist in the component. These can be accessed via the component events as follows:
eventId = event.eventId
itemId = event.itemId
The issue that I am running into is that these properties are only accessible if you are clicking on an actual scheduled event. What I am trying to do is get a popup to display based on the item that is clicked on, without having to click on a scheduled event for the item (in this case there are no events scheduled so the item has no events). Is this currently possible to do? The documentation leads me to believe no, but I am not 100% sure.
Oh, I see, so you want this information when clicking the item - not a scheduledEvent or downtimeEvent for that item. Let me think about it for a bit...
Yes, in my case, the item id for each item is the equipment path. I want it so that when a user clicks an item, not an event, it calls a popup and passes in the equipment path associated with the item clicked.
The way that I read it, an Item is a piece of equipment that can be scheduled (recorded?) as a Scheduled Event, recorded as a Downtime Event, or recorded as a Break Event. An Event can respond to a Click Event (or mouse over, or touch start, or...).
If the row is selected or the row header is clicked then reasonable expectation is that the Item would be able to be clicked or touched and that an Event (UI event) could be scripted to do something (e.g., add a schedule event, start a downtime event, ...)
Unfortunately, no - I don't think you'll be able to do this with the Component's available functions as they are today. You could manage something along these lines with the Context Menu available to the Component, but it would not be trivial.
Sure, we can do (most) anything, and provide hooks into thousands of events per component, but each individual hook takes a lot of development time, and so we try to anticipate the most likely interactions. We could definitely add a new onItemClick Event as a feature request.
OnDoubleClick has promise, but would require math to estimate the bounds of each row ... not particularly reliable perhaps in HTML5 and a flex container.
