Callback-based system. about libusbhsfs HOT 5 OPEN

Sure thing. This will be an ongoing WIP I intend to further explore over the course of the next week.

Changes will surely be pushed to dev, so feel free to take a peek at that branch and/or let me know if you want write access.

from libusbhsfs.

Thanks for the quick patch, I'll try to move my app to this system soon and give you feedback.
At a glance, I think the UsbHsFsPopulateCb could take an additional void* parameter, passed by the user in usbHsFsSetPopulateCallback. This way the user can conveniently access any kind of structure (eg. a drive manager object) from the callback.

from libusbhsfs.

Additionally this could be used to enable advanced communication with the user.
For instance, there could be a callback used prior to creating the fs context and mounting to devoptab, where the user could decide on a different mountpoint, if he wants to mount as read-only, maybe even have advanced settings based on the filesystem, ...

from libusbhsfs.

Just pushed the first changes related to this issue to dev, check 0299eae. A single callback is used at this moment, others may follow down the road.

I tested it a bit with all my flash drives and it seems to work fine.

from libusbhsfs.

@averne Had some time to spare, so I went ahead and implemented support for a user data pointer in 2c401e8. I'll be waiting for your feedback, there's some other stuff I want to tackle in the meantime.

from libusbhsfs.