Recent Posts

1

Feature Requests and Suggestions / Automatic window title update on directory change (or OnDirectoryChange hook)

« Last post by Amater on Today at 18:21:08 »

Hi Mathias,

First of all, thank you for creating such a versatile file manager!

I would like to have the active folder path dynamically displayed in the Windows taskbar/title bar (similar to Windows Explorer). I found that using SetAppCaptionTag( GetSourcePath() ); in MultiScript works well for updating the title, but currently it only triggers manually (via hotkey, button, or alias).

Is there any chance of adding an automatic trigger / event hook (e.g., OnDirectoryChanged) in a future update, or a native setting like "Show active path in Window Title bar"?

If there is already an existing workaround to automatically run a script upon changing folders that I might have missed, please let me know.

Thank you for your time and great work!

2

Feature Requests and Suggestions / Re: Default to last used folder on network drive when starting

« Last post by Mathias (Author) on Today at 12:41:33 »

Menu > Explorer Panel Settings > Display (Tab)
Close to the bottom of the list you havce a section named "Save on exit"
Disable "Remember only paths to local hard drive"

3

Feature Requests and Suggestions / Default to last used folder on network drive when starting

« Last post by Rudolf Otto on Today at 11:46:42 »

I have a NAS in my network. On the computers drives Y: & Z: are the drives on the NAS and defined with auto-reconnect. On starting Multi Commander the active path from the last session on the network drive is lost. I have to go to the network drive (i.e. Y:) and then 5 or more levels deep to get to the folders I worked on in a previous session. I would welcome it if, on starting a new session, the active path from the previous session would be default as it is with local drives.

4

Beta Releases / Re: MC V17 Early Access PREVIEW

« Last post by total_annihilation00 on Yesterday at 21:10:06 »

You cant assign PageUP/Down or they do not work after you assigned ?

When I assign keyboard shortcuts Ctrl + Page Up/Page Down, the entries appear invisible in the list view (see attached screenshot).

File color editing has not been change at all. I don't really understand the issues.. only shows white ? what is shown white..

I'll verify this behavior on a clean install and update accordingly, but I suspect it’s related to a misconfigured "Quick Look & Feel" setting. Even on a fresh copy of MC, the issue persists (see screenshot).

Regarding your earlier question about the background color selection in a Color Rule: the color picker only displays white, which might be due to the inability to create or select a new Color Rule at that time.

Additionally, I discovered a workaround for editing new Color Rules: creating two new rules allows one to become editable and selectable. You can rename and keep that rule, then delete the second one.

P.S. In V17, creating a new Column Layout and adding paths like "C:\ D:" with "Valid For All Future Paths" causes the sorting column to reset on startup. For example, a previous setting of "Date Ascending" resets to unsorted each launch. The only workaround, similar to V16.2, is to use only the "[Default]" Column Layout with that configuration, though this prevents assigning custom paths with "Valid For All Future Paths."

5

Beta Releases / Re: MC V17 Early Access PREVIEW

« Last post by Mathias (Author) on Yesterday at 19:19:51 »

P.P.S: Everything is working splendid now, just gotta resize the height of the "Keyboard Customization" dialog. Also I'am happy to report I don't see the "File Column Header" shrinking randomly as it was before in V16.2 but I'll test further. Thanks Mathias ! & yeah clicking close on the "Keyboard Customization" dialog & selecting "Yes" has no effect (should fix this.) One more thing: Ctrl + PageUp\ PageDown aren't recognizable as valid hotkeys (for instance, Previous Tab\ Next Tab) !

P.P.PS: The File Coloring Rules Editor is very buggy in V17, I tried making new Rules & they would not select (after a lot of hassle I was able to select the new Rule & move it to the top), & sometimes clicking on a Color in the Color Picker dialog has no effect (only shows white, then when dragging the slider it finally works.) This might be because I changed from "Windows Explorer Style Colors" to "Commander Style Colors" (I'am not certain.)

You cant assign PageUP/Down or they do not work after you assigned ?

File color editing has not been change at all. I don't really understand the issues.. only shows white ? what is shown white..

6

Support and Feedback / Re: Update the Microsoft Store version?

« Last post by mrsbean on Yesterday at 18:00:21 »

Version 16.2 is published in Microsoft Store, thank you very much :-)

7

Beta Releases / Re: MC V17 Early Access PREVIEW

« Last post by total_annihilation00 on Yesterday at 14:01:37 »

So what did you do before that did not work ?

I initially selected the default "Windows Explorer" style, but the issue has been resolved; it was an oversight on my part.

Hmm Strange.. for me it works.  Hmm are you running Windows Explorer style mouse/keyboard setup ? Then context menu is then on normal right click. Might be that they collide in the new UI List view

