I had used the address from your domain and it's still in my sent box. As you can't remember my email it was maybe killed by your spam filter? I remember some threads here in the forum with emails not received by the moderator, maybe that is an idea.
Presets for some well known Explorer columns
Sample ini file sounds like the best approach as it has already happened to me that I have overwritten my actual inifile with a fresh one. But I have decided to disable the new TC autoinstall feature currently due to the actual bug, permanently adding "/W" to the path defined in "pluginbasedir=" ini-setting, and I prefer the manual way and the Plugins Manager tool as it also allows to disable, uninstall and do other configuring stuff.
The user expectation is quite different where the settings file should be created by default. I started a discussion a weeks ago - noone replied yet. There seems to be no interest in finding a common way.
Not the first discussion IIRC. I think the arguments haven't changed since the last time, maybe that's why noone replied.
I haven't had time to create a user interface for that, sorry.
I don't think that this will be necessary. In the end all WDX-plugins behave the same and are configured in the same way. If you know how it works in one plugin you can use the others, too. That's why I haven't read your readme in first place as I expected to see some starting guide for beginners only. Configurable ini-locations are seldom nowadays but a very nice approach.
The reason why I chose this directory is that many people complain about too many INI files directly in Wincmd.ini directory.
Well, in the end it doesn't get better when there are a lot of subfolders INSTEAD OF ini files in the wincmd.ini directory, don't you think? It just makes the situation worse, one click more to find the ini file.
I love plugins I can unzip, install, configure and delete with one single click. This is only possible when everything is in one place by default.
Plugins that include stuff to be put in different folders are not very easy to use. Imagine the complications that will arise when you include an inifile in your distribution that has to be put in a subfolder manually by the user and that one doesn't use the auto install feature.
That's not really an argument for me. What other plugin authors do don't have to be the best way.
True on one hand, on the other it's what plugin users are used to meanwhile and it happens to sound most logical to me, so maybe I am just happy to see that my feeling of what should be default is shared by most developers.
I don't want to stop you from using my plugin but this feature is already included in Total Commander: tc.creationdate (tc.Erstelldatum)
I have seen it meanwhile, thanks.
Ok, one feature wish:
If possible include a setting for two-digit year presentation. Right now people have to change big Y to small y. Or is it a limitation of TC plugin interface?
Thanks
Icfu
