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.
