You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm working on a CompisiteView which displays a table, and the rows should be multi-selectable. The rows (ItemViews) have some triggers, which are catched, by the CompositeViews.itemEvents (#875 made this a lot smaller, thanks for this one!).
But here's my problem. I have no DOM-event in the handler anymore. Consider the example below:
Completely awesome what you can do in just a few lines of code.
Nevertheless, I have no DOM-event in clickRowSelect, so i can not check if the user uses ctrl, shift or alt to click on the rows, which i have to, to create a good selection ux.
// build the args for the eventvarargs={view: this,model: this.model,collection: this.collection,e: e};
Of course, sometimes, there is no DOM-event, but then, also collectionis undefined most of the times.
I can't see a reason, why the event is omitted, but maybe there is one?
The text was updated successfully, but these errors were encountered:
I'm working on a
CompisiteView
which displays a table, and the rows should be multi-selectable. The rows (ItemViews
) have some triggers, which are catched, by theCompositeViews.itemEvents
(#875 made this a lot smaller, thanks for this one!).But here's my problem. I have no DOM-event in the handler anymore. Consider the example below:
Completely awesome what you can do in just a few lines of code.
Nevertheless, I have no DOM-event in
clickRowSelect
, so i can not check if the user uses ctrl, shift or alt to click on the rows, which i have to, to create a good selection ux.By just adding the DOM-event to
args
i could do just that.https://github.com/marionettejs/backbone.marionette/blob/master/src/marionette.view.js#L103
Of course, sometimes, there is no DOM-event, but then, also
collection
is undefined most of the times.I can't see a reason, why the event is omitted, but maybe there is one?
The text was updated successfully, but these errors were encountered: