Messages

3276

Support and Feedback / Re: Delete Selected Folder in Tree

« on: March 12, 2014, 15:17:31 »

Mathias (Author): thank you for your fast and comprehensive response. The problem is that just about EVERY file manager I am aware of, including free tools created by single developers, allows to delete a folder in tree view. I appreciate that "MC is not build using the slow Windows Shell interface that a lot of others are using", but I would like to bring to your attention that there do exist file managers NOT based on the Win shell which allow a folder deletion in tree view.

As it happens I am software developer myself. I am risking being rude here, so please accept my apologies, as this is not my intention: what I see here is simply not finished, and not elegant. This is not beta, this is rel. 4.1. maybe FAQ should have a section: not yet implemented features you may expect to see, but they are not here yet? Are there any more?

On positive note: great tool, and I appreciate that you invested a lot of your time in creating it, and you released it free, for this you have my well deserved respect.

Just because FileMan X have it does not mean that it is as easy for everybody to add it. As a developer you knows that it also have to fit into the whole framework you have. It is not just a dumb tree controller that sits there. It have to glue it self into the explorer panel tab and into the core and plugin system.

The point is really that the issue is known, BUT there is no easy fix for it. If it was a 5-10 min fix it would have been fixed a lot time ago.
And since I do not use the shell I do not get the tree stuff for free. I have to create everything my self and it have to fit into the whole architecture of my core system.

And fixing it would require a lot of work. And since my time is limited I have to prioritize.
Should I spend a month redesigned a big chunk of code so delete from folder tree can works (a bug that has very few request to be fixed, and has a workaround, and that does not cause a crash)
Or should I instead fix issue A,B,C and add feature 1,2,3 ?
(So fix one minor issue or fix many issue and also get the the time left to add a couple of new features)
As a developer you know that you have to prioritize, and even if you got a bug you can not spent all the time fixing it if there are other more important stuff to do. specially if you work with a very large code base.

But it is on my fix list. And it will be fixed. Exactly when I do not know. I try to collect all the bugs and feature that are around the same area and do them all. That saves a lot of time.

And yes it is v4.1 but the FolderTree has not existed from the beginning, MC was developed like a pure commander clone from the beginning.
And there was no folder tree at all back then, and nobody ask for it, Because most hard core users of commander clones do not use it.
Then features was added to make "explorer" folk more at home in using it and folder tree was added, BUT the folder tree did
not fit exactly into the core framework so some stuff in it does not work.

3277

Support and Feedback / Re: Speed of Right Click Menu

« on: March 12, 2014, 10:17:11 »

Yes of course, Send me the dump and I can take a look.

It should be possible to see if it is one of the modules that are slow.
if it is some other general issue around shell extensions it might not be possible. Then more advanced tools might be needed

3278

Support and Feedback / Re: Delete Selected Folder in Tree

« on: March 12, 2014, 07:37:21 »

With respect, this is very poor answer. It is very unusual to find such basic and commonly implemented option missing in a file manager.

Might be an answer you did not like. But it does not change the fact that it is not currently possible.
MC is primary built to be used as a dual panel, Commander style file manager, and a folder tree is not used very often in that setup (since the tree view often is navigated with mouse and in commander mode you are often not using that.)
So the folder tree has not been a priority, It is planned to add it. But it is not as easy to do as one might think. There are some technical issue with it and that require a bit of work (You have delete from the context menu in the FolderTree, But you will see some refresh issues, This is part of the issues )
Also other issues have had higher priority.  But it is on the todo list.

There is also GUI problem: selecting a folder in tree view does not disable a button "Delete (F8)" and popup help "Delete files of folders" is still present.

That is because the button panel are not context sensitive. they are just buttons that you can assign whatever to.

Windows Explorer allows this, other two tools I am currently evaluating: XYPlorer and FreeCommander XE also allow this operation. I may be wrong, but from memory I do not remember any other file manager (and I used many) which would have such basic flaw.