Regarding the context menu behavior, I will investigate the "Commander Mouse/Keyboard" setting, as it seems the right-click menu may not be displaying correctly in that configuration.

will check so that is really save after close on X button.

That would be appreciated, thank you.

P.S. You're correct—selecting "Commander Style" for "Mouse" in the "Quick Look & Feel" options displays the "File Column Header" right-click menu. It might be beneficial to address this as a bug so that the "File Column Header" remains right-clickable even in "Windows Explorer" style.

P.P.S. The overall functionality is now stable; I just need to resize the height of the "Keyboard Customization" dialog. Also, I’m pleased to report the "File Column Header" no longer shrinks randomly as it did in v16.2—further testing will confirm. Thanks, Mathias! Additionally, clicking "Close" on the "Keyboard Customization" dialog and selecting "Yes" has no effect; this should be addressed.

One more issue: Ctrl + Page Up/Page Down are not recognized as valid hotkeys for actions like "Previous Tab" / "Next Tab."

P.P.PS. The File Coloring Rules Editor appears quite buggy in v17. I encountered issues creating and selecting new rules—sometimes clicking on a color in the Color Picker shows only white, and dragging the slider eventually updates the color. This may be related to switching from "Windows Explorer Style Colors" to "Commander Style Colors," though I haven't confirmed this.

8

Beta Releases / Re: MC V17 Early Access PREVIEW

« Last post by Mathias (Author) on Yesterday at 13:23:46 »

@Mathias,
Concerning keyboard customization dialog. It can be reduced.

1. For example, "Assigned shortcuts" list is simply duplicates main list info but it consumes a lot of space with only 3 columns. The primary "*" symbol can be printed in the main list.

2. As far as I can see, "Origin" only has two possible values - "Custom" and "Default". So this column can be removed, and default hotkey can instead be printed bold in the main list. It is also actual because of an issue: if you add a secondary shortcut to the default one, the Origin becomes "Custom" for both.

3. "Conflicts" memo only shows conflicts when I try to assign a conflicting shortcut. But if I actually do it, then they will not be shown if I later select this shortcut in the main list. So the conflicts can be shown as a warning icon in the main list, and the full list of conflicts -- in the separate dialog.

4. Changing a shortcut can be moved to a separate dialog.

1. Well you can define multiple keys to same command. And from this list you can remove one of them, The the list does not need to be full width.. then some of the buttons can be moved after it instead

2.Yes the columns will be tweaked.. right now all of them are show most for debug reasons.

3. I will check how conflicts can be improved

4. Yes,, But I would like to see if I can have everything in one dialog. that is a backup plan

9

Beta Releases / Re: MC V17 Early Access PREVIEW

« Last post by Mathias (Author) on Yesterday at 13:16:08 »

Issue #2, I resolved it by selecting "Commander Dark Mode" in "Quick Look & Feel" dialog, so that's fine now (gotta remember to select "Commander Dark Mode" as Color theme on first-time startup).

So what did you do before that did not work ?

Issue #1, Yeah it does not popup the File Column Header right click menu (see screenshots, possibly the only bug, the rest are cosmetic glitches, so just need to fix this, I got V17 today & it refuses to launch the "Customize Columns" or rest of its special menu items):

Hmm Strange.. for me it works.  Hmm are you running Windows Explorer style mouse/keyboard setup ? Then context menu is then on normal right click. Might be that they collide in the new UI List view

Issue #4, The height seems to fit the full screen, maybe a little shorter height might let me click the "Save" button. When I click the Close X button it says do you want to save, I selected "Yes", but the "Up Arrowkey" isn't designated the "Parent folder" Shortcut, so that's odd. But I think it should be resolved if it's narrower in height. Width is fine by the way.

will check so that is really save after close on X button.

10

Beta Releases / Re: MC V17 Early Access PREVIEW

« Last post by Jungle on Yesterday at 12:54:36 »

@Mathias,
Concerning keyboard customization dialog. It can be reduced.

1. For example, "Assigned shortcuts" list is simply duplicates main list info but it consumes a lot of space with only 3 columns. The primary "*" symbol can be printed in the main list.

2. As far as I can see, "Origin" only has two possible values - "Custom" and "Default". So this column can be removed, and default hotkey can instead be printed bold in the main list. It is also actual because of an issue: if you add a secondary shortcut to the default one, the Origin becomes "Custom" for both.

3. "Conflicts" memo only shows conflicts when I try to assign a conflicting shortcut. But if I actually do it, then they will not be shown if I later select this shortcut in the main list. So the conflicts can be shown as a warning icon in the main list, and the full list of conflicts -- in the separate dialog.

4. Changing a shortcut can be moved to a separate dialog.