In the igupload control, you are able to display a summary area. It contains overall bulk upload status and a done button.
By question is about the Done button:
Thanks
Actually, upon further inspection, the check mark associated to each file is not turning green. Is that the problem? What prevents that from turning green?
I do have a custom handler on the server side to ensure the files being uploaded to write over each other.
Well, after more investigation, this appears to be your normal control behavior.
The problem is that this UI confuses our end users. They feel the done button should be enabled so that it can be pressed when done uploading.
Is there an event called to let me know when all files have been uploaded?
Hi,
Thank you for contacting Infragistics Developers Support! You can use the fileUploaded event. There you can call the getFileInfoData method. It will return an object with information about the uploading process. The properties you need for this scenario are pendingQueueIDs and uploadingIDs. They are arrays that hold the id’s of the files that are in process of uploading or are queued for upload. To ensure that all the files are uploaded the length of these two should be 0.
I hope this helps!
Kind Regards,
Petko Zhekov
Software Developer
Infragistics, Inc.
I'm experience this same issue, the "Done" button (and also the "Clear Uploaded") is disabled.I've confirmed that both pendingQueuedIDs and uploadingIDs are zero, but the button is still disabled.Could you provide a code snippet of how you handle enabling the done button in the fileUploaded event?
I agree with this "expectation" that is Stephen is experiencing. When the "DONE" button is visible and the label states "DONE" then as a user I expect that I am able to click on it and restore the control back to the original state where was just a button that read "Upload". This will also cause the control to return back to its original state and possibly shrink down in size.
To implement this I suspect you'll need to listen to the fileUploaded event and remove the disable property on the button then listen for a one-time event. Only thing I can think of is to destroy the control and reinitialize it.