MC is not build using the slow Windows Shell interface that a lot of others are using. MC shows the file system as it really is.
MC is also built in a very different way, everything in MC is a extension/plugin, that makes it easier to add new features but will make some other things harder.
And as a said. MC was first built to be used in commander style setup first and did not even have a tree view since that is not even used there.

Why is it not implemented? The product appears to be mature (ver. 4.1). Some better explanation is needed here. Is it going to be fixed? This is definitely NOT a feature or a logical design decision, it is crippling lack of basic functionality commonly implemented in other similar tools.

Because not everything can be fixed at once, MC is free so there is very limited resources, I do not have a whole team of devs that works 24/7.
Also not many uses the FolderTree most users run MC in CommanderStyled mode and other issues have been more impotent to fix.
But it is on the list, and will be fixed.
It have not been categories as a major flaw since you can still delete, just go up one level and delete from the list part.

3279

Support and Feedback / Re: Locked TAB functionality.

« on: March 12, 2014, 06:57:00 »

Right click on the tab and you can lock the tab.
And there is also an option there called "Lock tab - Allow sub path change" 

Select that option. and you can browse into subpath. , but not to parent or other drives

3280

Support and Feedback / Re: Speed of Right Click Menu

« on: March 07, 2014, 18:32:34 »

If you run Commander styled setup. You have the Context Menu on RightAndHold on the right button.. Here button need to be pressed for 1 sec.
But you also have it on Double click of right button..Then it is called directly.
For Explorer Styled when ContextMenu is on right button down. then it is called directly.

But depending on what kind of Shell Extension you have installed it can take some time to build the popup menu.
All registered Shell extensions you have installed are going to be called and they do all kind of work to add items to the menu,  Every time it is shown.
This is out of the control of MC. And the speed depends on what the shell extensions are doing. MC is not involved in that process at all. Windows handles all the loading and calling of the shell extensions.

ShellEx View is a tool by Nir Sofer where you can list all your shell extension and enable/disable they easily.

3281

Support and Feedback / Re: Forward keys to commandline bar - PageUp/Home

« on: March 03, 2014, 18:09:16 »

It might be a temporary fix only. The fix might have side effect with other key combination.. and then it might need to be removed again..
But time will tell..

3282

Support and Feedback / Re: [BUG] Moved file has size 0

« on: February 27, 2014, 07:17:33 »

To network --> Write options(Target) --> Use system cache should be checked, then it works like a charm.

Maybe this could be the default settings in future releases?

No. MC has to assume that hardware works as they should, and how Windows require the hardware to work.

Enabling System Cache will hurt performance a bit since all data that should be written will now also be cached by Windows.
It can also give you false sense of the progress, since the progress you see is when the data have been sent to the cache, not the actual drive/target device.
And it can also give you a jerky copy experience, First the progress goes very fast, then it stops/halt because the system cache is full and everything stop and wait until all the data have actually been written and then it continues. And it continues to do so. This is specially seen on large files. But also depends on how much RAM you got left that the system uses for cache.

3283

Support and Feedback / Re: [BUG] Moved file has size 0

« on: February 26, 2014, 22:22:44 »

Found this in user comments on Amazon for that NAS D-Link 320
http://www.amazon.com/D-Link-DNS-320-ShareCenter-Network-Enclosure/dp/B004SUO450   (comment from April 6, 2012)

"Since the November 2011 release of Firmware 2.02, users have been reporting data integrity problems with the box - including files that get copied and then show up as "0 bytes". (See forums.dlink.com for DNS-320)"

So it might be a NAS issue. you can try to turn off optimized file copy in MC, then file copy will be less optimized but it might be what the NAS needs.
Either disable "Automatically detect read/write strategy for file copy" then the unoptimized read/write will always be done.
or you can tweak just that read/write strategy used for your network copy.. I guess to will be "To Network" (if it detects it correct) and then enable all checkboxes for write options.

3284

