Bundling additional resources creates separate directory for eachSee original GitHub issue
When I bundle up the additional resource. It autocompletes the destination part with the file name itself, and then what actually happens is, it creates a separate folder for each asset.
That’s counter-intuitive. While developing the app it is a fairly common practice to bundle them up in one folder. But here, we get a different folder for each, then I have to manually edit all the bundled resources’ destination to reflect a single directory.
My suggestion is instead of making a separate destination, just make a
asset folder and place everything inside it.
Although far-fetched, but it’ll be of great help, if we could upload all assets at once, instead of individually doing them. Nevertheless, that’s an enhancement.
- Created 6 years ago
- Comments:8 (5 by maintainers)
Top GitHub Comments
Thank you very much for your help on this, I really appreciate it!
That’s it. This commit fixes it. 👍
I just realized one more thing, it’s chrome. It cache’s the code somehow. I had to inspect and disable cache to make this update work, the first time. Although, it won’t bug the new users from here on.
But I was wondering if there was a way in code to ensure
no-cache, just in case if I ever need to disable cache somewhere. Any thoughts?
Just put a small line in the expansion of
Additional Files, when the user clicks to expand this, A small line is there.
Be careful when using additional files, update your code to work with pyinstaller, read this