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
We expose the FileEngine object which used to basically be a cache of the renderer's native event, allowing access to dragged/dropped files. Now that events have the native event type in them, this is no longer necessary! We should simply move these methods on the events themselves, simplifying the API and simplifying code that uses them.
For example, the snippet from our file_upload example
for file in evt.files(){ifletOk(contents) = file.read_to_string().await{
files_uploaded.write().push(contents);}}
This might require a type like a VirtualFile or something like that that implements the Read trait - or some reworking of methods, but overall the FileEngine object is awkward now.
The text was updated successfully, but these errors were encountered:
Specific Demand
We expose the
FileEngine
object which used to basically be a cache of the renderer's native event, allowing access to dragged/dropped files. Now that events have the native event type in them, this is no longer necessary! We should simply move these methods on the events themselves, simplifying the API and simplifying code that uses them.For example, the snippet from our file_upload example
could just be simplified to
This might require a type like a
VirtualFile
or something like that that implements theRead
trait - or some reworking of methods, but overall the FileEngine object is awkward now.The text was updated successfully, but these errors were encountered: