Closed mediaexplorer74 closed 3 years ago
Hi,
Instead of storing the node Name
and Id
in your Contact
variable, I think that you can store the INode
instance directly. This way, you will not have to recreate a new URI and you can call Download(INode)
or DownloadFile(INode)
with the previously retrieved INode
instance.
A second point is that's better to instantiate a single MegaApiClient
instance for your application (instead of creating a new instance on each Click_SelectChanged
call)
Good morning! :)
Thank You, I will research Download(INode) DownloadFile(INode) methods.
I noticed, INode
objects have interesting structure:
FullKey
SharedId,
etc...
I hope, Mega.nz accepts simple folder/file downloading without decription at my app's side... and FullKey field will not needed/used... ?
A single MegaApiClient instance is good idea (ohhh... yes, my early preview/app prototype needs many improvements))
Yes the INode
objects contain important data like the decryption key that's why my proposal was that you store the INode
instances instead of only the Id
and Name
Thank You very much. I fix the algorythm . You get me great comments + I find your code samples, and now my new pre-alpha of MegaBox can download files from Mega.nz storage =) Its a kind of magic ! I continue researching other closed issues (to find some useful data for my project)) Have a nice day!
You are welcome!
Hi, Grégoire!
I'm trying to use Your great Mega.Nz lib in my own UWP app (named "Megabox", utility to store some appxbundle files for Win10Mobile in future..).
The problem : I need to do multiple files downloads from my shared folder named W10MRepo: https://mega.nz/folder/YdlWiaxD#7qcjO0mtYukRBCuDzoIwGA
Code fragment :
Scenario: in ListView I select some item, and file must be downloaded for Mega.nz storage and be autolaunched.
My unsuccessful type of code ("item changed" handler for ListView):
Please help, if You can...
MegaApiClient Version: special reconstructed for UWP compatibility