Wrong logic is used in case of events about ember-cli-dropzonejs HOT 6 CLOSED

Yes, it seems that you are actually overriding the hooks instead of adding event listeners. Maybe adding properties like onaddedfile etc for adding event listeners to dropzone events would work. I think this problem is compounded by the fact that access to the Dropzone instance is impossible by actions unless you extend the component.

from ember-cli-dropzonejs.

I am having trouble understanding the issue. How would I go to recreate this problem?

Also, @kkamkou try assigning a function property instead of an action to the complete attribute.

from ember-cli-dropzonejs.

try assigning a function property instead of an action

It doesn't matter. In the variant you propose me, I lose the context of the callback. And it won't fix the problem.

Yes, it seems that you are actually overriding the hooks instead of adding event listeners.

true

I am having trouble understanding the issue.

I see it from the code. All you need to do (in case you want to fix it) is to register events like events and not like an attribute. forEach() if (this.complete is function) {dropzone.on('complete', this.complete)}

from ember-cli-dropzonejs.

@kkamkou oohh yes I see. Thanks for pointing this out. Will definitely fix this.

from ember-cli-dropzonejs.

Fixed the event handling logic 7eb7b33.

Declare the event function in controller for example:

addedFileEvent: Ember.computed(function() {
  return function() {
    // do something...
  };
}),

Declare component

{{drop-zone url=http://example.com addfile=addedFileEvent}}

You can update to version 0.7.0 to have this fix

from ember-cli-dropzonejs.

It works, thank you.

from ember-cli-dropzonejs.