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
Is your feature request related to a problem? Please describe.
When making an app, where you want to allow saving to a custom location (e.g. because you want your users to be able to work on multiple projects at once), you basically have to create a custom eframe::Storage implementation, which for me boils down to just copying the file that eframe::native::FileStorage resides in, removing the profiler macros and making the eframe::native::FileStorage::from_ron_filepath public.
Describe the solution you'd like
just make eframe::native::FileStorage::from_ron_filepath public
Describe alternatives you've considered
just copy the existing implementation
Additional context
The text was updated successfully, but these errors were encountered:
Not really no. I was thinking of being able to load/save from multiple different locations during the lifetime of an app (without re-creating the window). Something like being able to choose a project file to load/save to.
Your pr seems like it fixes the directory location on application start.
Is your feature request related to a problem? Please describe.
When making an app, where you want to allow saving to a custom location (e.g. because you want your users to be able to work on multiple projects at once), you basically have to create a custom
eframe::Storage
implementation, which for me boils down to just copying the file thateframe::native::FileStorage
resides in, removing the profiler macros and making theeframe::native::FileStorage::from_ron_filepath
public.Describe the solution you'd like
just make
eframe::native::FileStorage::from_ron_filepath
publicDescribe alternatives you've considered
just copy the existing implementation
Additional context
The text was updated successfully, but these errors were encountered: