Closed richbowen closed 8 years ago
If you navigate file browser to some other path then close and open Enki, does it open in System32 again?
No changing directory, closing and then reopening Enki doesn't reopen System32
, it stays on the directory.
It seems like the lag happens when FileBrowser loads too many files. It is quite difficult to fix and it won't happen often, because directories with sources doesn't contain so many files.
I think setting the default directory when opening files from outside Enki to %HOMEPATH%
instead of %SYSTEMROOT%\System32
(C:\Windows\System32
) because it seems to loads less stuff. It loads faster than C:\Windows\System32
and it's easier to navigate from %HOMEPATH% to desired directory than it is from C:\Windows\System32
.
Hmmm. Are you running from source or from the WIndows binary? What version?
Was running from the Windows binary. Enki version 15.11.1.
I think this is the relevant code that needs modification. I think the following modifications would do the trick:
if not sys.platform.startswith('win'):
self._dirsModel.setRootPath(os.path.expanduser("~/")) # unix based systems
else:
self._dirsModel.setRootPath(os.environ['HOMEDRIVE'] + os.environ['HOMEPATH']) # windows
or something more robust.
I haven't tested it so I don't know if it works or not.
The default folder when opening files from outside Enki (ie. opening a file from Windows Explorer) seems to be
C:\Windows\System32
.The implication of this is that Enki is unresponsive for a while when opening a file from outside of explorer or launching Enki with it in theSystem32
directory.Illustration: Fig 1.![ohjhgoknkk](https://cloud.githubusercontent.com/assets/5672238/13023106/91df7430-d1b3-11e5-8cd8-6112d5bdaa97.gif)