Support and Feedback / Re: [BUG] Moved file has size 0

« on: February 26, 2014, 21:23:50 »

Strange..
The FileOperation log looks correct and I can find anything in the ProcMon log that MC shorten/empty the file (Only the MC Process is available in ProcMon log, So I can't see if another program does something to that file.)

Sure it is not antivirus or something?

3285

Support and Feedback / Re: [BUG] Moved file has size 0

« on: February 26, 2014, 14:56:04 »

If you are used to advanced tools.

You can run the Microsoft tool Process Monitor to track all file access in the system.
And then you can filter out for just that file and see what is happening and what process that does it.
(Or you can save the entire trace log and send to me at http://multicommander.com/upload (let me know the filename to look for) )

3286

Support and Feedback / Re: [BUG] Moved file has size 0

« on: February 26, 2014, 14:42:08 »

Very strange.. Never seen anything like that. AntiVirus is also the first thing that popup in my mind that can mess with the filesystem like that.

Did the FileOperation log say anything ?

In Core Settings set log level to "Debug (eval)" for FileSystem Log.
and then copy the file that fails.
and then look in the log if there are any issues reported. (Ctrl+L to show log window, and click on FileOperation tab)

3287

Support and Feedback / Re: [BUG] Moved file has size 0

« on: February 26, 2014, 06:49:47 »

That is very strange.
I never seen that and no reports of it.

When moving a file the file is first copied and then the source is deleted, The source file is not deleted unless it successfully copied the file to the target.
It actually is verifying the target file size is correct before deleting the source file.
So how it can delete source file when target is 0 is very strange.

What is the network location.. Another Windows Server ? NAS ? Linux ? Mac ?
Any error in any log on the server ?
You are sure that there is no file system issue on the target device ? I seen file go to 0 if the filesystem was corrupt. specially on some NAS devices.
What does the fileoperation log in MC say ? Any error there ?
Do you see the file grow in size during file copy and then end up at 0 ?

3288

Feature Requests and Suggestions / Re: A Few Wish List Items #2

« on: February 24, 2014, 15:46:48 »

Sorry. That will not be possible without major rewrites.
They might look like the same thing but in reality they are two very different things.
The device toolbar is minor modified version of the standard toolbar UI component.
And the QuickLaunchBar is actually not even a real toolbar, It is a custom UI controller.

3289

Support and Feedback / Re: Forward keys to commandline bar - PageUp/Home

« on: February 22, 2014, 17:30:51 »

Not sure that is the same 0xff code. That looks like the hardware code. Windows will send a virtual key code to application. And it is that, that is 0xff.

Maybe MC can ignore 0xff in the future, problem is that some Fn+<key> combination is also sending that key code and then it should not be blocked.

3290

Support and Feedback / Re: Forward keys to commandline bar - PageUp/Home

« on: February 22, 2014, 16:50:50 »

Key 0xff is not the up/down key.  0xff is often sent if yo also have to hold the the "Fn" key when pressing the key.. (used on Laptop or mini keyboards.)
Why it is sent for a normal keyboard I do not know. It should not.

3291

Support and Feedback / Re: Forward keys to commandline bar - PageUp/Home

« on: February 22, 2014, 16:12:22 »

If you enable the Application Log with log level "debug" under Core Settings in the latest beta version.. (build 1629+) it will log what key that is triggering forwarding.

3292

Beta Releases / Multi Commander 4.2 Beta

« on: February 22, 2014, 15:46:01 »

This release contains only some minor fixed 


  300+ Changes and some of them are...

-- Build 1669
  UPDATE - Updated Language Packs
  FIXED  - 2 crash issues reported by Crash report system

-- Build 1665
  FIXED - QuickLaunchBar now works better with relative and enviroments paths.
  ADDED - Command line command ":one" now also work for going to OneDrive/SkyDrive folder
  ADDED - New MultiScript functions PathMakeRelativeMC(...), PathMakeAbsoluteMC(...), PathTranslatePath(...), TranslateEnvString(...)
  ADDED - User Defined Commands can now be duplicated.
 

-- Build 1660 ( 30-Mar-14 )
  FIXED - Color rules are now refresh when files are renamed or attributes changed (From inside MC)
  FIXED - Copying files to folder starting with ".." now works again. Eg "..Myfolder"
  FIXED - FileTypeSetup will not clear extension field if external program is selected
  FIXED - If sorting of column that shown extended info (data fetched in background), view will now resort automatically when data is ready.
  FIXED - Windows Shell context menu did not work in some locations.
  FIXED - Fixed a couple of strange issues with context menu handling
  FIXED - Fixed issue with overwriting existing file inside a zip archive.
  FIXED - Fixed refresh issues when a zip is rebuilt.
  FIXED - 2 crash issues reported by Crash report system
  FIXED - Command line fields dropdown history is now shown and saved correct.
  ADDED - Button panel changed so it can not be undocked. Then no close button is shown making it look better
  ADDED - Button is the Button panel can now be drawn transparent.
  ADDED - New column that shows the length of the name or fullpath.
  ADDED - Added option to enable/disable the refresh tab when application focus is returned to MultiCommander
  ADDED - Command line field can now show hits/tips when not used. (Can be disabled in core settings)

-- Build 1650  ( 22-Mar-14 )
  FIXED - Lots of more DPI scaling issues fixed. MC now look good in 150% DPI. Still some issue with 125%
  FIXED - Improved error handling and error reporting of read/write errors.
  FIXED - A lot of minor fixes and changes to error handling
  FIXED - Placeholder file is now being identified (Win8.1+ only)
  FIXED - 2 crash issues reported by Crash report system
  FIXED - When unpacking rar it could happen it complained that disk was full even if disk was not full.
  ADDED - Option for "Expand folder hovering over during drag and drop in folder tree". (Was always enabled before, can now be disabled)
  ADDED - Option if a new tab should be opened when browsing to new location in a locked tab.
  ADDED - Rule Based file coloring can now be configured to also change font style like Bold,Italic,Underline,Strikeout
  ADDED - Custom command MC.Explorer.NewBrowser now support TABCOLORS,TABNAME,TABLOCK paramters
  ADDED - New Custom command MC.Explorer.SetTabProp for setting tab properties like color, on existing tab
  ADDED - Duplicating a Explorer Panel tab. or opening a folder from one tab into a new tab. New tab will recieve same custom Tab Colors.
  ADDED - Custom Command MC.FileSystem.Unpack

-- Build 1640 ( 2-Mar-14 )
 FIXED - Lots of DPI scaling issue (Mostly tested on 150% DPI scaling)
 ADDED - Doing TapAndHold on touch devices will now be a right click. (Show context menu in most places)
 ADDED - Upgrade build system for MultiCommander to VisualStudio 2013 update 1
 FIXED - Improved error logging in a couple of places.
 FIXED - 2 crash issues reported by Crash report system

-- Build 1630
  FIXED - Last beta release was missing updated language packs.

-- Build 1629
  ADDED - MultiFileViewer have experimental support for line filtering (grep)
  FIXED - Some minor high DPI issues fixed.
  FIXED - Some icons was messed up if icon cached was cleared
  FIXED - 6 crash issues reported by Crash report system

-- Build 1623
  FIXED - Internal read/write buffer optimizations.
  FIXED - Context Menu key on keyboard now works for the ".." item
  FIXED - The settings "Remember Selected files/folders when changing path" now works again. (can be turned off)
  FIXED - Better error handling in a couple of places.
  FIXED - Improved error logging.

3293

Support and Feedback / Re: Forward keys to commandline bar - PageUp/Home

« on: February 22, 2014, 14:33:40 »

Strange. 
Something else must be causing it, because it does not make sense.

I looked at the code and pagedn/pageup can not be forwarded to the commandline field because those key are never reached the part the forward the keys.

Also the part that forward keys to the commandline field block all special keys from being forwarded.  and pageup/pagedown and the arrow keys are among them.
So some other key must be triggering it or something.

3294

Support and Feedback / Re: Forward keys to commandline bar - PageUp/Home

« on: February 22, 2014, 12:46:01 »

I don't know how you manage to do that.
PgUp/PgDn are hard wired to move the focus item a page up / down. And that key is never handled as unhandled and are not sent to the commandline field.
Do you have some unusual keyboard setup or something else that can change it ?
Do you use a laptop keyboard or some other mini keyboard that uses multiple keys on the same key ?

3295

Support and Feedback / Re: Delete Selected Folder in Tree

« on: February 20, 2014, 22:04:45 »

Delete is not possible from the tree side.

3296

Support and Feedback / Re: Focused Path Field

« on: February 19, 2014, 06:55:16 »

From the documentation
http://multicommander.com/docs/filetypesetup:

Under "Program Parameters" you enter the parameters you want to send to the program (if the Program type is "External Program"). There are a couple of tags you can also select that will for example expand to the selected file path. You will get a list of them by pressing the [<] button.

When I click the [<] button, I don't get a list of tags.  Is there something wrong with my configuration?

FileTypeSetup is found under Menu > Configuration > FileTypeSetup. It is where you configure default program to be used for Viewers and Editor based on file type.
It has nothing to do with the QuickLaunchBar. it does not support any script tags (Except Windows Enviroment strings. )

3297

Support and Feedback / Re: Focused Path Field

« on: February 19, 2014, 06:51:09 »

${sourcepath} is blank too.  I am using it as a Program parameter to a Quick Launch program.

That is because the QuickLaunch Bar is not a script.

It is like the QuickLaunch bar that you had/have in Windows on the taskbar, a place to quickly launch programs.
And you can drag and drop files on an icon and they will be sent as parameters to the program.
If you want it to interact with MC then you need to create a UserDefinedCommand and then add that to the Quicklaunch bar.

Here is a example, Create a new UserDefinedCommand of "CustomCommand" type
then enter

Code: [Select]

MC.Run CMD="C:\Bin\Notepad++\notepad++.exe" ARG="${sourcepath}"Then Right click on QuickLaunch bar and select insert User defined command.
The Right click on the quicklaunch program icon for the command and select customize and then you can modify the icon.

3298

Support and Feedback / Re: Command to Move File

« on: February 18, 2014, 22:07:31 »

That is because Multi-Script does not support the MultiTags for getting selected files and stuiff, MultiTags are only used for simple script.

MultiScript are powerful but more advanced and works more like real scripts. And you need to check the documentation.

Here are functions to use to get selected files and stuff.

Something like  this (not sure it is correct.. But if you run it via the MultiScript Debugger (under help menu) and you can tweak it )

Code: [Select]

@var $sourceFile = GetSourceFocusPath();
@var $targetPath = "C:\\Backup\\";
MoveFile( $targetPath, $sourceFile);

3299

Support and Feedback / Re: Command to Move File

« on: February 18, 2014, 19:47:50 »

You need to use UserDefinedCommand of MultiScript type for that.

And then use the MoveFile script command

3300

Support and Feedback / Re: Colouring of items in focus

« on: February 18, 2014, 19:45:26 »

ok, thanks for this!
It turned out I was misinterpreting "Focus" and "Selected and in focus". I assumed that clicking on a file or folder makes in in focus only, but according to this color setting this also makes it selected and moving up/down the list makes items focused+selected as well. Now, it doesn't matter which way it is so long I can make it work and I can!

Since you mention TC. I assumed that you used commander styled setup since it is also what TC uses.

Focus vs "Selected and Focus" is depended on settings. If you selected commander styled setup then it would only be focus because the selected items are not the same as a item in focus.
if you have Explorer Styled setup then focus item is also always selected so then you might need select and focus settings.