Similarly each frame for a level of the directory tree engages in such sliding and auto resizing every time the user navigated deeper or more shallowly in the tree structure or when the window resizes. If on the other hand, the window is resized to be narrower, the history pane is minimized automatically.
So, for example, if the window is wide enough that it doesn't otherwise need the space the entire left side gets a history pane of all the paths that you have navigated to.
Simultaneously, the window is dynamically resizing different aspects of the interface to try and make the best use of the window size. This interface was clearly designed around making sure the user would not need to move the mouse much in order to engage in folder navigation as the parts of the display that you are likely to need next slide away from the center of the screen so that the area you are working with stays centered. So the whole idea of OneCommander is built directly into it's unique folder navigation interface. There are a number of unique or interesting features: a drop list which functions as a visually interactive clipboard for moving and copying files from divergent sources integrated with a "task master" so that batch file operations can be managed, color-coded relative file-dates, "To-Do" lists based around every folder. (Thumbnail loading does not slow down the loading of the whole file list which is a point where many file-managers fail). The core functionality is there, and stable.Ī number of features that have become standard for 3rd party file-managers: tabs, integrated search, favorites, thumbnails, etc are all present. So here's a bit of a mini-review of OneCommander based upon my wholly subjective experience with it. (My favorites are Nexus File, A43, Explorer++, and Directory Opus). I'm a bit of a connoisseur of file-managers for windows.
0 kommentar(er)
